How to write out current frame range?

[ThinkingPicture]

OK, so I have a write node which I hit with an F7 which brings up the frame range to write out. It appears that this frame range defaults to the last frame range that was written??? Is it possible to have this frame range load up automatically with the current frame range I am working with? I can only suspect this can be adjusted in the prefs? But where?

Thanks in advance for any help.

Grant

[Diogo Girondi]

That prompt get it's value from whatever is set in the Project Settings, so "s" is your answer.

[ThinkingPicture]

Yeah, I thought it would be there - thanks. Is there a way to auto detect the frames once a file has been read? In Shake we would press the "Home" button and the timeline would be set to the filein's frame range and all flipbooks would also come up with that frame range as default.

Just trying to figure out how it would be similar....

thaNKS

[Diogo Girondi]

It should automatically inherit the frame range from the first file sequence that you read, if it doesn't you will have to set it manually in the Project Settings.

So a tip would be to always load the longest sequence first, or the one that has the the correct frame range for the project, otherwise you will have to manually edit that later.

But if all you want is the current frame range from your pipe in the viewer, just set the viewer in v5 to input and it should do it. Note that this won't change render range since it's value comes from the project settings.

[ThinkingPicture]

OK, thanks for that Diogo. It makes sense. I think my problem here is the actually naming convention of the files (179867 - 179923 for eg.) which doesn't make life any easier. Guess I'll have to batch rename these files and then frame ranges will be a lot easier to do manually.

all the best

grant

[Diogo Girondi]

Well, it should work nonetheless.

Be aware that changing stuff like that can have a negative impact on other parts of the pipeline. If you guys use that padding as a meta data at the conform stages or whatever would be better to keep it unchanged throughout the entire post stages.

We had instances in the past where the client did a telecine of the entire reels without any TC in the file header, so we had to keep the padding intact from in to out, so Scratch could use the padding to do the conform correctly.

But case it doesn't impact anything you should change it for sake of simplicity and readability.