Eric Johnson
Forum Replies Created
-
I would like to point out that by not checking “unique file names” you are creating Finder level issues that result in the errors you described, at least in the case of things not reconnecting properly.
When you don’t create unique names, the first instance of a clip (lets say shot #5) will be overwritten by the second instance (shot #7). This will continue every time a new instance of the clip is rendered because the Finder/file system will not allow duplicate file names in the same directory.
It sounds to me like you rendered the first half of the show, either had an error or stopped down, then resumed your render after re-opening Resolve. When you do this, it is only making the XML for what you just rendered.
Try re-rendering just the front end with “Unique names”, export the XML, and cut the 2 timelines together.
-
not to be nit-picky, but 3TB drives are slower than 2TB, 1.5TB, 1TB and 500GB due platter size, platter density and sector size… they may be slower by an infinitesimal amount, yet they remain slower.
And there is, in my experience, a significant difference between compressed formats (be they lossy or lossless) and formats such as DPX which are more traditional uncompressed formats (though there are different “compression” schemes for DPX, TIFF, etc)
Some of those differences are where the computing is done (gpu/cpu), others would be the efficiency of the Decode of your source at a system level and then there is drive speed, drive throughput, caching and pretty much the sum of your total machine…
-
I can’t say for certain, but I don’t believe that the Mac Pro can power 2 GFX cards of that size… and there will absolutely be heat issues w/ 2 double width cards.
-
I don’t recall where it is in v9, I really just don’t know if it was moved or not…, but in v8 there is an option where you create the project settings that lets you set how far into a clip you are when jumping by cut. If you change this from 0 (head frame) it also effects your wipe frame.
I hope that helps… this post is unfortunately vague…
-
Colortrace will allow you to selectively drag and drop your previous grades. Though you will lose any dynamics that were made.
At least you did in v8 as I recall….
-
That looks like potential clipping…. If not, I believe I read on here a while back about throttling down the render speed (you can do that on the screen you set your renders on) and that stuff going away.
-
To add to what Josh is saying:
For single shot fix’s/replacements you don’t need to re-export the whole show every time, as long as you have Sequence TC that matches you can bring in the new clip and the DaVinci will ask to resolve “conflicts” based on TC, and then you just need to readjust your grade.
Also, if you lean towards this, the Preconform workflow yields great results in Pro Res and DNxHD workflows. To the point where if you didn’t tell the client, they wouldn’t know…. not that you would do that.
-
For a luma matte, you can load your clips in the viewer, change your view from RGB to ALPHA. You should see a B+W of what your alpha should be… and export.
I’m sure there are other ways. That’s the way I know of.
-
Since you are already Spending the time to conform your timeline to ProRes… after you flattened it, why not just export on QT and pre conform with the EDL?
Or is that what you’re doing and still getting the drift? If that’s the case, I would think that your issue is likely TC related, whether its DF/NDF or rate, I couldn’t say.
-
Instead of an xml w/ 3 layers for your versions, how about bringing the xml in 3x. Do your Primary grade so they all get done at once, then create your different looks in each timeline using versions…
Or for the sake of Quick looks to get an ok on direction, do your looks in the Track node and have your versions there…. That’s not the best way for deep work… but it could be a way for getting an idea quickly across…