Reuben Evans
Well-known member
Did you try booting up the camera on without the media, and then inserting the media to see if it would read? This process worked for me when I saw the issue.
Welcome to our community
Be a part of something great, join today!
A Weapon of Destruction..... has this issue occurred to any other owners/operators?
- Thread starter Chris Angelich
- Start date
Nick Morrison
Well-known member
- Joined
- Nov 9, 2011
- Messages
- 9,141
- Reaction score
- 50
- Points
- 48
- Location
- Brooklyn
- Website
- www.smallgiant.tv
We did not. We were nervous to leave the mag in the cam.
I can ask Scott to test in the morning.
Nick Morrison
Well-known member
- Joined
- Nov 9, 2011
- Messages
- 9,141
- Reaction score
- 50
- Points
- 48
- Location
- Brooklyn
- Website
- www.smallgiant.tv
Reuben, answer to your question is here:
http://www.reduser.net/forum/showth...illing-mags-on-power-up&p=1667636#post1667636
Kenneth C Merrill
Well-known member
I cannot believe this isn't getting more attention. I haven't heard of another camera that you must remove the media to boot...
- Thread starter
- #45
Chris Angelich
Member
THIS in a nutshell sums up MY view also. I would gladly however remove the media each and every time IF that was an assurance that it would not cause a loss of data but it my case we lost all the media while changing a lense and not powering up/down...........so its not a consistent pattern at all.
Kevin DeOliveira
Well-known member
Any news on this? I've been trying to watch for updates, seems quiet.
PatrickFaith
Well-known member
- Joined
- Nov 4, 2011
- Messages
- 2,560
- Reaction score
- 0
- Points
- 36
- Location
- California
- Website
- www.pudls.com
I am pretty sure they are fanatically working on this. My woven is coming back from the time code/battery thing ... seems like they have that figured out. Weapon is just a totally new system with tons of new parts and interfaces, is actually more stable then I was expecting given the extreme rate of innovation at red. I do hope red mellows a bit on extreme innovation and focuses on volume production and stability for a year.
Antony Newman
Well-known member
Suggestion for RED.
In RED apps that mount RedMags on Desktops - introduce levels of reporting that users can Opt into:
Level 0 : No reporting (current behaviour)
Level 1 : Error Summary (Eg 1KB Error report) : Automatically sent to RED if PC is connected to internet
+) Searches through last week of Log file on REDMAG
+) Extracts minimal details and sends to RED (only if any issues occured)
+) Gives RED a 'pulse' if there are new issues introduced / or if all occurrences of a patched issue have been fixed.
+) Suggest this is the default for Release builds
+) Add option during camera startup that performs a 'log dump' (might add 0.5 secs to startup).
Level 2 : In Depth Reporting (eg up to 1MB Report): Automatically sent to RED if PC is connected to internet
+) Searches through last week of Log file on REDMAG
+) Extracts full logs of Login session that resulted in an 'unexpected error' or 'crash' - then sends to RED
+) Gives RED a large number of data points, patterns, to help determine any new issues
+) Gives RED rapid feedback that patched issue are have not recurred.
+) Suggest this is the default if on BETA builds
+) Suggest that Users on BETA are also given a tally of issues submitted to RED.
+) Suggest that on Beta Builds, there is a Startup option that Defaults to dumping logs onto the RedMag.
I would expect a fair proportion of Release users and Beta testers would opt into such an endeavor - useful for people who do hit unexpected issues, but do not want the 'manual overhead' of extracting a log report and having to 'manual email' it to Red.
AJ
In RED apps that mount RedMags on Desktops - introduce levels of reporting that users can Opt into:
Level 0 : No reporting (current behaviour)
Level 1 : Error Summary (Eg 1KB Error report) : Automatically sent to RED if PC is connected to internet
+) Searches through last week of Log file on REDMAG
+) Extracts minimal details and sends to RED (only if any issues occured)
+) Gives RED a 'pulse' if there are new issues introduced / or if all occurrences of a patched issue have been fixed.
+) Suggest this is the default for Release builds
+) Add option during camera startup that performs a 'log dump' (might add 0.5 secs to startup).
Level 2 : In Depth Reporting (eg up to 1MB Report): Automatically sent to RED if PC is connected to internet
+) Searches through last week of Log file on REDMAG
+) Extracts full logs of Login session that resulted in an 'unexpected error' or 'crash' - then sends to RED
+) Gives RED a large number of data points, patterns, to help determine any new issues
+) Gives RED rapid feedback that patched issue are have not recurred.
+) Suggest this is the default if on BETA builds
+) Suggest that Users on BETA are also given a tally of issues submitted to RED.
+) Suggest that on Beta Builds, there is a Startup option that Defaults to dumping logs onto the RedMag.
I would expect a fair proportion of Release users and Beta testers would opt into such an endeavor - useful for people who do hit unexpected issues, but do not want the 'manual overhead' of extracting a log report and having to 'manual email' it to Red.
AJ
Nick Morrison
Well-known member
- Joined
- Nov 9, 2011
- Messages
- 9,141
- Reaction score
- 50
- Points
- 48
- Location
- Brooklyn
- Website
- www.smallgiant.tv
I believe Scott sent his mag in to techs at RED.
I'll check in now and see if there's an update.
Elsie N
Well-known member
- Joined
- Oct 31, 2009
- Messages
- 6,658
- Reaction score
- 0
- Points
- 0
I read from a OS guru to never let your computer upload updates when they are released... wait a while so that others can discover any missteps and give MicroSoft (in this case) a chance to fix any problems.
May be the best approach to buying cameras... don't buy when first offered. Wait until all the glitches are fixed.