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

Epic File Glitches - Anyone run into this?

had exactly the same issue with my scarlet....it has been with RED for over a month now, several levels of QC...now an internal part has to be replaced and the whole thing tested again....do a search in the forum....corrupted files....this is in camera....
i had the issue on one shoot, with one mag, which led me to believe it was NOT the camera....sent it in anyway...after several levels of testing turns out it IS the camera....
and btw: i had the camera for about a month only to hand it over again to have it fixed....and it has been over a month now.....
 
paul schefz said:
had exactly the same issue with my scarlet....it has been with RED for over a month now, several levels of QC...now an internal part has to be replaced and the whole thing tested again....do a search in the forum....corrupted files....this is in camera....
i had the issue on one shoot, with one mag, which led me to believe it was NOT the camera....sent it in anyway...after several levels of testing turns out it IS the camera....
and btw: i had the camera for about a month only to hand it over again to have it fixed....and it has been over a month now.....
Click to expand...

Sorry to hear about your experience Paul. After all Red cameras weren't created by God. They can go wrong, they do go wrong like any other camera can go wrong. But the good thing is it really is, generally speaking, a very good camera with good service. I'm sure it won't be long before you get your camera back.
 
I have seen this, not for awhile. Re-booted the camera to factory, changed media, worked. I made sure to monitor after every shot. Could have been that the card was not fully seated as well. New Build seems to work.
Axl
 
I appreciate the conversation here. The client says that the glitch is on every file, which would have been over multiple cards. I still have two of the cards from the shoot with the original material on them. As I said, I tried to recreate their problem...copying the material over to one of my home drives, transcoding it with RCX-Pro. No problems. Missing parts to the recreation...I don't have their original drive, no was I able to use their media encoder. Perhaps it could have been the copy method, which did only go to one drive (bad form). I agree that I need to "own" the transfer process, as to not have these issues in the future. What types of transfer/verification utilities would be recommended?

Also, I have opened a ticket with Red, waiting to send them my log file.
 
Adam White said:
I appreciate the conversation here. The client says that the glitch is on every file, which would have been over multiple cards. I still have two of the cards from the shoot with the original material on them. As I said, I tried to recreate their problem...copying the material over to one of my home drives, transcoding it with RCX-Pro. No problems. Missing parts to the recreation...I don't have their original drive, no was I able to use their media encoder. Perhaps it could have been the copy method, which did only go to one drive (bad form). I agree that I need to "own" the transfer process, as to not have these issues in the future. What types of transfer/verification utilities would be recommended?

Also, I have opened a ticket with Red, waiting to send them my log file.
Click to expand...

The routines I have outlined should be pretty good at taking out transferproblems....

R3d manager checksum copy to 2 drives + visual runthrough or transcode before erasing cards....
 
Adam White said:
As I said, I tried to recreate their problem...copying the material over to one of my home drives, transcoding it with RCX-Pro. No problems.
Click to expand...

Adam, if you can't recreate the issue by playing back the files in camera or in transcode the corruption most likely was caused during the transfer. It's also possible that there's something funky going on with your client's system. If it's only happening on one system I'd start there (try transcoding from a fresh data copy, make sure all builds are up to date, etc) and work backwards to find the cause.

I second Gunleik's recommendation to use R3D Data Manager (I have no affiliation with them). It will slow things down a little, but it's still much faster and less costly than a reshoot.

For the posters insisting this is in-camera, there's no logical evidence to support that claim. Corrupt R3Ds look the same regardless of where the corruption occurred.
 
My scarlet had the same problem. It was the camera and has now been repaired. Gunliek makes excellent points about responsibility and file transfer procedures but if you read the many posts on this forum showing the same corruptions you'll find that it is no need a camera hardware problem and needs to repaired.
 
Mike Lary said:
For the posters insisting this is in-camera, there's no logical evidence to support that claim. Corrupt R3Ds look the same regardless of where the corruption occurred.
Click to expand...

Absolutely.

Indeed, the fact that the OP says he still has cards from the shoot with the media on them, and they are not showing the issue would seem to be fairly conclusive evidence that the issue was not in-camera.

Just because a small number of people (out of the very large number of RED cameras out there) have experienced corruption due to a particular issue does not mean every issue is the same.
 
Again pointing out that I am not in denyal, but that it is an excellent idea to rule out transfer bugs before blaming the camera...
And the point that the non-erased files playback fine, is pretty conclusive... :-)

@Matt.
The messups look the same wherever they happen, it seems.
Smart, then to take controll over what you can controll (which is everything post "record")

Cheers
G
 
Adam White said:
Hello,
My last job (shot on my Epic at 4K) seems to have had a problem after I gave it to the client. As we shot, I transferred each Red Mag to the client's HD via my laptop. Each 128GB mag was only shot to around 60% capacity, just to improve the download workflow. I spot checked a couple of files there at the job with RCX-Pro, just to make sure all was good, which it was. A few days later the client said they were getting glitches on each file, while RCX-Pro 16 was crashing during transcoding more than one clip at a time. I have attached the client's glitch example.

So, anyone ever here or see such a thing before? I have not had any other problem like this, nor was I able to replicate the problem at home with a mag still containing the client's footage.

Thanks,
Adam
View attachment 33302
Click to expand...

Ok just heard back from RED Europe and my Scarlet needs a new board. Should have the camera back by next week. I really hope this is not a weakness in the camera's architecture and just a defective board, as I've only had it for 11 months... Most of the comments I have read here seem to be one-offs.
 
Antonio Ribeiro said:
Ok just heard back from RED Europe and my Scarlet needs a new board. Should have the camera back by next week. I really hope this is not a weakness in the camera's architecture and just a defective board, as I've only had it for 11 months... Most of the comments I have read here seem to be one-offs.
Click to expand...


glad you get it fixed!
 
I had seen plenty (4-5 times, thats a lot for my standards) of these glitches back in the R1 days and they were all in camera and not replicable.
 
Hello,
So, here's how it all shook out. I started a ticket with Red, having sent them a log file and r3d snapshot of the corrupt frame. After looking through the log and checking out the frame, Red could find no fault with the camera. Which is what I suspected, since I had the original footage on on of the cards, and could find no problem with it.

I met with the client, and we tried an experiment. First I looked at his corrupt shots on my laptop through RCX. Yep, they were corrupt. So, we tried to replicate the problem: copying a card - same card, reader, laptop, cables and drive. No deal. We could not re-create the problem. The material copied just fine into a test folder.

The result of all of this? Here's what we learned: two weeks ago, in a climate controlled studio, on house power, we had a copy error of every file. What we do not know if why: constant surge in their power? laptop was searching for a wireless signal? ghost in the machine? any of the above....

The only moral of the story is to be more vigilant. 1) enough cards to not have to recycle them during the shoot day 2) watch the copy files, beginning to end 3) shut down all operations on the copying laptop during copy operations 4) use a check-sum copy utility, instead of the drag-n-drop method of copying. Like I have said before, this is the first time there has ever been an issue. I have since shot with the camera, and not had issue.


These new steps must be taken just for all to have confidence and peace of mind. In this world of digital cinema, there are always folks who are skeptical of the new, especially out here in the midwest. All we have is our reputations. The most we can do is ensure confidence in our next gig.


Adam
 
Adam,

Had the exact same issue with a client. 95% of jobs I take the RAW data transfer on my laptop then transcode at home using my tower with RR. A little painful but I control and it makes the whole process painless for the client. The one exception the client insisted they knew how to do it then only made one copy of the camera SSDs then did not look at the data for two weeks. Not a single shot was playable. When I asked who was responsible for the data transfer it turned out it was the work experience kid with his personal laptop. It was never going to go wrong was it?

At a minimum if no data wrangler use your own laptop and HDDs, there is always time to check on the copy if one or two shots playback in Redcine, when there is a minute you can always check playback in camera as well, make two copies of the original drive and if time allows use a checksum programme. Thats my approach anyway. Data is like motorcycling. Trust nobody.
 
You must log in or register to reply here.
Back
Top