Charles Haine
Forum Replies Created
-
Just tried 4.0.19 and 4.1.29 and I no longer get the error message, but playback is 2.5-6fps.
Weird, right?
-
Cubix support has been incredibly helpful, and it doesn’t appear to be the Cubix causing the issue. We still haven’t found out precisely what it is, but Cubix it is not.
thanks for all the advice, trying the cards one at a time in the Cubix definitely helped us determine what it’s not, which is a step on the process to figuring out what it is.
Charles
-
Thanks, I gave that a shot and it crashed again (no cards in the box at all). It took longer to crash (1 hour into a 2 hour render instead of 5-8 minutes in), but it still totally crashes.
So, it’s a bad Cubix; thanks!
-
Are you on a 12-core? The 12-cores seem to have this issue more than others.
But we have tried the 32bit boot and it didn’t seem to run differently than 64 bit, so we just leave it in 64bit mode.
Thanks though,
Charles -
Blackmagic Decklink 3D Extreme (though we’ve had the problems without the card in), dual drive internal RAID, we built the system, Kona tests come back OK.
HOWEVER, we might have found the culprit.
In desperation we tried just taking out the old (factory) RAM. We had the problem when it was just the factory RAM (so it wasn’t a mixing problem), and the place we bought it from told us they swapped out the RAM when we sent it back in to find out if they could find the problem.
After an hour without the old RAM, everything is working normally. Funny, the memory tester and rember didn’t find anything wrong.
Man, thanks for the quick replies, I’ll let folks know if this ends up being the long term solution or not.
Ch:H
-
Wish it were that simple 🙂
It happens on EVERY project. Projects with nothing but RED footage transcoded to ProResLT (1080) slow down, projects with da vinci or color renders (ProRes 422HQ) slow down, all with the sequence set correctly.
I know, it seems like we have a gremlin somewhere in there, a 4K Motion Jpeg or something eating our lunch, but none that we can find, no matter how many projects we do on it.
Unless it’s a problem with ProRes?
-
Oh, a few more things that I forgot to mention.
1. Our audio meters disappeared for like 6 months. Tried re-installing FCP, and it still didn’t work.
2. The whole system got strange recently (Quicktime 7 couldn’t open files, blackmagic couldn’t play out of FCP, etc) so we wiped the install hard drive (doing the “write 0’s” method), and did a fresh Snow Leopard install and then a fresh FCP install.
-for reference for those thinking of doing this who have internal RAID drives, they survived the wiping of the boot drive. took me a lot of research to confirm this before we did it.
3. Doing the clean install, everything is back to normal (audio meters! video out from FCP!), except FCP is still getting sluggish.
Any help would be much appreciated.
thank you
Charles Haine -
-
The other big question, of course, is are you planning on finishing in ProRes at all?
I used SCRATCH on a feature this year and really dug it, but Da Vinci writes ProRes natively (saved us a transcode step, and the included gamma shift that came with it), and it’s interface is far, far easier to use than SCRATCH.
And the tracker blow’s scratches out of the water.
So, if ProRes is part of your workflow, then it’s Da Vinci all the way.
-
As recently as just a few years ago eFilm was grading in 720p then rendering in 2K on film-out jobs.
Desktop Resolve does a great job of playing back 4K RED files (with a RED Rocket, of course) via Decklink over 1080p even with a few nodes stacked up (depends on your GPUs, of course). Then, render whatever you want (DPX, ProRes, up to 4K) which is a pretty standard workflow.