Welcome to our community

Be a part of something great, join today!

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

DSMC build 6.2.44 + REDCINE- X Build 39

Hi Adrian!
Every time you press the start stop button you lose a number of frames around 10. So the output on the HDSDI the video will actually pause for this moment and continue after the 10 or so frames. They don't appear after, just gone. It's like the system froze for a bit when you pressed stop and then again at start.

Hope I explained better this way, so yea, that doesn't help so much with the timecode I think. Anyway, should be fixed now!

Adrian Weinbrecht said:
Thanks Robert

Can you please clarify ? Does this mean you lose 10frames or so at the beginning of hitting record and then get an extra 10 frames at the end? Otherwise the footage and timecode matches up ?

Thank you very much
Click to expand...
 
Michael Lindsay said:
We have had a issue when using a plate that normally shoes % accurately. The problem is it jumps to 0% and then shuts down. Is this the fix for tha??

Thank you

M
Click to expand...

Still have the same problem. Which plate r u using. If it's an Element technica, i was toll they r Working on an Update for next week.
 
Is this really a release build? Seems like a big jump from the 6.0.46 that was released just a few days ago and there's no beta builds listed anymore.
 
Manfred Baulig said:
Still have the same problem. Which plate r u using. If it's an Element technica, i was toll they r Working on an Update for next week.
Click to expand...

No it is a older wooden camera wired plate that has worked well for 2 years (and still does with a epic dragon)

Thanks for answering..

M
 
Just upgraded my camera. Having an odd issue with my timecode. Set up my date / time / time zone, and it seems like my timecode is reading a minute and a few seconds earlier than what is set in-camera. Anyone else with happening?

EDIT: Seems like after a cold boot a few hours later, everything is back to normal.
 
Last edited:
Andre Vaternam said:
The Aperture on none of my Nikon lenses works!
Click to expand...

Hi Andre,

I'm sorry to hear about the issues you're having with Nikon lenses.

Could you please submit a Technical Support request on SUPPORT.RED.COM and attach the log file from this camera along with a list of the lenses that you're having issues with, we would like to get your information to our Engineers for further analysis.
 
I think I timed the boot on this build to around 22 seconds!

That is the stuff I really appreciate.

David
 
Brad Harris said:
Hi Andre,

I'm sorry to hear about the issues you're having with Nikon lenses.

Could you please submit a Technical Support request on SUPPORT.RED.COM and attach the log file from this camera along with a list of the lenses that you're having issues with, we would like to get your information to our Engineers for further analysis.
Click to expand...


Hi Brad,

thanks for getting back on this. I opened one Nov. 29, because I had issues with some lenses under 6.0.40 (and Beta 6.2.9 was a mess, like now): Nikon Mount [RED #41751]. But its gone. I send a list of all lenses I own and have issues with. Anyway, will open another one.
Love the camera, but the mount thing is so depressing :-/
 
...used this build all day Saturday with no issues. We shot 6kHD and 2K ProRes 4444 (RLF). ...loving it. The only downside we ran across was losing shots when the batteries drained as we couldn't see a percentage on the batt. I'm using the IDX adaptor to mount my V-mount PAGs on the ET A/B back.
 
I seem to be getting more info in the highlights and shadows using Log3G12 HDR gamma
on RED 1 MX footage. This is in comparison to REDLOG FILM GAMMA.
I know Log3G12 is intended for an HDR display but it might have use beyond HDR monitoring.


Brian Timmons
BRITIM/MEDIA
 
Quick Question..... HDR gamma curves...... Weapon footage specific? I'm unable to see the option for them
 
Anthony Berenato Jr said:
Just upgraded my camera. Having an odd issue with my timecode. Set up my date / time / time zone, and it seems like my timecode is reading a minute and a few seconds earlier than what is set in-camera. Anyone else with happening?

EDIT: Seems like after a cold boot a few hours later, everything is back to normal.
Click to expand...

Hi Anthony

The way time code is calculated was changed to correct another issue reported several months ago. You will see what you describe for the 'odd' rates, 23.9, 29.9, 59.9. The underlying issue is that RED does not do drop-frame logic for these rates. Essentially 23.9 and 24.0 both count 0-23 frames per 'second'. Frames is what time code counts, not really time per se. The actual duration of a 23.9 frame is 1.001 times that of a 24.0 frame. 23.9 is 24.0/1.001. So to get to some wall clock time of day (what the RTC in the camera represents) since midnight, it takes fewer 23.9 frames than 24.0. Everything lines up at midnight, and then the discrepancy increases as the day goes on. If you set your project rate to an 'even' rate, 24.0, 25.0, etc you should see the time code recalculate to match the time of day.

FYI, I have confirmed with Ambient that this is what their Lockits do as well.
 
Dave Winder said:
Hi Anthony

The way time code is calculated was changed to correct another issue reported several months ago. You will see what you describe for the 'odd' rates, 23.9, 29.9, 59.9. The underlying issue is that RED does not do drop-frame logic for these rates. Essentially 23.9 and 24.0 both count 0-23 frames per 'second'. Frames is what time code counts, not really time per se. The actual duration of a 23.9 frame is 1.001 times that of a 24.0 frame. 23.9 is 24.0/1.001. So to get to some wall clock time of day (what the RTC in the camera represents) since midnight, it takes fewer 23.9 frames than 24.0. Everything lines up at midnight, and then the discrepancy increases as the day goes on. If you set your project rate to an 'even' rate, 24.0, 25.0, etc you should see the time code recalculate to match the time of day.

FYI, I have confirmed with Ambient that this is what their Lockits do as well.
Click to expand...

Hey Dave, thanks for the information. I was actually thinking about the rates last night, and assumed it might had been the case. I guess most of my confusion came from setting my date / time in the past and watching the timecode jump to reflect it after the menu was closed. This time around I noticed it increased / decreased the timecode as I was adjusting the intervals on-the-fly in my date in time.

All seems good now anyway, must have been something I didn't notice before (or a slight change) that caught my eye.
 
What is Open Gate support again?

Edit: it's independent refresh rate on the EVF/LCD for when you're shooting at a slow frame rate.
 
Last edited:
On the Epix MX:
Aperture for Nikon 70-200 2.8 VII not working.
Camera fails to power up every 2nd startup.
When camera does power up the monitor sometimes doesn't power on.
 
I have a Red Nikon Mount and can't get manual or camera control of my Iris.
The Aperture display on the monitor is N/A
I set my lens to locked at F16 and still I have no Iris control.

I've just received my Weapon CF and I just updated to the latest firmware... is this a bug on Weapon or on this firmware?
 
Thomas Buchan said:
On the Epix MX:
Aperture for Nikon 70-200 2.8 VII not working.
Camera fails to power up every 2nd startup.
When camera does power up the monitor sometimes doesn't power on.
Click to expand...

When a stalled boot happens, try pushing the "power" button on the monitor. If it's what I think, the camera will boot but the physical buttons of the display will be different from default.

Also, does anyone know how to use pixel masking in RCX?
 
Last edited:
roryhinds said:
I have a Red Nikon Mount and can't get manual or camera control of my Iris.
The Aperture display on the monitor is N/A
I set my lens to locked at F16 and still I have no Iris control.

I've just received my Weapon CF and I just updated to the latest firmware... is this a bug on Weapon or on this firmware?
Click to expand...

Hi Rory,
I am sure its firmware. 6.2.xx seems to have major issues with Nikon, none of my lenses worked, while 6.0.xx "only" has issues with some Nikon mount lenses. I rolled back, so I can at least use the camera with some lenses. But this seems to be an issue for a while, at least for me.
 
You must log in or register to reply here.
Back
Top