Recherche avancée

Sur d’autres sites (8740)

• FFMPEG Error AVI to FFV1

  4 décembre 2012, par Nathan

  I'm encountering the following error when transcoding using FFMPEG. From what I've been able to find, I shouldn't have to input anymore parameters or anything. I tried adding the flag "-coder 1", which got me a file, but the video was a solid block of green.

  Here's my command :

  ffmpeg -i Glueck_Newsreel.avi -vcodec ffv1 -acodec pcm_s16le mp0001.mkv

  Here's the output

  ffmpeg version 0.10.4 Copyright (c) 2000-2012 the FFmpeg developers
  
    built on Jul 21 2012 10:40:08 with gcc 4.4.6 20110731 (Red Hat 4.4.6-3)
  
    configuration: --prefix=/usr --bindir=/usr/bin --datadir=/usr/share/ffmpeg --incdir=/usr/include/ffmpeg --libdir=/usr/lib64 --mandir=/usr/share/man --arch=x86_64 --extra-cflags='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic' --enable-bzlib --disable-crystalhd --enable-gnutls --enable-libass --enable-libcdio --enable-libdc1394 --disable-indev=jack --enable-libfreetype --enable-libgsm --enable-libmp3lame --enable-openal --enable-libopenjpeg --enable-libpulse --enable-librtmp --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-libvorbis --enable-libv4l2 --enable-libx264 --enable-libxvid --enable-x11grab --enable-avfilter --enable-postproc --enable-pthreads --disable-static --enable-shared --enable-gpl --disable-debug --disable-stripping --shlibdir=/usr/lib64 --enable-runtime-cpudetect
  
    libavutil      51. 35.100 / 51. 35.100
  
    libavcodec     53. 61.100 / 53. 61.100
  
    libavformat    53. 32.100 / 53. 32.100
  
    libavdevice    53.  4.100 / 53.  4.100
  
    libavfilter     2. 61.100 /  2. 61.100
  
    libswscale      2.  1.100 /  2.  1.100
  
    libswresample   0.  6.100 /  0.  6.100
  
    libpostproc    52.  0.100 / 52.  0.100
  
  Input #0, avi, from 'Glueck_Newsreel.avi':
  
    Duration: 00:09:45.11, start: 0.000000, bitrate: 226508 kb/s
  
      Stream #0:0: Video: v210 (v210 / 0x30313276), yuv422p10le, 720x486, 29.97 fps, 29.97 tbr, 29.97 tbn, 29.97 tbc
  
      Stream #0:1: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 48000 Hz, 2 channels, s16, 1536 kb/s
  
  File 'mp0001.mkv' already exists. Overwrite ? [y/N] y
  
  w:720 h:486 pixfmt:yuv422p10le tb:1/1000000 sar:0/1 sws_param:
  
  [ffv1 @ 0x13c8340] bits_per_raw_sample of more than 8 needs -coder 1 currently
  
  Output #0, matroska, to 'mp0001.mkv':
  
      Stream #0:0: Video: ffv1, yuv422p10le, 720x486, q=2-31, 200 kb/s, 90k tbn, 29.97 tbc
  
      Stream #0:1: Audio: none, 48000 Hz, 2 channels, s16, 128 kb/s
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (v210 -> ffv1)
  
    Stream #0:1 -> #0:1 (pcm_s16le -> pcm_s16le)
  
  Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height

• Why am I receiving an error about unterminated %{} near '{localtime' when using ffmpeg

  28 juin 2019, par Randy Bailey

  I am using a line of code to try to record a camera and overlay some timestamp data while im at it.

  I have attempted placing a / and an ’ in various locations around the complaint but cant seem to fix the code. The video records fine but there is no timestamp data overlayed.

  ffmpeg -i https://CAMERAURL -vf drawtext=fontfile=/usr/share/fonts/truetype/dejavu/DejaVuSans-Bold.ttf:text='%{localtime:%T}':fontcolor=white@0.8:x=7:y=700 -vcodec libx264 -bsf:a aac_adtstoasc /home/test/StreamDriveway_$now.mp4

  Ideally the code should record with no issues. This is a screenshot of whats going in in terminal https://i.imgur.com/mnFmNtd.png

• FFMPEG frames are choppy when piping images to mp4

  15 décembre 2020, par Michael Joseph Aubry

  I'm working to optimize my rendering technique, it has some noticeable frame drops here and there. It's hard to tell, if you take a look at this recording you will see what I mean https://share.getcloudapp.com/6quxYe5O

  


  My technique involves hardcoding a default FPS to be 25 and to use that to take a screenshot of the video every (25 / 1000) = 0.4 ms inside a Chrome instance.

  


  When I run ffmpeg -i ORIGINAL_VIDEO I get this output

  


  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'https://s3.us-west-1.amazonaws.com/storycreator.clips/e7d87660-51a8-11ea-a753-8f195b459e44':
  Metadata:
    major_brand     : isom
    minor_version   : 512
    compatible_brands: isomiso2avc1mp41
    encoder         : Lavf58.29.100
  Duration: 00:00:20.36, start: 0.000000, bitrate: 6095 kb/s
    Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 6092 kb/s, 25 fps, 25 tbr, 12800 tbn, 50 tbc (default)
    Metadata:
      handler_name    : L-SMASH Video Handler


  


  When I run it on the newly made video from the screenshots here is the ffmpeg output.

  


  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'https://s3.us-west-2.amazonaws.com/storycreator.testing/4aa5e5c0-3e89-11eb-a8b5-a38609fab693.mp4':
  Metadata:
    major_brand     : isom
    minor_version   : 512
    compatible_brands: isomiso2avc1mp41
    encoder         : Lavf58.29.100
  Duration: 00:00:15.04, start: 0.000000, bitrate: 4775 kb/s
    Stream #0:0(und): Audio: aac (LC) (mp4a / 0x6134706D), 16000 Hz, stereo, fltp, 83 kb/s (default)
    Metadata:
      handler_name    : SoundHandler
    Stream #0:1(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1080x1080 [SAR 1:1 DAR 1:1], 4698 kb/s, 25 fps, 25 tbr, 12800 tbn, 50 tbc (default)
    Metadata:
      handler_name    : VideoHandler


  


  Some slight differences. You can see the bitrate drops from 6095 to 4775. You will also notice audio was attached in the new one. The video size changed — this was intentional.

  


  You also notice it go from 6092 kb/s to 4698 kb/s not sure what that means, open to clarification. Another change before that is [SAR 1:1 DAR 16:9] to [SAR 1:1 DAR 1:1] not sure what that is.

  


  The last major difference I notice is handler_name    : L-SMASH Video Handler to handler_name    : VideoHandler. Very curious about those properties as a learning bit.

  


  Not sure out of those changes which one is the most important for smooth playback like the original. I assume its bitrate.