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

Forged Weapon killing mags on power up

Brandon Shafto said:
The issue has been recreated on DSMC2, DSMC, Minigams AND 1.8 mags all with the current firmware.
All roads point to latest firmware.

We know you're listening RED, we know you understand the severity of the situation. A little shout-out would help ease our minds. Is help on the way?
Click to expand...

Brandon, please refer to my post earlier in the thread. Tech support and RED sustaining engineering are working with people who have submitted log files and are looking into it.

If there is a meaningful update, I will post about it. While we appreciate you guys trying to piece things together and use data from this forums, please also don't let a hypothesis turn into fact (ie, "issue with latest firmware").
 
Brent@RED said:
If there is a meaningful update, I will post about it. While we appreciate you guys trying to piece things together and use data from this forums, please also don't let a hypothesis turn into fact (ie, "issue with latest firmware").
Click to expand...

Understood - sorry if I've been a part of that, media issues like this just makes me nervous!

Please let us know what you find out. Love peace of mind!

Best
 
Last edited:
Brent@RED said:
Brandon, please refer to my post earlier in the thread. Tech support and RED sustaining engineering are working with people who have submitted log files and are looking into it.

If there is a meaningful update, I will post about it. While we appreciate you guys trying to piece things together and use data from this forums, please also don't let a hypothesis turn into fact (ie, "issue with latest firmware").
Click to expand...

Copy that! Not trying to be "one of those guys". When I see others having same issues, I try to think through it logically. We were tossing around scenarios as to why/what caused said bricking of media. Not trying to create hysteria. My apologies if that has happened.
 
No worries, Dave and Nick. I cannot specifically speak to individual customers situations with repairs, but I can say from the initial review, we have not found evidence of firmware being the culprit. For one customer on this thread, we did have a defective 240GB SSD. Just happened to fail soon after firmware upgrade. And before folks turn from firmware as the monster to the drives, haha, note we test the living crap out of media before we qualify it. But, as with every single piece of electronics on earth, nothing is 100% perfect. We ship a ton of these drives and actual failures (aside from user induced, to note), is extremely small. Like, failure rate has a decimal point at front followed by many zeros...
 
Brent@RED said:
No worries, Dave and Nick. I cannot specifically speak to individual customers situations with repairs, but I can say from the initial review, we have not found evidence of firmware being the culprit. For one customer on this thread, we did have a defective 240GB SSD. Just happened to fail soon after firmware upgrade. And before folks turn from firmware as the monster to the drives, haha, note we test the living crap out of media before we qualify it. But, as with every single piece of electronics on earth, nothing is 100% perfect. We ship a ton of these drives and actual failures (aside from user induced, to note), is extremely small. Like, failure rate has a decimal point at front followed by many zeros...
Click to expand...

Cool! Thanks Brent.

Are there any best practices we should keep in mind?

Ie...making sure firmware formatted on cards matches...firmware on cam?

Similarly...is there anything we should be mindful of regarding shutdowns? Wasn't sure if these power downs were found to be related, but thought I'd ask!

thanks!
 
Brent@RED said:
Brandon, please refer to my post earlier in the thread. Tech support and RED sustaining engineering are working with people who have submitted log files and are looking into it.

If there is a meaningful update, I will post about it. While we appreciate you guys trying to piece things together and use data from this forums, please also don't let a hypothesis turn into fact (ie, "issue with latest firmware").
Click to expand...

Copy. Apologies. Thank you for your hard work. Trust me, we *know* you guys care.

Also, may have been a little drunk when I wrote that...
 
Been a while since I revisited this thread. I did the firmware update that shorty followed my initial post. Though I still tend to pull mags before powering up or, even better, to put in the next mag and then power cycle, I have not had a third incident of the issue. I probably have a couple hundred power cycles on the camera without incident so it does indeed seem to have been a firmware related issue for my camera or at least to have been remedied by the firmware update. Same camera, same power, same mags, new firmware. Or just a ghost in the machine trying to really fuck with me.
 
Last edited:
Joel Voelker said:
Been a while since I revisited this thread. I did the firmware update that shorty followed my initial post. Though I still tend to pull mags before powering up or, even better, to put in the next mag and then power cycle, I have not had a third incident of the issue. I probably have a couple hundred power cycles on the camera without incident so it does indeed seem to have been a firmware related issue for my camera or at least to have been remedied by the firmware update. Same camera, same power, same mags, new firmware. Or just a ghost in the machine trying to really fuck with me.
Click to expand...

Great to hear Joel. Keep us posted!
 
Hate to bring up an old thread, but is Erich having this old issue?


Erich Roland said:
Ive had a problem already if anybody has any idea's.

Went out this am to collect some clips for you guys around DC. The mag formatted fine, and the first few clips I had played back and everything was working properly, so I shot a bunch more. Eventually the battery ran out and the camera shut down, but I'm pretty sure I was not recording at the time it shut down but I could be wrong. I didn't think much of it (seen it happen many times) and changed the battery. With the new battery I turned the camera on and got a warning "media not formatted for this camera". I changed the media, formatted the card and made a few more shots. I get back to the office and sure enough that first mag wont mount, with the same kind of warning. Any idea's how to "repair" or "retrieve" the work?

Edit; working with redundead, not sure yet if all that work will be avail or not.

Thanks, Erich
Click to expand...

I was hoping the power down leading to mag issues...had gone away...but it looks like it hasn't?

Any ideas how to work around this?

Is it related to the batteries being used? Ie do batteries need to have a built in "RED" protocol to warn the camera before a shutdown?

Love to get some definitive answers on this!
 
My issue didn't have anything to do with the camera shutting down because of low voltage; it happened with a standard battery swap too. It seems to have been fixed by the firmware update shortly after I started this thread.
 
Looks like another example of a mag getting bricked after a powerdown.

Not sure what firmware David was on, I've asked him to check.

David Blair said:
Hi guys,

So we had a bricked 1TB minimag this morning, our Woven 6K Weapon shut itself down while recording, then when rebooted doesn't recognize the mag. My PC can't see it either. Just filed a report so I'm sure it will get itself sorted, but the dangers of single-mag recording have made themselves very apparent.

So now I'm now looking into dual-recording options. There doesn't seem to be a module with an extra mag slot on offer, so I guess an external recorder + SDI out must be the way to go. That's disappointing from a keeping-the-rig-super-compact perspective, but we just can't take the chance that this will happen again.

What solutions have others found that work for them?
Click to expand...
 
Thanks Nick, my firmware was 6.2.51. A bit old sorry, should have been on top of that earlier. Good to know that the issue may have been resolved there.

I'll give REDUNDEAD a go this afternoon to recover the footage from this morning.
 
David Blair said:
Thanks Nick, my firmware was 6.2.51. A bit old sorry, should have been on top of that earlier. Good to know that the issue may have been resolved there.

I'll give REDUNDEAD a go this afternoon to recover the footage from this morning.
Click to expand...

Awesome. Let us know how it goes!
 
Certainly hope it's not the same issue I had! Firmware update will hopefully fix things for you. The newer firmware updates have some great UI speed improvements.
 
Just to chime in about my issue which seems to not be the same as most of the others having the "card not formatted for use in the camera. I started a thread today describing in detail what happened to my Weapon:

1) My weapon is 3 days old.
2) The latest firmware installed
3) Two brand new 512gb mini mags, both formatted thru the DSMC
4) The camera was NOT powered down when the error occurred.
5) We had just changed lenses. Pushed the record button for another shot and received the "message" and lost 430gb of footage on mini mag #1. Ran redundead on it stated that it wrote ( recovered 184 clips ) which ended up meaning IT ONLY recovered the first frame of each file and the 2nd frame was corrupted on all 184 clips thus losing 9 hours of 2nd unit.
6) ejected the media of mini mag #1, powered down and after booting up, inserted mini mag #2 and after one take IT received the same message and we lost that one clip.
7) The next morning had Keslow camera in Chicago reinstall the newest firmware and it happened again.
8) I do not use V Mount. I use gold mount with Swiftronix batteries.

So, the issue is not constant for any of us. I doubt both of my mini mags would be corrupted since they each were brand new ( 2nd day of shooting with them. IT has to be in the DSMC and evidently it is not an isolated issue. My 3 day old Weapon is rapt Red in Irvine, Ca. I submitted the log txt files for both mini mags.

The he fact that as users many of us have to live with fear of losing our "work" is not right OR fair. I had to re-shoot an entire day of footage and it cost me over $9,000 in location fees , permits, extras and crew for a brand new Weapon with less than 35 hours of use.

i truly wish that I was the only one that has suffered this issue but evidently I am not.
 
Roll back 1 firmware release version, the latest release is causing all sorts of issues
 
Jake Wilganowski said:
Roll back 1 firmware release version, the latest release is causing all sorts of issues
Click to expand...

That may help.

But the issue that mags can suddenly corrupt is still present.

New firmware is clearly not helping.

Brand new DSMC2 brains are similarly affected
(Chris's Weapon and Erich's 8K Helium were in their infancy when errors popped up this month).

This entitre situation is terrifying for numerous reasons:

1) New firmware did not address this issue - though it was supposed to.

2) New scenarios are popping up - its no longer an improper shutdown, now LENS CHANGES can perhaps be a trigger?

But of course, neither reason should matter. When you pay 50K for a camera, you expect a TANK. It should withstand anything. My old Epic Dragons with OLD firmware are tanks. These new "quirks" feel very UN-TANK like.

Id love some official word from RED.

Worth noting no one with a Raven or Scarlet-W has chimed in yet with an issue.
 
Last edited:
Nick Morrison said:
That may help.

But the issue that mags can suddenly corrupt is still present Two brand new perfectly formatted mags in my case

New firmware is clearly not helpi. My camera 3 days of use) has only run with the new firmware so I cannot comment on the previous firmware versions
Brand new DSMC2 brains are similarly affected Correct
(Chris's Weapon and Erich's 8K Helium were in their infancy when errors popped up this month).

This entitre situation is terrifying for numerous reasons:and something Red needs to address and tell us.

1) New firmware did not address this issue - though it was supposed to helped some that have had issues but not all It seems to have helped some camera but based on other board members the new firmware seems to the the reason this is happening NOW

2) New scenarios are popping up - its no longer an improper shutdown, now LENS CHANGES can perhaps be a trigger? With no shutdowns in my case it happened twice with two different 512gb mini mags simply from changing a lense.

But of course, neither reason should matter. When you pay 50K for a camera, you expect a TANK. It should withstand anything. My old Epic Dragons with OLD firmware are tanks. These new "quirks" feel very UN-TANK like.

Id love some official word from RED. I do NOT think they know. Each case is different . There does seem to be some similarities. Most occur with the 512 gb mini mags.

Worth noting no one with a Raven or Scarlet-W has chimed in yet with an issue.
Click to expand...
a total loss of if this issue/problem was something that was only an inconvenience most if not all of us could deal with it. However when this issue causes a total loss of clips/ images / data / a day's work this is totally unacceptable.
 
You must log in or register to reply here.
Back
Top