[vlc-devel] DASH access plugin
christopher.mueller at itec.uni-klu.ac.at
Thu Apr 14 12:45:07 CEST 2011
Currently I have some time to work on the DASH-Plugin. But I have seen that
my questions are still not answered.
For me your initial request
* The plugin still seems to override all HTTP URIs. This is not acceptable
as VLC supports some other XML file formats over HTTP too, and they still
need to work. There are two ways around this:
So is it necessary to port everything to another layer? If it is necessary,
DASH supports byte-rage seeking and time-based seeking but I think the
"stream_filter layer" would fit best? Do I have to take care about anything
when I move the plugin to the "stream_filter layer"?
> Gesendet: Montag, 07. März 2011 20:34
> An: 'Mailing list for VLC media player developers'
> Betreff: Re: [vlc-devel] DASH access plugin
> > Le lundi 7 mars 2011 20:15:36 Christopher Müller, vous avez écrit :
> > > - p_access->psz_demux = strdup("avformat") will only be set if the
> > XML is a
> > > valid DASH XML
> > > I thought that this will fix what you have mentioned, because the
> > HTTP URI
> > > will only be overwritten if the XML is a valid DASH XML?
> > You're still forcing one more HTTP/TCP connection for each and every
> > HTTP URI
> > that is ever opened with VLC. This is _not_ a good idea.
> I could check the file extension before I open the HTTP connection
> this be ok for you? But also other plugins at the access layer that try
> open the XML, have to open a HTTP connection to check the content of
> file or? I do not want to port everything to the stream_filter layer if
> is not necessary.
> vlc-devel mailing list
> To unsubscribe or modify your subscription options:
More information about the vlc-devel