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 :)

Redcine render errors

Joined
Apr 21, 2007
Messages
15
Reaction score
0
Points
0
Website
www.amfmstudios.com
Hi,

I'm so completely a novice to all of this, hell to using forums even so forgive me if this is an easy answer, I just can't seem to find anyone with the problem on the forum.

I can only seem to render out quicktime prores files out of redcine. I tried DPX and i tried TIFF and both give me the error that the files could not be rendered.

I've tried DPX at 10 bit (my only option) and I've tried tif at 8,16, and 32 bit.

The reason I'm doing this is I exported the quicktime prores for After effects to do some greenscreen stuff and I keep getting this weird speckle pattern of black dots across my image and I was wondering if it was just After effects not liking the prores file.

Just wondering if there was something I was missing.

Thanks!
 
Hello,

One issue could be the naming of the files you are creating, which is specified in the "output path" box under the "OUTPUT" tab.

Being frame based, a DPX or TIFF sequence needs to generate a new file name for each frame, and you need to tell REDCINE how to do that.

In the output path, type something like "EVENT#Z\#F_#06.E" (no quotes)

This will create a new folder for each shot, for example "EVENT001" then within that will create a dpx or tif sequence, named as the original R3D file with an "_" followed by a six digit counter to represent the frame number, thus making each frame unique.

Hope that helps
 
David, could you elaborate on the naming of the file a bit more. I'm used to rendering image sequences, but not with the strict guidelines this seems to have.

Obviously I was having the same problems Chris was! Thanks!
 
David, could you elaborate on the naming of the file a bit more. I'm used to rendering image sequences, but not with the strict guidelines this seems to have.

Obviously I was having the same problems Chris was! Thanks!

One problem I have experienced happens when you enter a filename, such as "myImageSequence" into the output path and filename box when rendering image sequences. REDCine takes you at your word, so it renders the first frame as "myImageSequence" and then renders the second frame as "myImageSequence", thus overwriting the 1st frame. This at best leaves you with one frame after a lot of rendering or can also throw errors as it over writes.

Have a look at the release docs on the support page at red.com for naming variables (under the release history of redcine). The one I suggested above "EVENT#Z\#F_#06.E" means...

"EVENT" can be anything, its just a name.

"#Z" is replaced by the event number, 001 for the first shot in the timeline etc

"\" makes REDCine create a directory from what preceeded it - so in this case
it will create directories for each shot "EVENT001", "EVENT002" etc

"#F" is replaced by the original r3d file name

"_" I just added that as a seperator to the file name

"#06" means add a 6 digit count to the file name - this is what prevents over writing because it's a counting frame number

".E" means to add the default extension for the file ".dpx", ".tif" etc

So the above render would create a new folder for each shot on the redcine timeline called "EVENT001", "EVENT002" etc. Then each of those folders will contain (for example) dpx sequences that are named as the original red file such as "A001_C001_081005_000000.dpx", "A001_C001_081005_000001.dpx" etc.

One interesting bug is that strictly speaking "#F\" should create a directory named as the original red file. For DPX conforms, this is one normal standard as to where to hold the reel name - i.e. in the folder name, and this would match where the EDL, XML or AAF specifies the original red file name. However, for some reason, this doesn't work. It doesn't create a directory named as expected. We found that our Mistika systems don't care, because they are happy to find the reel name in the dpx file name, but our eQ's and Smokes need to have the directories renamed to match the reel name.

DC
 
Back
Top