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

DSMC v6.0.23 Release

Wow, Dan...hidden talents...and Sean, way to bring out Dan's "good side"!! Thanks to all the development team for this sweet release!
 
Sync Port bug?

Sync Port bug?

Matthew B said:
Has anyone sent their side handle in to get the PC sync port put in? I still have the non functioning version in my grip - I'm curious what the process is to get the "gold port" put in?
Click to expand...
Yes. If your sync port is black you need to send it in to have it replaced with the gold one that works. Contact your BS Rep to arrange an RMA.
I had this done quite awhile ago. I played around with firing strobes during motion capture by programming a button on the Side Handle to Trigger Strobe. Of course it's hit or miss wether the frame is fully exposed or not unless you have a Motion Mount.

Thanks Red Team for this great update! However, there seems to be a bug now as far as the sync port is concerned. It appears to be stuck in an "always on" state rather than sending just a pulse. When I plug my strobe radio/slave transmitter into the Side Handle, the strobe fires, but won't fire again unless unplugged and replugged because the transmitter is seeing a constant signal from the sync port.

I would hope that the firmware can be tweaked so that the sync port outputs a trigger pulse simultaneously when the Side Handle record button is pushed while in single frame Stills Mode.
 
Is there a new user manual coming with this firmware?
I'm having a hard time figuring how to use the auto exposure and more than that how does it work...
 
This is an interesting one:

A fortnight ago I ran into a serious sensor issue. On the left third the sensor showed in overexposed white parts a white, vertical line that only vanished when I stopped down. Ok. Red's reaction was, send us a log, no better the camera. Fully understandable. Because of many other things that needed attention I postponed the shipping.

Today I updated the camera and voilá, the white line is gone. My guess is that my Dragon sensor is much better black shaded with this build than with any other build before. When I pulled up sensitivity to ISO 12.000+ the noise is remarkably even and no hidden pattern is visible. Much, much improved than to previous builds. Today evening I will do a noise test. Perhaps the noise also improved.

I also noticed that camera is running hotter, could be subjective.

Hans
 
vincent kardasik said:
Is there a new user manual coming with this firmware?
I'm having a hard time figuring how to use the auto exposure and more than that how does it work...
Ok, I'm going to be honest, I'm totally confused by the Stills mode, it seems that I can shoot at 25fps at 2:1 or maybe the frame rate doesn't affect the compression anymore?!
Click to expand...

Hi Vincent,

There is now, under the download section on the RED Store site, an operation guide for 6.0.23.

One cool thing is the touchscreen access to stills mode as well.

Thank you very much

Fury
 
Nick Fury said:
Hi Vincent,

There is now, under the download section on the RED Store site, an operation guide for 6.0.23.

One cool thing is the touchscreen access to stills mode as well.

Thank you very much

Fury
Click to expand...

I totally missed that!
Thanks a lot Nick!
 
Last question... At least on that thread ;)
Has the frame rate zero influence on recording time and compression rate in Stills mode?
It feels like we can record forever in RC 2:1 or 3:1?
 
vincent kardasik said:
Last question... At least on that thread... Has the frame rate any influence on the RC in Stills mode?
It feels like we can record forever in RC 2:1 or 3:1?
Click to expand...

In Multi-Shot record mode (the default record mode for STILLS mode) the frame rate essentially sets your max frame burst rate. It does not affect your REDCODE setting. However, you cannot continuously record at all frame rate / REDCODE combinations. Eventually you will start dropping frames - but continue to capture frames while pressing the record button at the media offload rate.
 
Trent Lillehaugen said:
In Multi-Shot record mode (the default record mode for STILLS mode) the frame rate essentially sets your max frame burst rate. It does not affect your REDCODE setting. However, you cannot continuously record at all frame rate / REDCODE combinations. Eventually you will start dropping frames - but continue to capture frames while pressing the record button at the media offload rate.
Click to expand...

Thanks a lot for your reply Trent.
I just recorded a more or less 14 seconds sequence at RC 2:1 with a time base of 25p.
According to RCX it's 364 frames...
File is heavy, 3,84Go but when I lay it on my timeline in FCPX it plays just fine, I don't see any dropped frames...
Am I missing something or can we record motion sequences with a lower compression rate in Stills mode than in Motion mode?
 
vincent kardasik said:
Thanks a lot for your reply Trent.
I just recorded a more or less 14 seconds sequence at RC 2:1 with a time base of 25p.
According to RCX it's 364 frames...
File is heavy, 3,84Go but when I lay it on my timeline in FCPX it plays just fine, I don't see any dropped frames...
Am I missing something or can we record motion sequences with a lower compression rate in Stills mode than in Motion mode?
Click to expand...

Without more information (camera type, record format, media type, etc) its impossible to say at what point you'd start dropping frames at 25fps/RC 2:1.

If your goal is to capture short motion sequences at a higher REDCODE, you should really look at the REDCODE Burst record mode. It will let you see how many frames we can guarantee to be captured at a given record format, framerate and REDCODE.
 
Trent Lillehaugen said:
Without more information (camera type, record format, media type, etc) its impossible to say at what point you'd start dropping frames at 25fps/RC 2:1.

If your goal is to capture short motion sequences at a higher REDCODE, you should really look at the REDCODE Burst record mode. It will let you see how many frames we can guarantee to be captured at a given record format, framerate and REDCODE.
Click to expand...

Thanks Trent.
I was shooting with an Epic Dragon, in 6K FF on a 1.8" 512Go SSD.
I will definitely investigate more about the Burst mode.
I just checked it briefly when it was announced and didn't realize how I could use it but now I think it's definitely interesting.
 
You must log in or register to reply here.
Back
Top