The OSG uses the Chain Of Responsibility Design Pattern for the
plugins - so it's the plugins themselves to decide what formats they
can load. This enables them to handle multiple formats if they can
support it. From the description it sounds like the ffmpeg isn't
doing a good enough at deciding what it can or cannot load.
On 18 October 2016 at 18:18, Riccardo Corsi <riccardo.co...@kairos3d.it> wrote:
> Hi Robert and all,
> I'm currently using the ffmpeg plugin to load some movies - it works just
> fine but my application started generating a lot of errors on console like
>> FFmpegImageStream::open : av_open_input_file() failed : AVERROR_NOENT
> every time an image has to be loaded.
> You can reproduce the issue with the modified osgMovie example in attach,
> which also loads the textured cow model.
> Digging a bit I've seen that's because the file reading mechanism tries to
> read from all the already loaded plugins, reagardless of their extension(s)
> See here:
> I thought that the extension supported by each plugin was checked before
> trying to use it.
> Besides the annoying errors on the console, wouldn't it be more efficient?
> osg-users mailing list
osg-users mailing list