Recherche avancée

Sur d’autres sites (6441)

• Writing metadata (Artist Name, Song Title, Year, Album, Duration, Genre) to mp3/m4a audio file using youtube-dl (subsequent AtomicParsely error)

  10 décembre 2016, par IRNotSmart

  I am extracting audio only from youtube videos using youtube-dl. I would like to write the metadata (i.e. Artist Name and Song Title, Year, Album, Duration, Genre) into the mp3/m4a file after downloading. My attempt to accomplish this starts with this code :

  @echo off
  
  youtube-dl --format m4a/mp3 --youtube-skip-dash-manifest --embed-thumbnail -o "%%(title)s.%%(ext)s" --metadata-from-title "%%(artist)s - %%(title)s" --add-metadata 2Y6Nne8RvaA
  
  pause

  This code produces the following output :

  [youtube] 2Y6Nne8RvaA: Downloading webpage
  
  [youtube] 2Y6Nne8RvaA: Extracting video information
  
  [youtube] 2Y6Nne8RvaA: Downloading thumbnail ...
  
  [youtube] 2Y6Nne8RvaA: Writing thumbnail to: Kungs vs Cookin' on 3 Burners - Thi
  
  s Girl.jpg
  
  [download] Destination: Kungs vs Cookin' on 3 Burners - This Girl.m4a
  
  [download] 100% of 2.99MiB in 00:01
  
  [ffmpeg] Correcting container in "Kungs vs Cookin' on 3 Burners - This Girl.m4a"
  
  
  
  [fromtitle] parsed title: This Girl
  
  [fromtitle] parsed artist: Kungs vs Cookin' on 3 Burners
  
  [ffmpeg] Adding metadata to 'Kungs vs Cookin' on 3 Burners - This Girl.m4a'
  
  ERROR: AtomicParsley was not found. Please install.
  
  Press any key to continue . . .

  As you can see, I am able to successfully able to add a few of the tags from the video, but not all of them and the Year is royally screwed up.
  

  What is this AtomicParsely error and how do I remedy it ? Do I need this program to correctly add all the Metadata to the file that I want, or can this be accomplished in another way ?

  Referencing Steven Penny’s post, FFmpeg metadata not showing in Windows ?, is solving this problem as simple as using an ffmpeg command ?

  When I do a google search for this song, the first link that shows is the exact link I’m using on YouTube, and the search shows pertinent metadata (see below). I’m not sure if this data is input manually by users, or if Google mined this from the video :
  

  I admit that I’m new to using youtube-dl and ffmpeg, but with the help of the commenters on StackOverflow, I’m learning more each day. This post is a follow-up to my previous question : Downloading YouTube to mp3 and writing metadata (artist/song title) to mp3 file using youtube-dl

• 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.