-
Notifications
You must be signed in to change notification settings - Fork 500
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
Play streams from STDIN #51
Comments
This seems related to #29 |
Have you tried the mkfifo trick? |
I tried the mkfifo trick, in combination with wget. IE:
But when the wget command finishes before omxplayer finished playing the stream, it will quit and say: "Have a nice day.". Is there a trick to evade this problem? |
Try: popcornmix@75f213a |
I'll try to build it including your commit. In File.cpp [L59] I see the following code:
Does this mean I have to use |
See: basically use "pipe:0" as a filename, and it will read from stdin. E.g. Note: keypresses won't work in this mode as they also use stdin. |
And this is the only option I have? |
A future feature would be accepting control from a socket, allowing control from another process (with it's own stdin), or external devices (e.g. iPhone/Android). But this request is implemented. |
See here for a (future) solution to controlling omxplayer when stdin is streaming a video. |
mkfifo solution works, but omxplayer terminates if no data in fifo. And, well, that's okay. But, omxplayer does blocking terminal. pipe:0 solution gives error and player terminates: Inconsistency detected by ld.so: dl-tls.c: 446: _dl_allocate_tls_init: Assertion `listp != ((void *)0)' failed! |
This feature can be a lot of help for stuff like get-iplayer or livestreamer, without having to resort to scripts that have to hack around this limitation with FIFO files to get support in omxplayer.
I tried adding a special case to translate the file "-" into a streaming URL "pipe:0" in OMXReader.cpp, but while omxplayer detected the stream type and information, it quit before playing any of the stream.
The text was updated successfully, but these errors were encountered: