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

Scarlet dropped frames

A

Alex Veitch

Well-known member
Joined
Jun 16, 2009
Messages
118
Reaction score
0
Points
0
Location
UK
Website
www.alexveitch.com
Hi All

I've just found that a project I worked on suffered quite a number of dropped frames. I'd had this on an earlier firmware but had thought that the problem had been resolved. The issue can be seen in the R3D frame grabs, there are various frame grabs in the following folder (sorry, couldn't get R3D attachments to upload): http://alexveitch.com/red/

I am now running the latest non-beta, and to my knowledge haven't had the problem since. However, any advice on what might have caused this, and how to avoid it again, would be appreciated.

At the time of shooting, camera was being handheld (but it was still a relatively static set up, no running about). I used 8:1 4K, 25 FPS. The download was to two drives (but done separately, both show the error). ONe was connected by firewire, the other connected via eSATA. I don't have the original card anymore but don't have any reason to believe the error would be in the transfer, as its in the same place on both copies, and the transfer was managed with Shotput Pro.

Any thoughts? As mentioned its the second time I've had this issue so I really need to know that I'm not going to be suffering the issue as more work is coming for the camera.Equally, I've not been alerted to this on any more recent work, but don't want to come up against the same situation in the future.

Thanks all in advance,

Alex
 
The only time I experienced damaged data was with a rented Epic on a very hot summer day where it was exposed to the sun constantly and probably ran too hot at some point.
 
The strange thing was, it was the first card of that day's shoot and the only time on that job when I'd had an issue. Hmm.
 
Maybe the connection to the redmag wasn't 100% stable. Causes could be dust or a hit to the redmag while shooting or maybe your SSD-side-module doesn't sit perfectly tight.

You did format the REDMAG in camera, not just deleted files (or formatted it) on a computer, right?
 
Hi Maik

Yes, I did - cards are always formatted in camera. Its odd that it was just that card, that does make me wonder if it was a connection. Yet it worked perfectly well later (and since). Perhaps as you suggest its dirt / dust based interference?
 
Bump... Its happened again. Tripod mounted, not running hot, and contacts etc cleaned. Is this looking more like a service issue?
 
And again... downloading to a different computer, different cables, different cards. Same issue - corrupt frames.
 
You must log in or register to reply here.
Back
Top