Welcome to our community

Be a part of something great, join today!

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

Build 16 V3.2.1 playback and record codec error to CF only

Brian Broz

Well-known member
Joined
Dec 28, 2006
Messages
457
Reaction score
0
Points
0
Website
www.brianbroz.com
Hi,
Yesterday we were shooting a PSA on RED build 16v3.2.1 4K 2:1 23.98 Redcode 36 (and 28) to RED branded 8GB CF. Tested the new build the previous few days with no codec errors/issues whatsoever (on several cards in several locations). The fact that we were fighting light in a field at sunrise (4:30 AM !) didn't make it as easy as usual to troubleshoot.
While having these problems the camera was mounted to a Steadicam that was both downconverting (via AJA box), transmitting with a Modulas (that was underneath the camera at the front of the Rig. Also in operation was a FIZZ wireless follow focus (controlling cam via RS232). The RED battery was powering the Steadicam rig, RED camera, AJA box, focus motor and RED LCD.
A large power draw for sure, but the Steadicam operator had worked with RED before.
The first 4 cards we shot were full of record or playback codec errors. Alot of the clips simply had no QT reference files or they would play back black/dark green in QT. When you would open the .R3Ds in REDcine the application was crashing constantly. Camera was indicating it was dropping frames. In camera playback (when it worked) was often displaying a mirrored or reflected image of talent that was blue. Almost like a lens reflection but only a blue reflection, displayed on the right side of the image.
Re-booted the camera appox 8 times, unplugged all cables waited 10 secs before re-booting. Tried shooting Re-set/initialized the camera and still no improvements. Switching to REDcode 28 didn't help.
That is until we switched to RED drive. Once we switched to the drive (which the Steadicam op only wanted to shoot CF) all our problems went away. Although we lost our really gorgeous sunrise light everyone was happy at this point.
When we caught a ferry to our next location I re-formatted one CF card and no issues or problems (without any of the Steadicam extras).
So does anyone have any idea why a Modulas, Preston FIZZ, AJA downconverter, or possibly a high power drain from powering everything from RED would cause issues recording to CF only?
It made for a rough start to the day but all was fine in the end. I'm just trying to troubleshoot after the fact so that it won't happen on the next shoot!
 
Can you send me the log files asap? (d e a n a n - a t - r e d . c o m)

Was the codec error warning showing up on the camera?
Are the cards being ejected or just pulled?

Thanks.
 
Hi Deanan,
Cards were always ejected. Codec error warning was showing up on the camera. Both playback and record codec errors. I think there were only one or two instances of record codec errors but mostly playback errors.
Not at my computer till the evening but will send log files tonite.
 
Well, yesterday I shot 4Kraw redcode28 and the camera gaved me that same redcode error on the CF card. Build 15 though.
The redbrick batery was only with powering the LCD, the camera and the CF...
Cheers
Carlos Filipe
Portuguese Avid|DS Operator
RED ENG
 
You might suggest that your operator power all the accessories from his sled power, i.e Modulus, FIZ, AJA etc. and power only the camera from the Red battery.

Been operating as such for three weeks, recording to drive, Build 16 without dropped frames, its been very solid.
 
Hi Deanan,
Cards were always ejected. Codec error warning was showing up on the camera. Both playback and record codec errors. I think there were only one or two instances of record codec errors but mostly playback errors.
Not at my computer till the evening but will send log files tonite.

Thanks Brian. The log files will definitely help.
 
Hey Brian and Deanan,

i had strange problems with CF as well. 4K 25fps 16:9 RC28 @ CF

one particular card
-> _codec_error then _playback_error_ then _internal_error and _file_clip_error...

Changed the card and was ok. Can Codec_errors be triggered with BAD CF card? We already have 3 faulty cards from RED out of 8! Got another Lexar cards and they are pretty solid holding. (we shoot around 40 cards per day...EDIT: turnaround...) The files are usually damaged if there is playback_error

As well I noticed weird thing. We have two cameras 1649 & 1650. we set them side by side, upload firmware 3.2.1, blck shade them, put the same lens on (Zeiss 25mm) and connected to our Panasonic monitors. One camera (B) is looking significantly cooler then (A) and (A) is more saturated then (B). If I check ALL settings, everything is set to default on both cameras. Including ASA, WB, TINT, COLOR...LOOK all you imagine is identical. Then change outputs, switch monitors, switch lenses. Still (B) is blueish and (A) is little more saturated. Is there possibility that these cameras are not same on output or in chip?
Truly I didn't check files in RedAlert yet. But if I will find different results what that implicate?

OPLF? Mysterium Sensor? Inside settings? Output? A/D?
 
Hi Martin,

I would try restoring settings on both cameras and then restore the black shading. Then try redoing the black shading on both.

Regarding the CF problems, if you could send the log files that would help diagnosing the problems. It's hard to tell if it's a CF problem or if the problem is elsewhere.
 
It's in the black shading menu. I forget the wording of the menu selection exactly.
 
Hmmmmm

Ok - we are having very similar problems (although we are not running any powered accessories on our cameras) - here's the story.

Currently testing 2 REDs ( #1103 and 1124 ). Both have been upgraded to B16 3.2.1 and we are recording to RED 8GB CF Card RC 28 4K 2:1 24fps (specifically because we are doing a film out test). RED 1103 has been performing perfectly. RED 1124 has been giving us intermittent playback errors. These errors do NOT show up as codec errors during recording - they show up in playback and looking at the structure of files on the CF card something seems to be going amiss. Posted is a snapshot of the CF card file structure in the Finder. As can be seen - thing dont look as they should. CF Cards are always formatted in-camera and unmounted when removed. Deanan - I will email you the log file for your reference.

When opening proxies all we get is green screen in QT. In REDALERT or REDCINE (and yes these are all the latest versions of everything - we only performed the upgrade 2 days ago) the clips just appear as black.

So obviously there is some issue going on. We will try using the REDDRIVE on 1124 today to see if the problem continues. BUT the real question is - is there any way we can resurrect the file structure on the CF cards to get these clips working? We dont want to junk them because there were some beautiful shots on there.

Any help would be greatly appreciated. :help:

Thanks

Cam
 
ozcam it seems we have the exact same issue. Some folders are missing quicktime reference files as well as the green screen playing back in quicktime.
The CF module is working fine now...so either the issue is intermittent or something weird was happening (on the shoot yesterday) with RF or maybe with the RS-232 port that was triggering start/stop?!
 
Ozcam, If you can upload the shots for us, we'd like to take a look at them along with the logs. Do all the clips on the card look bad or just some?

Brian, same thing, we'd like to look at the logs. It is possible that the rs232 could be triggering in a strange way.
 
Thanks - Deanan - I'll try to sort out an upload for you.

None of the shots from this card will play. We tried the card in both cameras. And same result on 2 different MBPs.

Only powered attachments to our REDs are the LCDs.

Thanks for getting back to us.

Cam
 
Just done a few tests and managed to get the error only when using Compact Flash, not with the RedDrive. When I was shooting I got an "Internal Error" message when I hit record. The playback problem seems to exist at the same point I got this error. I shot 10 shots in total, number 5 was the problem - As I scroll through the shots in playback it gives the codec error when I get to shot number 5. I then shot another shot and number five was still the problem so I personally think it's linked to when an error occurs during shooting. The error message didn't stay for long on the screen. I couldn't replicate it either, I thought it was possibly to do with pressing the record button too quickly before post had finished or something.

Log file attached.

Paul
 
Bit more info...

Quicktime for shot number 5 shows green, RedAlert! shows black and RedCine won't load it. All other shots seem fine.

I have a zip with the problem file that I'll happily email to whoever needs it, PM me an appropriate email address.

Cheers
Paul
 
Out of interest... It is possible to simply delete the problem shot and playback earlier files from the camera.

Paul

EDIT: Delete the shot from flash card using computer of course!
 
Paul,
Your point of pressing the record button too soon after stopping the last recording is an interesting possibility. As the camera was being triggered wirelessly from the Preston FIZZ there were a couple shots that were only a second long that seemed like unintentional records. These may have happened milliseconds after a good shot...hard to say.
Again, I didn't have the luxury of being near the camera during shooting (to keep an eye) as it was a 360 steadicam shot.
But I would think being trigger happy (accidental or not) especially being wireless is worth looking into. When I shoot each clip has a definite start and stop (as I press the side record at the start and end of each take) whereas with a wireless trigger you can hit the button several times and not even notice it (?) even though I can't be blamed for that :-)
 
Back
Top