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

POSTED: EPIC Firmware v2.0.5 (Release)

Is this release of 2.0.5 firmware the verion that Im told in some circumstances kills the camera when using HDR, 48fps, 5K ? ala Ketch's problem or is this fixed now ?

This is the same code as the beta 2.0.5 - it has just been moved from beta status to release status. That means any bugs or problems reported are not fixed in this version.
 
This is the same code as the beta 2.0.5 - it has just been moved from beta status to release status. That means any bugs or problems reported are not fixed in this version.
So what justifies this as a "Release Version" if the bugs in the Beta version haven't been fixed? Is this now "recommneded for commercial productions?"
 
FWIW, I have rolled back from BETA v2.05 to the previous RELEASE FW (v1.7.10, i think) without issue, so if this new release FW is the same as the previous Beta, rolling back isn't impossible...I just don't know of any potential complications that might occur (other than having gotten accustomed to the newer UI and missing it upon reverting back)...

Cheers,
Clint
 
Thanks Cliint,

I tend to trust the release notes, I've installed and have not tried to roll back. I don't think they just bumped it from beta to release without changing a thing. I could try a rollback later tonight.

David
 
Thanks Cliint,

I tend to trust the release notes, I've installed and have not tried to roll back. I don't think they just bumped it from beta to release without changing a thing. I could try a rollback later tonight.

David

The beta and release versions are indeed the same - the firmware reports the same version and SVN revision. Furthermore the binary upgrade images are identical (you can perform a md5 or sha-1 hash to quickly confirm).
 
Cool,

Thanks trent. Then the release notes are wrong.

Cool.

David
 
i) Is it yet possible to focus manually (and wirelessly) with the Redmote jog?
Currently I'm able to do this partially stepwise but not all the way up to inf. Tested this with the EF 16-35mm/f2.8 L USM II and EF 24-70mm/f2.8 L USM lens.

ii) Is it possible to get the LCD to update the focus distance whenever and despite of how the focus is changed?
 
Still can't get my Camwaves to work with the 720p signal from the 2.0.5 release. Anyone tried it with a successful outcome?

There's definitely something weird going on with 1080 & 720p HD-SDI outputs. It's just not switching between those two - it requires a reboot. I can't even get the 720p signal to work with my Panasonic 1760 monitor.
 
720p playback

720p playback

720P playback on current 2.0.5 firmware is @ 29.97 fps instead of the normal 23.976fps.
The Panasonic BT-LH 1700 series cannot deal with that frame rate...or so I am told.
Neither can most video assist systems like Q-Take...so they must go thru another step in ingesting material on set before playback.
We just did a shoot on my Epic at 60fps for a 24fps layback, and used Q-Take...we ran the video assist from the SD out at 1080, instead of 720. The 60 fps playback looked stuttery at 24fps whereas the cameras internal playback looked great.
I'm betting they will fix this in a new future build.
 
Yes! To be able to pull focus on the Redmote would be very nice! Last week, we were using a 25' jib and when then jib was at the highest point the redmote would lose connection. We couldn't pull focus but we did use redmote to trigger red start/stop. I am not sure if there is a way to add an antenna to the redmote or Epic, but I think it needs an antenna or little bit of boost. A wired version would be a great more solid solution. The redmote offers a usb connector that could be used to connect to the Epic somehow.
 
I don't do too many shoots with sound but yesterday I did my first Sync sound job of the year with the new 2.0.5 build. There was a very noticeable delay when viewing the on set monitors. It was a bit distracting especially for the client. Does anyone know if this video latency is an issue that is present in all Epic Builds or is it specific to this firmware. I would consider rolling back if I can provide realtime video to the director.

Thanks
 
I am not sure if there is a way to add an antenna to the redmote or Epic, but I think it needs an antenna or little bit of boost. A wired version would be a great more solid solution.


I remember a sentence from someone at red that said REDmote could have two power settings of which one only the lower is enabled yet.
There is hope.
 
Bug Report for 2.0.5
Despite the many choices of HD-SDI monitor outputs, my system and monitors tell me that the Epic only can put out 720P @ 29.97 and 23.98, neither of which can be recorded by my Video playback system. I'm hoping someone from RED sees this buries amongst all the useless posts.
 
Has anyone else had problems with their Canon mount after this firmware? Our Epic keeps locking up after rolling, the LCD still shows a moving image but the RedMote goes IDLE, the touchscreen is completely unresponsive, and none of the on camera buttons work. It can be powered down by the normal holding of the power button but when it powers back up it says "Camera was improperly shut down".
 
Bug on 2.0.5:
With Canon mount + Manual Nikkor 50mm f1.4 and Anamorphic adaptor (Kowa 8z) with 5ANA resolution, the clip doesn't playback. On other resolutions it does.
Do not know about PL mount.

Operational notes specific to Build 2 v2.0.5:
"5K ANA clips not supported in playback"
 
Back
Top