From: Michael R. <mr...@us...> - 2004-10-02 10:39:34
|
Hi Mike, > > That's true, this handling is a bit strange, but what is wrong with > > calling _x_demux_control_start()? After all, when the coding of the audio > > stream changes, you could argue that this is close to starting a new > > stream. _x_demux_control_start() has no side effects except resetting > > some engine values. > > I see. I thought it assigned new buffers etc so I was a bit reticent to > continue using it. The patch I sent to the list yesterday works around the > need for it by using the xine playlist and removing the OSD channel > selector, This way, the xine-engine 'knows' that each 'channel' is a new > set of PIDs and potentially, stream types. It also has the advantage of > working the way a new user might expect :) I think that's an even better solution. Michael -- If a packet hits a pocket on a socket on a port, And the bus is interrupted as a very last resort, And the address of the memory makes your floppy disk abort, Then the socket packet pocket has an error to report! |