Forum Replies Created

Page 5 of 16
  • Reuben Martin

    August 4, 2013 at 1:25 am in reply to: ffmpeg uncompressed avi to x264

    The order of the CLI arguments matters. Any options pertaining to the source file needs to go in front of the “-i” option, otherwise they are in reference to your desired output.

    ffmpeg -f rawvideo -pix_fmt bgr24 -i "MTS-07.avi" -vcodec libx264 -b:v 2000k -acodec libmp3lame -ar 48000 -ab 192k -y MTS-07-x264-mp3.avi

    Also, AVI is a sloppy format for codecs that are not intra-frame only codecs. You would probably be better of putting it in an mp4 container or something similar.

  • Reuben Martin

    June 4, 2013 at 1:10 am in reply to: vob to prores conversion

    That version of ffmpeg is way too old. It neither supports ProRes encoding nor the newer argument style you are attempting to use. Update.

  • Reuben Martin

    May 12, 2013 at 4:22 am in reply to: Is ProRes HQ 444 useless?

    It sounds like the source of your problem is with conversion between systems the use full range luma and systems using 16-235 luma.

    However that sounds a bit odd, since bt470bg is for the older 601 standard-def transform for PAL. You might want to check and see if you shouldn’t be using bt709 color primaries.

  • Reuben Martin

    May 11, 2013 at 6:27 pm in reply to: Is ProRes HQ 444 useless?

    I’m not sure what you are asking.

    yuv444p10 is somewhat pointless. It offers no advantage over plain RGB. The whole point of YUV colorpspace is to lower the bitrate by reducing chrominance samples. But if you are not dropping chrominance samples, why store it in a YUV colorspace to begin with? If you are concerned enough about color fidelity to be using full chrominace 10 bit sampling, you are just as well off to store the data as an image sequence.

    You can force the color space of the input by specifying it’s pix_fmt in front of the “-i” option. If there’s still color issues, then either the color transform is incorrect, or you are doing it wrong.

  • Reuben Martin

    April 6, 2013 at 4:14 pm in reply to: Total newbie 🙁

    There is a “-t” option to specify duration from the start point, or there is a “-to” option to specify the stop point.

    The official documentation can be found here: https://ffmpeg.org/ffmpeg.html

  • Reuben Martin

    April 4, 2013 at 10:36 pm in reply to: Total newbie 🙁

    Using ffmpeg within a bat script is quite messy. It parses text differently than a posix compliant shell does.

    You will have to escape the “%” character in order to use it within a bat script. It’s been a long time since I’ve used bat files, but if I remember correctly you can escape that character by doubling it up. (“%%” in place of “%”)

    You might save yourself a lot of trouble by installing a windows port of bash, and using that to write shell scripts rather than bat scripts.

  • Reuben Martin

    April 4, 2013 at 1:22 am in reply to: Total newbie 🙁

    Don’t copy the html “bold” tags that got placed in there for some reason.

  • Reuben Martin

    February 20, 2013 at 6:05 pm in reply to: video twice audio speed

    Sorry. Brain fart.

    Replace MP4Box with ffmpeg. ffmpeg should be able to mux m2ts directly. I was going to suggest trying to dump the h264 stream using MP4Box, but I doubt that would make any difference.

  • You will have a lot more control integrating the libraries from the project rather than trying to call ffmpeg directly.

  • Reuben Martin

    February 19, 2013 at 9:00 pm in reply to: video twice audio speed

    First, try updating ffmpeg. The version you are using is quite old.

    Secondly, try using MP4Box to mux the ts and see it that works any better. You could probably re-mux it directly from mp4 to ts that way.

    The 1/90,000 is probably being used because that is what is compatible with RTP.

Page 5 of 16

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy