-
Notifications
You must be signed in to change notification settings - Fork 109
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 thrown shortly after clicking movie #11
Comments
It seems like you are missing Right now ffmpeg is required to convert movies, however issue #9 aims to fix that, making ffmpeg an optional dependency. You'll need to install ffmpeg with Let me know how this works for you. And if it works provide the install command for ffmpeg, and I'll add it to the README. |
Hmm ok. I had installed ffmpeg from the repos before building. I'll see On Mon, Jul 8, 2013 at 2:59 PM, AaronO [email protected] wrote:
|
Ok ffmpeg output concerning theora and vorbis ffmpeg -codecs D VSD theora Theora |
Compiled ffmpeg from source and made sure to have --enable-libtheora --enable-libvorbis as configure options Same error. Is there a way to have the runtime more verbose about the error? |
also experiencing the same issue |
ffmpeg's output on stderr is piped to the process' stderr so you should see it display on the command line. I'll add some extra logging to TV.js' server side when dev mode is activated which should help. |
Everything I do to redirect stderr to a file or stdout just prints events.js:72 Best I can think is something messed up in the compile process. There were a bunch of things I had to manually install (npm install whaterver the build errored out on). |
I got the same. ffmpeg version 0.8.6-4:0.8.6-0ubuntu0.12.04.1 is installed. is there a solution for this yet? |
Built on an Ubuntu 13.04 machine with node 0.10.12
In terminal shortly after clicking movie (when it says buffering to 1%)
Server listening on: http://localhost:8888
events.js:72
throw er; // Unhandled 'error' event
^
Error: spawn ENOENT
at errnoException (child_process.js:980:11)
at Process.ChildProcess._handle.onexit (child_process.js:771:34)
The text was updated successfully, but these errors were encountered: