Qmaster - Move Operation Did Not Succeed

[user_deleted]

Hi!

Trying to get Qmaster working but having some issues. The closest I have is ending up with "move operation did not succeed" and a file that contains the last 10 frames..

Well, my setup. Tried different things but right now I have 2 machines, 1 is running Shake and the other one is running a QuickCluster. Only thing I have done with the Quickcluster setup is that I have changed the cluster storage to a different local drive.

On the Shake machine I have the script with all the files in a folder on a mediadrive that is read/write for everyone that wants it - this drive is mounted on the Quickcluster. The only naming convention for the mediafile paths that work in the script is /Volume/mediadrive/path to files. The file out node is also pointing to the same folder on the shared drive.

So, well, when I submitt the batch to the QuickCluster it starts working but complains about "move operation did not succeed". The test script is 30 frames and it splits that up on to 3x10 threads. I end up with a file that includes the last 10 frames..

Any1 got any ideas?

Thanks,

Lars Petter

[user_deleted]

are you trying to make a quicktime? at least up thru 3.5 you couldn't use qmaster to make qts since it has to eventually reassemble it all into a single file. don't know if that was addressed in 4.

[user_deleted]

Yes, I was doing QT and what happens is that it overwrites each file when it is finished with parts of it. That is, as I mentioned that it renders in group of 10 frames.

I tried changing to targa to render out a targa sequence instead but same thing happens, it actually overwrites each file and I end up with 1 file of the last frame. The target is set in the script as a file out node. I must be doing something fundamentally wrong here? Why does it overwrite the file instead of making a sequence of targa files?

LP

[user_deleted]

pardon me for asking, but did you include a sequencial symbol in your filename?

like: /path/to/myFileOut.#.tga

i'll try to set up a Qmaster render myself soon, i'll let you know if i have similair issues.
++ christoph ++

[user_deleted]

have to agree with zem, sounds like you didn't provide for a sequence and were just overwriting the same file - which would make sense if you were trying to write a quicktime before and forgot to change the output name to accomodate a sequence.

anyone know if they're planning on adding the ability to make quicktimes to qmaster clusters?

[deke-kincaid]

QUOTE(deepstructure @ 02/09/06, 11:38 AM) [snapback]227936[/snapback]
anyone know if they're planning on adding the ability to make quicktimes to qmaster clusters?
Compressor does this and you can net render through FCP with the "export to compressor" option. So maybe this will be added to a future version of shake.

Personally I prefer to work with all frames though. Much faster and less issues.

[user_deleted]

QUOTE(beaker @ 02/09/06, 11:44 AM) [snapback]227937[/snapback]
Personally I prefer to work with all frames though. Much faster and less issues.

i absolutely agree. i work predominantly with 2k cineon frames. however, we increasingly have a need to create quicktimes of our sequences - either for editorial or director review, etc. and i've been using shake for this as it allows me to add burn-ins, down-rez, etc., and because of it's command line, is scriptable in a unix shell. so i was disappointed when i found out i couldn't utilize my render farm (at least not thru qmaster) for this process.

i am able to essentially do the same thing using csh scripting, it's just a bit of work on my part to parse out the list of directories to my five render nodes. each machine just cranks out one qt at a time, instead of all five cranking out one in a fifth of the time.

with a batch of quicktimes with no immediate delivery need, this is fine - but if i've got a 3000x sequence i need to create a quicktime of right now, it would be nicer to be able to assign all five machines to work on it rather than only be able to have one machine do all the work (and take an exponentially greater amount of time).

im sure this is simply using the wrong tool for the job. i've been looking at iridas' sequence publisher. it seems like a good option givent that it's batchable, scriptable, stampable, etc.

[deke-kincaid]

Why bother with sequence publisher when you already own shake? Render to a sequence and then have qmaster spawn another script that makes a qt movie but only renders it on one machine.

[user_deleted]

QUOTE(beaker @ 02/10/06, 01:48 PM) [snapback]228054[/snapback]
Why bother with sequence publisher when you already own shake? Render to a sequence and then have qmaster spawn another script that makes a qt movie but only renders it on one machine.

that's even more work than im already doing. right now i have scripts that will take a list of directories, grab the frames from those directories and make quicktimes from them. so i simply have multiple copies of this script with different lists of directories and each machine runs their own version of the script.

i mentioned sequence publisher because besides also being a dedicated tool that others could use, i thought it might have distributed rendering capability.

[deke-kincaid]

QUOTE(deepstructure @ 02/10/06, 04:03 PM) [snapback]228061[/snapback]
i mentioned sequence publisher because besides also being a dedicated tool that others could use, i thought it might have distributed rendering capability.
I don't know of many packages that will net render movie files besides qmaster/compressor/fcp. There are a few standalone distributed mpeg 2 encoders, but that is about it.

Seq publisher looks pretty cool, they have a full demo for download on the site, check it out. If this is for an I/O person or one dedicated machine then great, just that iridas doesn't have floating licenses of their software which is really annoying.