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

Some clips playback in camera, but OFFLINE in RCX

A

Anthony Melton

New member
Joined
Feb 8, 2013
Messages
2
Reaction score
0
Points
0
Hi There, I've got a problem, where by some clips shot onto SSD (128GB) with RED Epic will playback in camera, but appear as OFFLINE on RCX.

This is true when the clips exist on the SSD (128GB), whole card induced to LOCAL, clips ported out to different card.

Clips will play on camera, even if you push them back to the camera on another SSD (128GB).

I've tried REDundead with no success. When I run REDundead and set it's source as the SSD mounted in a REDMAG and its destination somewhere on my MAC... Terminal quickly responds Done! as if I attempt to set both source and destination to a local directory. If I mount a disc image and place the card contents there, I can point REDundead at the image and it runs successfully but only copies the files to the destination which then continue to appear as OFFLINE in RCX.

RED Data manager cant find anyfiles on the SSD through the REDMAG either?

I have read that this can be due to finder thinking the file is called one thing and then the data within the R3D file say another... this is not the case both the file name in finder and the two text instances of the file name within the R3D file are the same.

Can anyone think of a solution or just an explanation as to why I can view the files in camera and succesfully output them via HDMI to a 1080p monitor?

I've tried just about everything? Read just about everything in this forum.

Mystified, surely this file is recoverable being as it can be played in camera.

Thoughts?
 
Having the same issue!

I shot a scene yesterday at a local restaurant. 18 video files in total. SSD 64 GB. The issue is with the last file. It plays fine on my Scarlet-X but on REDCINE-X build 17.26437 64-bit Windows version I get an OFFLINE message on the thumbnail previews. Tried copying it to different local HDDs to no avail. No program would read it, even directly off of the SSD via REDMAG.

HELP!!!

*UPDATE- Opened tech support ticket*
 
Last edited:
Play the file out of camera & record to a pix 240 or Atomos or BM Hyberdeck. It will not be raw but at least you'll have it.
 
Mike:

Thanks for the tip, but that's a workaround. Unfortunately, I don't have an external recorder because I only work with RAW. I opened a RED ticket support to shed some light on these. If there is a solution I'll share it.

Mike Garrick said:
Play the file out of camera & record to a pix 240 or Atomos or BM Hyberdeck. It will not be raw but at least you'll have it.
Click to expand...
 
I had the same issue after upgrading to firmware 4.0.10 (not the BETA version).
It happened to all clips larger than 4GB. The camera would separate the clip into clip # .001 (4.03GB or so) and .002 (rest of the clip),like it always does, but it left the first (larger clip) corrupted. It plays in camera but RCX or Finder can't read it. The second clip reads fine, but it contains only the end of the clip. It seems to be a clip spanning issue.
I went over the issue with RED support,they couldn't solve it but did offer to try to attempt to recover the files.
I reverted back to firmware 3.2.21 and my camera works fine.
 
I have also experienced a similar issue after upgrading to firmware 4.0.10.

32 of 99 clips on a Mag were reporting as offline after ejecting. They also appeared as offline in Redcine-X. When inserted back into the camera, the same 32 clips would not play back (they previously had). The percentage remaining value had also changed to 45%. The Mag was ejected at 22%.

After trying different SSD readers, cables and computers I tried REDundead and was able to recover 31 of the 32 clips. The first of the offline batch was the only one I was unable to recover.

I did also submit a support ticket to RED (who responded within minutes). They suggested after a short dialogue to send the Epic body in for testing.

No problem was found with the body or related Mag.

RED support suggested it was good practice to do a "Secure Format..." on Mags after a firmware update. (Secure format is available under "Utils...", the button to the right of "Format Media...")
 
Hello all,
we get the same issue but the Scarlet is running on version 4.0.12, do somebody know if the bugs concern to this problem has fix in the newer version?
Thanks,
 
You must log in or register to reply here.
Back
Top