Great News! The new Media Composer 2019.8 release along with Media Composer | First 2019.8 is now available.
Location at Launch: Updates to Media Composer will be made available from Avid Link, MyAvid and the Avid Download Center (login and password required).
Dongle Info (Mac Only): If you have a dongle, 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. If you have a dongle, manually install the driver from this location (/Applications/Utilities/Avid_Utilities/Sentinel_Driver).
Status of Support Plan: The ability to launch Media Composer software is dependent on the status of your Upgrade and Support Plan on the date this software version is released. Media Composer 2019.8 released on August 30, 2019.
Location at Launch: Updates to Media Composer will be released at the same time and will be made available from Avid Link, MyAvid and the Avid Download Center (login and password required).
Media Composer v2019.8 notes:
Windows - If you are installing the editing application and you have a previous version of the editor on your system, go to the Control Panel and manually uninstall the editing application before you try and install v2019.7. You might receive a “cannot continue” error if you perform the installation without manually uninstalling first.
MCDEV-11537: If you intend to use full-frame stereoscopic with an Avid Artist DNxIQ, you may want to remain with Media Composer 2018.12 until the issues with stereoscopic support are resolved in a future version.
Mac os version 10.14.6 is now supported in Media Composer v2019.8
Changed in Media Composer v2019.8:
Composer.
Media Composer. With this release, you have the option to install or not during the install
process. For details on this plug-in, see “Support for NewTek NDI Video over IP” in the Help
“QuickTime Workflow Using QuickTime Live Link” in the Help. TIFF files are linked using the
Avid Generic Plug-in.
Using Live Link with still images is supported. Using Live Link with image sequences is not
currently supported.
- Bug Number: MCDEV-11197. In some instances, the Interleave option might not appear in the Export As dialog box. If you are performing an Export using the Avid Media Processor, the Interleave option should appear when you choose Stereo, 5:1, or 7.1 Audio. Workaround: If it does not appear, briefly toggle back to the Mono setting, then toggle to Stereo Mix once again. Doing so should reveal the Interleave option.
- Bug Number: MCDEV-8641. (AMD Graphics). Systems with AMD graphics cards might display tearing when performing Full Screen playback.
Fixed in Media Composer 2019.8:
The following have been fixed:
1. Bug Number: MCCET-3018. Importing .scc files toggled the input/output signal on the AvidArtist DNxIO
2. Bug Number: MCCET-2878. In some instances, consolidating HD material in a UHD projectwould blackout a Quad Split client monitor.
3. Bug Number: MCCET-3136. (Mac) Arrow keys and Command+W did not always respondwhen in the Marker window.
4. Bug Number: MCCET-3046. Timeline video quality playback settings altered AVC Long-Gcolor difference when transcoding full vs 10bit.
5. Bug Number: MCCET-3063. You might have received
“CDCIReader_Unkown_Compression_Type” error when trying to link and playback Telestream
files in MXF OP-1A Prores HD format.
6. Bug Number: MCCET-3094. You might have received “assertion failed “errors when trimmingcompressed stereo MP2 audio clips if audio scrubbing was enabled.
7. Bug Number: MCCET-3156. (Mac) Video Satellite offset and delay fields changed from -1 to4294967295 when re-opened.
8. Bug Number: MCCET-3105. Shift + F10 to select a camera angle was not working properly.
9. Bug Number: MCCET-3008. In some instances, vertical centering during image import weresometimes offset by one pixel.
10. Bug Number: MCCET-3099. Playback stopped after adding a Mark IN/Mark Out in ScriptView Mode.
11. Bug Number: MCCET-3116. You might have received a “filename already exists” messageeven when saving an export setting with a different file extension.
12. Bug Number: MCCET-3155. You might have received an “assertion failed” error when openinga sequence with Dynamic Relink enabled.
13. Bug Number: MCCET-3114. Logging into Media Central from Media Composer using % or &
in the user name or password resulted in a “Requested time out” error.
14. Bug Number: MCCET-2990. It could take up to a few minutes when logging out from Production Management in Media Composer.
15. Bug Number: MCCET-2987. Markers ignored sync lock when using extended trim.
16. Bug Number: MCCET-2955. In some instances, pressing JKL intermittently scrubbed on itsown, or did not stop when pressing K (pause).
17. Bug Number: MCCET-3106. Project metadata was not displayed in the Project column forlinked then consolidated/transcoded media.
18. Bug Number: MCDEV-11718. (Bin all views) You were able to create empty clip name usingspaces.
19. Bug Number: MCDEV-11729. The Mac Desktop Audio was muted on launch. This helps users
who launch Media Composer while they are in the middle of a video call.
20. Bug Number: MCDEV-11719. Timeline Track Color feature did not show color correctly.
21. Bug Number: MCDEV-11749. Dragging a few selected clips in Frame Bin View to Timeline
added clips in wrong order.
22. Bug Number: . MCDEV-11370 Bins: Creating too long Bin View name caused an Assertion
failed error message.
23. Bug Number: MCCET-3123. The width of columns did not adjust to the clip or sequence name
automatically.
24. Bug Number: . COGS-5897: Timeline - Display tooltip when hovering over sequence name on
bottom row.
25. Bug Number: MCCET-3113. In some instances, the option “Set column for selected clips” was
not available for selected clips.
26. Bug Number: . MCDEV-10584 Adding a Custom Column worked incorrectly with an empty
bin and columns cannot be rearranged.
27. Bug Number: MCCET-3146. Using the Mark clip (default T key on the keyboard) did not work
in Script view in a bin 2019.x. Note that other keys that were supported in previous releases are
also included in this fix:
E - Mark In Key
R - Mark Out Key
T - Mark Clip Key
I - Mark In Key
O - Mark Out Key
D - Clear In Key
F- Clear Out Key
G - Clear Both Key
28. Bug Number: . MCCET-3088 Minimizing the application with dual monitors behaves better on
Mac and Windows.
29. Bug Number: MCCET-2926. Zoom into Region was not visible on all tracks.
30. Bug Number: . MCCET-3124 After sifting some clips and then sorting, other clips (not sifted)
appeared.
31. Bug Number: MCCET-3117. Timeline Quick Find to the left and right was not working if the
sequence contained an audio track effect.
32. Bug Number: MCCET-3098. You might have received a “failed to import” message when
trying to import exported AAF media.
33. Bug Number: MCCET-3087. In some instances, the editing application would crash when
rendering audio effects on a long audio clip.
34. Bug Number: MCCET-2992. The Stop and Pause buttons did not work if you used them from
the Active Palette option of the Command Palette or if you mapped them.
35. Bug Number: MCCET-3134. In some instances, after opening and closing the Audio Punch-in
Tool, some text is missing from the window.
36. Bug Number: MCCET-2981. In some instances, clicking the Stop button on the Audio
Punch-In tool only worked intermittently.
37. Bug Number: MCCET-3145. The editing application might have crashed or resulted in an “Out
of memory” error when trying to load an archived sequence.
Limitations Media Composer 2019.8: Listed below are the known limitations in v2019.8.
1. Bug Number: MCCET-11796. Larger than 10 bit DPX files might fail to link correctly.
o Workaround: Go to File > Settings and click the User tab. In the Link Settings, click the Link
Options tab and make sure Alpha Channel is set to Ignore.
2. Bug Number: MCCET-3110. When in Text View, you no longer have the option in the Bin
Window to columns during scrolling left and right.
3. Bug Number: MCDEV-11430. Media Tool ignores the “Current project” filtering option and
lists media files that are not associated with the current project.
4. Bug Number: . If you launch a project and receive an “Enable 3rd Party Emulation” warning,
even if you select Enable in the warning dialog, you should also perform the following: Select
File > Settings and click the Project tab. Click General Settings and select “Enable Bin Sharing
on 3rd party storage emulating Avid NEXIS/ISIS.”
5. Bug Number: MCDEV-11197. In some instances, the Interleave option might not appear in the
Export As dialog box. If you are performing an Export using the Avid Media Processor, the
Interleave option should appear when you choose Stereo, 5:1, or 7.1 Audio.
Workaround: If it does not appear, briefly toggle back to the Mono setting, then toggle to
Stereo Mix once again. Doing so should reveal the Interleave option.
6. Bug Number: MCDEV-8641. (AMD Graphics). Systems with AMD graphics cards might
display tearing when performing Full Screen playback.
7. 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.
8. 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.
9. 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.
10. 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.
11. 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.
How to obtain the Media Composer 2019.8 Update:
1. Customers who have an active support and upgrade plan will be notified of the availability of the 2019.6 via Avid Link and it will be available via Link, MyAvid and the Download Center. 2. New perpetual and subscription Licenses purchased on or after Friday, August 30th, 2019 will also receive 2019.8.
Robert Davis CEO/Creative Director
Davis Advertising, Inc.
Visit my latest blog, "Concept to Creation" on the Avid Community site
[/url] Visit my Behance portfolio site
OUnder Windows it says to try to uninstall previous versions before installing 2019.7. Then is 2019.8 a patch or is this a typo?
Dan Powell - Take One Digital Media
I am still encountering this:
23. Bug Number: MCCET-3123. The width of columns did not adjust to the clip or sequence name automatically.
I was able to reproduce by changing a sequence name and the column did not move until I re-sorted or reloaded my view. Anyone else having this continue?
M. Cebrian
Fazz Powell: OUnder Windows it says to try to uninstall previous versions before installing 2019.7. Then is 2019.8 a patch or is this a typo?
It is a full install. It is always good practice to uninstall the previous version as there may be leftover files otherwise that can cause issues. Fwiw, I personally, do not uninstall the previous version unless there is an issue. In this case, Avid is informing you of a potential issue if you do not uninstall first.
Marc Cebrian: I am still encountering this: 23. Bug Number: MCCET-3123. The width of columns did not adjust to the clip or sequence name automatically. I was able to reproduce by changing a sequence name and the column did not move until I re-sorted or reloaded my view. Anyone else having this continue? M. Cebrian
I've escalated this to Avid and I'll followup when I get feedback.
Anyone else getting a lot of white-screen application freezes? We keep watching the RAM Memory go from 3000MB to 179MB over time before it suddenly stops working. The only way to get out of this, is a force-quit. I've opened a case. Just curious if we are the only ones.
Yup - Crash central this morning. Random white screens that require a force quit. Plus, Im getting 'Standard Exception' errors that require a force quit.
On top of that - every new bin is opening with a layout that seems to have every column choice active - even though its supposed to open with my selected bin layout (i.e. FOOTAGE). In the bin layout choice its says FOOTAGE.1 as my dropdown option. I can manually choose FOOTAGE, but its a PITA.
Maybe Ill have to create new settings again. Really don't want to have to that all over again.
EDIT: the bin automatically changes whenever I drag footage in. I created a brand new bin and it opened the way it should (FOOTAGE layout), but as soon as I dragged some DNX transcoded RED footage into that bin - the bin layout changed to add a TON of extra column options.
I entered a tech case for Macr the crashing with white screen 03778470.
RalphC
Ralph, my case number is 03777895. I've been working with a tech. It seems like it is pointing more and more to our shared storage (non-Nexis). I just rebuilt all the databases on 60TBs of data to see if this clears up the issue. We've had stop-work issues with this on two stations today, even after restarts. If this keeps doing this, we are rolling back to 2019.7, which did not have this issue.
Thanks,
Marc
I'm experiencing this issue too. Mainly on importing graphics off a fibre shared storage environment
We have had to uninstall and roll back to 2019.7 due to this evolving into a "stop work" issue on all our machines. I was informed by the Avid tech we are on an unsupported version of Windows 10: 1903. (Though the ReadMe says 1803 "or later") We cannot roll back. So, this could be the root of the issue. It seems like a graphics card problem, as I can now get Avid to crash using Snipping Tool to capture parts of the screen. I am not certain it has anything to do with storage any more, but I cannot tell.
I ran a Blackbox last night and got it crash pretty quickly, but we have to roll back to keep working. The more folks report this, the more likely the are able to address.
Im on Win10 1809 and nvidia 431.70Doesnt crash everytime which is frustating, you get used to working then import and white out
Also I’ve just discovered .8 breaks baselight.
If you try and apply baselight fx to a project that didn’t have it on, I get the white out issue too
Ant.... I have a case going and Marc I updated yours....
I will reach out to Martin at Baselight as well.
Marianna
marianna.montague@avid.com
© Copyright 2011 Avid Technology, Inc. Terms of Use | Privacy Policy | Site Map | Find a Reseller