Motion Recording was cancelled due to a limitation from the writing speed of the card

C

cam123

Active member
Has anyone encountered this?

I was shooting this morning and It would
exit after 30 secs of recording. Sometimes after 2 minutes, sometimes 3 minutes.
Like random exit while recording.

Mine is hacked with Lpowell settings.

Card is 16GB Panasonic Gold Class 10

Not sure if my card is corrupted.
 
The only time that's happen to me was in Victoria (BC) harbour when I was shooting one of the little tourist boats coming in on a bright sunny day (stopped down, everything in focus, lots of colour everywhere - hence a huge amount of detail).

I was using a Class 6 card with the hacked firmware - "safe settings".

None of the files were corrupted and I was able to continue recording as soon as the file was written out, which was very quickly.
 
Then when we got to the store I noticed this blockiness in the footage.
It was bright there so I increased the shutter speed ISO was 200.
I guess I should have left the shutter speed at 1/60 and increased the aperture instead.
Aperture was set manually at f/2.

Note: I am new to this so probably I did something wrong with the settings.
Nevermind the focus. I'm using a manual lense and finding hard to focus. :)

1280x720; 720p 120fps

IMPORTANT NOTICE: No media files are hosted on these forums. By clicking the link below you agree to view content from an external website. We can not be held responsible for the suitability or legality of this material. If the video does not play, wait a minute or try again later.
I AGREE
 
Kin Lau said:
The only time that's happen to me was in Victoria (BC) harbour when I was shooting one of the little tourist boats coming in on a bright sunny day (stopped down, everything in focus, lots of colour everywhere - hence a huge amount of detail).

I was using a Class 6 card with the hacked firmware - "safe settings".

None of the files were corrupted and I was able to continue recording as soon as the file was written out, which was very quickly.
Click to expand...

None is corrupted either.
Using a kit lens this time. In my case it happened while I switched to iA and set to Auto Focus Continuous.

It records then it exits after 30 sec then I hit record again then it exits again after a while. I set it back to Manual Creative mode then
it's fine again. So I guess it likes manual mode only or my card is corrupted
because I switch it back and forth from computer to camera.
 
Yes, It's formatted in the camera.
I think I may be doing something wrong like viewing the card in my PC
because I noticed it created some temporary files there.
Next time I'll copy the whole directory instead to my PC before viewing.
 
Every time I put a card in my PC, I make sure I write protect it just to make sure the OS doesn't get all stupid and try to add extra files to the card that don't need to be there. There's practically no reason to ever need to copy from a PC to an SD card that you are using to shoot on, so just make that a common practice.
 
Yup. Seems like media player added some temporary files.
I see these files in there.

00039.MTS.sfk1
00037.MTS.sfk1

Will flick the write protect only notch next time. Thanks for suggestion subtleinspiration.
 
I should ask if you've read through all of the sticky threads..

The "card speed" error is well known and has been gone through in great detail in MANY threads.

As I've said before, the "hack" is exactly that. A hack. It's not perfect and nobody should take it as being perfect. People will have problems with it when other people do not have problems with it. EXPECT problems. That's the nature of hacking code to do something it was never meant to do.
 
Strange. I've stress tested my class 4 San Disks and never had a problem. Lots of trees and bushes at high aperture and shutter speed, lots of diff shutter speeds, jerking around at different speeds.
 
I have found that 720 60p with high bitrates can cause write speed errors at times, while I have never encountered them with 1080 24p. Ran some tests and found that if I set the 'Overall Bitrate' a bit higher than suggested, that I eliminated these errors. Now I have it set to 44,000,000 - 2,000,000 more than the suggested 42,000,000 when FH/SHD 'Video Bitrate' is set to 40,000,000. Also, set H mode to 24,000,000 so if I were to find a situation that caused these errors again, I could still get 720 60p with a decent bitrate.

Here's my setting that have been working like a charm:

Prevent version compare=Checked
Native 24p/25p=Checked
Video Bitrate FHD/SH=40000000
Video Bitrate H=24000000
Overall Bitrate=44000000
 
I think you're exactly right about the overall bitrate setting being too low with the "C" settings, and in other cases as well. I believe the overall bitrate has to do with buffereing requirements and if it is too low strange things happen. Unfortunately, with 24p checked odd things happen all the time, like wrong GOP lengths, empty frames, etc...

I put a feature in Stream Parser where is shows what the buffering requirements are (in the info window) after you have loaded a clip. You'll notice that with the C settings it shows a number higher than 52000000, for example. From my tests I've concluded that the overall bitrate needs to be set at a higher level than shown there for reliable operation.

Chris
 
Last edited:
You must log in or register to reply here.
Back
Top