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

DSMC v6.0.23 Release

Nino -- I tried 6.0.31 with a Canon Motion Mount on an Epic Dragon. Canon EF lenses caused major problems [weird shutter speeds, strange values in the Motion Mount pane under Lenses --->]
Lenses with Canon Leitax mounts (lenses without CPUs) seemedto be OK with the Motion Mount & 6.0.31

With the "regular" Ti Canon Mount & 6.0.31, Canon EF lenses seemed to work OK. With the "regular" Ti Canon Mount, even the Tamron 15 - 30mm would show up if I booted
several times & held my mouth just right.

You might give 6.0.31 a spin, but beware of the "you can't downgrade" restrictions, as this may close off options you want to leave available.

Tx,
Serge


I still have issues with 6.0.28 after the EF mount problems of not recognising EF mount lenses in the previous firmware version.
I though it solved some problems but after one day of shooting with this build. I had several major issues.
The camera would not find my TI PL mount on booting (ef mount ok) and the redtouch would only display a frameline and no other control information even after several boots.
I also had a 'critical error contact red' message on booting the camera at one time after several boot attempts, I've never seen this before on my camera.
Im rolling back to 5.3.42 until these issues are ironed out.
 
Nino -- I tried 6.0.31 with a Canon Motion Mount on an Epic Dragon. Canon EF lenses caused major problems [weird shutter speeds, strange values in the Motion Mount pane under Lenses --->]
Lenses with Canon Leitax mounts (lenses without CPUs) seemedto be OK with the Motion Mount & 6.0.31
Which mount was on the camera when you installed 6.0.31 (or 6.0.28 before)?

What i have noticed about firmware builds since 6.0.23 is, that after upgrading the cameras firmware the camera started to upgrade the firmware of my Canon-Mount too. Once it did it right after the upgrade and asked me to reboot again, thats how i expect it. But another time, with 6.0.28, it did the lens-mount-update when i powered down the camera.

Those newer builds clearly have to upgrade the lens-mounts and i guess that sometimes didn't happen the way it was intended/right after firmware-flashing. Which results in running a outdated lens-mount-fw together with the newest brain-firmware.

I would try to reflash (force_upgrade) the newest firmware again, with the lens-mount in question installed and then give it one or two reboot-cycles. Maybe the camera doesn't upgrade all accessories (SH, Lens-Mount) at once? Wild guessing here of course. ;)
 
I had the EF AL mount on during the upgrade. What your saying makes sense and I'm sure your right.
I solved the problem of the PL lens mount by trying out the PL mount on the rental house body and it did the upgrade after a boot and worked ok after that on my camera. So a different camera upgraded it successfully.
Im still concerned about the 'critical error' message i got and don't trust it. Ive rolled back to 5.3.42 for the time being and all is rosy again.
 
I am on set with a rental epic and NEEED to update the firmware to be compatible with the bridge. I do not have the right permissions as it is my camera. Any suggestions?!
 
I read though most all of this thread and still can really determine what version of firmware to be on to get my dam canon lenses to work.

If anyone can chime in and let me know that be awesome. Last thing I want to do right now is spend half a day testing firmware versions.

6.0.31, 6.0.28, or all the way back to 5.3.42 ?

Cheers!
 
Last edited:
Daniel K.B.
The minor interface upgrades really aren't worth the trouble this v6 update has caused me. The image quality is not improved by a firmware update, which is really all that matters.
. I don't use or care for the still mode so theres no incentive to upgrade to a super buggy firmware version. I went back to 5.3.42 and the camera now works like clockwork.
 
I've been debating about upgrading to 6.0.31 after hearing things were still a little buggy early on. Haven't seen any issues posted for a couple of weeks now. How is this release been treating everyone? Anything to report or has it been stable?
 
For me the upgrade 'broke' the jog wheel, select and navigation arrows on the side handle (Scarlet X). Mapped other keys to compensate but bummed that I have to send SH in to get it corrected. Any way to back out a peripheral firmware upgrade?
 
On the newest one you still have to restart sometimes when changing lenses. New Sigma 23-35 still not working.
 
Sent in to RED for repairs - $300 to replace SH main board and jog wheel / navigation assembly. Happened during upgrading peripherals step (SideHandle). Guess I am only one it happened to.
 
Peripheral lock out on SH, PL mount and Touchscreen and no iris info on EF mount a real problem with these 6.xx builds.

Working a lot better with the newer build but not 100%. Switching to stills then back to motion on the Sidehandle stills switch seems to fix the iris info issue.

New FW please for 6xxx to address these issues please!

Craig Lees
ED & SX UK
3dstories.co.uk
 
Peripheral lock out on SH, PL mount and Touchscreen and no iris info on EF mount a real problem with these 6.xx builds.

Working a lot better with the newer build but not 100%. Switching to stills then back to motion on the Sidehandle stills switch seems to fix the iris info issue.

New FW please for 6xxx to address these issues please!

Craig Lees
ED & SX UK
3dstories.co.uk

What does "Peripheral lock out on SH, PL mount and Touchscreen" mean?
 
Trent, the legend!

It locks out the ability to use the device! Had this on my PL mount then touchscreen them sidehandle. Lights are on but buttons do nothing. On my SideHandle it fixed after a reboot (I think it might have performed a peripheral upgrade to the sidehandle at the same time). So that's all good now but the touchscreen is still a worry though I haven't come across it again yet in 6.0.31. Seems to be working a Lot better on the newer FW but it still scares me it could go again, though are you happy this is fixed in 6.0.31? Problem was you couldn't press the agreement button when loading the new firmware on the touchscreen but after a load of reboots, it suddenly started working again. It is very sporadic. We have had initial genlock sync problems too with an earlier 6 build, which I think was an EF lens related-thing which we eventually fixed but was something we encountered that never had to fixed before.

Is it possible to roll back to 5.3.42 after loading up 6.0.31?

Thanks in advance Trent. Having you here on reduser is a real boon for the tech support I can't figure out!

Cheers!

Craig Lees
ED & SX UK
3dstories.co.uk
 
"Freeze" instead of "lock-out" might be a better description!

Craig Lees
ED & SX UK
3dstories.co.uk
 
Will there be a new build out for Epic before the standard OLPF ships (compatible with the standard OLPF)? I usually don't upgrade until I know it's a safe upgrade, but I will probably buy the standard OLPF on day one.
 
Back
Top