Recherche avancée

Sur d’autres sites (4108)

• Passing shell variables containing spaces as arguments

  29 octobre 2014, par Julian Delphiki

  I know there are many of these questions out there already, but my situation is unique enough that none of them have helped me thus far.

  I’m writing a script that will reformat my (poorly tagged) music library. It’s currently in the form of Music/Genre/Artist/Album/##-Title.wav.

  From the Music directory, I run my script1, which calls find -name "*.wav" -exec script2 {} ${other_args}. Script2 parses the path to variables, creates the appropriate output directory if it doesn’t exist, and then calls ffmpeg to do the compression.

  ex : ($sourcefilepath contains {} from find)

  ffmpeg -i "$sourcefilepath" "$path/$to/$outfile.$extension"

  If my file name or path contains no spaces, it works like a charm.

  If it contains spaces, ffmpeg fails, with the following error :

  Blues/Country Blues/Rhythm, Country And Blues/08-Natalie Cole & Reba
  McEntire Since I Fell For You.wav : No such file or directory

  Note : that’s the source file it can’t find. The output file appears to be working correctly, even with spaces. That’s not the full command I’m running (it has some -metadata flags too, but that also appears to be working correctly. I’m debugging with the command I wrote above).

  The interesting thing here is that ffmpeg is NOT interpreting $sourcefilepath as two args, it just can’t find the file I specified. Running the following from the Music directory works.

  ffmpeg -i Blues/Country\ Blues/Rhythm\,\ Country\ And\ Blues/08-Natalie\ Cole\ \&\ Reba\ McEntire\ \ \ Since\ I\ Fell\ For\ You.wav output.flac

  I’m kind of stuck here. The other information on the web involves getting a command to see a variable with a space as one arg instead of multiple. I appear to have done that, but ffmpeg can’t find my file now.

  Normally I’d just use find -name "*.wav" -exec ffmpeg -i {} ${args} \; but I need to process the file path to extract my metadata.

  I’m fairly new to shell scripting ; does anybody know what’s going on here ?

• How to cut and concatenate the files so they are not off-beat when the file I got the bpm from is being muxed ?

  27 janvier 2017, par P. Dee

  I am cutting files with ffmpeg based on the bpm I found in a music file. So let’s assume, the file’s bpm = 120. That means, there are 2 bps and 1 beat every 500ms.

  So I cut a video files with multiples of 500ms length, ie 500ms, 1500ms, 3000ms etc. length. But cutting it using

  ffmpeg -ss start -i fileorig.mp4 -t duration part_number.mp4

  and finally creating a mylist.txt with

  file 'part_1.mp4'
  
  file 'part_2.mp4'
  
  ...

  and adding them via

  ffmpeg -f concat -i mylist.txt -c copy output.mp4

  and replacing the audio track with the music file, makes the videos be off-beat after some time.

  How to cut and concatenate the files so they are not off-beat when the file I got the bpm from is being muxed ?

• Invalid audio stream. Exactly one MP3 audio stream is required

  4 juin 2019, par user11588722

  I’ve written a small line to concat two mp3 files and add background music to the result. It works quite well, but I’m getting some weird errors. Can anyone identify the cause ?

  (inside a for loop)

  ffmpeg -y -i "Input/%%i" -i "Assets/outro.mp3" -filter_complex "[0:a][1:a]concat=n=2:v=0:a=1;amovie='Assets/music.mp3':loop=999,volume=0.2[s];[0][s]amix=duration=shortest" "tmp.audio.mp3"

  Errors :

  [mp3 @ 000000000059f180] Invalid audio stream. Exactly one MP3 audio stream is required.
  Could not write header for output file #0 (incorrect codec parameters ?) : Invalid argument
  Error initializing output stream 0:1 —

  Log file : https://pastebin.com/PLnu0Fvn