Great news…….  a new November release of Media Composer has just launched. 
 
Status of Support Plan: The ability to launch this Media Composer 2019.11 software is dependent on the status of a customer’s Upgrade and Support Plan on the date this software version is released - today November 18th, 2019.
 
Location at Launch: Updates to Media Composer are available from Avid Link, MyAvid Master Account and the Avid Download Center (login and password required).
 
What’s Changed in 2019.11:  The following has changed in Media Composer v2019.11.
 
IMPORTANT: macOS Support

- Media Composer v2019.11 does NOT currently support macOS v10.15 (Catalina).
 
Drawing Shapes and Text with Titler+

-  In previous releases, when working with shapes in Avid Titler+, drawing a shape displayed in the middle of the screen. You could then move the shape to the desired location. With this release, you can simply draw the shape at the desired location. 
-  When creating text with Titler+, simply click and type. There is no need to draw a box first.
 
Additional Support for XAVC HD Intra (CBG) Class Resolutions

-  Additional XAVC HD Intra CBG resolutions are supported with this release. The following table lists the XAVC HD Intra CBG Class resolutions. 
 
Note that XAVC HD Intra CBG Class 200 MXF is not supported for OP1a export or media creation. It is supported for OP-Atom media creation.
 
What’s fixed in 2019.11:  The following has been fixed.

* Bug Number: MCCET-3346. You might have received an “Exception: Audio Buffer for TMF Export” error when performing a Send to Playback.
* Bug Number: MCCET-3321. When importing an XML with markers, the markers appeared in the Timeline but the Markers window was blank.
* Bug Number: MCCET-3343. With a Japanese locale, characters appeared corrupted in the Project format tab of the Settings window.
* Bug Number: MCCET-3327. When entering fade values in a Fade Effect, the opacity in the fade would go from 0 to 1 instead of 0 to 100.
* Bug Number: MCDEV-12124. Typing in the Effects Palette search field would crash if a Symphony Color Correction relationship effect had been deleted or muted in the Timeline.
* Bug Number: MCCET-3192. The Timeline jumped to the blue bar if you clicked one of the segment mode buttons on Timeline Palette.
* Bug Number: MCDEV-11970. Reloading frames when opening multiple bins in Frame view was very slow.
* Bug Number: MCDEV-11982. If the Motion Effect Editor window was open, pressing the K (pause) key did not stop playback.
* Bug Number: MCDEV-11827. The Timeline Video Quality menu reverted to a previous setting when a project was re-opened.
* Bug Number: MCDEV-12099. When in Frame View, subclip thumbnails recached every time the bin was opened.
* Bug Number: MCDEV-12055. Match Frame selected clips from the wrong track.
* Bug Number: MCDEV-11989. The bin did not refresh after a save when Set Bin Display was set to Show Reference Clips.
* Bug Number: MCDEV-11998. In some instances, performing Waveform Sync on a sequence resulted in an “AutoGainPane EXCEPTION not handled” error.
* Bug Number: MCDEV-10649. Performing Choose Column did not place the newly added column to the right of the selected column.
* Bug Number: MCDEV-11048. Creating a new bin or renaming a bin temporarily blanked out Side Bar data.
* Bug Number: MCDEV-11772. (Mac) In some instances, Media Composer crashed when turning off Dual-Monitor configuration and switching between workspaces.
* Bug Number: MCDEV-11895. In some instances, deleting media files from a bin deleted columns and caused Media Composer to crash.
* Bug Number: MCDEV-11906. Long clip and sequence names were cut off.
* Bug Number: MCDEV-12000. Changing the default Transition Manipulation icon in Timeline toolbar did not persist between launches.
* Bug Number: MCDEV-12002. Transition Manipulation was unexpectedly disabled when clicking in the ruler if the Timeline Settings were set to click the TC Track or Ruler Disables Smart Tools.
* Bug Number: MCDEV-12017. The Color picker didn’t show the selected bin background color.
* Bug Number: MCDEV-11565. The Composer and Timeline windows sometimes used an incorrect font.
* Bug Number: MCDEV-11918. Show Bin in Sidebar failed if the bin was in a folder.
* Bug Number: MCDEV-12034. Media Composer vaporized when running out of space during render.
* Bug Number: MCDEV-12031. (Mac) (Titler +) Grouping was not working with Title +.
* Bug Number: MCDEV-12018. (Titler +) Field interpolation was lost when adjusting roll/crawl position.
* Bug Number: MCDEV-11945. (Titler +) In some instances, spaces were inserted at the beginning when typing text for a title.
* Bug Number: MCDEV-10457. (Titler +) The contents of the title did not change correctly when adjusted using the Global|Foreground Level slider.
* Bug Number: MCCET-3198. (Mac). In some instances, dragging items from Interplay Access did not always place the selected items in the bin.
* Bug Number: MCCET-3121. You might have received a “PMM insufficient media” error when performing an Audio Punch-In.
* Bug Number: MCCET-2618. The HW/SW button might not have detected an attached hardware device.
* Bug Number: MCCET-3082. Group clips did not match-frame accurately if the group clip had a different frame rate than the project.
* Bug Number: MCCET-3205. In some instances, MXF DV25 420 files could not be imported.
* Bug Number: MCCET-3188. When a search was filtered, Media Composer would freeze when editing Timeline Clip Notes in the Timeline Clip Notes window.
* Bug Number: MCCET-3203. Audio waveforms were offset on a muted audio clip, if the previous segment on the Timeline had a dissolve effect added that ended on a cut.
* Bug Number: MCCET-3057. Group clip names were not in order.
* Bug Number: MCCET-3271. You could not adjust 3D warp border and perspective parameters by 1 using arrow keys.
* Bug Number: MCCET-3232. Linking BWF files linked as non-drop frame even if drop frame was selected.
* Bug Number: MCCET-3240. Media Composer inadvertently allowed you to drag sequences without frame-rate conversion from Interplay into the Source monitor.
* Bug Number: MCCET-3185. Effects became unrendered after a sequence was consolidated twice. This fix applies to media consolidated with this release.
* Bug Number: MCCET-3141. Media Composer would intermittently hang, vaporise, and display a Breakpad message, when performing the following actions: adding In and Out points, trimming, double clicking on clip from Product Management window (to be loaded on Source Monitor), loading a sequence from the bin, clicking on the Lift button, entering Timeline Fast menu from right click.
* Bug Number: MCCET-3173. In some instances the Text View button, Frame View button, search field, thumbnail slider, and scrollbar would disappear from the Source Browser.
* Bug Number: MCCET-3182. Sometimes the system would hang when performing Loop Play and then switching workspaces.
* Bug Number: MCCET-3076. Color space metadata was not included in QuickTime when AMA linking.
* Bug Number: MCCET-3254. You might have received an Exception error after dragging and dropping the Stabilize effect to a segment on the Timeline.
* Bug Number: MCCET-3075. Some DPX exported images were distorted/corrupted.
* Bug Number: MCCET-3290. You might have received “FatalAbort VDM Scheduling failed” and “MultiFrameCombiner” errors when trimming.
* Bug Number: MCCET-3253. Newly created bins using shortcut keys Cmd+N (Mac) or Ctrl+N (Win) could not be renamed easily.

Media Composer 2019.11 Documentation: The “ReadMe” document for this release of Media Composer 2019.11 is available on the Knowledge Base.
 
Limitations Media Composer 2019.11:  For the list of limitations in Media Composer 2019.11, please references the “ReadMe”.
 
How to obtain the Media Composer 2019.11 Update: The new Media Composer 2019.11 is available today,  Monday November 18, 2019 @ 12:00 Noon ET.
 
1.  Customers who have an active support and upgrade plan will be notified of the availability of the 2019.11 via Avid Link and it it is available via Avid Link, MyAvid and the Download Center.
 
2.  New perpetual and subscription Licenses purchased on or after Monday November 18, 2019 will also receive 2019.11.

I have tried to download and extract the zip file and keep getting an error 0x80010135: path too long

Did you try unpacking the .zip file from the root level of your C:\ drive?  ( C:\Media_Composer_2019.11_Win.zip)?

I will try that now. I also got an error when trying to install from Avid Link.

Doing the unzip and install from :\ drive?  ( C:\Media_Composer_2019.11_Win.zip) has worked. Thank you for the advise.

Nice to see that avid STILL can't sort out AMA'ing H264 files correctly.
There's still a 1 or 2 frame difference in duration when AMA'ing with avid generic plugin compared to quicktime plugin.

I've asked before and I'll ask again, is there no way that 'new' updates or important Avid/MC posts can also be added to/copied to and pinned to the Mac forum? Appreciate different moderates etc., add to or respond to either the PC or Mac side of MC forum, but rarely did this use to be the case. Sorry for the rant and posting this on in the PC forum.  

Hey Ant....

Got the engineers ear on this one....Do you have a recipe or a sample file perhaps?  If so, if nothing else, they can try your file and see if we can still repro...

email me.

Marianna

benholden:

I've asked before and I'll ask again, is there no way that 'new' updates or important Avid/MC posts can also be added to/copied to and pinned to the Mac forum? Appreciate different moderates etc., add to or respond to either the PC or Mac side of MC forum, but rarely did this use to be the case. Sorry for the rant and posting this on in the PC forum.  

Don and now to spank my Mac moderators who didnt do this yesterday.

Marianna

PM sent

Marianna,

I suspect AntCaladine's problem is the same one I have been corresponding about with support for MONTHS, and you may remember the threads/PMs.  I'm working in 2019.9 currently and thought a solution was just around the corner, last I was told anyway, so I checked this forum post.  The engineers need to understand that this ongoing Quicktime file linking issue is a BIG MESS to those of us who have to work with MP4's and such.  File support + accurate timecode is kinda essential in a professional video editing system.

Just today I brought a project back online (originally cut in MC 2018.12.6) in which I had been so careful to not link any video assets with Avid Generic plugin. However I quickly discovered that some of my JPEGs were unintentionally linked with Avid Generic Plugin, and mysteriously, the files wouldn't link again even though there wasn't an obvious time code discrepancy in the bin.  Had to relink via QUICKTIME plugin in the source browser instead (because Avid Generic wouldn't even load these jpegs in the source monitor for some strange reason) then relink the original clips to those newly linked instances - so I found a path to get the job done.  But when deadlines are tight it's a big pain in the butt to have to fiddle with files that in any other version of MC would just - POOF - relink immediately and without fuss.

Ive been manaully relinking timelines for months now - ever since Avid finally decided to fix the Canon AVC timecode probelm - where all the files came in with 00;00;00;00 TC. Of course after dozens of projects and I don't even know how long - at some point it got fixed.

Try bringing those files back online thru AMA now - giant mess. Nothing wil relink- I've tried every possible combination I could find, all the TC's are now correct which messes EVERYTHING up and all of my old sequences need to be relinked by hand. 

I am having the same problem with error showing up when I extract the downloaded file. So, not being too familiar with computer procedure, what do you mean/and how do I unzip the file from - C:\Media_Composer_2019.aa_Win.zip?

You can try to create a new folder in C: example. C:/NewFolder then copy paste the downloaded zip file then extract.

RalphC

AntCaladine:

Nice to see that avid STILL can't sort out AMA'ing H264 files correctly.
There's still a 1 or 2 frame difference in duration when AMA'ing with avid generic plugin compared to quicktime plugin.

Hell will freeze over before this gets fixed.

And if they fix this problem, all files previously linked with the generic plugin won't link anymore.

Also: don't work with linked clips.