Compressor and QMaster screwed up

[Rafael Amador]

Hy Kiler,
Try cleaning the “History window” if there is any thing there.
rafael

http://www.nagavideo.com

[Andrew Wilson]

I assume you’re using compressor on a self-contained QT file (or a reference movie) and not using the “Send To Compressor” Feature of FCP.

Maybe I should have put “Feature” in quote marks instead because I’ve never had the “Share” or “Send To…” commands work well.

Andrew Wilson
WestView Digital Video & Design
http://www.westviewdigital.com

[Paul Jay]

What kind of FCP sequence?
Did you export quicktime movie with current settings before opening in Compressor?
It shouldn’t take this long. Even without Qmaster clustering.

[Kyler Boudreau]

Thanks for the feedback – I did in fact export the QT file before bringing into Compressor.

Honestly…I’m loving the new Mac, but on two new Snow Leopard Macs in the last year I’ve seen this happen. They come perfect from the Apple Store, you install FCP and things work for a bit, and then Compressor and QMaster have this odd falling out, and at this point the only way I can get it to work again is to reinstall everything.

If I dump the QT file into compressor and then look at system info, it isn’t spreading it out. All of the QMaster tasks sit at 0.0 – completely idle.

Rafael – I did clear out the QMaster files.

Type of sequence? Apple ProRez.

Does it happen on more than one sequence/quicktime file? Yes.

_______________________
kyler boudreau
http://www.theatereleven.com
ph.310.425.2231

[Mark Spano]

Simple solution for me is always this:

Go to Compressor.
Click here:

Tell it to Reset and cancel jobs

Wait a minute.

Then send your batch.

Clears up the problem every time (for me)…

[Kyler Boudreau]

Oh nice! I’ll try this….next time. Just reloaded the entire OS and feeding it FCP disks now.

Whatever.

But that’s cool – QMaster and Compressor seem a bit flaky, and if it is that simple, that would be SWEET.

_______________________
kyler boudreau
http://www.theatereleven.com
ph.310.425.2231

[Mark Spano]

Yes they can flake out from time to time. Mostly on systems that have multiple user accounts, I have found. Sometimes users submit batches and between the batch process and users logging in and out, QMaster gets confused. A job that is running will hang, or even sometimes a job will finish but still present itself to QMaster as ‘not done’. Then, no other jobs will be processed, or will have other issues. That command, to reset and cancel jobs, clears the QMaster queue for all users. At least that’s what I gather happens when I hit it.

[Rafael Amador]

Right.
This is why I suggested to clean the “History window” in Compressor (no the QMaster cue).
Some times jobs that get stopped, they try to relaunch their self if they are still on that “History window”.
Similar to what Mark points about the “Background processes”.
rafael

http://www.nagavideo.com