20,741
edits
Canvas development: Difference between revisions
Jump to navigation
Jump to search
→Placement/Element for Streaming: Computer Vision
| Line 1,972: | Line 1,972: | ||
# The UAV guys want to view/use external live video inside FlightGear as an instrument/texture (which would require a new Canvas::Element to render an external video stream to a canvas) | # The UAV guys want to view/use external live video inside FlightGear as an instrument/texture (which would require a new Canvas::Element to render an external video stream to a canvas) | ||
# the computer vision (OpenCV) guys want to stream FlightGear live video itself to another application for image processing purposes - the latter would require streaming FlightGear's main window view to an external program (i.e. by using FlightGear's CameraGroup code), possibly by using a corresponding "virtual Placement" that opens a socket to provide a live stream of the FlightGear main window via background thread. This makes only sense to pursue once we can [[#Supporting Cameras|render camera views to a canvas]] though.}} | # the computer vision (OpenCV) guys want to stream FlightGear live video itself to another application for image processing purposes - the latter would require streaming FlightGear's main window view to an external program (i.e. by using FlightGear's CameraGroup code), possibly by using a corresponding "virtual Placement" that opens a socket to provide a live stream of the FlightGear main window via background thread. This makes only sense to pursue once we can [[#Supporting Cameras|render camera views to a canvas]] though.}} | ||
The HTTP server already does this - if you select a ‘low compression’ image format such as TGA or uncompressed PNGs, it’s very close to what you want. It will be using a local TCP socket, not shared memory, but unless you want really large images, I am not sure the additional complexity is worth adding an entirely new image output system for. See the code for how to increase the max-fps (defaults to 5H but could be 30 or 60Hz) and file-format of the http-server; any image format supported by OSG ReaderWriter plugin should work. (Well, so long as the plugin implements writing!)<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/32522423/ | |||
|title = <nowiki> Re: [Flightgear-devel] Rendered image export to Shared Memory </nowiki> | |||
|author = <nowiki> James Turner </nowiki> | |||
|date = Jun 30th, 2014 | |||
|added = Jun 30th, 2014 | |||
|script_version = 0.36 | |||
}}</ref> | |||
{{FGCquote | {{FGCquote | ||