Alan Gordon
Forum Replies Created
-
I had the same issue with some QT files. I had a project with both H264 and ProRes4444. If I imported only the h264 they worked fine or only the prores, they worked fine, but if I imported them both, QT would crash. I solved the problem by converting the h264 to prores. Though a true fix to this would be good.
-
Third. Also more blur for keys.
-
I just built a system around the Z9 PE-D8 WS. And dual 2670 2.6GHZ processors. And as of yet I can only get 1/2 premium at real-time in Resolve. The 2620 is slower than that so 1/2 good may be the all you can get and maybe not even that. Davinci uses 8 cores for DPDecode, which appears to do the decode, so I don’t even think it’s leveraging full 16 cores. I think you need the dual 2787w 3.1Ghz processors to get full debayer real time.
The 1650 can only be used in single cpu systems and therefor is NOT a good match for the motherboards you list. If you use it, you lose HALF of the RAM and PCI-e capacity. If you went 6 core high clock route, go with the i7 CPUs and maybe overclock.
The Asus board is very well designed, but I have been having some boot issues. Also, 16 RAM DIMMS would have been nice as well.
I recommend at least 32GB RAM for Davinci as V9 can use quite a bit being 64bit. And you also want to have it spread over 4 DIMMS on a single CPU system or 8 DIMMS on a dual cpu system.
Watercooling is not really necessary with Xeons except maybe the 2780w because they are relatively low TDP.
I also went with a 256GB SSD, but I’m wishing I had gotten at 512. Or Dual 256. With all the caching that Premiere and After Effects do, I run out of space quickly.
-
This usually works for me when I’m not having a really weird bug that interprets the timecode from Premiere wrong:
Prep your sequence for color.
Create a new PP project with ONLY that one sequence.
Export XML.
Import XML to DaVinci. Select Import Automatically AND Ignore Extension.
DaVinci will ask where the media is–Point DaVinci to the folder that has the high quality files.
This seems to work with most projects.
Cheers,
-AG -
Okay so that clears up why DNXHD doesn’t work with those apps, they don’t have support for 444.
Now I really hope I can figure out why the XML won’t work from my windows machine. I should do a test this week rendering uncompressed QT files and see if that makes any difference for the XML. I’d rather not move to an uncompressed workflow. Most of my clients have no need and in fact don’t want uncompressed deliverables.
-
Interesting, I just noticed that the issue in 5.5 may be contained to DNXHD 444 I just tested it with DNXHD 36 and it looked fine.
This is what DNXHD 444 looks like in premiere 5.5:
And while playing back:
Obviously though, for workflow, I’m much more concerned about the broken fcpxml workflow. I had hoped that it would be easy enough to get clients to install the DNXHD codec on their machine and I would be able to continue just as I was when delivering prores. Now it seems that may not be the case.
-
No, I’m not. The files import into all those applications, the video is just very messed up, I’ll try to get a screenshot probably by tomorrow.
-
I haven’t even completely finished building my new PC rig (1 CPU, half of the RAM, and the decklink card are still not installed) but I decided I needed to put Davinci through its paces.
This rig at the moment is a single 8 Core Sandybridge E5 2670, 32GB of RAM, and a 4GB OC GTX 680 for both GUI and GPU.
Standard Candle results are as follows:
2, 4, 6 nodes of blur: 24fps
12 nodes of blur: 15 fps
NR 4: 24fps
NR 3: 24fps
NR 2: 12fps
NR 1: 3.5These results are remarkably similar to the single GPU test WITH a dedicated GUI card. I think the days of a dedicated GUI card may be over.
-
I think Color Trace should help with this issue. It should apply the correct grade based on timecode. Or you can do it in manual mode.
Cheers,
-AG -
Any results from the tests? I’m looking to do something similar.
Cheers,
-Alan
