8000 If I specify the output file as /dev/stdout, dvbjet seems to not flush the output · Issue #1 · lightful/DVBdirect · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

If I specify the output file as /dev/stdout, dvbjet seems to not flush the output #1

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

Open
YoshiWalsh opened this issue Feb 14, 2019 · 1 comment

Comments

@YoshiWalsh
Copy link
YoshiWalsh commented Feb 14, 2019

I'm trying to read the output of dvbjet into a NodeJS script. I'm using Node's child_process to launch dvbjet, and I'm specifying /dev/stdout as the output file on the dvbjet command line.

My NodeJS script never receives any data from dvbjet's stdout. I suspect the data is being buffered. If I use node-pty instead of child_process then I receive output, but as node-pty converts all output to a string the data is corrupted.

I'm wondering if it's possible to make dvbjet correctly flush stdout if /dev/stdout is specified as the output filename. I've tried a few things myself, but I don't know c++ so I'm not having much luck.

@phpbg
Copy link
phpbg commented Jun 2, 2019

Hi,
thats weird. I'm using dvbjet /dev/stdout in this PHP TV project and I receive correctly the output.

It doesn't seem to be a dvbdirect/dvbjet issue...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
0