Hello everyone,

First time on a TV movie (used to work on features), in France, for french TV. I'm wondering if these programs are still broadcasted in interlaced fields nowadays.

I think it will be shot in 25p, but I wonder if I should set my project in 25i. It's confusing me.

Thanks for your advice.

Hi - I'm planning to pick up a non-qualified Lenovo Legion 7i laptop that I'm hoping will be able to run Media Composer 2019.12.

It won't be used for client work, so I'm not so concerned about the full stability that I'd expect from a qualified laptop, but I'd love to know if there are any known confllicts with the below system/components -- or if it should it theoretically work fine? 

Lenovo Legion 7i 15"

• 10th Generation Intel® Core™ i7-10750H Processor (2.60 GHz, up to 5.00 GHz with Turbo Boost, 6 Cores, 12 Threads, 12 MB Cache)
• NVIDIA® GeForce RTX™ 2070 Super Max-Q 8GB
• 16 GB DDR4 2933MHz
• 512 GB PCIe SSD
• 15.6" FHD (1920 x 1080) IPS, anti-glare, Dolby Vision™ HDR 400, 500 nits, 144Hz
• Windows 10 Home 64

And would any of these upgrades be recommended for Media Composer?

• NVIDIA® GeForce RTX™ 2080 Super Max-Q 8GB
• 32 GB DDR4 2933MHz
• 1 TB PCIe SSD
• 15.6" FHD (1920 x 1080) IPS, anti-glare, Dolby Vision™ HDR 400, 500 nits, 240Hz
• Windows 10 Pro 64

Thanks for any advice!

-erik

Hi 

I know it is not a big thing but why is 2019.6 limited to 2 highlight colours when previously there were about 7? (This is in the interface setting)

I was partial to the default blue but am now limited to either a brightish white or a purple. Why the change in the number of colours for this setting?

Ta

Neil  

I recently updated to 2020.6 and I'm getting the following error:

Exception: Structured Exception, ExceptionCode:3221225477, ExceptionString:ACCESS_VIOLATION ...

This wasn't an issue before the update from a 2019 version. It is only happening when working with effects, mainly when manipulating Matte Key positions of PIP positioning. Maybe it would happen more with others, but this is when it's mainly popping up and it's frequent. Happening in UHD 29.97 & 1080 29.97 projects.

Any ideas on solutions? I already tried restarting, reinstalling Avid, disabling devices like my BM monitor mini, disabling OpenGL acceleration inside Avid, wiping the MCState files. I'm out of idea. This is crashing at least twice an hour when working with effects, but rebooting clears it up for a little bit and the error doesn't linger on a particular spot on the timeline. After I reboot and revisit the same effect on the same clip it works fine, but then 30 mins later, I'll apply a PIP and change the position or scale and it crashes again.

Specs:
Dell Worstation (approved)
Media Composer 2020.6
Windows 10 Pro (10.0.18362)
Dual - 8core Xeons
64GB Ram
AMD FirePro Card on recommended driver (A little old but I disabled OpenGL previews to see if that was related and the error still occurs)
Blackmagic 4k mini monitor (disabled in device manager to test and the probelm still occurs w/out this being enabled)
Using only local, internal SATA storage

Hi, 

I'm facing whit this issue. (I quote, It's summarizes the problem well)

"Sometimes when footage was shot with 50FPS for example, editors want to have it synched with sound (if there is any).

So what happens is, that an assistant Editor applies a timwarp (200%) on the Video Master Clip, syncs it with the audio file and generates a subclip. This method works well up to a point where you want to transfer an edit to DaVinci Resolve to online the whole thing. (for the editing process the footage was converted from ProRes4444 to DNxHD36)

An AAF File doesn't seem to transport the information that there is a timewarp applied to the footage and it has to done by hand. It's not a problem when there are only a couple of them but if you have a sequence with minutes of those it takes hours to do it."

more here

My project 1080p 25FPS

Delivery will be approx 60min long 25FPS 1080p

All footge shoot 50FPS, multicam, (4k, 8K),  all comes with Audio.  Has to be synced, groupped.

DnxHD36.mxf created with resolve  - 25FPS

In Avid, Version:2019.12.1.53716.0  (slowmo) clips were dropped to a sequence, (one by one each has own),  with 200% speed up motion fx on them. Put the audio under them, and created subclips. Subclips were gruppped. As soon they get into a sequence, they behave as normal 25FPS, i can do resize, stabilze, etc... But at export, AAF / EDL doesn't take 200% the motion fx to resolve.

So, do you anyone (Avid tech crew as well) know any sollution for this? Will be fixed?

Or any other workflow how to deal with a tonns of 50FPS footage in to a 25FPS project?

Thanks.

Are there any plans to add keyboard customization to the numeric pad in the (hopefully) very near future? If not, what are the technical or general reasons why not? I've been hoping this would be added since I started using Media Composer in 2003. 

Ideally, keyboard shortcut levels could be expanded beyond just the shift level - I'm maxed out as it is. I'd like to see all modifier key and combo possiblities available and all commands be mappable.

The numeric pad would be extremely useful and efficient. Multicam angles could be mapped, video and audio tracks, primary editing commands - all in a convenient area of the keyboard using different shortcut levels.

The more I can map to the keyboard the less I have to mouse around and then move my hand between the mouse and the keyboard. This might not seem like it takes a lot of time but it adds up and reduces efficiency. 

Premiere and Resolve, iirc, both allow for numeric pad and all modifier keys (alt, control, option, command, etc). 

This may require a re-work of how shortcuts are applied (command palette/menu commands dragged to the keyboard) but I think it would be tremendously helpful. 

A feature that really sped up my editing was the keyboard shortcuts for "move clip up/down". Seems so small and simple but is a really big time saver. If holding a modifier key could by-pass overwriting as you move a clip up or down that would be awesome. 

Further, a shortcut to select clip at position would be great too. So, I don't have to mouse to the clip and then left-click to select. Holding a modifier key and going to next edit could select multiple clips. Another modifier or setting could ignore tracks.  I know you can alt + drag to lasso select clips but that's using the mouse again.

While I'm at it - support for other control devices. Like the Loupedeck devices. My understanding is they need access to an SDK to implement support. Currently Premiere Pro and FCP X support this.

Using the loupdeck to control colour correction, effect parameters, audio levels, etc. would be amazingly helpful.

Hopefully I'm not the only editor that's been wanting some or all of these suggestions but anything that can be done to increase our efficiency and customization of how we interact and control Media Composer would be most welcome. Thanks!

So I just finished editing my project.  There are two people I have to send my timeline to.  One is the colorist who is using Blackmagic Resolve and the other is the post sound who is using Pro Tools.  The colorist already has the raw files (I've been editing on proxies).  What AAF settings should I use specifically to send her so that it works with resolve.  The guy doing sound does not have the audio files, what settings should I use to send him.  Bare in mind that for both I have to email or dropbox them.  What I'm looking for is a specific AAF setting so that I can get them what they need :)

I'm using MC 2018.12.3

Hi, 

I use a 4k monitor as secondary display on my laptop. I get bad frame tearing with the composer window on the secondary monitor. I installed 2020.6 but the specified nvidia 441.28-desktop-win10-64bit-international-nsd-dch-whql driver is not compatible to my hardware. Is the tearing a result of the graphic driver? Are there any configuration tips and tricks?

When I use the composer window on the main laptop display there is no tearing. Any advice? Other than buying a certified system? ;) It used to work just fine for years with GeForce cards, but I only just now started using the 4k display @ 25Hz. Changing it to 1920x1080 does not help.

I have a GeForce MX250.

Cheers and thanks! 

Thomas

Just incase you needed some info on titler plus here is video by

 Roger Shufflebottom. 

https://vimeo.com/433695839

Hi,'

I have an opportunity to purchase a used system for $899. After a fair bit of research this seems like a pretty good system that would run Avid Media Composer with no problem.

Here are the specs:

• Lenovo Thinkstation D30
• Type: 4223DD5
• 2x Intel 6 Core Xeon E5-2630 2.30ghz
• 16GB (2x 8GB)
• 500GB SATA Hard Drive
• DVDRW
• Nvidia Quadro 4000 Video Card

Obviously I will need a few extra hard drives and an OS.

Would you say this ia a good deal?

TIA

Hi All

The Audio Punch-In tool doesn't work any longer for me as it did for years.

Scenario:Mark-in point is set. Input source: windows mixer. When I want to start a voice over, MC make only "Pling". No error message, nothing. The same is true if I hit the Play In/Out Button.
I can enter in the Punch-In tool whatever I want: New channel, existig channel, different target bins, with or without mark out point, with or without pre/post/handles.

Where is my mistake? I have no idea where to search. Probably it is something within the settings, as the system is setup new.

My system: New built computer with i7-7700K, new Win 10 Prof, fresh installed MC 8.9 one month ago.
The Microphone is connected via audio-input on the mainboard. With the connected loudspeaker I can hear that it is working.

Project: 1080i/50

Thank you for your help!

Hi,

I have 15 workstations editing with MC2018.12.11.

Some are mac based, others are win7, win 10 based, some have black magic cards and others mojo DX.

Strangely, since some weeks, my win10 + mojoDX setups are suffering about a very strange issue : when exiting the application,  we get a BSOD trashing all setting files (Site settings ,  Project settings ...) and corruping all unsaved bins.

Seems to be dx driver related , But don't Know how to solve It.

I really dont know what changed. 

Need help.

Today, April 30, 2020 at 12:00 noon ET, we launched a new Media Composer Long Stream Maintenance Release - Media Composer v2018.12.11.  

Location at Launch:  The Media Composer v2018.12.11 (Mac and PC) is available on the Download Center at launch.  

ReadMe:  Media Composer 2018 Documentation page .

IMPORTANT INSTALLER INFO (Windows) Both a full installer and a patch installer are provided for Win Media Composer v2018.12.11.  To use the patch, you must have v2018.12.3 already installed. Then use the 2018.12.11 patch to update to v2018.12.11. 

Note: Avid will NOT approve nor test Catalina on any 2018.x versions due to the extensive work to remove a lot of 32-bit code and making large changes that could have adverse effects on users who rely on 2018.12.x.    If anyone need to run Catalina, they should upgrade to Media Composer v2020.4.  Anyone with an expired license will need to crossgrade to a subscription to get current and be able to run Media Composer 2020.4.  This can be done through their MyAvid master account.

Limitation:  Bug Number: MCCET-3573. Cross-rate linked media that was created in Media Composer v2019.x is not backward compatible with Media Composer versions 2018.12.x and earlier. Attempting to use cross-rate linked media from Media Composer v2019.x to 2018.12.x might result in errors. 

What’s fixed in 2018.12.11:  The following has been fixed in this release.

• Bug Number: MCCET-3499. The Frameflex scaling quality might not have been good when linking to a mov file. 
• Bug Number: MCCET-3485. Media checked into Interplay as XAVC I CBG Class 100, was checked out in new project as AVC-Intra 100. 
• Bug Number: MCCET-3276. With a Black Magic device attached, in some instances, the editing application would hang and goes into the 'whiteout' state during editing. Updating to Black Magic Desktop v11.5 fixes the issue. 
• Bug Number: MCCET-3462. Closing a bin that is Read Only at the OS level resulted in an Exception.
• Bug Number: MCCET-2921. Some captions from CaptionMaker were missing in preview. 
• Bug Number: MCCET-3466. (macOS) Media Composer may have appeared frozen while using audio scrub. 
• Bug Number: MCCET-3356. (List Tool) Comparing XML Change lists containing Varicam media resulted in an “Error encountered in list” error. 
• Bug Number: MCCET-3412. Performing an Edit While Capture could not trim newly captured media after 30 seconds. 
• Bug Number: MCCET-3459. In some instances, group clips do not redraw correctly in the Timeline when you zoom in and out. 
• Bug Number: MCCET-3442. The AudioSuite Reverse effect was not working correctly. 
• Bug Number: MCCET-3451. The AudioSuite Vari-Fi effect was not working correctly. 
• Bug Number: MCCET-3414. In some instances, you might have seen banding issues after rendering or performing video mixdowns. 
• Bug Number: MCCET-3316. When working with the SubCap effect, the Outline Weight behaved differently in Media Composer v2018.x and above (the space between the letters became larger) compared to Media Composer v8.x. In order to fix this, the Outline Weight includes two options to choose from: Basic Outline and Basic Outline (extra spacing.) 
• Bug Number: MCCET-3449. In some instances, toggling Dynamic Relink setting between high res and proxy resolutions did not successfully update. 
• Bug Number: MCCET-3233. If there was filler between segments, jumping to specific timecode did not work properly. 
• Bug Number: MCCET-3473. In some instances, you received a “You cannot import this file into a bin” message when trying to import a file you previously exported. 
• Bug Number: MCCET-3487. After adjusting the volume on track, the local clip color might have reverted to its default color. 
• Bug Number: MCCET-3482. When working with Dynamic Relink, if relink was set to Highest Quality and you do not have access to the drive containing the highest quality media, you received a “cannot find file requested” error message rather than remain linked to the lower resolution media. 
• Bug Number: MCCET-3275. Using an anchor when synchronizing a SubCap effect did not work. 
• Bug Number: MCCET-3329. With certain keystroke combinations you might have experienced behavior such as slow motion frames or K not stopping playback.
• Bug Number: MCCET-3069. (NRCS Tool) You might have experienced issues on your first attempt at scrolling down and clicking at the bottom of the Story Panel.
• Bug Number: MCCET-3527. The XDCam HD export option was missing if you chose to Export As using the Avid Media Processor.
• Bug Number: MCCET-3541. Media Composer could have an exception when performing a Bin Sift.
• Bug Number: MCCET-3252. In some instances, Timecode changed when checking out clips from Interplay to Media Composer when Dynamic relink wass enabled.
• Bug Number: MCCET-3474. Marking an IN and OUT and then dragging an effect to the Timeline sometimes caused multiple additional add edits.
• Bug Number: MCCET-3279. A new setting has been added to Trim Settings. The “Sync Rollers at Position In Filler” puts sync rollers at the blue bar in filler just like non-filler. This makes sure markers in filler will stay in sync with other tracks as they are trimmed. This option is defaulted off.

Hello,

I have a problem with Avit Titler +. Since I upgrade to MC 2020:2 the titler is lost. I can not edit old titlers and there is no reaction when i click the T+ buttom. There is no Title section in the Effect meny.

I have uninstall Avid Link and Media Composer two times and reinstall, but the Titler + is still disaperaring.

Just now, I have no clue how to problem shuting or get back to 2020:4

As per advice seen here, I recently purchased the HPZ 820 to run my Symphony 6.5 on WIN 7 -- see specs below. I bought it with an Nvidia K4000. Perhaps I have made a mistake and should have chosen the 4000 instead. But the problem I am having is that processing of complicated FX does not seem as fast as it should be, at least as opposed to my previous Z400. There is also a very slight but maddening delay upon repositioning the cursor on the timeline. Hopefully the problem has to do with finding the correct K4000 driver. Anyone have any advice Re drivers? Or maybe I need a different card. I have an Nvidia FX 4800 on my Z400. Should I try that one? Thanks.

Hello,

I have a problem with Avit Titler +. Since I upgrade to MC 2020:2 the titler is lost. I can not edit old titlers and there is no reaction when i click the T+ buttom. There is no Title section in the Effect meny.

I have uninstall Avid Link and Media Composer two times and reinstall, but the Titler + is still disaperaring.

Just now, I have no clue how to problem shuting or get back to 2020:4

I just upgraded from 2020.5 to 2020.6, but avid titler+ cannot be opened at all.... So I installed it back to version 2020.5.

Let's say for example that I have a very simple project: I only use one video clip that is 1 hour in duration and large in size. But in my sequence I use only 1 minute from that long clip. I was wondering if it is possible to backup my project without archiving the whole 1 hour clip, but just that 1 minute that I use in my sequence with just some overhead.

I know that in the audio world there is an option in Pro Tools that you can trim your files with some overhead so you don't have to backup everything.

Can we do something similar in Media Composer?

I produce 60- to 160-minute videos of plays and musicals.  For years it was quick and easy to export a mixdown reference file to Squeeze.  After Squeeze, I found Adobe Media Encoder (2017 v.11.1.4) that accepted the MC Quick Time reference file.  Now apparently ME 11.1.4 is no longer available or functioning.

It takes hours to export my work to .mov, etc.  Has anyone come across new software that likes QT Reference files?

I'm still getting to grips with my massive upgrade from Xpress Pro to MC 2018.

When I connect an external drive pretty well all files on that drive get linked to an open bin. Is there a way to prevent this, I just want to select certain files - and usually I like to import rather than link.