-
-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Freezes #139
Comments
I also have this issue. I found that lowering the resolution to 720p got rid of the freezes. Another work-around is to keep it at 1080p but enable VFR. For me, this got rid of the freezes but the average frame rate according to VLC was in the low 20's, not the 30 I set it at. It's almost like picam is having issues keeping up somehow, though I know the Pi's h264 encoder is capable of 1080p30 (works with with raspivid) and picam's CPU usage is only around 60%. |
Same to me. I set video size to 1024x720 and frame rate to 25. If I play the video with Media Player Classic Home Cinema, it freezes extremely, and when I click on "properties", it shows me: BUT: if I insert this video into the timeline of a project in Adobe Premiere, everything looks fine, and nothing is frozen. The frame rate is shown as a little bit below 25. But those results came from some experiments. I formatted a partition on my SD card as NTFS, and this seems to be a very bad idea because it takes much more time to save data. So I went back to FAT32, left all those video size and fps settings away, and now I get videos in 1280x720 and more than 25 fps. I was surprised by the fact that there is no delay between audio and video. |
Same issue with raspberry pi 4 4Gb and camera_HQ Video Freeze at regular time, every 2-3s ./picam -w 1280 -h 720 --fps 25 --> OK |
fps higher than 20 may be too high for resolutions larger than 1280x720 because picam does some processing in addition to H.264 encoding. Try lower fps, resolution, or |
IMHO it is rather useless to work with large resolutions and high fps because you can not expect really good quality when the video bitrate is 2000000. Fast movements in the pictures lead to blocks and artefacts in the pictures. Recording video and audio is a difficult task. Somewhere I read the statement that Raspberry is in general too weak to capture audio from USB and compress it with AAC, and so it seems to be a miracle that picam is even able to record video on the same time. From my experiences it is better to reduce resolution and fps, but enhance the video bitrate. This leads to "starving buffer" errors. Using --vfr seems not to be very useful, it leads to videos which have wrong speed in some players and also in Adobe Premiere CS6. Best results come from lowering --gopsize. I recommend One question: if file size does not matter, what is the smallest possible gopsize which needs the minimum of calculation power? |
Idea for new release, user can be enable/disable backend processing options to preserve cpu load for FullHD resolution and 25 fps |
Thanks for these tips! I too would randomly get the "Record buffer is starving." error messages which would lead to corrupted video file. I am going to test your settings and see if that resolves it. Curious how to get 60fps? Sounds like it is impossible with the picam? |
Update: I've increased the GPU memory under "raspi-config" from 128 to 256. Now it us running A LOT more stable. Have only seen this "starving buffer" message only once in a 100+ video recordings . Before I was getting it one in every 20 videos. |
Hi
I'm using the last version of picam (1.4.8).
When I play the video recorded, I got a lot of freezes on the videos, but the sound continue correctly.
The picam doesn't say anything wrong:
using AVC High Profile Level 4
configuring devices
capturing started
o-o-o+o+o-o-o-o+o-o-o+o-o-o-disk_usage=3% start rec to rec/archive/2020-05-13_21-56-40.ts
I'm using it like this:
./picam -w 1920 -h 1080 -v 2000000 --fps 20 --volume 20 --alsadev hw:1,0
I don't think it's a sdcard issue, the file is very light, and it's a class 10.
Do you have an idea?
Thanks
Pi Zero / gpu_mem at 256MB
The text was updated successfully, but these errors were encountered: