-
Notifications
You must be signed in to change notification settings - Fork 93
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
Command-line interface (CLI) #63
Comments
Worth checking out: https://github.com/empirical-soft/command-interface |
Not sure for what purpose you really want to add this but this pattern most of the time just makes code harder to maintain. |
Here I was talking about creating a separate executable that can be run from the command line using command line parameters. Something like this:
In essence, this would enable using uvgRTP in simple situations without having to create a separate program. This would be really cool with our hevc encoder (which already has a command line interface), so one could take raw input and pipe it to kvazaar and then uvgRTP and the receiving uvgRTP would save it to a file on another computer! (I will update the description) This feature would not affect the existing code much, but would be an addition to it. That link was just something I found on HN, not sure if it is relevant or not. |
Ah k, then I misunderstood your intention.. yeah, would be a nice thing to have... |
There has been talk that this could be a useful feature for uvgRTP. Command-line interface would mean that outside programs could call uvgrtp from the command line and perform RTP operations that way without having to create and compile a separate application.
Something like this:
uvgrtp --input cin --format hevc --destination 127.0.0.1:10000 --source 127.0.0.1:9000
or
uvgrtp --input file.hevc --destination 127.0.0.1:10000 --source 127.0.0.1:9000
Outside contribution are welcome.
The text was updated successfully, but these errors were encountered: