-
Notifications
You must be signed in to change notification settings - Fork 10
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
Starting the websocket server? #1
Comments
Have you built WSStreamer yet? If you have, you can use the WSStreamer executable in the following way:
It defaults to
Let me know if you need help building WSStreamer |
Make sure you have the Boost libraries installed and setup properly first:
|
I've added a README. Let me know if you need anymore information. |
Thanks so much! I'm still resolving some issues with building boost. While I get that ironed out, do you think it would be possible to seek/skip around on an h264-encoded stream using websockets? |
It should be possible, but you won't be able to seek based on time as there's no time index. The .264 files are just NAL frames strung together. You can however implement a system where you index the file first by searching for all the NAL headers (they start with a 4 byte header (0x00000001) and saving the file read head position for each one so you can seek based on NAL number. Then you can implement a "SEEK" message in WSStreamerHandler::on_message that adjusts the file read head. Unfortunately I don't have time to implement this in the next few weeks. You are welcome to try to implement that in the source though :) |
I'm a bit confused on how I can get your code up and running, any help would be appreciated. It looks like some really cool stuff you've built, but I can't play around with it unless I can setup the websockets, etc. Thanks!
The text was updated successfully, but these errors were encountered: