Recherche avancée

Sur d’autres sites (13119)

• FFMPEG codec "Error opening filters" error on Windows server

  12 février 2019, par Frank Nicklin

  Im using NReco Videoconvertor on and asp.net web service but its failing with the error

  ****Error : Cannot convert media : Error opening filters !****

  When testing on my local development PC Windows 10 VS2017 it works fine. If I manually run ffmpeg as this too work fine

  ffmpeg -i c:\tempfolder\5239.hevc c:\tempfolder\5239.mp4. 

  However if I try the same from my Windows 2016 Server I get a could not find codec parameters error :-

    D:\webservice\Bin>ffmpeg -i d:\video\1234.hevc d:\video\5225.mp4
  
  ffmpeg version N-56060-gbcd1c20 Copyright (c) 2000-2013 the FFmpeg developers
  
    built on Sep  6 2013 00:42:37 with gcc 4.7.3 (GCC)
  
    configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libcaca --enable-libfreetype --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib
  
    libavutil      52. 43.100 / 52. 43.100
  
    libavcodec     55. 31.101 / 55. 31.101
  
    libavformat    55. 16.101 / 55. 16.101
  
    libavdevice    55.  3.100 / 55.  3.100
  
    libavfilter     3. 83.104 /  3. 83.104
  
    libswscale      2.  5.100 /  2.  5.100
  
    libswresample   0. 17.103 /  0. 17.103
  
    libpostproc    52.  3.100 / 52.  3.100
  
  [mov,mp4,m4a,3gp,3g2,mj2 @ 028fa380] Could not find codec parameters for stream 0 (Video: none (hvc1 / 0x31637668), 352x288, 937 kb/s): unknown codec
  
  Consider increasing the value for the 'analyzeduration' and 'probesize' options
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'd:\video\1234.hevc':
  
    Metadata:
  
      major_brand     : qt
  
      minor_version   : 0
  
      compatible_brands: qt
  
      creation_time   : 2019-02-04 10:35:12
  
    Duration: 00:00:20.25, start: 0.000000, bitrate: 965 kb/s
  
      Stream #0:0(und): Video: none (hvc1 / 0x31637668), 352x288, 937 kb/s, 30.01 fps, 30 tbr, 600 tbn, 600 tbc (default)
  
      Metadata:
  
        rotate          : 90
  
        creation_time   : 2019-02-04 10:35:12
  
        handler_name    : Core Media Video
  
      Stream #0:1(und): Audio: aac (mp4a / 0x6134706D), 22050 Hz, mono, fltp, 23 kb/s (default)
  
      Metadata:
  
        creation_time   : 2019-02-04 10:35:12
  
        handler_name    : Core Media Audio

  Any thoughts please.

• How do I fix the "PES packet size mismatch" error in FFmpeg ?

  8 février 2021, par Ed999

  How to fix the error PES packet size mismatch in FFmpeg -

  



  I'm going to answer my own question, because the phrase PES packet size mismatch comes up regularly in posts relating to ffmpeg, but I've nowhere seen a satisfactory solution to it.

  



  It usually figures in a problem involving .TS transport stream files : either in relation to concatenating such files, or relating to re-muxing them (from .ts to .mp4). Somewhere in the output from ffmpeg, the deadly phrase packet size mismatch will suddenly start repeating.

  



  A solution is to concatenate them as .ts files (i.e. in their original format), then take the output .ts file, split it into a video file (.ts) and an audio file (.ts), then remux them (to either .ts or .mp4) using the "itsoffset" option. Even if stream copy is used, outputting to .mp4 will often give worse picture quality than retaining the .ts format.

  



  The following code does that, outputting either .mp4 video or .ts video (copy the code into a simple .bat batch file, then run that file) -

  



  .

  



  :: Program Location
SET ffmpeg="C:\Program Files\FFmpeg\ffmpeg.exe" -hide_banner  


::  STEP 1 -

::  Create File List
IF EXIST mylist.txt DEL mylist.txt
FOR %%i IN (*.ts) DO ECHO file '%%i'>> mylist.txt

::  Concatenate Files : TS
%ffmpeg%  -f concat  -safe 0  -i mylist.txt  -c copy  -threads 1  out.ts


::  STEP 2 -

::  Extract Video stream
%ffmpeg%  -i out.ts  -vcodec copy  -an  -sn  -threads 1  video.ts

::  Extract Audio stream
%ffmpeg%  -i out.ts  -acodec copy  -vn  -sn  -threads 1  audio.ts


::  STEP 3 -

::  Combine Video and Audio streams (with .MP4 options)
SET mapping=-i video.ts -itsoffset -0  -i audio.ts   -map 0:v -map 1:a
SET options=-flags global_header  -movflags faststart  -threads 1
%ffmpeg%  %mapping%  -c:v copy -c:a copy  %options%  output.mp4

::  Combine Video and Audio streams (with .TS options)
SET mapping=-i video.ts -itsoffset -0  -i audio.ts  -map 0:v -map 1:a
SET options=-threads 1
%ffmpeg%  %mapping%  -c:v copy -c:a copy  %options%  output.ts


  



  .

  



  Addendum :

  



  There seems to be some dispute about my suggested solution, as detailed in the Comments below. It seems to be being said that my solution is ignoring the fact that data is missing in the source files.

  



  I think the least I can do is admit that since ffmpeg is reporting an error in the source files, with its 'packet size mismatch' warning, the objection raised in the Comments might be valid.

  



  However, even if data is missing, my suggested routine will at least give you a file which will play in most media players. In many cases, there will not even be an audible or visual fault at the join point specified in the reported error.

  



  It's difficult to see how the missing data might be restored, but do please chip in with suggestions. There must be scope for improving my script, because so little attention has been paid to this type of fault previously.

  



  Happily, it seems that this type of error will NOT cause the sound to lose synchronisation with the picture. So the audio after the join-point will not go out-of-sync, even if some data is missing at the join.

  


• What is causing "unspecified pixel format" and "Error opening filters !" error in ffmpeg ?

  19 février 2019, par SJAndersonLA

  I’m writing an mp4 to HLS transcoding process that works as intended on files smaller than 7 gigabytes (sample size is 100 videos). When attempting to transcode anything larger than 7GB, it crashes.

  The command :

  ffmpeg 
  
    -i large_file.mp4 -y 
  
    -vf scale=w=1920:h=1080:force_original_aspect_ratio=decrease 
  
    -c:a aac 
  
    -ar 48000 
  
    -c:v h264 
  
    -profile:v main 
  
    -crf 20 
  
    -sc_threshold 0 
  
    -g 48 
  
    -keyint_min 48 
  
    -hls_time 4 
  
    -hls_playlist_type vod 
  
    -b:v 5000k 
  
    -maxrate 5350k 
  
    -bufsize 7500k 
  
    -b:a 192k 
  
    -hls_segment_filename /1080p_%03d.ts 
  
    -threads 0 
  
    /tmp/output-ef42dc65-1d3d-4682-b32b-68d7c712fb9c-raw-test/1080p.m3u8

  The error :

  ffmpeg version 3.2.12-1\x7edeb9u1 Copyright (c) 2000-2018 the FFmpeg developers
  
    built with gcc 6.3.0 (Debian 6.3.0-18+deb9u1) 20170516
  
    configuration: --prefix=/usr --extra-version='1~deb9u1' --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --enable-gpl --disable-stripping --enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libebur128 --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libmp3lame --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-omx --enable-openal --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libopencv --enable-libx264 --enable-shared
  
    libavutil      55. 34.101 / 55. 34.101
  
    libavcodec     57. 64.101 / 57. 64.101
  
    libavformat    57. 56.101 / 57. 56.101
  
    libavdevice    57.  1.100 / 57.  1.100
  
    libavfilter     6. 65.100 /  6. 65.100
  
    libavresample   3.  1.  0 /  3.  1.  0
  
    libswscale      4.  2.100 /  4.  2.100
  
    libswresample   2.  3.100 /  2.  3.100
  
    libpostproc    54.  1.100 / 54.  1.100
  
  [mov,mp4,m4a,3gp,3g2,mj2 @ 0x555888d821c0] Could not find codec parameters for stream 0 (Video: h264 (avc1 / 0x31637661), none, 1280x720, 3856 kb/s): unspecified pixel format
  
  Consider increasing the value for the 'analyzeduration' and 'probesize' options
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'large_file.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.26.101
  
    Duration: 05:56:12.51, start: 0.000000, bitrate: 4061 kb/s
  
      Stream #0:0(und): Video: h264 (avc1 / 0x31637661), none, 1280x720, 3856 kb/s, 29.99 fps, 30 tbr, 100k tbn, 200k tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 194 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
  [buffer @ 0x555888d88180] Unable to parse option value "-1" as pixel format
  
      Last message repeated 1 times
  
  [buffer @ 0x555888d88180] Error setting option pix_fmt to value -1.
  
  [graph 0 input from stream 0:0 @ 0x555888d81e40] Error applying options to the filter.
  
  Error opening filters!

  The error says to try increasing analyzeduration and probesize, which I set to max value (based on an answer from this post), however that didn’t seem to change the behavior. I also suspected that the file was corrupted, but the fact that this is failing for all files larger than 7GB makes it more difficult to suggest its something not related to the size of the mp4.