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

HDR-X Warning with Build 2.0.5!!

He he, guys, please don't forget whom you are talking to here... ;)

I Have been working on 2.0.5 as I have for every single BETA software since the very first one with M8 about a year ago... ;)

In this case I had been working on 2.0.5 since its release and the entire shoot in Dubai form end of November till end of December was done on Build 2.0.5 on all 5 cameras.

Only issue has come up as we used HDR-X, I paid the price here as I didn't had my Redmote update, so not working with current camera build, and for this I
could not Turn HDR-X off since the LCD and or EVF were not working with this Bug, and not having the Lap top and or a pre formatted and loaded SSD with the
Force Upgrade as I usually always have, did not allow me to do anything til I was back at the Hotel.

Lesson learned the hard way, and as reminder I come up openly making full of my self for having been cut unprepared and off guard in the
hope that it does not happen to any one else here.

I guess what I am trying to say is that, because nothing ever happens to you, don't get too comfortable using BETA Builds without been
prepared for the worst case in which you do encounter a Bug and need to re-install to get out of the Bug if all else fails you, I did just that,
as in an entire Year I never had a single problem, this time I had one and was cut off guard, end of story for me, Warned al others...
Wish to no one to have it happen how it happened to me, just don't mistaken me for a Novice he he, it happens once and trust me it will never happen again... ;)


Happy Shooting!!
 
It's a good idea Patrick. That and all the disaster prep Ketch recommended.
 
Thanks for infos Ketch. They are very valuable...on one side, on the other I make a living around the Epic too (I don't own one but I shoot often on it, though) and I know that for a fact next week when I'll go on set the new rumour will be that its better not to use HDRX as it will freeze irreparably the camera.

Lets not do irreparable harm to ourselves. Best conduct would be to contact Support at Red directly and make sure that the thing is repaired in next build, without making a fuss out of it. A butterfly wing batt really often turns into a storm in our set gossip world.
 
Thanks John... Yeah I am so precisely always careful that pisses me off I wasn't the only time I had a problem come up... :(

Most welcome Bob,

and don't worry, no matter what, there wilL always be the "CLASSIC IDIOTS" on any given set the "CLASSICAL ANTI RED"
which will spread rumors like wild fire, and exaggerate things out of proportion...

I could give a S%$#^@ less about any of them, as in the years I have grown to just simply ignore this Ignorants,
but this type of info does no good kept out of our community, we need it to know, if some one else had posted about it I would have
known and better dealt with it the first time around, now all of those that read this post will know, and will not be cut unprepared,
and that is all I'm happy about it, RED understands this is valuable info to the community and appreciate this type of initiative posts,
even when I', actually showing that I too have my weaknesses and am not perfect, I'm sure not a RED God as many make me to be,
it does not pleases me to show that I have a huge mistake here not been prepared as I should always be on set and lost a HUGE SHOT OPPORTUNITY
because of it, but I do post, and I do not care to make a full of my self, because it is for the good of the community!!

Also if RED didn't want posts like this to come public about Bugs, they will not otherwise have give a BUG section to us to post about it... ;)


Besides if those IDIOTS do read carefully they also read that the solution "When prepared" is fast and effective, and there are actually more then one SUPER FAST FIX,

1) Use the Redmote to Navigate to HDR-X and Turn IT OFF

2) Use a Pre-Formatted SSD with a Force Upgrade Build Folder in it, and Re-Install the BUild of choice

3) If you don't have neither of the Above 2, then better have your Laptop and your SSD reader,
with a formatted SSD and put a Force Upgrade Folder with BUild of choice in it and proceed to Re-Install.

And of course LAST but NOT List, DON'T USE BETA BUILD ON A PAID GIG, USE the RELEASE BUILD, and leave the unknown to us... ;)
 
were u able to get one of the other 3 cameras into your A position?

thanks for posting. i like the idea of having a force build on a SSD at all times....although i dont even know what that is yet! :)
 
Unfortunately NO Jack, the other 3 cameras were in other Buildings, which at that time giving distance and the Super Populated Streets
would have made it IMPOSSIBLE to be transferred over to my position.

Im sorry to hear this. I appreciate the information tho. You are keeping it real.
 
He he, guys, please don't forget whom you are talking to here... ;)

I Have been working on 2.0.5 as I have for every single BETA software since the very first one with M8 about a year ago... ;)

In this case I had been working on 2.0.5 since its release and the entire shoot in Dubai form end of November till end of December was done on Build 2.0.5 on all 5 cameras.

Only issue has come up as we used HDR-X, I paid the price here as I didn't had my Redmote update, so not working with current camera build, and for this I
could not Turn HDR-X off since the LCD and or EVF were not working with this Bug, and not having the Lap top and or a pre formatted and loaded SSD with the
Force Upgrade as I usually always have, did not allow me to do anything til I was back at the Hotel.

Lesson learned the hard way, and as reminder I come up openly making full of my self for having been cut unprepared and off guard in the
hope that it does not happen to any one else here.

I guess what I am trying to say is that, because nothing ever happens to you, don't get too comfortable using BETA Builds without been
prepared for the worst case in which you do encounter a Bug and need to re-install to get out of the Bug if all else fails you, I did just that,
as in an entire Year I never had a single problem, this time I had one and was cut off guard, end of story for me, Warned al others...
Wish to no one to have it happen how it happened to me, just don't mistaken me for a Novice he he, it happens once and trust me it will never happen again... ;)


Happy Shooting!!

Sound advice from a Professional! Thanks for letting us know. This is one of the great things of this community. Keith could have stayed silent and maybe some of us would get hurt in a similar scenario.

With Beta software its important we share over here all the bumps to help both fellow users and Red. Lets just hope that @ssholes and people with agendas are not going to interpret these BETA bugs as if they are the end of the world.
 
Im sorry to hear this. I appreciate the information tho. You are keeping it real.

Most welcome Jack, I'm trying to... ;)


Sound advice from a Professional! Thanks for letting us know. This is one of the great things of this community. Keith could have stayed silent and maybe some of us would get hurt in a similar scenario.

With Beta software its important we share over here all the bumps to help both fellow users and Red. Lets just hope that @ssholes and people with agendas are not going to interpret these BETA bugs as if they are the end of the world.
Most welcome Sergio,

and it is because of my exact agreement with those like you that I did posted here, as it is IMO a must do as a service to our community, no matter the cost.
 
Holly crap Ketch! Did it hurt to much the shot? i guess yes since it was the A camera.
Any way to compensate with footage from the other cameras?
 
Holly crap Ketch! Did it hurt to much the shot? i guess yes since it was the A camera.
Any way to compensate with footage from the other cameras?

Yeah It sure did Christian... :(

NO way to compensate as my camera was the only one with the entire building in frame.

But we'll see what my boys got and what my Editor can pull up out of the other 3 cameras one of which He was also the shooter on, not the same for sure.
 
I had the same issue a month ago on my last day of shoot in India.
I was shooting 5K with my Epic-M and HDRx was turned on. I shut down the camera between two takes and when I powered it on again, the LCD was shutdown and I could only see color bars in the EVF.
I had the Redmote with me but I wasn't able to turn off the HDRx with it... Only positive point is that it was an extra day and we weren't supposed to shoot this afternoon.
I came back home the day after and did a force upgrade and everything came back to normal but I can imagine your frustration Ketch... especially if in your case it was a key shot... I feel sorry for you.
This summer I had minor issues with my Epic-M, nothing bad but it was sometimes buggy, I posted some of it here and people told me it wasn't a good idea and that I should only report to Red about that... That's the reason why I didn't mention on Reduser what happened to me in India with the new firmware.
It looks like we shouldn't power down our camera with HDRx activated.
Anyway, hope you will manage to save your shoot Ketch!
Best wishes and happy new year!
 
Thanks Vincent, besides the fact I should hand over my head on a silver plate to my client, I am happy that at list we did get some shots form the other 3 cameras,
just the same the frustration is not something I can put in words, but lesson learned, there is always a first time, even for those like me that prepare for every possible scenario,
and that seem untouchables to any RED issues by many here, I guess I am touchable he he, and BIG time!!

But better on a even Unique shot like this that an other year has to go by before been able to re-shoot then on one of a multimillion dollar Movie shot I am about to embark on this year... ;)
 
Ketch,

Did you ever send the camera logs into RED for an evaluation. Any report back from RED.

SHOuld we just completely stay away from HDR X on this build?

I didn't think HDR X crash the camera so bad, I barely ever turn it on.

David
 
Edit:

Yes David File Log now sent.

I do strongly advise to shoot HDR-X on the release Build, and if you must do so on 2.0.5 Beta build, then be prepared with your Redmote, knowing how to put it to Local and take HDR-X off
so to fix the issue, or at last resort have the SD with the Force Upgrade BUild on it to Re-Install if the camera freezes on you while trying to use HDR-X.
 
No David I didn't.

There is no recorded Log, I shot my last clip, then put HDR-x On set the 4 Stops, then shot off the camera and waited till 15minutes till Midnight,
turn the camera back on and No image on the LCD, only Color Checker board on the EVF, the camera would not Record an image, no matter how many times I shot it down and restart it,
no image would come up, and no way to get it to Record either.

I do strongly advise to shoot HDR-X on the release Build, and if you must do so on 2.0.5 Beta build, then be prepared with your Redmote, knowing how to put it to Local and take HDR-X off
so to fix the issue, or at last resort have the SD with the Force Upgrade BUild on it to Re-Install if the camera freezes on you while trying to use HDR-X.

There should still be a valid log file on the camera - you should send it in to RED support.
 
Thanks Ketch for your valuable input! Great use for a spare 64GB SSD. For those of us stuck without a REDmote for months now... comes in handy the spare SSD with firmware build.
 
Very sorry to hear about this, Ketch, but to reiterate what others have said, thank you for sharing this cautionary tale.

I'm also waiting on a RedMote, so of course I'm curious to know if there would be any possible way to turn off HDRx in such a circumstance using the Side Handle?

On a related note: having a force upgrade handy on a laptop or a spare SSD does seem like a good idea, but having a 64gb SSD essentially set aside (for the truly prepared) seems a little unrealistic for most, if not a bit cost prohibitive. I only have 256gb media, and while such a notion could work in certain circumstances such as Ketch has outlined, it would also be a bit of a juggling act for regular implementation.

This reminds me of the plans Red had mentioned in the past about an SSD->CF adapter...it would be amazing to have a force upgrade saved to an 8gb or whatever CF card that you could save for use in time-sensitive emergencies (especially when you might not have a laptop set-up and ready), without having to take one of your SSD mags out of rotation. I'm hoping they haven't completely abandoned the idea of such a reader, even if it's only real value would be for upgrading firmware, saving and loading camera looks, etc.

Thoughts?
 
Back
Top