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

Firmware Choices

P

Peter Lyons Collister ASC

Well-known member
Joined
May 23, 2008
Messages
1,339
Reaction score
1
Points
0
I am curious how many Epic owners have gone from Build 1.7.1 to 2.0.5 and how they feel about the transition. I have a few commercials coming up in the next 2 weeks and I am wondering if I should make the move.

Many thanks,



Peter
 
The only issue I have seen is sometimes (not all) the monitor output goes completely out (on both the LCD and bomb) after switching to HDRx. It's not that big of a deal because if indeed that happens, you can regain the live feed and regain control of the camera by docking the REDmote on the back of the brain and turn HDRx off via the REDmote...
 
Ketch Rossi had disastrous results when he was using 2.0.5 and HDRX on a shoot in Dubai. If 2.0.5 is out of beta, then you should be alright, but the new rule is to make sure you
have a laptop or spare SSD to download a new camera firmware if your camera freezes. Other than that, I can't speak about the new features.
 
The same issue was repeated on his camera as was mine. I wouldn't call it a "disasterous" result with the firmware itself, in a sense that you can't reverse the issue on set without even a re-boot. It was only that (1) he did not have a REDmote with an equally updated REDmote to proceed towards turning off HDRx and (2) this happened 15 minutes before the new year.
 
I've shot a few commercials with 2.0.5. Had a couple weird bugs along with an error message appear on startup but nothing that was not solved with a reboot. I had the camera freeze during recording but it's probably because I was changing some menu settings on the redmote while rolling. If you need the playback or additional resolutions and frame rates or other features it might be worth the small gamble. It came in handy yesterday as we wanted to shoot 3k 160fps. Hopefully it will be out of beta soon.
 
Thanks for the responses..... Joseph, I can't help but love to see that shot of you with your signature hat in Black & White.... makes me smile....
 
Peter Lyons Collister said:
Thanks for the responses..... Joseph, I can't help but love to see that shot of you with your signature hat in Black & White.... makes me smile....
Click to expand...

Thanks. It makes me smile that REDuser gives us all a chance to make each other better and build each other up with knowledge. Thanks for being here, and thanks for being awesome. ;)
 
The only problem I've had is the left hand 1/3 portion of the monitor went wack after the 1:1 focus assist. It has only happened once and a quick reboot fixed it. No problems with the HDRX here.
 
I had one small issue. Top half of the monitor was lagging about a second behind the bottom half. It looked similar to an extreme rolling shutter. However it naturally corrected itself later in the take without a reboot needed. Upon reviewing the footage it was just a monitoring issue and was not displayed during playback. It only happened a few times and did not cause major problems on any occasion.
 
zero problems here, but I haven't used HDRx at all with the new build.

Mr. Collister - do you need a Local 600 DIT for your Commercials? I'm available ;)

Dan Kanes three two three four four five zero nine nine nine
 
Peter Lyons Collister said:
I am curious how many Epic owners have gone from Build 1.7.1 to 2.0.5 and how they feel about the transition. I have a few commercials coming up in the next 2 weeks and I am wondering if I should make the move.Many thanks,Peter
Click to expand...

Peter, only issue ever encountered was the HDR-X one, which we got that first on Joseph's camera in November while shooting Skydiving
in Dubai and a second time again in Dubai on my camera, solution is easy, if you remember to have the Redmote updated and have it with you... ;)
I was able to fix and show Joseph how to take care of the issue via the Redmote, (docked or not does not matter), all you need is the Redmote update
so to communicate to the camera.Problem for me was that, even so I had already seen the problem before and taken care of for Joseph's,
I had forgotten on the spare of the moment, I was also working with high Fever that night, that didn't helped, we also had been at that location
for almost 12 hours waiting for the critical moment of the midnight fireworks.My Redmote was not updated so I had no direct link to the camera,
I had no laptop and or SSD reader with me either to be able to do a Re-install on location, so even so it is a Bug on the BETA 2.0.5 build,
it was all on me, as I not only already knew the issue and had it fixed and teached others how to fix it, but I forgot about it and
was unprepared to fix it, shame on me... ;)

I posted here: http://www.reduser.net/forum/showthread.php?69679-HDR-X-Warning-with-Build-2-0-5!!

David Collard said:
Ketch Rossi had disastrous results when he was using 2.0.5 and HDRX on a shoot in Dubai. If 2.0.5 is out of beta, then you should be alright, but the new rule is to make sure youhave a laptop or spare SSD to download a new camera firmware if your camera freezes. Other than that, I can't speak about the new features.
Click to expand...
Joseph Hutson said:
The same issue was repeated on his camera as was mine. I wouldn't call it a "disasterous" result with the firmware itself, in a sense that you can't reverse the issue on set without even a re-boot. It was only that (1) he did not have a REDmote with an equally updated REDmote to proceed towards turning off HDRx and (2) this happened 15 minutes before the new year.
Click to expand...
Well it was actually REALLY "disastrous" to me as it happened to be in an unique Shot moment so I lost that shot because of it.
 
I've found that if the monitor goes weird with upper and lower parts out of sync or other visual artifacts (usually occuring when switching to 1:1 mode) I just switch to playback mode and back again and it corrects itself. Sometimes I might need to do it twice though.
 
Also, one thing I just remembered- every time I power up on 2.0.5 it fails to recognize the audio inputs. I have to physically unplug and replug the mini cables on the brain and then it works fine. Good to know if you are recording audio on camera for any reason!
 
You must log in or register to reply here.
Back
Top