chrisruk
chrisruk
Thanks for reporting this, just looking into the reason behind this issue
@CricGuru Hi, I've created a new example, which I think is similar to what you wanted to do, in the 'next' branch of this repo. This should get merged into...
The changes for this are now in main. Please re-open if there's any remaining issue.
Thanks for reporting this, which I can also replicate. I've had a look into it and it seems due to wheel files (.whl) not actually executing/containing the code from setup.py....
Good question, I'll have a look at this.
@ccostes Hi, In the 'next' branch I added support for generating a file with timestamps, along with an example - https://github.com/raspberrypi/picamera2/blob/next/examples/capture_video_timestamp.py
The changes for this are now in main. Please re-open if there's any remaining issue.
Thanks for reporting this, will work on this soon. In the meantime if you add the pts parameter in this example - https://github.com/raspberrypi/picamera2/blob/main/examples/capture_mjpeg_v4l2.py you should get a timestamp.txt file.
Thanks for pointing that out! That appears to be a bug too, it shouldn't be h264 data.
Ah yeah it could well be that. I checked that I am still setting V4L2_PIX_FMT_MJPEG. When using 'file' on the output it says - test.mjpeg: JVT NAL sequence, H.264 video...