dying for the .2 release. having incompatible frame rate errors when I change my project to uhd. Seems to work in 1080 but i originally started the project in uhd. I think its the new groups causing this. Some groups have mixed frame rate clips, but the project is 80min and trying not to commit the entire thing.. hard to find the problem when I can

I've said this before but avid should really allow manual relinking to files. The relink method is a mess. Somtimes one just wants to SIMPLY point media composer to the correct files.

Really looking forward to this release because my subcaps are jumping like crazy. thank you

why not just make the mxf's in redcine-x and move them to your avid mediafiles? im a fan of the ama method but at some point one has to do what they have to do to start cutting.

Groups that have mixed rate clips in them (created on a timeline/the new feature) can be very problematic when attemping to commit multicam edits. I keep getting: range specified for dup is outside range of component and "tracks have incompatible edit rates" I am manually match framing my non native fps clips and overwriting since commiting

id a get a eurocom with at least 64gb ram. but thats just me.

What is your streaming solution for monitoring in another city (internet streaming) I'm looking into it and will update. Looks like it works with skype. https://www.youtube.com/watch?time_continue=72&v=5Zhh8iwL7c4 thx

A) MXF export via media processor solves most export issues. b) you're using the first version of 2018. Avid fixes bugs with each . version.

edited to be much shorter. I was in the middle of a music video that used mixdowns (director shoots everything slomo and only way to group performances is to timewarp, mixdown with timecode burn, then go back to raw when locked). Had a motherboard die. I rebuilt my system with an extra motherboard i had here in an hour with no issues. However new motherboard

Back to the topic and I don't want to beat a dead horse. And I shouldnt be complaining about exporting a 82 min uhd timeline to dnxhr_sq via media processor in 15-16mins. But its just strange to me that a fully rendered timeline is using so much cpu (although im glad my $ was well spent) to export. Ideally, a fully rendered timeline should mainly