-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: spawn ffmpeg ENOENT #15
Comments
Do you have ffmpeg installed? See the Installation section in the readme. https://github.com/parshap/node-ffmetadata#installation |
@parshap Yes i have.
|
I also have this issue. I do not have ffmpeg installed globally, as I am using this in an Electron app (not all users will have ffmpeg installed). Instead I am using ffmpeg-binaries to load ffmpeg locally. This works fine for fluent-ffmpeg but seems incompatible with this lib. I have tried setting |
@jonbarrow It's been a long time, but I use ffmpeg-static-electron, and it works fine.
|
Error reading metadata { Error: spawn ffmpeg ENOENT
at exports._errnoException (util.js:1022:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:189:19)
at onErrorNT (internal/child_process.js:366:16)
at _combinedTickCallback (internal/process/next_tick.js:102:11)
at process._tickCallback (internal/process/next_tick.js:161:9)
at Function.Module.runMain (module.js:607:11)
at startup (bootstrap_node.js:158:16)
at bootstrap_node.js:575:3
code: 'ENOENT',
errno: 'ENOENT',
syscall: 'spawn ffmpeg',
path: 'ffmpeg',
spawnargs: [ '-i', 'song.mp3', '-f', 'ffmetadata', 'pipe:1' ] }
C:\Sumit Ridhal\GitHub\audio-meta\node_modules\ffmetadata\index.js:41
stream.emit("error", new Error(error.getBody().toString()));
^
TypeError: Cannot read property 'toString' of undefined
at ChildProcess. (C:\Sumit Ridhal\GitHub\audio-meta\node_modules\ffmetadata\index.js:41:50)
at emitTwo (events.js:125:13)
at ChildProcess.emit (events.js:213:7)
at maybeClose (internal/child_process.js:897:16)
at Socket.stream.socket.on (internal/child_process.js:340:11)
at emitOne (events.js:115:13)
at Socket.emit (events.js:210:7)
at Pipe._handle.close [as _onclose] (net.js:549:12)
The text was updated successfully, but these errors were encountered: