watchfolder and luminancelevels

[Steve Roberts]

Does this help?

Chris_Meyer said on Jul 9, 2007 at 11:05 AM :
A gotcha to watch out for with multimachine renders: Some codecs (such as
some generations of the Avid and Aurora codecs) had a switch, set either in
their format options or through a separate control panel, on whether or not
they expand the 16-235 internal luminance range of a video stream to
0-255 when they hand files off to an application such as After Effects. Make
sure this is set the same on all computers involved in a network render with
these source, or otherwise different computer may input the source with
different visual contrast.

[Frank Feijen]

As far as i can tell, i can only set this “switch” when exporting my footage from avid to QT-same-as-source. Or when interpreting my footage in ae. But since the different computers use the same project to render, they should all use the same settings within ae, or not?

[Steve Roberts]

It might be something in the AE Prefs, which is independent of the project. Different machines running the same project may have different prefs.

It’s hard for me to say for sure — I don’t have first-hand info on this. Maybe Googling would help, or you could go to cybmotion.com and write Chris Meyer himself.

[Nel Johnson]

Hey Frank, I had the same problem very recently. Might be worth checking the thread.

https://forums.creativecow.net/readpost/2/927308

Basically it turned out that I was rendering JPG sequences with unmanaged colour spaces, meaning that each rendering station was imposing it’s own colour profile into each file it was rendering. Hence the flicker you are probably witnessing when you pull the sequences back in.

The solution is to make sure that the initiating machine has set a colour space for the project. I quote Darby “The working space is defined in the Project Settings of the project.”