Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Proxies in Compressor

Dave French

Active member
Joined
Sep 27, 2007
Messages
35
Reaction score
0
Points
0
Are there different steps involved when using Compressor to render the QT proxies to ProRes as opposed to just rendering regular QT files to ProRes in Compressor? No problems using other QT's in Compressor but the red proxies always produce an error saying no audio or video detected and the render fails. All the latest versions of FCP, Leopard, Quicktime, RedCode codec, etc are installed.

Thanks
Dave
 
I had some luck using compressor with Wrapped QT clips made from L&T.
 
Thanks.

I'm just looking at creating ProRes from the Proxies. I don't want the extra step of having to create the wrapped QT's in L & T.

Dave
 
Thanks.

I want to distribute render this though over multiple CPU's. And a proxy through Comprossor seemed like the fastest way.
 
If I'm not mistaken, the new log and transfer will make ProRes pretty quickly. I think you can tie in a color space and ISO as well so it looks like a good option.
 
But can you distribute render the Log and Transfer process?
 
But can you distribute render the Log and Transfer process?

I don't think so, FCP rendering or export processing can be sent to Compressor with cluster settings, then Compressor actually use multiple FCP licenses on each clustered machine to do the Qmaster rendering, but not L&T.

Converting Proress in L&T is still slow to me (Wrapped QT is fast, I like it), so I'm on the same search to do easier ways to utilize Qmaster.

At least now, the way I described, sending compressor the wrapped QT would allow you to use the Qmaster. Including the support of applying the grading with RedAlert!. I'm pretty happy with that.
 
Thanks

We're trying to avoid the extra step of wrapping the Quicktime. Have had some success re-creating the proxies in Red Alert, so I think the problem lies with the proxy created in the camera. Still working on the distributed rendering part. Other normal quicktimes distribute fine but the proxy renders do not seem to be utilizing the full processing power of the CPU's.

Anyone else successfully have this working?
 
Back
Top