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

Released: Beta Firmware - Build 15

That's what I thought. Good stuff.

Except... isn't it something like 3.56:1 unsqueezed? you have to crop again to get 2.4:1 on a 16x9 sensor...?

it doesn't use the whole sensor, just the middle 1.2:1... i think, lol
 
Anamorphic

Anamorphic

What are the pixel dimensions of the anamorphic modes? i.e for 4k, is it using the full 2540 pixel height of the sensor?

Its 2304 pixels high and therefore 1.2 x that dimension wide = 2764 x 2304
 
.RDM folder

.RDM folder

"Addition of root directory (.RDM) to digital media"

What does this do?

Will this allow us to record in multiple formats on the same media without formatting?

The .RDM folder allows all the clips recorded on the digital magazine to be located in one folder, which is intended to make transfer or archive of all the clips on a magazine easier - just drop and drop that folder onto your backup media.

You can record at any combination of resolution and quality setting now, provided that you do not change the Project Frame Rate (Varispeed and Ramp and Timelapse are O.K - I'm talking about the Project Frame Rate) as that is the fundamental timebase of the project itself and affects timecode. If you do change that, the camera will still report "media is incompatible"
 
CF Cards

CF Cards

with built 14 we could use SONY 8GB CF cards,396x46MB/s, No problem with every supported frame rate. With built 15 we can not - media too slow.
we know that the speed of the card is nearly the same as the RED cf card,
it is a little faster than the RED.
Anybody with same experiences?
 
Look at post #37 and #86 in this thread

with built 14 we could use SONY 8GB CF cards,396x46MB/s, No problem with every supported frame rate. With built 15 we can not - media too slow.
we know that the speed of the card is nearly the same as the RED cf card,
it is a little faster than the RED.
Anybody with same experiences?
 
A tiny spelling fix - the menu for formatting a magazine with existing clips on it has a spelling error "magaine" instead of "magazine".

Oh and since I'm nitpicking, the Theory of Operation heading in the manual is a different font to the rest of the headings.... :)

HTH!

Paul
 
Maybe even better would be pushing up or down jumps up in increments of 10 or 20, and turning the knob is for fine adjustments.

You might additionally make it so if you are already at the minimum setting, pushing down once more wraps around to the maximum. This is a time-saver because I think the most-used settings are probably going to be the min and max points.

Of all the non-24 fps footage posted, I think nearly all of it is 72 or 75 fps. Just about no one used intermediate speeds like 50 fps, etc.
 
Its 2304 pixels high and therefore 1.2 x that dimension wide = 2764 x 2304

How does it handle the monitor outputs for the Anamorphics? Does it unsqueeze for preview? On both the EVF and the LCD? How functional is it with the beta build?
 
Removing color on the viewfinder menu and shooting in BW seems to make it's way to RedCine?!! I would expect that anything I do in the viewfinder menu will just be for the viewfinder only and not be a starting color choice in RedCine. If I made a BW selection in the sensor menu, I would expect that to make it's way to RedCine--but not the viewfinder.

I was poking around quite a bit and haven't had a chance to go back so I may have inadvertantly made a mistake and didn't notice--but it seems to me I removed color in the viewfinder menu, shot, and took the footage into RedCine and it was BW.
 
Removing color on the viewfinder menu and shooting in BW seems to make it's way to RedCine?!!

We know the camera records raw so it must be getting saved as metadata. I think in RedCine you can reset/ignore all metadata from the camera somehow. Try that.
 
We know the camera records raw so it must be getting saved as metadata. I think in RedCine you can reset/ignore all metadata from the camera somehow. Try that.

Sure, it was there, all I had to do was bring the saturation up--but it seems to me that viewfinder choices should not make it's way into the color workflow.

If an operator wants to shoot BW for whatever reason (maybe to make the Red highlight easier to see) then great--but it should not then require extra effort in RedCine and RedAlert.

I think that choices made on the Viewfinder settings should be for the viewfinder only and not be recorded to the metadata.
 
I think that choices made on the Viewfinder settings should be for the viewfinder only and not be recorded to the metadata.

I don't think you need to explain it. I think everyone can see it's a bug and they'll squash that one easily.

I was just trying to help you with this particular clip.
 
...I was just trying to help you with this particular clip.

Thanks! Just a goofing around clip anyway and it's already been deleted.

This is what I love most about this camera: I can experiment to my heart's content and delete the junk and save the gems without even worring about burning up tape--let alone film!
 
It has been like that since build 1.

False Color Focus assist just got added in build 15. Are we talking about something else now?

EDIT - I just re-read and saw he's mentioning monochrome viewing. Nevermind. Maybe it should come through with the metadata. Or not. Whatever you guys think.
 
Viewfinder and Metadata

Viewfinder and Metadata

it seems to me that viewfinder choices should not make it's way into the color workflow.

If an operator wants to shoot BW for whatever reason (maybe to make the Red highlight easier to see) then great--but it should not then require extra effort in RedCine and RedAlert.

I think that choices made on the Viewfinder settings should be for the viewfinder only and not be recorded to the metadata.

If you use the COLOR parameter in the VIEWFINDER menu it does not find its way into the metadata. If you set SATURATION = 0 in the VIDEO menu it does find its way into metadata, but even then it is just metadata and can be ignored / updated with a mouse click in the post apps.

The above I know to be true for RED ALERT, I'll double check for REDCINE ... logically it must behave the same though.
 
Back
Top