Hi Evgeny,

On 29 March 2013 01:26, Evgeny Pereguda <[email protected]> wrote:
> I had downloaded OpenSceneGraph-3.1.5 and looked at listing of ffmpeg plugin. 
> It has the same problem. State FFmpegPacket::PACKET_END_OF_STREAM interrupts 
> synchronization between video and audio. I understand that ffmpeg plugin has 
> ImageStream interface for including in OSG, but I think that it would be 
> better to have a separate interface for video files. I read that ImageStream 
> interface was created for texturing by series images, which are kept in one 
> file (for example format GIF), and there is not need a deep control of 
> ImageStream. But in my case, I need to show a video texture like element 
> video-player in 3D space. As a result, I need more deep control of it. I need 
> that code can receive event of finishing video.

ImageStream is written as the base class for dynamic imagery such as
video's that's why it's interface has video related features - just
not all the ones you are after ;-)

ImageSequence is subclass of ImageSequence for managing a sequence of images.

FFmpgImageStream is a subclass of ImageStream for wrapping up ffmpeg video.

If it just an end of stream event that you are after?  Don't forget
the OSG is open source so why not prototype yourself by modifiying
ImageStream base class to provide the callback and then modify the
ffmpeg plugin to utilize this when the appropriate callback is
attached to the ImageStream.  Once you've got something that works
well for your purposes then submit the full modified files to
osg-submissions if you feel they in a final form, or just post them
here on osg-users if you feel that you'd like further discussion.

This is how much of the OSG is developed - members of the community,
including myself develop a feature to solve a specific problem,
keeping an eye open for other usages, and then submit this for merging
directly if it's in a mature state, or submitting to for discussion
and this then evolves into something suitable for merging.  As
features are developed to solve specific problems they are kept
minimal and complete for that usage model.  As new users come along
they push the software in different ways and come up against
limitations for their particular usage model so then having to pitch
and adapt these features to encompass their usage needs.  This isn't a
strictly linear process but it does mean the software solves real
testable problems.

Cheers,
Robert.
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Reply via email to