Guillaume Cottin
Forum Replies Created
-
This is incorrect. From Arri’s website:
“Apple specifies that ProRes should be legal range. Our tests have shown that an extended range ProRes file can result in clipping in some Apple programs. However, the difference between legal and extended coding are essentially academic, and will not have any effect on any real world images.”
ProRes codecs CAN contain extended range data (some external recorders like the KiPro do it), but legal range is always the expected setting. In this regard, Arri respects Apple’s specifications.
Resolve 10 misinterprets ProRes 4444 footage. -
Yes. All ProRes codecs are by definition Legal range, including Log-C ProRes 4444.
I have also seen that Resolve handles the levels incorrectly, resulting in the Arri LogC to 709 LUT to produce lifted blacks. -
Oh and : Can I use my standard GeForce 8800GT as a helper card instead of the (apparently less powerful) GT120 ?
-
Hi everyone,
I also have a Mac Pro 2,1 with 16GB ram and an Nvidia 8800GT. I work on OSX 10.6.8 to ensure compatibility with Final Cut Pro 7, and use Resolve 9.
I am very interested in the GT120 + GTX 285 GPU solution for Resolve. How fast is it ?
Could someone explain how it works exactly ? Do you just put the cards in the right slots and it works ?
I know the first card, the EFI32 GT120, is only used to have the other card (GTX285 -or any other ??) EFI64 card work…Does the more powerful card have to be in a slower slot ?
Is there any specific software to use to make it work ?
Is it still possible to expand with a Cubix PCI-E expansion box with this configuration ?Sorry for asking so many questions at the same time!! 🙂
Cheers,
-
Yup. Dunno what else to say.
I also was certain that there were no corrupt files in the folder, but as it turned out, there was one corrupt file out of 630+, and that was enough to mess everything up.
Are your files ProRes LT? I’ve heard somewhere that LT has issues with Resolve.
Did you try to import a few files into Compressor and “recompress” into the same .mov format? (this adds a generation so it would be only for troubleshooting purposes)
Did you try to remove all accentuation and spaces from the path to your files?This QTDecoder issue can be a real pain.
G.
-
Hi everyone,
I had the same problem and contacted Blackmagic’s technical support and they were very supportive.
DaVinci does use the system’s QuickTime engine, but in my case, we found that the issue was due to a corrupted video (.mov) file inside one of my directories. It appears that when you open a folder in Resolve, the software scans all the files inside that directory, and if it finds a corrupted file, QTD stops working -without telling you what precise file caused the issue.
Look for corrupted or unsopported media files in your directories, put them somewhere else and let me know if it helped.
Best,
G.
-
Hi,
Thank you for your answers.
I don’t think the Mac Pro is the bottleneck. It’s old for sure, but I have 8 cores and 16 Gb of RAM that DaVinci doesn’t even use. DaVinci is the bottleneck, because it only uses GPUs, barley the CPU and RAM.In comparaison, when Premiere Pro CS6 (which is really an optimized software), can play a Red R3D in real time (1/2 resolution), with color correction filters applied to it, DaVinci comes and can barely play 1080p ProRes in real time without filters.
Apple limits the software to make us think we need to upgrade. In my case, with a 2.1 Mac Pro, I can’t use the latest GPUs on my system because 10.6.8 doesn’t support them, and if I need the drivers I need Mountain Lion but then, I can’t install Mountain Lion on my computer (because for some obscure reason, the latest version of OSX that is compatible with the 2.1 is Lion). Purely software limitation. I spent $$$ on processors and memory that are not even used, the latest graphics card can work perfectly on my computer but I can’t use them, and then I am told to upgrade my hardware whereas DaVinci doesn’t even use 30% of my computer’s actual processing power.
Bottom line: I ever upgrade, it will be to a PC.Anyway guys, I’m glad to know the GTX570 will not work well. For now, I found that the combination of a GTX285 and a GT120 apparently gives the best results for a 2.1 Mac Pro computer, as seen here :
https://forums.creativecow.net/thread/277/11244
But these two cards need a flashed ROM and that’s hard to find as hell!
Best,
G.C.
-
Hey guys,
I am having the exact same error on my Mac Pro 2.1, OSX 10.6.8, with Resolve 9.0.3. , with ProRes 422 progressive clips from a Ki Pro Mini. Video becomes black when I try to import more than, say, 10 clips, or when I browse folders. But if I don’t import and just try to grade the clips I’ve imported, it works fine…
I don’t get this error with MPEG2 422 MXF footage.
At first I thought I should upgrade to OSX Lion, but now as I read this thread, I tend to think it’s not related to the OS or even the hardware since PC users and Mac users with various graphics cards get the same error.Does anyone have a solution ?
WA