Jeff Franklin
Forum Replies Created
-
Couple of other tips:
Export your clip out to the desktop (or RAID etc) Then take that clip to Compressor. Trying to send it to compressor from FCP or Motion generally does not work.
Also try this app to clean up compressor and Qmaster problems: https://www.digitalrebellion.com/compressor_repair.htm
-
Try using fewer instances. Leave a couple free for the OS and the apps to use.
-
The software will be $15k + $2k maintenance agreement. It will require a Kona 3 card. Not sure about storage – a very fast RAID and Fibre Channel card would be the norm here. Also not sure if the system will require a GIVO type of card for video monitoring like the current Linux based Autodesk systems do. As others mentioned Autodesk tends to certify every single part including ram and the monitors (right now they like Eizo monitors which are pricey but really, really good). I did hear that the software will work seamlessly with the various Apple codecs including ProRes. It will also be able to handle Red, but I have no details on that.
The software, MacPro, RAID, monitor, tablet, ram, FB card, graphics card, 4 port NIC and few other incidental items makes a grand total of ~ $40k. That would be if you bought everything yourself. I doubt that’s how it will work. You will buy everything from Autodesk and the price will most likely be closer to $50K.
-
“Does Qmaster work?”
I would say only when it feels like it.
-
Same issue. I got closer than I ever have before with the cluster controller on the same computer with Compressor. The Xserve has just service running. This seemed to work tantalizingly well – ripping through a huge uncompressed HD file transcoding to H264. Then, it failed right near the end with the “shared storage client timed out” error. I have been getting this error regardless of how I configure the cluster/controller/compressor puzzle. NFS is running, volumes are mounted, services are running.
Qmaster would be a big help to our machine room staff for doing these kinds of compressions. If only it worked.
Apple.
-
One of my editors just told me that his system has been giving him problems since we did the Ver 7 driver update. He is running FCP 6 on a MacPro with Kona 3. He has been seeing dropped frame errors and had layoffs be 1 frame off to HDCAM. I’m going to roll him back and see what happens.
-
Did anyone ever find a resolution to this problem? I just rebuilt the system drive on our old G5 Dual 2.5 system with Kona 2 – OS X 10.5.8 and FCS 2. Went ahead and tried the 6.0.3 Kona update and it still has this issue of not stopping the digitize at the outpoint. This is a totally clean install – no legacy stuff from the old drive. Did not use the Migration Assistant.
Guess I’m headed back to 5.1! This is silly.
-
Double true that! Exact same issue here, same solution – 5.1 downgrade. Has anyone mentioned this to AJA?