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

Glitch in my EPIC?

Jon Jones

Well-known member
Joined
Nov 5, 2011
Messages
910
Reaction score
0
Points
0
Age
48
Location
Puerto Escondido, Oaxaca, Mexico
Website
jonivyfilms.com
I noticed that on the last shoot I did my EPIC which we primarily shot at 48fps-96fps acted like we were shooting at 12fps. The footage plays back really fast, even though it's supposed to be high frame rate. This has happened on one shoot with my SCARLET when I first got it, and I have no idea why.

Has anyone else experienced this same anomaly?
 
If your project base frame rate is high fps like 60 then shooting at 96fps for 1sec will play back at about 1 1/2seconds so it will be fast but slower than real life, so your project frame rate might need lowering, if that is not the problem then seek advice from RED.
 
Can you adjust timebase after the .r3d is recorded, or would you have to do in the timeline of NLE.

If you're shooting at 48fps, and your timebase is 48fps, it'll playback at regular speed with half the motion blur and a lot more smoothness than 24fps (less "film look")... It would look "fast" compared to 24fps at 1/48th shutter because of how smooth it is. Usually you want to set your timebase to be 24fps, that way playback will be slowed down from whatever framerate you were recording at.
 
If its looking super fast as in even faster than real time, could it be that the project timebase was changed to 48and the sensor FPS was left at 24?
 
It all depends on if the frames are there or not. Load the clips into RCX, and look at the META tab and it will tell you exactly what you need to know. Project frame rate and Sensor frame rate is what you are looking for. Also, if you have access to Primiere, just drop an r3d in the timeline and see how it plays back, just make sure you have the res dropped to 1/4 or lower so that it will play in real time:)

The camera will play it back the way it was set to, so if you were shooting 96fps on a project frame rate of 24, the camera will play back as slow mo. What I haven't tried is to then change the project rate of the camera to see if it will change the playback speed of the clip, or if it will only playback using the metadata that's embedded in the clip. Something to tinker with tomorrow.

Matt
 
I'm not sure I like the way new firmware interface is laid out on the Redmote. (3.3. )
Sensor FPS and project FPS are right next to each other and when you shoot 24 they both read 23.98
Its easy to make the mistake of altering the time base instead of sensor fps after a long day on set. Never happened to me but I've seen more than one thread here recently with this same problem.
I don't see the need to alter the project time base on the fly, I would be happy for this feature to be buried in the menus.
This is kind of stuff you set up during the prep, not on the set.

Just my 2 Dinars.
 
You can move the Sensor and Project slots around to suit your needs, I believe, so you can hide them to suit your needs. Just put the redmote in LOCAL mode, navigate to the slot, select SETUP->SETUP SLOT and choose what you want there. Quite handy, I think. I just wish updating the firmware didn't wipe out my slot assignments.

matt
 
Back
Top