From: Miguel F. <mi...@ce...> - 2003-04-03 14:06:32
|
On Thu, 2003-04-03 at 10:36, Jeroen Asselman wrote: > Miguel Freitas wrote: > > > On Tue, 2003-04-01 at 07:14, Jeroen Asselman wrote: > > > Currently xine seems to be blocking when reading from an empty fifo > > > (that is: xine fifo:///tmp/fifo) and it doesn't respond at all until > > > something is written into the fifo. It isn't even possible to close xine > > > the normal way. > > > Is this intentional behaviour? > > > > that should be fixed in current cvs. at least you should be able to stop > > or quit while fifo is blocked. > > I don't want to be anoying. But I downloaded a CVS xine-lib version, (3 april > '03). And the problem still seems to be there. you mean a fifo that has never received any data? ok, that will block on a different stage (trying to probe demuxers). the case that was fixed is stop/quiting xine when the fifo gets empty, but has delivered some data to start with... regards, Miguel |