POST error - Record/post stuks

[Lucas]

Hi friends!
Somebody knows what does POST when you stop recording means?

I have the same trouble with this. The camera is a Build 15, recording on RED 8Gb CF cards. I´ve made a 4K 2:1, 24P, Redcode 36 project.
I started shooting one short clip that I cut to save memory and stops normally, then I push the back trigger again and the car goes. When it comes back, the display says: POST, 5 drops, Memory 2, the tally was ON and nothing works except Video menu.
I restart, change the CF, format it. And start shooting. The camera comes back showing tally ON, POST, 9 drops, don´t remember how much memory, and I cant stop it!!! I turn it OFF to unmount, I copy the CF to the Mac Book and I found that I have no QT (it was checked on) but I have 4 R3D files that weighted 7.1Gb
Then I mount the camera again in a truck, start shooting... stop... Ok!!! Playback and everything OK. Second shot at 6 fps starts... stop... Ok!!!

Then we go to the crane, same way to mount it, same proyect and the same trouble with the record/post stuck , I´ve tried whith 2K, changeing CF, formating 4 diferent CF cards, power cycling, restoring everything, pushing the side trigger, etc.

The sun cames up and two clips were done.

I´m sad.



Lucas Mormandi

[Deanan]

POST means post (as opposed to pre) recording functions like creating the quicktimes. Please contact support about this as there could be something up with your CF writer module. Check to see if you have any bent pins on the module also.

[Brent J. Craig]

POST stays on the screen for a long time after you cut when the camera has dropped frames. Today was my first experience with it staying on indefinitely and requiring a reboot as well.

Build 15 2.2.5, 2K 2:1

This only seems to be an issue with very new 8G cards (received in the last 6 weeks). Has anyone else seen this?

It'll be nice when my favorite rental house signs off on Build 16. Rumored to be next week.

[Lucas]

Thanks guys!!!
I´m going to check this possibilities with the owners tomorrow.

Lucas Mormandi

[Errol Afed]

I had the same problem with our camera, the guys from Red advised me to reinstall the firmware but still the same (Build 15, latest version). I read somewhere about disabling the QT proxies so I did and I still had the same problem. I was using 8GB cards, our drives haven't arrived yet. I had to send the camera back to Red. Now it's working fine so far, I asked Red what the problem was but have not yet gotten an answer. Funny thing is everytime this happened I would have to boot 2 to 3 times cause the menu buttons would not work.

[Esteban Sosnitsky]

I think this issue could be related to the fact that you cant record in RC36 on cf cards in 4K, only RC28. I would try to set the project to that setting and try again after formatting the CF card. Deanan could you confirm this please?? I downloaded the iSee4K and when those settings are applied the max frame rate is 0. Try that and let us know.

[Errol Afed]

When we experienced the post error, camera was set on RC28 and the post error would happen whether I was shooting 2K or 4K. Every time it happened I would have to change the card since the card inside the camera is not recognized anymore.

[Cüneyt Kaya]

its a broken cf module....you have to get a new one

[Filipo]

Its broken ! I had that problem.

[Stephen Pruitt]

Yep. . . your CF card reader/writer module is shot. . . we just replaced ours. . . very frustrating. . . ours was so intermittent it was ridiculous, but RED sent us out a new one and so now we're good as gold.

As for shooting with Redcode 36 on CF cards? We shot an entire feature film on 8gig cards at Redcode 36. We never once moved to Redcode 28. It works perfectly.

Stephen

[Deanan]

The occasional stuck in post error is fixed in B17 beta.
Please try that version.

[Esteban Sosnitsky]

Deanan, can you actually record with this settings?
4K
36 RC
2:1
24fps
to a CF Card? If so I gotta write to iSee4K to fix that!
Thanks.

[Stuart English]

can I record with this setting to a CF card?
4K
36 RC
2:1
24fps


Not to an 8GB CF card, you would need a RED 16GB CF card or RED-RAID.

Change to RC28 and the answer is yes.

For more details see Page 44 of the current Operations Guide

[Lucas]

Finally the problem was solved. Nobody knows how, but the camera warked fine.
That night I told you that I have the "Record/Post Stuk" problem, I ´ve tryed everything, including 4K 2:1 24 Fps Redcode 36. The page 28 of the Build 15 Op. manual says that it is possible to record this way. And the camera never sayd "non valid settings".
The only thing we done physically with the camera was remove the CF reader... and put it again. "Misteriously" the camera worked good, in all possible settings. I ´ve been shooting a few days ago and nothing happend.

I´m glad to know that Build 17 solved this trouble, but in some versions of Scratch it´s dangerous to mix Build 15 with Build 16 files. So, the producers don´t want to update the camera to protect the movie.

I like the camera, but I hate to wait to the following problem every time I go to work with it.

Lucas Mormandi
Cameraman - DIT

[Deanan]

I´m glad to know that Build 17 solved this trouble, but in some versions of Scratch it´s dangerous to mix Build 15 with Build 16 files. So, the producers don´t want to update the camera to protect the movie.

B17 also adds a mode selection that enables better compatibility with Scratch but at the expense of some of the quality and stability gains of B16.

[Brent J. Craig]

Deanan, can you actually record with this settings?
4K
36 RC
2:1
24fps
to a CF Card? If so I gotta write to iSee4K to fix that!
Thanks.

We used these settings on a 7 week around-the-world documentary in May and June. We did the final color correction in Technicolor Toronto's Lustre DI suite last week, and it premieres in Las Vegas next week. Footage looks amazing! Two Terabytes of footage and not a single dropped frame. Shooting mostly to 8G CF cards and some Reddrive.

[Stephen Pruitt]

Stuart is wrong. You certainly can use 8gig CF cards with those settings. Those are the exact settings we used to shoot 5 TB worth of footage on our feature. Only got dropped frames ONE TIME (when the camera was excessively hot). RC 36 works perfectly with CF cards. And we were on Build 15 the entire film!

Stephen

[Joel Kaye]

Yep. . . your CF card reader/writer module is shot. . . we just replaced ours. . . very frustrating. . . ours was so intermittent it was ridiculous, but RED sent us out a new one and so now we're good as gold.

As for shooting with Redcode 36 on CF cards? We shot an entire feature film on 8gig cards at Redcode 36. We never once moved to Redcode 28. It works perfectly.


Were you shooting 2:1? In 16x9 I get "media too slow" at RC36.

[Stephen Pruitt]

We used the settings suggested above (4K; 2:1; RC 36; except we used 23.976 instead of a true 24). We shot 2:1, 'cause 16:9 was not an option at that time (in Build 15).

Stephen

[CJ Roy]

I used to get the stuck on "Post" error quite a bit. I found that disabling the QT proxies in the camera fixed it. You can recreate them in Red Rushes pretty easily now.

Might be worth a shot, if not already fixed.

[Errol Afed]

It's great to hear that Lucas! Our camera had to be sent back to Red and I finally got an answer. The problem according had something to do with an "internal component on the card path". Anyway camera works great, I've been
testing it the past few days and no problems.

[Dan Blanchett]

My Red froze during POST way back in March on red drives (build 13) and still occasionally freezes on POST using the Red Drives, not CF cards, using BUILD 16. On our current shoot (a 3-week feature), this is happening about once a day, and we end up losing that take. You have to power down, swap drives, reformat and then it's okay.... for another day or so.

So it's not just a CF card issue. I have 3 red drives and it happens on all three. Very annoying!

Will Build 17 fix this too?

[Cüneyt Kaya]

My Red froze during POST way back in March on red drives (build 13) and still occasionally freezes on POST using the Red Drives, not CF cards, using BUILD 16. On our current shoot (a 3-week feature), this is happening about once a day, and we end up losing that take. You have to power down, swap drives, reformat and then it's okay.... for another day or so.

So it's not just a CF card issue. I have 3 red drives and it happens on all three. Very annoying!

Will Build 17 fix this too?

maybe its the connector on your body?
did you have problems with cf?

[Brice Ansel]

My Red froze during POST way back in March on red drives (build 13) and still occasionally freezes on POST using the Red Drives, not CF cards, using BUILD 16. On our current shoot (a 3-week feature), this is happening about once a day, and we end up losing that take. You have to power down, swap drives, reformat and then it's okay.... for another day or so.

So it's not just a CF card issue. I have 3 red drives and it happens on all three. Very annoying!

Will Build 17 fix this too?

I had the same problem with build 16 and red drive (ocasionnaly once a day).
http://www.reduser.net/forum/showthread.php?p=303866#post303866

Since I upgraded to build 17 it seems the issue disappeared.
Best regards
Brice