Recherche avancée

Sur d’autres sites (9758)

• Revision cb1e60fb28 : Fix bug in reference frame counting. vp8_encode_inter_macroblock() is called in

  17 juillet 2012, par Ronald S. Bultje

  Changed Paths : Modify /vp8/encoder/encodeframe.c Fix bug in reference frame counting. vp8_encode_inter_macroblock() is called in both pick_mb_modes() as well as encode_sb(), thus the number of macroblocks in the counter were twice as big as actual numbers. This doesn't affect output. (...)

• converting .mov file to .h264 file

  29 août 2011, par Robin Rye

  ok, this is the case, i actually want to parse frames from a mov file. get the encoded h264 frames. and i've managed to do so by using ffmpeg but when i try to make a movie again by using ffmpeg -i test* test.mov i get test00: Invalid data found when processing input so there is something not correct with the structure of the frames. as i understand it a frame should have the following appearance :

  00 00 00 01 XX data -------------

  where XX is say whether it is a I-,P- or B-frame. or more specifically type(XX) = 0x0F && XX says if it is I(type(XX) = 5 ?),P(type(XX) = 7 ?) or B(type(XX) = 8 ?) frame. I'm not sure about these number, i've been looking for it but not found good sources. so that's question number one, what number should the NALU be for the different frames ?

  anyway, when i use av_read_frame on the mov file, i get frame that look like this :

  4B = size, 1B = XX and then data. (at least this is what i think i get)

  the files where i store the frames are always size long when i look at them in a hexeditor(otherwise as well of course). and XX is always 65(ie. type(XX) = 5) in the first and then 61(ie. type(XX) = 1) for a couple of frames and then back to being 65 for one frame and so on.

  i guess that these are frames like : I P P P P P P I P P P P P P P I P P P P P P P .... however then my assumption about the type numbers for the different frame types are false, which is highly likely. (any suggestion on reading about this ? except the ISO/IEC 14496-10, i don't understand it really).

  I've tried to remove the size and append 00 00 00 01 before the XX byte and the data but without success. any tips on how i could modify the frames to be valid H264 encoded frames ?

• How to calculate ffmpeg output file size ?

  25 septembre 2011, par poundifdef

  I am using ffmpeg to convert home videos to DVD format and want to calculate the output file size before doing the conversion.

  My input file has a bit rate of 7700 kbps and is 114 seconds long. The audio bitrate is 256 kbit (per second ?) The input file is 77MB. To get this information I ran :

  mplayer -vo null -ao null -frames 0 -identify input.MOD

  So in theory, the input file should have (roughly) a file size of :

  ((7700 / 8) * 114) / 1024

  That is, (7700 / 8) is kilobytes/second, multiplied by 114 seconds, and then converted to megabytes. This gives me 107MB, which is way beyond my 77. Thus I am skeptical of his formula.

  That said, after converting the video :

  ffmpeg -i input.MOD -y -target ntsc-dvd -sameq -aspect 4:3 output.mpg

  The numbers seem to make more sense. Bitrate is 9000 kbps, and applying the above formula, I get 125MB, and my actual output file size is 126MB.

  So, two questions :

  1. How do I factor the audio bitrate into this calculation ? Is it additive (video file size + audio file size) ?

  2. Do DVDs always have a 9000 kilobit/second rate ? Is that the definition of a DVD ? Or might that change depending on video quality of my input video ? What does "-target ntsc-dvd" guarantee about my video ?

  3. Why does my input file not "match" the calculation, but the output file does ? Is there some other variable I'm not accounting for ?

  What is the correct way to calculate filesize ?