Tag Info

New answers tagged

1

The first thing that I noticed is that your camera is delivering yuv422p - which isn't bad in and of itself, but you could try forcing it to yuv420 by adding -pix_fmt yuv420p to your command. (This is nice if you ever plan on displaying your video on anything that isn't linux.) The second thing that I noticed is that the start times are wildly different - ...


0

Without knowing the exact details of your workflow it is hard to answer this question, so more information would be greatly helpful. One approach would be to use raw video during your "joining" phase of the algo to strip the moov atom. The final step would be to convert your concat'ed raw video back into mp4.


1

From FFmpeg Documentation – Detailed Description: ffmpeg calls the libavformat library (containing demuxers) to read input files and get packets containing encoded data from them. When there are multiple input files, ffmpeg tries to keep them synchronized by tracking lowest timestamp on any active input stream. Encoded packets are then passed ...


0

Yes, compositing, as it is known in the industry, involves decoding two or more assets in to video streams and them combining those streams in some way. The end result is then saved as a new file on render. There is some variation in when rendering is done though. Some software can put off rendering for a while to reduce the number of re-encodes required. ...


2

It is actually quite easy using a videofilter with select. This is quite sensitive to video changes: -vf "select=gt(scene\,0.0098)" whereas this is not so sensitive: -vf "select=gt(scene\,0.3)" EDIT (added your command) so your command would look like: ffmpeg -f video4linux2 -s 800x600 -r 15 -i /dev/video1 -maxrate 800k \ -minrate 1k -bt 800k ...


2

I struggled with a similar issue on Ubuntu 12.04.3 LTS. I fixed the problem using the static ffmpeg build which is available from http://ffmpeg.gusari.org/static/64bit/ffmpeg.static.64bit.latest.tar.gz


0

Did you try using the -compression_level flag? It takes an int from 0-100 afaik (maybe the range is even higher, the docs just say "int"). That should set a lossy compression strength. There is also an interesting blog post about creating DCI compilant JPEG2000 encodes with FFMPEG for DCP's. Which require lossy encoded JPEG2000.



Top 50 recent answers are included