better understanding GV job monitor

[nath]

Am I understanding this new GV job monitor render process correctly that when sending something to be rendered it is like executing the render within the state that the timeline is in, even without first saving anything?

So technically I could go on modifying my timeline without messing up my render; even turning on or off channels?

The reason I am asking is that I have bin experiencing some unpredictable behaviors on the audio side.

[antonsvideo]

once you see that the export has started in job monitor with the progress bar, you could change anything in the timeline or even close EDIUS and it will finish the export

however, I am not sure if it can be fully trusted?

[nath]

"... not sure if it can be fully trusted?"

Thant is the part I was wondering about.

[GrassValley_PS]

Once the job is cached for the export you should be able to do that. However, not many people use that workflow (I know I am going to a different/new sequence). So I think we just need a few people to try this and report back.

[kpot]

Once the job is cached for the export you should be able to do that. However, not many people use that workflow (I know I am going to a different/new sequence). So I think we just need a few people to try this and report back.

Hi:

"once you see that the export has started in job monitor with the progress bar, you could change anything in the timeline or even close EDIUS and it will finish the export

however, I am not sure if it can be fully trusted?" (Anton).

- The blue marked part of the above sentence works fine at me.

- I still have to test the orange marked part of the sentence.
kurt

[GrassValley_PS]

Thanks. I think there is no doubt you can close EDIUS and the JM will stay open and complete the export. They are pretty much independent at that point. The question would be exporting and going back to the same timeline to are further edits.

[nath]

So far I can attest that Edius and GV Job Monitor work completely independent. I have been switching projects, even closing Edius, without any problems with jobs in the queue. Even hibernating your system works.

I sometimes find myself working on different export versions without saving between versions, while layering things in my timeline. I just need to make double sure to have it all ready to go, when sending it from my batch list to the GV Job Monitor queue.

The way I now look at it is that as soon the export is sent to the queue one is free to do anything in Edius without messing up the queued job.

The job is based on the timeline state it is in, a "snap-shot" of sort, when the job is sent to the queue.


This is how a typical timeline looks for me. I use the orange markers to keep track of where my files start and end. And I use MacroGenerator Pro to compile my batch export list. A simple Ctrl+(.) is all I need to press to start my macro, which sends segments to the batch list. Once in the batch list I reuse that list over and over, always sending the files to that same landing-folder. (Too bad Edius does not have a way to batch-change the destination folder...)




Render steps:
Layer 1-2 dead pixel correction.
Layer 3 vignetting correction, mirroring and centering of image.
Layer 4 image stabilization, sharpening, color grading.
Layer 5 Neat Video debris reduction and final cropping.

Unfortunately each of these layers/steps requires a separate rendering... would be nice if one could do it without in-between rendering.
This Edius X update saves me so much time now, no need to switch to another workstation!