Recherche avancée

Sur d’autres sites (4328)

• Concatenate videos with audio and overlay with complex Filtergraph in FFMPEG [closed]

  15 octobre 2024, par Jamie Shepherd

  I am new to FFMPEG and trying to get my head around the concepts and the syntax.

  


  I have 3 video files that I am trying to concatenate into one file, while overlaying an image on the middle video, all while maintaining the audio. Sadly however there is not many assurances on these files so the resolutions could be different, different audio channels etc. The documentation on the "concat" video filter states that :

  


  


  All corresponding streams must have the same parameters in all segments

  


  


  As such I have tried to use a complex filtergraph to scale all videos to the same resolution before using concat however I am getting an Unable to choose an output format error and don't fully understand what it means. The command I have so far is this :

  


  ffmpeg \
  -i intro.mp4 \
  -i main.mp4 \
  -i outro.mp4 \
  -i imageOverlay.png \
  -filter_complex \
  '[0] scale=1920:1800 [scaledIntro];' \
  '[1] scale=1920:1800 [scaledMain];' \
  '[2] scale=1920:1800 [scaledOutro];' \
  '[3] scale=1920:1800 [scaledOverlay];' \
  '[scaledMain][scaledOverlay] scale=1920:1800 [scaledOverlayOutro];' \
  '[scaledIntro:v] [scaledIntro:a] [scaledMain:v] [scaledOverlayOutro:a] [scaledOverlayOutro:v] [scaledOutro:a] concat=n=3:v=1:a=1 [v][a];' \
  -map '[v]' -map '[a]' files/output/output.mp4


  


  The error I get is :

  


  [AVFormatContext @ 0x121f08d40] Unable to choose an output format for '[1] scale=1920:1800 [scaledMain];'; use a standard extension for the filename or specify the format manually.
[out#0 @ 0x121f08c80] Error initializing the muxer for [1] scale=1920:1800 [scaledMain];: Invalid argument
Error opening output file [1] scale=1920:1800 [scaledMain];.
Error opening output files: Invalid argument


  


  Would love to understand what is going on here.

  


  Have I made a syntax mistake ? Am I missing something conceptually here ?

  


  Many thanks for your time

  


• Having issues making an app with py2app ffmpeg and ffprobe

  23 septembre 2024, par Nuno Mesquita

  I have made an app in OSX Python, that uses FFMEG and ffprobe.

  


  It runs fine in my VS Code.

  


  I want to make a self sustained app, that others can use, without needed to install anything themselves. So, I manually included the static libraries in the bin folder of my main app, and am able to run the app using the libraries inside my bin folder.

  


  I have lost many hours trying to figure this out, and am always getting the same error.

  


  My best shot was being able to open the app inside app/contents/resources and running via Python, but still have the issue saying that ffprobe is not available.

  


  I´m losing my mind...

  


  Should I try a completely different approach ?

  


  For now, I just want my OSX friends to be able to use the app, then I will want it to run on Windows too, but baby steps.

  


  I am not quite sure what to include in setup.py, so I would love to include everything that is in my app folder, to avoid all sorts of errors in missing .pngs and stuff.

  


  I also made sure that libraries are executable (they are about 80MB each (ffmpeg and ffprobe))

  


  Can anyone help =D ???

  


  I described above, tested different ways, checked stuff like redirecting the libraries to the folders of the app :

  


  For the last try my setup.py was :

  


  from setuptools import setup

APP = ['mpc.py']
DATA_FILES = [
    ('bin', ['./bin/ffmpeg', './bin/ffprobe']),
    ('theme/dark', ['./theme/dark/*.png']),
    ('theme/light', ['./theme/light/*.png']),
    ('theme', ['./theme/dark.tcl', './theme/light.tcl']),
    '.',  # Add current directory to ensure everything is included
]

OPTIONS = {
    'argv_emulation': False,
    'packages': ['pydub', 'pygame', 'requests', 'freesound'],
    'includes': ['pydub', 'pygame', 'requests', 'freesound'],
    'resources': ['./bin/ffmpeg', './bin/ffprobe', './theme/dark/*.png', './theme/light/*.png',     './theme/dark.tcl', './theme/light.tcl'],
}

setup(
    app=APP,
    data_files=DATA_FILES,
    options={'py2app': OPTIONS},
    setup_requires=['py2app'],
)


  


  And I also had this in the beginning of my Python script :

  


  # Set ffmpeg and ffprobe paths relative to the app's Resources/bin directory
app_dir = os.path.dirname(os.path.abspath(__file__)) 

# Set ffmpeg and ffprobe paths relative to the app's Resources/bin directory
ffmpeg_path = os.path.join(app_dir, 'bin', 'ffmpeg')
ffprobe_path = os.path.join(app_dir, 'bin', 'ffprobe') 
AudioSegment.converter = ffmpeg_path
AudioSegment.ffprobe = ffprobe_path


  


  Don't know what else to try.

  


• Determine which decoders/demuxers/parsers ffmpeg needs to successfully consume file

  10 octobre 2024, par rschristian

  I'm trying to custom compile a build of ffmpeg.wasm as the prebuilt, "support everything" is a tad hefty at 35mb. This base build (as well as standard ffmpeg, running on my desktop) works perfectly fine for the provided file, however, so I do have something I can work against.

  


  My issue is that I'm a bit stuck on figuring out what precisely I need to support the provided file, the correct combination of decoders, demuxers, parsers, etc., and the encoders, muxers I'll need to use to convert it to my desired output.

  


  I'm sure I can brute force this with time, but is there a way of having ffmpeg report precisely which combination it's using when running against a file ? I've tried -report but it doesn't seem to contain this information, really it contains no more useful codex information than the standard output log as far as I can tell.

  


  For example, I can see the current file I'm testing with (foo.m4s) is h264 video and aac audio, so I tried the following flags based on what I've been able to find online and by looking through the list of muxers :

  


  --enable-decoder=aac,h264
--enable-demuxer=aac,h264
--enable-parser=aac,h264


  


  However, this results in the following error :

  


  foo.m4s: Invalid data found when processing input


  


  So it seems like it's not quite the correct list.

  


  Is there any good way to debug this ? Some way of having ffmpeg itself report exactly what I'll need set to handle this conversion using my own compilation ? As the goal is a minimum build, adding the kitchen sink and slowly reducing over time will obviously be super time consuming, so I'd like to avoid it if at all possible.

  


  ---

  


  Edit : Trial and error got me down to this, though I don't quite understand it (and the question still stands as I could reasonably need to handle other files in the future) :

  


  --enable-demuxer=aac,mov
--enable-parser=aac


  


  mov for some reason ended up being the fix ? The first line of ffmpeg's output was Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'foo.m4s', and so I simply grabbed those one-by-one and sure enough mov worked, despite the video having h264. Would love if someone could explain this too.