Darrin Stemple
Forum Replies Created
-
So the best thing we can end on is that this is a normal function of Media Composer and somehow we just haven’t realized it because we always cut the multigroups into sequences before handing them over to editors. I’ve called friends in three other offices and they all have multigroups that show the same issue. If anyone else has any further thoughts into this I would absolutely love to hear it!
Thanks,
Darrin
-
Sorry, that would’ve been good info. I’m multigrouping by aux TC in a sequence. Initially I was using Quickeys but now I’m doing it manually. Both methods I’ve used for years and never had this issue.
-
Just an update: I tried to multigroup the same cards but as transcoded to DNx36 instead of consolidated media and the same thing happened.
One other thing, these aren’t REAL sync maps, I’m just trying to make test material from two cards/cameras.
-
I just finished the update but the export still isn’t going. The big tell is if there’s no time that appears in the export dialogue box and the progress bar fills in quicker than it should. Every time this has happened the export has failed. It’s an easy way to tell in the first two minutes instead of having to wait for the full hour.
-
Hey there, thanks for catching this. I’m updating on one of the machines in the office right now as a test but, in my experience, the further ahead your OS gets from the Avid version the more problems there are :\
Right now the only work around we can think of is to export the 10 minute chunks, open them in Quicktime Player, and use its functionality to stitch them back together into one video. Fortunately we still have 3-4 machines on Mountain Lion and Avid 7.X which export fine.
Honestly, your avatar perfectly shows how I feel right about now. I can’t believe a version of a professional video editing program passed QC while “exporting with custom settings is a known bug that crashes Avid.” It’s utterly ludicrous to me. As I replied to the above poster, though, I’ll definitely keep this updated with everything we find. Hopefully there will be a solution.
-
So last night I tried to export with a video/audio mixdown that were both created to my local drive and it failed. I also tried to consolidate media to the local drive and export and that didn’t work either. The latter was at the suggestion of an Avid tech but I don’t understand why as you’d think that nothing would export if the media drives were the issue and this sequence clearly does when broken up. I will keep this ticket updated with everything we find.
-
For this particular full length sequence I have not. A co-worker created a video mixdown of one that was about 23:00:00 and giving the same error on Friday and nothing was fixed though. I hesitated to do it as I thought that if it exported the same sequence in 10 minute segments it should do the full thing. Also doing it same as source shouldn’t necessitate a mixdown right?
Honestly that’s my next step but the swing shift workers are in the office now and my test machine is being used for work. Hoping there’s something that wont mean double the export time for every output we create as we generally run about 8-9 hours of exports each night :\
-
First off, here’s the answers to your couple questions, hopefully that will clear up a couple things.
1. Yes, I did indeed mean SD ProRes Proxy
2. They were originally HD and were transcoded down to SD to minimize stress on our systems and to ease the burden of delivering ftg between editors/AEs etc.
Secondly, you recommend removing the basic motion and distort attributes. I am receiving these project files from different editors, and am not the one doing the actual cutting (I am the AE on this project.) My biggest fear in doing this is that I will accidentally remove a forced cut in or zoom for people that don’t use Pan Zoom Pro or a different plugin.
If I reconnect the HD clips to the SD timeline BEFORE copy and pasting it into the HD timeline, will that prevent the upscaling and, theoretically, bring everything up in the right size?