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

Red Alert 3.4.8 bug - "Renumber"

Peter Majtan

Well-known member
Joined
Feb 29, 2008
Messages
3,986
Reaction score
0
Points
36
Location
Tokyo, Japan
Website
www.petermajtan.com
I have been processing footage from stereo (3D) shoot on two cameras. Since we have not used remote trigger to simultaneously start/stop the recording we had almost always few frames offset between the two cameras (but I did manage twice to press the buttons at the exact same time - at 36 FPS! :) ). While rendering out the sequences in Red Alert (3.4.8) I noticed a small bug. While positive "Renumber" works as predicted - there is problem with negative offset. When I put negative number, the first 7 frames are adjusted as expected, but from then on all consecutive frames have their original values...

Lets say I start rendering sequence 755~1456 and I will get the following sequential numbers with "Renumber" set to "-744"

1,2,3,4,5,6,7,763,764,765...

I suspect the 7 frames has something to do with my preference to use 7 out of my 8 CPU's...

Any clues?
 
Sorry, it was never intended to work with negative numbers.
This is for dpx/tiff, correct?
 
Yes Deanan, I have been rendering out the TIFFs from the Foundry Stereo Shoot - they need it for IBC...

I hope You can see why it would be useful to work with negative values. Even in non-stereo situations. This will allow me to pick any starting frame in my shot and export it from No. 1... :)

Thanks

Peter
 
Renumbering is absolute so if you want to render #744 as #1 then use 1 as the renumber value intead of -744. Choosing -744 should really mean -744 but then you can get strange results (it's untested) and negative frame numbers can cause problems in other programs.
 
That is not the way it works for me. When I put "1" it simply adds "1" to my current frame number. So rendering sequence from 744 with "Renumber" value of "10" will start outputting TIFF's from 754 onwards... I f we could make it absolute - that will be great as well - I am happy either way as far as I can start my sequences from lower number then the current frame... :)
 
Oops, RL works as absolute but RA is relative. Both should be absolute so I've changed RA to be abs in the next version. If you want absolute out of RA directly, use render in terminal for now.
 
Ah, thanks Deanan for that explanation. It makes sense now. This renumbering error in RA was driving me nuts a while back before we got redline farmed and doing the hard work. I gave up on trying to make sense of it and used a command line app to renumber clips after rendering. Nice to know it will be fixed.

cheers
Chris
 
As soon as audio is ready. If you need a temp build, email me.
 
Can someone explain this renumber feature?
 
Back
Top