Recherche avancée

Sur d’autres sites (4944)

• How to make mpv more compatible with ffmpeg filters like minterpolate ?

  1er octobre 2020, par F usedEmacs -con fused

  ffmpeg filter minterpolate (motion interpolation) does not work in MPV.

  



  (Nevertheless the file then is played normally without the minterpolate).

  



  (I researched using search engines and throughout documentation and troubleshooted to make a use of opengl and generally tried everything apart from asking for help and learning to understand more in the source code and I'm not a programmer)…

  



  --gpu-context=angle --gpu-api=opengl also does not make opengl work. (I'm guessing opengl could help from seeing its use in the documentations).

  



  


  Note

  
 


  To get a full list of available video filters, see —vf=help and
 http://ffmpeg.org/ffmpeg-filters.html .

  
 


  Also, keep in mind that most actual filters are available via the
 lavfi wrapper, which gives you access to most of libavfilter's
 filters. This includes all filters that have been ported from MPlayer
 to libavfilter.

  
 


  Most builtin filters are deprecated in some ways, unless they're only
 available in mpv (such as filters which deal with mpv specifics, or
 which are implemented in mpv only).

  
 


  If a filter is not builtin, the lavfi-bridge will be automatically
 tried. This bridge does not support help output, and does not verify
 parameters before the filter is actually used. Although the mpv syntax
 is rather similar to libavfilter's, it's not the same. (Which means
 not everything accepted by vf_lavfi's graph option will be accepted by
 —vf.)

  
 


  You can also prefix the filter name with lavfi- to force the wrapper.
 This is helpful if the filter name collides with a deprecated mpv
 builtin filter. For example —vf=lavfi-scale=args would use
 libavfilter's scale filter over mpv's deprecated builtin one.

  


  



  I expect MPV to play with minterpolate (one of several filters that MPV can use, listed in http://ffmpeg.org/ffmpeg-filters.html) enabled. But this is what happens :

  



  Input : "--vf=lavfi=[minterpolate=fps=60000/1001:mi_mode=mci]"

  



  Output :

  



     cplayer:  (+) Video --vid=1 (*) (h264 1280x720 29.970fps)
   cplayer:  (+) Audio --aid=1 (*) (aac 2ch 44100Hz)
        vd: Using hardware decoding (d3d11va).
    ffmpeg: Impossible to convert between the formats supported by the filter 'mpv_src_in0' and the filter 'auto_scaler_0'
     lavfi: failed to configure the filter graph
        vf: Disabling filter lavfi.00 because it has failed.


  



  (Interesting is also that --gpu-api=opengl does not work (despite that according to specification my—not to brag—HD Graphics 400 Braswell supports its 4.2 version)… And that aresample seems to have no effect too, and with the few audio filters selected playback often doesn't start nor output errors.)

  


• Automator bash shell script trouble

  6 avril 2015, par Dae

  I’m probably missing something really simple here, but I’m have trouble building an automator service that runs a bash shell script. All of the elements of the script work fine when plugged into shell, but for some reason the automator service is failing to run. The script calls ffmpeg to convert an audio file passed to it from the finder :

  for f in "$@"
  
  do
  
    fn="${f%%.*}"
  
    ~/Applications/ffmpeg/ffmpeg -i "$f" -acodec libmp3lame -q:a 7 -ar 8000 -ac 1 "$fn.mp3"
  
  done

  The script runs fine without the ffmpeg command, and the ffmpeg command runs fine in the terminal on its own. Where’s the error coming from ?

  Thanks !

• Homebridge camera ffmpeg : rtsp stream accessible with vlc but not with Home app

  20 mars 2023, par someone

  I can access the stream of my esp32 cam with vlc but it doesn't load in home app. Here is my config :

  


  {
    "bridge": {
        "name": "Homebridge 963D",
        "username": "0E:B6:BD:6E:66:9B",
        "port": 51600,
        "pin": "399-77-791",
        "advertiser": "bonjour-hap"
    },
    "accessories": [],
    "platforms": [
        {
            "name": "Config",
            "port": 8581,
            "platform": "config"
        },
        {
            "name": "Camera FFmpeg",
            "cameras": [
                {
                    "name": "cam1",
                    "videoConfig": {
                        "source": "-i rtsp://192.168.178.118:8554/mjpeg/1"
                    }
                }
            ],
            "platform": "Camera-ffmpeg"
        }
    ]
}


  


  the homebridge logs didn´t helped too. There is no video, so the problem is in homebridge ffmpeg