Error: spawn ffmpeg ENOENT

[nerijusgood]

Hi,

SPD works just fine on MAC. However on Windows installed properly it give Error: spawn ffmpeg ENOENT error after every song is downloaded:

 - Downloading: Nine Inch Nails - Closer
 -  - DONE: Nine Inch Nails - Closer
Error: spawn ffmpeg ENOENT

I tried installing ffmpeg via npmjs and even via regular installation (downloading zip from their website...). Well nothing changes.

OS: Windows 10 Node: v0.12.7 npm: 2.11.3

Is it possible to avoid using ffmpeg at all? I googled similar issues on other projects using ffmpeg and in a lot of solutions the author just switched to something else or just avoided using ffmpeg. I am not sure what for it is used in SPD, so just a random suggestion :)

[qrpike]

If you can find a better cross platform tool I will change it. It is used to write the ID3 data to the .mp3 file. So when you load the file into iTunes it knows the Artist, track name, etc.

Thanks,

On Thu, Aug 27, 2015 at 2:02 PM, Nerijus notifications@github.com wrote:

Hi,

SPD works just fine on MAC. However on Windows installed properly it give Error: spawn ffmpeg ENOENT error after every song is downloaded:

• Downloading: Nine Inch Nails - Closer
• • DONE: Nine Inch Nails - Closer Error: spawn ffmpeg ENOENT

I tried installing ffmpeg via npmjs and even via regular installation (downloading zip from their website...). Well nothing changes.

OS: Windows 10 Node: v0.12.7 npm: 2.11.3

Is it possible to avoid using ffmpeg at all? I googled similar issues on other projects using ffmpeg and in a lot of solutions the author just switched to something else or just avoided using ffmpeg. I am not sure what for it is used in SPD, so just a random suggestion :)

— Reply to this email directly or view it on GitHub https://github.com/qrpike/spotify-playlist-downloader/issues/18.

[Ron-J1]

Found a solution! Installing ffmpeg doesn't add it to your PATH variable. I was lazy and copied the three executables into a bin folder within my PATH variable and the script runs without errors now. Alternatively, you should add the path to the executables of ffmpeg to your PATH variable.

Also, be aware, that ffmpeg writes id3v2.4 which isn't readably by the windows explorer or windows media player.

modifying the downloader.js from line 115 - 128 to read:

Track.prototype.writeMetaData = function(filepath) {
  var id3;
  var options = {
            "id3v2.3": true,
  };
  id3 = {
    artist: this.track.artist[0].name,
    album: this.track.album.name,
    title: this.track.name,
    date: this.track.album.date.year,
    track: this.track.number
  };
  return ffmetadata.write(filepath, id3, options, this.cb);
};

fixes it until qrpike can integrate it into a new update.

Greetings, Ron

[Ron-J1]

If the id3v2.3 fix doesn't work straight away, you might have to install ffmetadata above version v.0.4