Recherche avancée

Sur d’autres sites (6514)

• Drop the unofficial extension prefix for MPEG and MPEG-TS formats

  29 novembre 2014, par Florent Le Coz

  Drop the unofficial extension prefix for MPEG and MPEG-TS formats
  As per the RFCs :
  
  http://tools.ietf.org/html/rfc3555#page-38
  
  http://tools.ietf.org/html/rfc3003
  CC : libav-stable@libav.org
  

  • [DBH] libavformat/mp3enc.c
  • [DBH] libavformat/mpegtsenc.c
  • [DBH] libavformat/rawenc.c

• Piping output of youtube-dl to a script using ffmpeg looks ok using echo but returns an error when executing

  22 février 2016, par user556068

  I am trying to use youtube-dl to get the urls of some videos and then pipe the resulting urls into the input of my script. So in my terminal I do

  youtube-dl --ignore-config -iga ~/Desktop/youtube/videolist.txt | myscript.sh

  In my script I define things as

  command='ffmpeg'        
  
  inputArgs='-i'              
  
  outputArgs='-c:v libx264 -preset ultrafast -qp 0'       
  
  directory="${HOME}/Desktop/Videos/"
  
  output="video${count}"      
  
  extension='mp4'         

  I test it with echo to make sure everything appears in the correct order.

  echo "${command}" "${inputArgs}" "${input}" "${outputArgs}" \
  
  "${directory}""${output}${count}"."${extension}"

  And the output from that looks correct. But when I try to run the same thing without the preceding echo command, i.e.,

  "${command}" "${inputArgs}" "${input}" "${outputArgs}" \
  
  "${directory}""${output}${count}"."${extension}"

  I get an error message that says

  At least one output file must be specified.

  So it seems pretty obvious to me that I’m doing something wrong when attempting to execute it.

  I have tried :

  • quoting the entire line as a whole
  • quoting different sections together
  • using the exec command in front of everything

  No matter what I do, an error occurs at some point in the process. I know it’s something simple I’m doing wrong. Would someone please enlighten me as to what that might be ?

  I feel very strongly that the . shouldn’t just be in the middle of everything like that, but I really don’t know.

  Again, everything looks as it should when I run echo before the string of shell parameters.

  If more of the script I’m using is needed to understand what I’m talking about, that is not a problem.

• Piping output of youtube-dl to a script using ffmpeg looks ok using echo but returns an error when executing

  29 mai 2020, par I0_ol

  I am trying to use youtube-dl to get the urls of some videos and then pipe the resulting urls into the input of my script. So in my terminal I do

  



  youtube-dl --ignore-config -iga ~/Desktop/youtube/videolist.txt | myscript.sh


  



  In my script I define things as

  



  command='ffmpeg'        
inputArgs='-i'              
outputArgs='-c:v libx264 -preset ultrafast -qp 0'       
directory="${HOME}/Desktop/Videos/"
output="video${count}"      
extension='mp4'         


  



  I test it with echo to make sure everything appears in the correct order.

  



  echo "${command}" "${inputArgs}" "${input}" "${outputArgs}" \
"${directory}""${output}${count}"."${extension}"


  



  And the output from that looks correct. But when I try to run the same thing without the preceding echo command, i.e.,

  



  "${command}" "${inputArgs}" "${input}" "${outputArgs}" \
"${directory}""${output}${count}"."${extension}"


  



  I get an error message that says

  



  


  At least one output file must be specified.

  


  



  So it seems pretty obvious to me that I'm doing something wrong when attempting to execute it.

  



  I have tried :

  



  

  • quoting the entire line as a whole

  


  • quoting different sections together

  


  • using the exec command in front of everything

  


  



  No matter what I do, an error occurs at some point in the process. I know it's something simple I'm doing wrong. Would someone please enlighten me as to what that might be ?

  



  I feel very strongly that the . shouldn't just be in the middle of everything like that, but I really don't know.

  



  Again, everything looks as it should when I run echo before the string of shell parameters.

  



  If more of the script I'm using is needed to understand what I'm talking about, that is not a problem.