Welcome to our community

Be a part of something great, join today!

Log in
  • 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 :)

25fps/24fps issue, where's it at?

D

Dylan Reeve

Well-known member
Joined
Oct 29, 2007
Messages
1,151
Reaction score
0
Points
0
Website
www.shotwrangler.com
Has any progress been made on this issue?

Is the framerate of 25fps clips being correctly read on load into REDCINE yet? I haven't had the opportunity to upgrade yet, and I can't find any mention of a fix yet.

If not - is it on the radar at RED? We poor PAL users get a real hard time as it is, it'd be nice if there was one less annoying hoop to jump though :)

(I won't inflict my 'PAL vs. Varicam' rant upon you all just at the moment, but I am feeling unloved down here in the 50Hz world).
 
http://www.reduser.net/forum/showthread.php?p=164880#post164880


Originally Posted by Nick Shaw View Post
Redcine certainly seems to be improving with each new version. However, one major issue which still has not been resolved is the frame-rate one. Not only does it show all clips from 25 or 29.97 fps projects as being 24 fps in the meta-data, but more importantly it reads the timecode as if it was 24 fps. This means the timecode is correct on the first frame of the clip, but rapidly slips out of sync, and you end up rendering out 30fps QuickTimes with 24 fps timecode for example. Red Alert does not do this, so is the only solution for non 24 fps projects. However this obviously means 4k 16x9 is not available.

This is a serious issue which needs to be fixed as a matter of urgency.

If I am missing something, and there is a way of getting this to work properly, can somebody please let me know!
Nick,

While this is investigated, there is a quite easy workaround.

In the Library, click on the bottom third of a clip. This pulls up a metadata window for the clip. Change the framerate to 25. Now go back to the Player and scrub source timecode, and you will see it count from :00 to :24.

Now go back and change that framerate to 24. Player will now count from :00 to :23.

Best,

Lucas
------
ASSIMILATE, Inc.
LA, CA, USA

_____________________________________________________________
 
yeah flame....this is what kevin says

In build 82 - import a bunch of 25fps clips to a 25 fps project - all clips import with 24 fps timebase - how do I change ALL clips at one time to 25 ???



Try creating a new Redcine project, save it, import your footage (using either "load all" or "load shot") once the footage is in the timeline try selecting each clip (one at a time) by swiping the timeline slider over it. Now change the Framerate in the Format Settings in the Project Tab to 25fps. You will have to do this for every shot just as you would to adjust the shot framing or color. It should keep the 25fps you specified for each shot upon processing. You can batch process all of your clips into separate folders by clicking the #6.E button in the Output Settings tab, then clicking the Separate Folders button. NOTE: Redcine does not like to write over existing files, either delete the previous output folder and/or set a new folder path to ensure you are seeing the changes you made and not a previous version. Let me know if this helps.
__________________
http://www.reduser.net/forum/showthread.php?t=8070
 
Not working still

Not working still

I am with Dylan on this one.

Open a fresh "empty" Redcine project. (by deleting the preferences in the library)
Set the Project Framerate to 25fps
Load all (or one) 25 FPS shot to the timeline.
The project setting remains 25FPS BUT....the edgecode on the clip only goes to 23 frames, the Metadata panel in the shot menu says its 24fps material and as far as I can tell the DPX sequence has 24fps code too. If you burn the code in you get 24 fps code even tho the camera footage is definitely 25 (plays back off the camera fine and in RedAlert.)

So I am stuck with using RedAlert which reports the TC correctly without issue. Trouble is I have 67 Clips to manually load and render before Monday pm when the offline guy wants to start.....Arghhhh. It would be far easier to load the lot into Redcine, hit render and walk away for a few hours.

So as Dylan says....Please fix this one guys.....each shot should be loaded onto the timeline in redcine with the correct metadata (fps, ISO, resolution etc) so that when rendered out to a DPX seq we actually get what was intended on the shoot. There could be a global "render the lot out in 2k (or 3 or 4 etc)" button no matter what the input res was...that would be nice...but when a clip is on the timeline it must be in the form described by the metadata. Otherwise a days shoot could take another whole day just to get the damn data out:)

Cheers

Michael
 
c4camera said:
So I am stuck with using RedAlert which reports the TC correctly without issue. Trouble is I have 67 Clips to manually load and render before Monday pm when the offline guy wants to start.....Arghhhh.
Click to expand...

Michael,

Find yourself a handy geek and get them to script up something with REDline (the RED Alert command line) should be relatively easy.

I don't have access to a Mac right now, so I can't test anything, but there's a few examples around... Try the script here for example - it should just require some option changes in the Redline command:
http://www.reduser.net/forum/showpost.php?p=163254&postcount=5

Good luck!

Cheers,
Dylan
 
The lastest redline spits out the full redline command to the clipboard (from the render window). You could use that to generate the look and then the script Dylan mentioned to go through all the clips and render them.
 
Thanks Dylan and Deanan....I can geek up a script so I'll try that.

For what its worth after 67 x 3 mouse clicks I now have Redcine rendering out a 2K seq of 116000 frames at 25FPS....It was shot 2K and it looks like its only going to take about 6 hours on the 8 core MacPro. Then I am going to try importing it all into Pablo and assembling from an EDL which I generated from the camera proxies in FCP....so we will see if the TC remains consistant thru the DPX seq.

Wouldn't normally do it this way but need to try a few other workflows. if this is cool all I need to do is dub out the rushes to tape( remember that stuff:) and then anyones normal offline/online favourite way should work no prob:)

All very well when you have a Pablo with enough storage.

Cheers

Michael
 
TC in the DPX files from RedAlert is Absolute/TOD timecode.
 
I'm still struggling with this - is there any sign of a solution to this that doesn't require clicking on every single clip 3-4 times. It's not fun with a couple of hundred clips.

I could just make a modification to the details in the XML file (changing 24 to 25) but that doesn't correct the start timecode (which makes the timecodes from REDCINE different to those from the Proxy files).
 
Crimson solution

Crimson solution

I have found that if you use Crimson to roundtrip to FCP, all these issues disappear. You can load a 25fps sequence into RedCine, leave the wrong metadata, render out the selected clips, and then the 24fps frame rate is ignored when pulled back into FCP as Crimson's roundtrip FCP xml file automatically gives it a 25 fps rate, as it is taking that info from the original FCP xml export.

It's not a fix for the RedCine bug, and won't help if you're not conforming on FCP, but if you are, it's a great workaround. Crimson is a brilliantly useful tool all round.

Chris
 
Thanks for the crimson round trip tip, but I need workflow for 4K 16/9 and you need to render first using redcine to be able to edit with fcp...

I've asked Assimilate why Scratch does not have this issue, while REDCINE has, and I've got the answear that they will look at it.
We really need this bug to be resolved as it is a real killer for lot of project.

thanks,
antoine.
 
Issue to the 24/25fps problem?

Issue to the 24/25fps problem?

Hi,

Try this one:
Open Compressor and enter your output settings.
Save them.
Load your shoots (proxy's ones, for example the H one is great)
You can load up to at least 50 shoots, maybe more, but I didn't go any further...
Rename them if you want.
Start the task.
Go rockclimbing or whatever.
When you'll come back, your shoots will be ready!
This procedure is approximatively 4 times faster than Redcine, the shoots are soundfull (so you don't have to extract the sound of the proxies via QT or anything else), and the timecode is correct, that means it fits with the source tc.

Hope this helps.

regards


Caroline
 
Caroline, the problem is that 4k 16:9 won't work in compressor. You still need redcine for that task.
 
Caroline said:
Load your shoots (proxy's ones, for example the H one is great)
You can load up to at least 50 shoots, maybe more, but I didn't go any further...
Click to expand...

Not helpful if I need to one-light due to incorrect camera metadata (of course, I could step through every R3D with REDALERT but that's a bit tedious)

EDIT:I have used this method to get audio out of 100+ shots.
 
You must log in or register to reply here.
Back
Top