I'm in a 1080p/25 project with 4K footage shot with a DJI Inspire drone. The aerial footage is super sharp to the point where I get a very noticable "moire" effect on brick walls and corrigated iron roofs. Is there any way to fix this within MC 8.8? I can bounce all this over to After Effects to fix but it would be great to fix this right within Media Composer and save some time.

MC 8.8

Basically I don't see the waveform anymore after I render for example the Maxim audio effect (and NugenLM Correct 2 also), using the AMA Link method. Tried to create another project/user. No success. On file import, everything works. Is there an option to enable?

Thank you!

I have just upgraded to 8.5.3 from 8.4.5, and can not find the 'output to DV device' setting. It was a right-click on the video quality settings icon, the wee green screen icon at the lower left of the timeline. Am I missing something?

Thanks in advance,

Paul.

Hi, I've got a strange problem. Tiff sequences brought from After effects, when put on the timeline, they flatten luma levels. This only happens (I think, can't confirm as Im not at the offis) when exporting, not on the timeline. So the exported file has flattened levels when there is a for instance a lower thirds graphic or something in the shot.

Any ideas?

After editing down an existing timeline by a few seconds, I have not been able to remove the blank space at the end of the timeline.  (I've been an Avid user for 15+ years, and this is the first time I've ever encountered this issue!)  I've done all the things I always did--set the in/out points and hit "X" and it has always worked until just now.  I've tried re-inserting material and deleting it.  I can lengthen the timeline with filler material just fine, but when I remove it, it reverts back to its original length (28;30;00), even though there's only about 28 mins of material.  I've got to think there's some obscure box or setting that got accidentally checked or unchecked that has locked my timeline length, but I can't for the life of me figure out what it is.  The only "workaround" I have found thus far is to "select-in/out" the entire video (minus the blank space I don't want) and copy-and-paste it into a new blank sequence, which then gives me the desired length.  But I have many timelines I need to do this with, and it seems unnecessarily cumbersome step, especially since it's a brand new issue for me. Has this happened to anybody else?  Any thoughts?  Much appreciated!

I'd like to buy a Intensity USB 3.0 interface to work with Media Composer 6 in Windows 7 64bit, did this interface supported?

Will it works in 10bit?

Thanks!

Hi

Have an error message that I'm not sure if can be fixed.

I consolidated a finished project to an external drive and checked the timeline played ok...it did.

Having now deleted some of the original media files on the attached raid to free space when I load up the consolidated project from the external drive the sequence loads but there is an error as below

MXF DIDMapper Segmented: Get Parsed Index Table Segmented.

Any ideas ?

Greetings,

I realize this info probably exists somewhere, but sadly I can't find it, and therefore throw myself before you and plead for mercy, and information.

I am running latest 8.9.3 MC, on Windows 10 Professional. Quadro K2200.

Is 385.41 the correct driver?  It seems to work, but I have occassional issues with other (non-video editor) applications.

Best Regards

Media Composer v8.9.3 is being released today, October 30th, 2017.  

Location at Launch:  Media Composer v8.9.3 will be available from My Avid account, Application Manager, and the Avid Download Center (login and password required), Monday, October 30th, 2017 @12:00 PM EDT.  

Installer:  There is a Media Composer v8.9.3 Mac and v8.9.3 Win Installer. 

What’s New in v8.9.3: The following has been changed in this release.

• Effects Parameters Update - With this release, the following effect parameters have been updated to include a decimal for better precision.
• Move Clips Up and Down in the Timeline - Two new commands allow you to easily move clips up and down the Timeline.
• Color Info Tool Setting - A new setting has been added to the Effect Editor that allows you to disable the Color Info Tool from automatically launching when you access a color picker.
• Dynamic Shuttle - With this release, you can use the Dynamic Play Forward and Dynamic Play Reverse buttons to adjust play speeds at smaller increments than with the usual J and L keys.
• Audio Pitch Correction - This release includes an Audio Pitch Correction option. Go to the Audio Settings in the Project window.
• Color Correction Presets - A number of color correction presets have been added to the effects library.
• Adjusting FrameFlex Parameters - With this release, using the Shift key while adjusting the X, Y, Size, and Z Rotation framing parameters, allows for a more controlled adjustment.
• Tool Palette Update - This release includes changes to accessing the Tool Palette.
• Motion Adapters and Source Settings Support for Matte Key Effects - In previous releases, Motion Adapter effects were not applied to clips with Matte Key effects. With
• this release, Matte Key’s support Motion Adapters. Adapters are applied to both the graphic fill and alpha sub tracks.
• Relinking Across Frame Rates - With this release, you can relink across different frame rates. A new option has been added to the Relink dialog box that allows you to relink to clips across different frame rates

What’s Fixed in v8.9.3:

• Bug Number: MCCET-2091. You might have received an “EXCEPTION: CM_NO_SOURCE” error when adding filler to the start of an audio track containing an Audio
• Track Effect.
• Bug Number: MCCET-2093. (Mac) You could not open a bin by accessing the Finder and double clicking a bin from the Avid Projects folder.
• Bug Number: IPI-1784. The length of spanned P2 clips were different when you checked the clips into Avid Interplay.
• Bug Number: MCCET-1953. You could not always smoothly drag The Tool Palette Fast Menu to open the Tool Palette. There is a new Tool Palette button that properly opens the Tool Palette. See “Tool Palette Update” in the Media Composer v8.9.3 “What’s New”.
• Bug Number: MCCET-1912. You might have experienced a delay when opening the project window if an Avid Nitris DX was connected.
• Bug Number: MCCET-1869. In some instances, while in Script View or Frame View, the thumbnails might not display clearly. This is because the application prioritizes displaying the thumbnails faster rather than having the best resolution for the thumbnails. A new option, “Faster thumbnails” has been added to the Bin menu. For bins with a lot of thumbnails, it is best to leave this option enabled. If you prefer better resolution for the thumbnails displayed in a bin, deselect Faster thumbnails from the Bin menu. This option only applies to the currently selected Bin.
• Bug Number: MCCET-1966. (Avid DNxIO) If the Source/Record monitor was minimized, the client monitor might not have updated properly.
• Bug Number: MCCET-2070. In some instances Media Composer would hang when applying a Timewarp effect.
• Bug Number: MCCET-1735. (Avid Nitris DX) If you had a master clip with a D-track loaded in the Source monitor, and you had a sequence without a D-track, the client monitor would flash black if you switched from the Source monitor to the Record monitor.
• Bug Number: MCCET-2004. The “Allow 16 channel output” setting in the Audio Project Settings was not sticking.
• Bug Number: MCCET-2047. If you copied a 3D Matte key from one clip and applied it to another, the 3D Matte key did not apply properly.
• Bug Number: MCCET-2020. You could not successfully import XDCAM media if “Enable legacy XDCAM import” and “Enable legacy P2 import” were selected in the Link Settings menu.
• Bug Number: EPIC-1856. When your locale was set to German, Spanish, or Italian, a number of Media Composer dialog boxes displayed cut off text. Avid has made improvements when displaying these languages so the text is displayed properly. Also, a number of dialogs now include tool tips in the appropriate language. Avid will continue to make improvements with subsequent releases.

Known Limitations:

• Bug Number: MCDEV-8421. It is not recommended to use Avid Media Composer v8.9.3 with Media Indexer v3.8.1.
• Bug Number: DAMAN-1927. (Mac) In some instances, the Canon AMA plug-in causes the editing application to crash. Remove the plug-in if the system continues to crash.
• Bug Number: MCDEV-8397. In some instances, when loading media into the Source or Record monitors, you might have received an “STD Exception” error.   Workaround: The current workaround for this issue is to disabled the Dual Copy Engine option in the Video Display Settings

Documentation:  The What’s New Guide and ReadMe for Media Composer v8.9.3 will be posted to the Media Composer 8.x Documentation page on the Knowledge Base at launch.

How Customers will obtain the Media Composer v8.9.3:   

1.  Customers who have already installed the latest version of Media Composer will be notified of the availability of the v8.9.3 upgrade via the AppMan. The Apps tab will also provide a link to download and install the update when desired.

2.  New customers who purchase Media Composer on or after October 30th, 2017 will receive this v8.9.3 update in their Avid Master Account.

3.  Customers on current valid Upgrade & Support plans can download the Media Composer v8.9.3 and either update from their Avid Master Account  or the Avid Download Center (login and password required.) after launch.

4.  Customers NOT on a current Upgrade & Support contract that wish to upgrade to Media Composer v8.9.3 must purchase a new Subscription or Perpetual License.  

Moved to Media Composer - Mac forum. You can find it here:

http://community.avid.com/forums/t/183044.aspx

Hi

We have a brand new HP z840, with dual E5-2634 v4 Xeon processors at 2.2ghz (10 cores each) and 32gb of ram. Video card is m4000 with drivers avid recommended. It is connected over cat-6 gigabit to an EVO SAN with 96tb and raid 5. We have a single 17 minute clip shot in AVC Intra 4k 422 on the Panasonic Varicam that is shot VLOG in an MXF wrapper -- and that plays fine. But as soon as we put like 1 or 2 color changes to it to make it brighter or darker, it starts to stutter. Am I missing something here? We also have the very very latest version of MC (I forgot the number but it was upgraded like a couple days ago to the newest) and an ARTIST I/O. Is it that my system is not strong enough? Seems like a crazy idea considering my friend edits this same stuff on his high end macbook, i think. What can we do?

Help!?

I'm stumped on an issue involving the RED AMA plugin.  After weeks of searching and coresponding with Avid Support, i'm left puzzled on why some of our Z400's load the plugin and others do not.

Our Z400's are all spec'd identical both in Hardware and Software.  We have footage that was shot with a newer RED Cam that requried us to upgrade our RED AMA plugin from v 1.11 to v 1.19.0.1000 on Media Composer 7.0.5 in order for it to AMA properly.

Several of our Z400's have no trouble loading the plugin during the startup of MC.  While others fail to load the plugin at all.  I've tried uninstalling and reinstalling as well as incrementally stepping through each version of the RED Plugin linked in the version matrix on the RED AMA Plugin support page.  I've also tested versions of MC 7.0.5 - 7.0.7.  As a last hope effort, I recently reformated one of the Z400's, installing MC 7.0.7 from the ground up and only installing the RED plugin.

I'm unable to determine why the plugin will not load on MC startup.  I test to see if the plugin loads by running the "ama_listplugins" command in the console. 

Does anyone have experience with this issue or know how to get a verbose log of MC during its startup to see why it is skipping over loading the plugin.  No errors are presented when it fails to load the plugin.

System Specs:
Avid Qualified HP Z400, Xeon W3540, 12 GB RAM, Quadro FX 3800, Win 7 SP1

Note:I've also loaded the plugin on non avid qualified laptops and qualified Z800's and it successfully works on MC 7.0.5 - MC 7.0.7 with RED AMA plugin v 1.19.0.1000 on both Windows 7 and Windows 10 even though the Support page annotates that the version requires MC 8.6.

Not sure what I'm missing, but my timeline now stutters much more than it did before my fresh OS reinstall. 

The only big difference I can think of is that I'm now back on Windows 7 since I can't figure out how to get the free upgrade back to Windows 10 that I did before. I doubt that matters much for playback.

I'm using the recommended Quadro driver for my 2000D card. And recommended Quicktime too. Perhaps I should roll back to something?

Also, I thought there was a way to boost the RAM that MC uses, but can't find that info anywhere.

Regardless, any suggestions would be helpful.

EDIT - found in MC where to bump the memory used, so I changed it from 1 GB to 7.  I can't imagine why the default is so low. Regardless, I also changed the Windows theme to "Basic". I also rolled back to an older version of the Quadro driver. And all of those things seem to have helped some, although there is still some stutter while playing back even rendered sections of the timeline. Not ideal.  

Hi,

I need to import AAF from Premiere which almost works fine. The sequence looks OK and the source files are offline in the bin and the filenames look correct. 

But all WAV files are in 29.97 FPS which means they differ in length and it is not possible to batch re-import them to make them not offline. Is there any chance to change this wrong metadata and batch import them?

So far I use a workaround with another project at 29.97 fps but it seems to me not ideal to have media with 29.97 fps in all 25fps project.

Thanks a lot.

Hi,

When I apply an effect on a clip and go to effect mode, the record monitor is filled with the same image as the effect editor. So it is impossible to ad an animatte for instance. When I go back to playback mode the record monitor starts having glitches of the effect editor. Until I restart avid.

Please advice, thanks.

Avid media composer 8.9.2, intensity pro. Windows 7 pro, NVIDIA Quadro K2000, 

Great news!  Media Composer v8.9.4 launched today, Monday, December 4, 2017 at 3:00 pm EDT.   

Location at Launch:  Media Composer v8.9.4 is available from My Avid Master Accounts, Application Manager, and the Avid Download Center (login and password required) @3:00 PM EDT.  

Installer:  There is a Media Composer v8.9.4 Mac and v8.9.4 Win Installer.    

Patch - There are NO Patch Installers. There are updates on the patch page, but they are full installers only there because some users only go to the editor patch folder to grab the latest build.

What’s New in v8.9.4: The following has been changed in this release.

• Support for HiRes Monitors with Mismatched Scaling - In previous releases, Media Composer supported dual HiRes or HiDPI monitors when both monitors were set to the same scaling. With this release, you can mix 100% and 200% scaling for Win10 dual monitor setups.
• Go to Next/Previous Event - The Rewind and Fast Forward buttons have been renamed and have new icons to reflect what the buttons actually do. The new names are Go to Next Event and Go to Previous Event.
• Composer Settings: Move (Formally the FF/Rew tab) - The options in the Move tab control how the position indicator moves when you use the Go to Previous and Go to Next buttons in your Avid editing application monitors.
• Searching for Items in the Timeline - With this release, when you search for items in the Timeline, the Find window will display the Timeline elements matching the search text.
• Mappable Segment Preview Button - You can now map the Segment Preview button. The button has been added to the CC tab of the Command Palette.
• Mapping Bin Fast Menu Commands to the Keyboard - You can map bin fast menu commands to the keyboard.
• Appending All Markers to EDLs, Cut Lists, and Change Lists - You can now append all Markers from a composition to an EDL, Cut List, or Change List. Previously, if the marker was in the composition but was not part of an event, it was not included in the output.
• Previewing In-Progress Sequences and Clips While Exporting - This feature allows you to link to a file that is still being exported (on another system).
• Video Data Rate Column Heading - You can now choose to display an additional bin column heading. The Video Data rate column displays the data rate of a linked clip.
• Support for Playback of 4 Streams of XAVC-I - This release of the editing application supports playback of 4 streams of XAVC-I in an UHD 59.94p project.

Fixed in v8.9.4: 

• Bug Number: MCET-2145. You could not export subclips as OP1a if the Use Marks option was selected.
• Bug Number: MCET-2075. While in the Effect Editing workspace, the editing application crashed when undoing changes in a Paint or AniMatte effect.
• Bug Number: MCET-2090. Even with “Copy all media” selected as the Export method for an AAF export, the entire clip was not copied.
• Bug Number: MCET-2168. Only the topmost clip of a group clip retained its LUT. All clips in a group clip now retain their LUT.
• Bug Number: MCET-2187. In some instances, you could not enable 12-channel or 16-channel in the Audio Project Settings even when “Allow 16 channel output” was selected.
• Bug Number: MCCET-2115. You might have received an “Insufficient Disk Space” error when importing multiple AVCHD clips.
• Bug Number: MCCET-2099. If you pressed the Enter key on the numeric keypad after renaming a track, the Rename dialog box would not close. Now, once you type a new name, the OK button is highlighted and pressing Enter on the numeric keypad will retain the new name and close the Rename dialog. This fix has also been incorporated into the Rename, Timeline Clip Notes, and Marker windows. The following applies when you are working with the Rename, Timeline Clip Notes and Marker dialogs:

•  
  • Pressing the Enter key on the numeric keypad will perform the task of whichever button has current focus, such as OK, Cancel, Remove, etc.
  • Pressing the keyboard Enter (Windows) or Return (Mac) key will add a line break if the cursor is active in the text area. If the cursor is not in the text area, the behavior is the same as pressing the Enter key on the numeric keypad.
  • Pressing Esc will cancel the dialog.
  • When you are in the dialog window, pressing the tab key will move the focus from one element to the next within the dialog.

• Bug Number: MCCET-2119. In some instances, if you performed a mix-down of a clip containing an audio suite effect, the editing application would hang during the render operation.
• Bug Number: MCCET-2165. You might have received an “Assertion failed” error when selecting an EVS Transfer Manager profile.
• Bug Number: MCCET-2088. (Interplay) The editing application might have hung when Media Stream Manager (MSM) was performing a rescan. This occurred if the media file folder name was in lower case. This has been fixed.
• Bug Number: MCCET-1979. (Windows) You might have seen ghosting or redraw issues when performing a trim.
• Bug Number: MCCET-2175. In a previous release of the editing application, the Master Audio monitoring fader default was -20. The correct default is 0.
• Bug Number: MCCET-2127. A grouped transcoded clip with a LUT applied would ungroup if you pressed the up or down arrow key while the clip was in the Source/Record monitor.
• Bug Number: MCCET-2128. Bullets (•) in a clip name did not translate properly in the List Tool.
• Bug Number: MCCET-2073. In some instances, pre-rendered source-side motion effects did not remain rendered when loaded into the Source monitor.
• Bug Number: MCCET-2117. The number of clips being transcoded in the transcoding process window did not always reflect the number of the actual clips being transcoded.
• Bug Number: MCCET-2108. Banding artifacts might have appeared when you transcoded XAVC Intra 100 to DNxHD (8-bit) media containing color transformations.
• Bug Number: MCCET-1902. After performing a batch reimport. .wav files might have had the wrong timecode.
• Bug Number: MCCET-2072. When performing a match frame on a sequence containing group clips brought forward from an earlier release of the editing application, you might have received a Crash Report followed by an Exception error.
• Bug Number: MCCET-2113. You might have received a “No Filler NAL unit found” error when performing a Send to Playback of consolidated clips.
• Bug Number: MCCET-1983. In some instances, when you were in trim mode and monitoring effects on a higher track, incorrect video would momentarily appear.
• Bug Number: MCCET-2133. You might have received a “FatalAbort Assertion” error when trying to play some consolidated clips.
• Bug Number: MCCET-2031. In some instances, when you enabled Sync Lock, Ripple Trim rollers did not return to their original position when audio tracks were reselected.
• Bug Number: MCCET-2139. In some instances, after relaunching Media Composer, a portion of the Timecode window was transparent.
• Bug Number: MCCET-2143. The first “Text to Find” field wasn’t automatically highlighted when you performed a Custom Sift.
• Bug Number: MCCET-2132. In some instances, the editing application did not return results when performing a search for text when “Scripts in Project” was selected as a search criteria. This has been fixed. NOTE: For this fix to work on existing scripts, you must open the script and then save it.
• Bug Number: MCCET-1981. After a batch re-import, a consolidated subclip and new master clip playback from the original master clip rather than the Mark-IN point of the subclip.
• Bug Number: MCCET-2109. Project info in the Project Selection window would sometimes show the wrong raster dimension.
• Bug Number: MCCET-2092. If the Transcode option was selected in the Export dialog, you might have received an “Exception” error when exporting a seq. with various frame rates as an AAF.
• Bug Number: MCCET-2024. In some instances, group clips would display n/a as the source name in the Timeline.
• Bug Number: MCCET-2134. In an Interplay environment, Color Correction Presets were missing in the Effect Palette.
• Bug Number: MCCET-2096. In some instances you could not cut or remove filler at the end of the Timeline.
• Bug Number: MCCET-1895. You received an “ADM_DIO” error when trying to output video to DV deck via Firewire. The Output to DV Device option is no longer supported with the Media Composer editing application.
• Bug Number: EPIC-1856. When your locale was set to German, Spanish, or Italian, a number of Media Composer dialog boxes displayed cut off text. Avid has made improvements when displaying these languages so the text is displayed properly. Also, a number of dialogs now include tool tips in the appropriate language. Avid will continue to make improvements with subsequent releases.

Notes:  

1. (Mac) With this release, the Avid DX Driver is not automatically installed when you install the editing application. If you need to install the Avid DX Driver to work with your Avid IO device, during the installation process, click the Media Composer Editing Application opener and choose the Avid DX Driver and click Continue. If you do not install the driver during the installation process.

2. ( Win ) The Avid DX Driver is still automatically installed with the Windows version of the editing application.

Documentation:  The What’s New and ReadMe documents will be uploaded to the Knowledge Base at 3:00 pm EDT - Media Composer v8.0 Documentation page.

How Customers will obtain the Media Composer v8.9.4:   The latest update to Media Composeris available in My Avid Master Accounts, the Download Center and AppMan.  My Avid and AppMan will push after the Download Center goes live at 3:00 pm EDT.

1. Customers who have already installed the latest version of Media Composer will be notified of the availability of the v8.9.4 upgrade via the AppMan. The Apps tab will also provide a link to download and install the update when desired.
2. New customers who purchase Media Composer on or after December 4th, 2017 will receive this v8.9.4 update in their Avid Master Account.
3. Customers on current valid Upgrade & Support plans can download the Media Composer v8.9.4 and either update from their Avid Master Account  or the Avid Download Center (login and password required.) after launch.
4. Customers NOT on a current Upgrade & Support contract that wish to upgrade to Media Composer v8.9.4 must purchase a new Subscription or Perpetual License.  

Hi,

I've had this problem before where when I load up media composer I get a message saying that quicktime is not on the system (when it *** well is) which prevents me from exporting my videos.

I've already tried uninstalling and re-installing media compose along with quicktime (and yes I've done it in the correct order) but still no joy.

I could export videos using media composer the other day but since I've had some microsoft technician via remote access fix my pro tools problem where it was not working period.  I fear that he may have inadvertedly removed or deleted the necessary file(s) that allow me to export from media composer.

Please help.

HP Z440 Workstation

Intel(R) Xeon(R) CPU E5-1620 v3 @ 3.5 GHz

3.5GHZ 1TB HHD Internal Memory 16GB RAM

Nvidia Quadro K2200 graphics card

So I've spent a lot of time on this and have been unable to get definitive answers. I thought that DNxHR 444 was RGB by default, but I believe that's not the case.

So a few questions:

1. Is DNxHR 444  RGB or YUV 444?

2. There a way to specify it to be RGB or YUV 444?

3. Is some advantage of one over the other? I've read that YUV 444 is easier to compress than RGB because the luma is seperated from the R and B color channels. But I have no idea how accurate that is.

BTW, below is screen print of how ffmpeg analized a DNxHR 444 file.

Hi

So i had some earlier problems and I have isolated and here is our current issue.

We had AVID MC with symphony 8.9.1 and when you open a project regardless of the user or format or ANY settings it suddenly spikes memory usage to 96%. We have another machine in the next room that is exactly the same and it never goes over 30%. Any idea what can cause this? We are desperate!

Thanks!