-
Notifications
You must be signed in to change notification settings - Fork 15
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
Live video stream support #273
Comments
The ROV provides an analog 1080p50 signal via SDI. In order to get a HTTP video stream, a video encoding device like this would be required. I see the following issues:
|
Investigate which exact device would provide the correct video stream that would be compatible with a browser and BIIGLE. The GEOMAR people might buy such a device. Create a mockup for a setup with BIIGLE and live video streaming. |
I think this device would be the correct one. It converts an SDI video stream to an MPEG-TS stream that can be served via HTTP. However, it is not clear if the stream is compatible with video streaming JavaScript libraries (i.e. HLS, HTTP Live Streaming). It claims that "live stream previewing on any web browser" is possible in the web interface of the device, so it should work. I asked the manufacturer via email to be sure. |
The manufacturer did not respond. However, I found an alternative (cheaper) device here. It's a 3G-SDI to H.264 converter which supposedly supports live streaming via HLS. This would work with hls.js. The availability of such a device means that we could do an experimental implementation with a fake HLS stream and hls.js. The library includes a |
Here is an example command to use VLC to convert a video to static (non-live) HLS files (source):
|
Something to read on video live streaming: https://www.daily.co/blog/video-live-streaming/ |
Here is a summary of an informal meeting with representatives of DFO Canada, Marine Scotland, GEOMAR and Bielefeld University discussing live video annotation. Existing solutions
Essential features of a live video annotation system
Next steps
Technical thoughts
|
Right now I tend to prefer the OFOP/IRLS solution of not showing the video stream in the annotation application. The application should run on desktop machines but also on a tablet or phone. It should be able to read metadata (including the current time) from the ship systems (GPS?). Users should be able to press different predefined buttons to mark the current timestamp with a (whole frame annotation) label. If they keep the button pressed, a multi-frame whole frame annotation is recorded. In addition to the timestamp, the app can also record additional predefined metadata coming from the ship (e.g. geolocation, ROV sensor data). Later, the app produces a file that can be imported in BIIGLE to create annotations of a video. To make this easier, it should also offer a label (tree) import from BIIGLE so the labels can be matched with their UUIDs during the import. Additional idea: Users can record a "voice label". They just speak what they see which may be quicker than entering a new label on the fly that does not yet exist as a button in the app. The concept of a voice label could be added to BIIGLE too. |
I played around with video stream support. An OGG stream via HTTP can be created with VLC like this:
The stream is published at
localhost:8080
. If I set this as the video source in the video annotation tool it works, if somewhat flaky. The following issues need to be resolved:0
when the stream is opened. Annotations created like this do not have the correct time when later applied to the original video file.Idea: BIIGLE itself listens to the video stream and records it. The video annotation tool then shows a stream of the recorded version of the video. The keyframes of new annotations must be placed relative to the start of the recorded version.
This can't continue until we have more information on how the actual video streams of the ROV work.
The text was updated successfully, but these errors were encountered: