The November release of Media Composer 2018.11 is available today, Tuesday, November 16th, 2018 @ 12:00 noon EDT.

Location at Launch: This update will be made available from MyAvid Master Accounts, Application Manager, and the Avid Download Center (login and password required).  

Media Composer Notes:  Listed below are a few hot items that you need to be aware of.  Please check the ReadMe for additional notes relating to Media Composer 2018.11. 

-  Application Installers:  With this release of 2018.11 (as with 2018.9 and 2018.10), you have a single installer for Media Composer and Media Composer | First. The option to run as Media Composer | First is now include in the Avid Media Composer Activation window.

-  Dongle Info (Mac Only): The Dongle Sentinel driver installer is no longer automatically installed when you install the editing application. The driver is now located in the Avid_Utilities folder (/Applications/Utilities/Avid_Utilities/Sentinel_Driver). If you have a dongle, manually install the driver from this location.

-  Avid Artist DNxIO and Avid Artist DNxIQ: If you are using Avid Artist DNxIO, Avid Artist DNxIQ, or a BlackMagic Designs video device, please update to Desktop Video software version 10.10.1 or higher. The minimum Desktop Video version that will work with Media Composer v18.5.1 is 10.9.11. Older versions will be rejected, and you will not be able to use your hardware until you update.

What’s New:  The following are new features in 2018.11:

-  DNxUncompressed Update - DNxUncompressed is available at any raster dimensions (HD, 2K, UHD etc.) With this release, 8 bit and 10 bit DNxUncompressed are supported.

-  Timeline Settings Change - In previous releases, Show Four-Frame Display was on by default. Show Four-Frame Display is no longer on by default.

What’s Fixed: The following have been fixed in 2018.11:

• Bug Number: MCCET-2722. In some instances, the editing application would crash if you were trimming with the mouse and Caps Lock was enabled.
• Bug Number: MCCET-2719. Creating a “Bin based on Folder” when performing a link was not working correctly.
• Bug Number: MCCET-2715. Audio might not have played correctly when linking back an AMA File export of XDCAM 50 using the Avid Media Processor plug-in.
• Bug Number: MCCET-2725. Trying to link to P2 resulted in a “Cannot open bin, please choose bin” dialog showing an empty Select dialog window.
• Bug Number: MCCET-2706. You might have received a “PMM_INSUFFICIENT_MEDIA” error if you changed the playback rate in the Source Settings
• Bug Number: MCCET-2386. In some instances, a sequence with linked media could not be sent to playback.
• Bug Number: MCCET-2478. If you opened the Interplay Folder setting window, the previously entered “Interplay Root Folder for this Project” setting was lost.
• Bug Number: MCCET-2703. Subclip exports using the Avid Media Processor might have had wrong Timecode.
• Bug Number: MCCET-2675. If “All Markers at End” in the List options was enabled, saving an EDL to several files crashed the editing application.
• Bug Number: MCCET-2686. The editing application might have force quit when scrubbing a DNxHR HQX sequence.
• Bug Number: MCCET-2591. Audio might not have played back if you were in Trim mode and “Pitch Correction during Shuttle” was enabled in the Audio Settings.
• Bug Number: MCCET-2473. You might have received an “Exception: Failed to get the sample temporal 0ffset from the AMA Plug-in” error when exporting an XDCAM OP1a file. Get the
• latest XDCAM plugin from the nablet webite to fix this issue. See avid.com/ama.
• Bug Number: MCCET-2712. In some instances, Exporting AIFF-C or QuickTime Ref with AIFF-C crashed Media Composer with an “ACCESS_VIOLATION” error.
• Bug Number: MCCET-2692. Adding filler at the start did not position the section marked IN-OUT correctly.
• Bug Number: MCCET-2617. Intermittently, Group clips displayed in green, in the Source Monitor (Quad split or Nine split).
• Bug Number: MCCET-2663. You might have received an “Exception: QualityManagerImpl::relinkMaster” error when loading certain clips into a bin. 

Limitations:

• Bug Number: MCDEV-9909. Beta 1 Known Issue - (Mac) You receive an “Unable to load JRE” message when trying to start Background services.
• Bug Number: MCDEV-9837. (Interplay) If you receive the error “DeleteLocalBinMedia FormatDescriptor is not known” you can only delete the media using Interplay Access.
• Bug Number: MCDEV-9460. Windows 7 systems with Nvidia Maxwell or Nvidia Pascal cards might experience playback issues that could result in “Play Consumer timeout” errors.Workaround: Select “Disable GPU Effects” in the Render Settings dialog box.
• Bug Number: MCDEV-9142. You might experience hangs or crashes when performing a video mixdown with a 16K project on systems with less than 64GB RAM.
• Bug Number: MCDEV-9269. (Media Composer | Cloud) After performing a remote download operation on a sequence containing AVC-I 100 remote media, the downloaded media appears as
• XAVC-I 100. Workaround: Download the entire master clips.
• Bug Number: (Mac). You may occasionally see the menu bar flash followed by a brief beach ball. To fix this: deactivate “Displays have separate spaces” under System Preferences > Mission
• Control settings.
• Bug Number: MCDEV-9011. Intermittently, when working with the XDCAM Nablet Plug-in, you might see “Failed to get the sample position from the AMA Plug-in” errors if you have waveforms enabled in the Timeline.
• Bug Number: COGS-2560. While working in the Script Window, text operations (cut/copy/paste/delete/editing) can only be done in edit mode. See “Editing a Script” in the Help.
• Bug Number: MCDEV-5650. When working with Panasonic LongG media, you might receive an “SFPlayConsumer Timeout” error if audio waveforms are enabled. Workaround:Turn off audio waveforms.
• Bug Number: MCDEV-5385. MultiCam editing with Panasonic LongG media is not supported with this release.
• Bug Number: MCDEV-5384. Currently, when working with LongG media, you might see dropped frames when editing 4 streams. This might occur when playing from a single stream to
• multiple streams (and from multiple streams back to a single stream). The dropped frames usually display around the edit point (transition to a different stream).

How customers will obtain the November Media Composer 2018.11 Update:  

1.  Customers who have already installed the latest version of Media Composer will be notified of the availability of the upgrade via the Application Manager. The Apps tab also provides a link to download and install the update(s) when desired. 

2.  New customers who purchase Media Composer will receive the update in their Avid Master Account.

3.  Customers on current Avid Update plans can download the Media Composer update from their MyAvid Master Account and the Avid Download Center (login and password required.) 

4.  Customers NOT on a current Upgrade plan must purchase either 1. new Media Composer Subscription Crossgrade or 2. new Subscription or 3. new Perpetual license to receive this update. 

Reminder: This release of Media Composer requires an active Upgrade plan.

Hi there! I downloaded the ZIP-file for MC2018.11, unpacked it and tried to install it. Somewhere in the process I get around 10 messages of audio filters/setting are missing. screenshot of the first three messages enclosed. I click then "ignore" for each of the messages, and MC2018.11 will install. I tried this with two different ZIP-downlaods, each time the same. I believe there's something missing in the installer.

You should try to  unzip the installer to the root level of your drive and then install.  

How good is the beta  for .12?  Ill give it a shot if its decent.  Im starting a good project for it.

But since I'm using it on a job ill roll back pretty quickly if there are issue with this group update.

Very interested in that feature.

is .11 stable and good?

will I regret my self if I spend the weekend at the office and upgrade all of my 35 Avid workstations?

Hi, we did the upgrade with our pc systems yesterday. Today Pro Tool 9 HD (on a mac) doesn´t accept aaf Files with embedded media anymore. Lucky that I had an mac mini with 2018.10 on board. This worked. Has anybody else noticed issues with aafs and old Pro Tools HD Systems?

Hi Stereoscopix,

  We tested both version (Mac, Windows) before the release we did not get any problem, did you check out David's suggestion to unpacked to root?  I don't see your screenshot please repost. Thanks!

Thanks,

RalphC

Hi Armin, do You set the various export options the same on both the unsuccessful system and the Mac Mini? Other than that, I always export AAFs with the media on a separate folder rather than embedded, I find it more troublefree; also lately my sound guys ask to commit multicam edits before export.

Hi luca.mg,

we always export embedded aaf Files, I like the simplicity of one file and before 2018.11 our old Pro Tools 9 HD Systems had no problems to handle this files, but now it seems, this has changed. Although the file size ist big enough, Pro Tools shows empty tracks. All files are missing. Relinking or synchronizing doesn´t help. If I export the sequence in 2018.10 Pro Tools works as usual. I will observe this issue. In certain circumstances we have to downgrade to 2018.10. again.

Well Armin, it's Your decision, fair enough, but kind of a boomerang. If embedded is a source of problems I would certainly drop it, dealing with computers requires workarounds sometimes, and a flexible mind/approach. Anyhow: 

luca.mg:

...do You set the various export options the same on both the unsuccessful system and the Mac Mini? ........ also lately my sound guys ask to commit multicam edits before export.

And is edit protocol enabled in the export settings?

Hello luca.mg,

thanks for your support and well, I´m editing with Avid Systems for about 20 years, so I hope operator errors can be excluded...

The funny thing is, Pro Tools 9 HD can´t read aaf Files with embedded media since the day after the Composer upgrade to 2018.11. I think, nothing else has changed. If I have time, I will try out a few other variations of crosses on/off and who knows, perhaps the folder option is moving more and more into my sight.

Hi Armin, it could be that the AAF export is broken, and that it won't even work with the folder option, who knows. It could also be operator error, any of us could slip on a banana skin. I'd start making sure all options are correctly set, if the embedded export still won't work try the folder export, if nothing works than someone running 2018.11 has to replicate the issue so that it can be filed as a bug and fixed in a future release.

just used .11 the last week for a huge freaking project.

as far as stability goes, its rock solid.  nice work avid.

can't wait for .12

Hi there

I have the same problem here, every aaf from 2018.11 cant load in protools

Did a few AAF exports yesterday and they loaded without problems in protools 2018.10.
Thomas, did you check the export option "AAF Edit Protocol"?