Skip to content
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

Feature request: obecli daemon #7

Open
mraaroncruz opened this issue Oct 30, 2012 · 6 comments
Open

Feature request: obecli daemon #7

mraaroncruz opened this issue Oct 30, 2012 · 6 comments

Comments

@mraaroncruz
Copy link

I would love to be able to use a config file that looks something like

# obe.conf
set input decklink
set input opts video-format=pal
set stream opts 0:vbv-maxrate=1000,vbv-bufsize=3000,bitrate=1000
set stream opts 1:bitrate=384,format=mp2
set muxer opts ts-muxrate=5000000
set output rtp

and I could run it like

obecli -d -c obe.conf --probe-input=true -p /var/run/obe.pid
# -d = daemonize, -c config file, -p pid file

and it would give me output like

Probing device: Decklink card 0. Timeout 20 seconds
Stream-id: 0 - Video: RAW 720x576i 25/1fps 
Stream-id: 1 - Audio: PCM stereo 0kbps 48kHz Language: none
Running with PID 1234

Our current solution is sending commands to a detached screen session which feels very much like a hack to me. Especially considering a control script in init.d or update-rc.d to start and stop obe.

Thanks,
Aaron

@mraaroncruz
Copy link
Author

I don't write C but I will start looking into implementing this myself. This has become a pain point because our audio/video sync is off (resynced when obe is restarted). Often when using the screen hack to restart obe it fails. The obecli is still running so i can't track the process and restart it with a system monitor.
I will create both the out of sync issue and the actual error when OBE fails to restart in other issues, the next time they occur.
Another issue with the obecli is when it is printing to console in my screen session, when it prints out a bunch of output, I am getting memory overuse issues. Which makes it very hard to log into my server and do anything at the most important times (when everything is exploding).
So as I said, I will work on this, though I have very little of an idea how - lcthw ;).
I would really appreciate even a short response letting me know that you have read the request.


Thanks,
aaron

@kierank
Copy link
Owner

kierank commented Dec 23, 2012

OBE only prints to the console when running when you have serious mux problems (and that'll get changed soon). What are the error messages? Whilst I'm not saying the use of screen is a good thing, there are people that do a lot of restarts and they work ok. The lipsync issue is of concern but nobody has reported any issues with that recently. There were issues with Blackmagic cards on certain drivers. I suppose if you want to see if OBE is running you could make it hold a lockfile.

Regards,

Kieran.

@mraaroncruz
Copy link
Author

Here is some example output.
Do you have a link to something that describes what you mean by hold a lockfile in this instance? Or could you give a brief explanation?
Thanks,
aaron

@kierank
Copy link
Owner

kierank commented Dec 23, 2012

You don't seem to have enough CPU on that machine as far as i can tell and some very serious SDI problems. Also this is syslog output, not terminal output.

@mraaroncruz
Copy link
Author

sorry, these lines are what are showing up in the screen session.
speedcontrol underflow (-0.039377 sec)
spitting out line after line of that.

PS. Is this a good place for this thread? If there is a better one, let me know.

@kierank
Copy link
Owner

kierank commented Dec 23, 2012

Then for some reason your OS has decided to redirect syslog calls to stderr/stdout for some bizzare reason. I have no idea why this is the case.

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