Dirk Meyer wrote: > Hi, > > I came across a problem when writing kaa.player. When using xine it is > possible to keep the vo open between two files. This is a nice feature > we should use. On the other hand, if the user does not want to play a > new file after playing is done and we keep the vo open, freevo won't > be visible because xv and fb based vo will write above freevo. So how > can we make it possible? Should the user call die() when he doesn't > need the player? How can we notify the dead player to the user? The > 'quit' signal comes to mind, but for mplayer we always go to > STATE_NOT_RUNNING and die() will have no effect? And IIRC we need the > quit signal for canvas shared memory changes. > > I hope this is clear :) > > Ideas? > > Dischi
Maybe im totally out of my mind now, but what about drawing freevo directly on xine/mplayer to use things like mplayer -vo zr and the like? that way the player will always be open and only what is shown is changed? Just my quick reactions //NiXZe ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Freevo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freevo-devel
