Forum Replies Created

Page 9 of 9
  • use -shortest. As in ffmpeg -shortest -i inputone-%05d.png -i inputtwo.wav -map 0:0 -map 1:0 output.mov. It will truncate the output to the length of the shortest input stream

  • It looks like it’s having trouble parsing the path – if you look at the line that reads Error parsing options string: 'tempvideosfile2.mp4', that looks to me like it’s interpreting the backslashes as posix style escapes. Try giving it an absolute path to the movie, and escaping your backslashes eg movie=c:\temp\videos\file2.wmv

  • Stephen Dixon

    February 3, 2012 at 12:02 pm in reply to: fixing audio in MPEG 2 multiplexed file

    As far as fixing the audio, you might want to use audio compression (not to be confused with file sizes). Putting it simply, Audio compression turns down the volume on the loud parts and brings up the volume of the quiet parts. I don’t think ffmpeg has audio compression filters, but Audacity (free) certainly does.

    Just to extend on William’s post, to use the map command you use “-map input:stream” so for your situation: -map 0:0 -map 1:0 to map the first stream of the first file and first stream of the second file (the count starts at 0, so 0:0 is first stream of first file). If you want to know which streams are which just typing “ffmpeg -i yourfile.mov” will display all the file info including the streams, without doing anything.

    As far as converting it to MPEG, the ffmpeg.org FAQ is a good starting point:

    -stib

  • Stephen Dixon

    December 29, 2011 at 1:14 am in reply to: make fails when building with libx264 – osX

    Removed all traces of x264 and it seemed to work. Interestingly I had to specifically enable shared libraries when I built x264 again, because it’s off by default.

    Thanks

  • Stephen Dixon

    December 28, 2011 at 10:59 pm in reply to: make fails when building with libx264 – osX

    Thanks. I’m guessing they’ll be in /usr/local/lib?

  • Firstly, memory has nothing at all to do with how much space you have on the hard drive. You seriously need to read a basic guide on how computers work if you’re making that kind of mistake.

    But it’s probably not the issue anyway: the “error out of memory” thing often pops up when you have large images in your timeline. If you have any big (over 4k pixels wide) pictures in the timeline, scale them down in an image editor (If you need them really big in order to zoom into them use motion or another program to do it).

    As far as the timebase thing goes, yes you need to create a new sequence with no clips in it and copy and paste (or you can cut all the clips out of the sequence, change the timebase and paste, but that leaves you with no original copy if it all goes to custard). If there are timing issues once you do that you will probably have to correct them manually. Why are you needing to change it?

  • Stephen Dixon

    December 28, 2011 at 12:30 pm in reply to: Merge Video (without audio) and MP3

    do you want to have the mp3 play at the same time as the video, or before the video? It’s unclear from your question.

  • Stephen Dixon

    December 28, 2011 at 12:28 pm in reply to: Encoded video is black

    What does ffmpeg report when you try to encode the unsuccessful files? Are there any error messages?

    BTW: Is there a reason you’re using aac instead of libfaac?

  • Stephen Dixon

    December 28, 2011 at 12:24 pm in reply to: video transcoding process

    That would depend on the codec used.

    FFMPEG is able to read and encode a lot of codecs, many of which use some or all of these methods, and it can also write uncompressed raw video.

  • Stephen Dixon

    January 14, 2009 at 7:12 am in reply to: Canon XH G1 vs XH A1

    SDI stands for serial digital interface. It’s uncompressed digital video. So it’s like firewire, but better.

    Not sure about the cameras in question, but I know there are cameras out there that record in 4:2:0 natively, but can output SDI at 4:2:2.

Page 9 of 9

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