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

5k @ 24 FPS with recode 12:1 Pleaze ?

My assumption is that the Red Dragon upgrade (more expensive for Scarlet owners) will have the frame rates you are wanting. This is why I went with Scarlet and not a RED One. Hopefully, we will find out a bit more about the new sensor at NAB.
 
:beatdeadhorse5::beatdeadhorse5::beatdeadhorse5::beatdeadhorse5::beatdeadhorse5::beatdeadhorse5::beatdeadhorse5::beatdeadhorse5::beatdeadhorse5::beatdeadhorse5::beatdeadhorse5::beatdeadhorse5::beatdeadhorse5::beatdeadhorse5::beatdeadhorse5::beatdeadhorse5::beatdeadhorse5::beatdeadhorse5::beatdeadhorse5:
 
I'm walking right into the pun of the above post, but I have to play Captain Obvious here and say that it looks like someone is beating a dead horse with this one...

On a side note, I don't know why, but I feel like I've seen someone shooting 5k at 24 fps on a Scarlet..I will look for the picture to prove it..I might be wrong. I probably am wrong..but I will look into it.
 
LMAO ... that emote is perty funny, i think i get the hint. My low cost but tricky work around will be:

1) go to motion control (aka stepper motors), break up the scene into 2 phases (one at 12 fps, another at 24 fps)
2) shoot at 12 fps at 5k for where i need the 1.3 crop
3) go to next stage in motion control (for the 24 fps steps)
4) shoot actor or something at 24 fps, looping back to start position (so this process can mask)
4) composite things back together

Really though, changing the sampling to allow 1.3 crop on the scarlet shouldn't be impossible.
 
Jeremiah Kuehne said:
On a side note, I don't know why, but I feel like I've seen someone shooting 5k at 24 fps on a Scarlet..I will look for the picture to prove it..I might be wrong. I probably am wrong..but I will look into it.
Click to expand...

It was 5k/24 playback (presumably left on the REDmag.)

PatrickFaith said:
LMAO ... that emote is perty funny, i think i get the hint. My low cost but tricky work around will be:

1) go to motion control (aka stepper motors), break up the scene into 2 phases (one at 12 fps, another at 24 fps)
2) shoot at 12 fps at 5k for where i need the 1.3 crop
3) go to next stage in motion control (for the 24 fps steps)
4) shoot actor or something at 24 fps, looping back to start position (so this process can mask)
4) composite things back together

Really though, changing the sampling to allow 1.3 crop on the scarlet shouldn't be impossible.
Click to expand...

Seems like a real pain in the buttocks; fine for short landscape type shots/videos, but definitely not a feature.

I think the only possible option would be a "5k" WS mode that uses the entire 1.3x width of the sensor (but crops the top and bottom to get to 2.4:1) and/or a "5k" Anamorphic mode, which uses the full height of the 1.3x sensor (but crops the sides to 4:3, which is than de-squeezed to 2.4:1 when used with anamorphic lenses). Both of those modes should be well within the pixel throughput of the Scarlet, and hence should be doable, however neither mode uses the full 14mp MX.... it'd still be ~8-9mp (like 4k), but instead of a 1.6x centre crop it'd be 1.3x frame with the top/bottom or sides cropped.
 
Last edited:
Thanks, Mike! That makes a lot of sense and was definitely what I was seeing now that I think about it.
 
Mike P. said:
I would also prefer 5k/24 over 4k/24-HDRx . Alas, it's been confirmed that it's not possible in the current configuration, so there's no point dwelling... Maybe Dragon will enable 5k/24 on Scarlet (but enable 6k on Epic.) Who knows.
Click to expand...
Call me late to the party:nonod: But where was it confirmed that 5K24 fps is not possible for the scarlet?
 
It think it would be fair to let you scarlet guys to be able to record at least 5k 2:41. Even though you only paid a fraction of the epic costs. Since 5k wide is less pixels than 4k I can not see why the scarlet could not do this.
 
I'd really like access for motion at 5k, ya know the full sensor:laugh: Maybe if possible as the Dragon enters the epics...
 
At the very least 4.5k WS should be possible. 4096x2160 = 8,847,360 pixels per frame = 4608x1920 (2.4:1). As far as I'm aware (and until RED explain why not) I'm going under the impression that the amount of pixels per frame would be the limiting factor (lowest common denominator), and not where those pixels are collected from (after all, the entire sensor is active and read every frame otherwise the 5k look-around area while recording wouldn't be possible.)

Conversely, the "4.5k WS" mode on both R1mx and Epic is actually something like 4475x1920, which is LESS pixels per frame than 4096x2160... of course it uses a wider portion of sensor and would offer more oversampling than shooting 4k and cropping to 2.35 or 2.4 (which would then be 4096x1707...)

Alas, not giving the camera 4.5k (or 5k) WS is a lot different than Canon charging $12-15k for a camera whose hardware is exactly the same as the 1D X ($6k) but has 4k video enabled via firmware. Still, it would be nice to use more of the sensor.
 
Last edited:
Hehehe, yet another thread about wishes and dreams for Scarlet to get more power. ;) Guys, don't get crazy about that. I mean, all has been said (multiple times) and we can be sure that RED already knows. Don't think about what you miss every day, it will make you feel bad. And feeling bad about Scarlet? Come on, that can't be right. Think about what you already have in hands! Scarlet is a great tool as it is.

And honestly, don't hope for a magic software-update that enables 5k@24 and such things, its not going to happen. 3k@50 on the other hand should be possible. ;)

The next big thing is Dragon, be patient.
 
Maik Müller Menendez said:
Hehehe, yet another thread about wishes and dreams for Scarlet to get more power. ;) Guys, don't get crazy about that. I mean, all has been said (multiple times) and we can be sure that RED already knows. Don't think about what you miss every day, it will make you feel bad. And feeling bad about Scarlet? Come on, that can't be right. Think about what you already have in hands! Scarlet is a great tool as it is.

And honestly, don't hope for a magic software-update that enables 5k@24 and such things, its not going to happen. 3k@50 on the other hand should be possible. ;)

The next big thing is Dragon, be patient.
Click to expand...
This is an old thread, I replied to a statement about it being official that the scarlet could not do 5K24fps, but I can't find RED saying no deal. I understand its a long shot... It still is a ways off before the scarlet will get a Dragon sensor and there still are some functions yet to be enabled.
 
It is the matter of marketing policy... Technically Scarlet should be capable of capturing 24P 5K WS.
And I do believe it won't make EPIC owners asking for refund (all sales final anyway), ha ha :)
They not buying 1 extra K for extra 20 grands anyway it is all about HIGH FPS where EPIC compete with Phantom :)
 
Björn Benckert said:
Or actually, Within a week or so both epic and scarlet will be the gateway to the magic dragon.
Click to expand...

For some reason this made me thing of Puff the Magic Dragon....but anyways I would also rather see 4K at 48 or 60 FPS
 
How About a Node System for Image processing inside the Camera?

Seems like there are a lot of good ideas in this thread ... and this might be totally insane ... but would be so nice if there was a node system for the epic/scarlet kind of like NUKE. The node system could do things like what magic lantern does ... but the node system would be more controlled. For example the nodes would only be able to load json that would define fps/shutter/x-width/y-width/fan/wavelets/summing/hdmi_routing ... etc (probably would need to have the nodes aligned to system modules).

There would be a "RED Node Validator" to validate/simulate that the node/json is within spec, then as long as the nodes were valid, we could do what we want. If a problem developed, the camera would drop the custom nodes and go to default. I'd think this would also be nice for the "big guys" too, since they would test a specific node configuration and have that run as the "specification" on all their camera's. (i.e. would simplify camera management and configuration). INSANE? I don't know, but RED can do about anything. At least this way the community could "help" while also working within the limits of the camera design.
 
You must log in or register to reply here.
Back
Top