From: Thibaut M. <tma...@no...> - 2002-03-19 23:20:56
|
Hi, > Hi there, > > On Mon, 18 Mar 2002, Thibaut MATTERN wrote: > > html ? What ? entryref is simply a link to an another asx file > > oki, the mms plugin should be able to play back more than one stream. I > think there are two things to implement here: > > - make the asx parser correctly handle files containing more than one > stream Can I try to clean the code a little ? I don't understand the http request because it looks like a http server response and not a request. Who is the author ? > - make demux_asf <-> input_mms communicate about stream ends > so input_mms can connect to the next stream and demux_asf knows when a > new stream starts > > But even with the "only mms" way there is problems : > > Asx file can contain multiple "entry". The player should play each entry > > one by one. > > see above. this should be handled by input_mms and it needs to inform > demux_asf about stream ends/starts (or alternativly demux_asf must be able > to survive sudden stream changes) What is the easier ? > > And each "entry" can contain multiple "ref". The player should try to > > play the first, if the player can play it, it should play it and jump to > > the next entry after, if it is not, it should try to play the next "ref", > > ... > > ok, that can be easily handled within input_mms. > > > I've problems with the current asx parser, that's why I've tried to write > > a new one. > > I believe there is a lot of asx files that contain more than one "entry", > > and lot of broken links. > > I have no objections against your parser in that respect. I'm just worried > about input/demuxer plugins taking over the engine, that is likely to > break or lead to problems in the future because it breaks xine's > architecture. if you add your parser to input_mms, that's fine - the > current parser is truly a hack, so if your parser works better and handles > multiple streams in one asx file, that's great! Ok, I will try :) > ...but if you want to fully support .asx files, then you're implementing > playlists and these are handled in the gui, the xine engine itself doesn't > have playlists. > > Thus, whatever you do, make sure you don't break xine's architecture If you think about not calling xine_play from input_mms, I promise I will not try to do that. :=) > Cheers, > > guenter Thibaut |