On Thu, Jul 24, 2003 at 09:56:18PM +0200, Dirk Meyer wrote: > > 1) xine ignores the .xine/config file completely > > This works for me. I can't help you there.
Sorry, I wasn't specific; fbxine seems to ignore the file. I tried putting a couple of options in there to avoid the benchmarking, and enable passthrough, but it seemed to ignore them. > Yes and no. In current cvs (as in since yesterday) there is a patch > from me to control xine over stdin. I guess it's in your xine version, > too, but the patch to the --help is only on my hd now. Use --stdin to > control xine over stdin (and you should use --no-lirc, too -- but this > is not working for fbxine until I submit my new patch). Than write > stuff like "pause" or "quit" on stdin. I used --stdctl; though I patched stdctl to use stdin instead of stderror so I could try it from the command-line. > I use vidixfb for G400 framebuffer output. The docs say we should use > syncfb for G400, but I failed to get it running. One problem: vidixfb > doesn't support deinterlacing right now :-( I noticed :) syncfb wouldn't even compile for me... but vidix is ok as a starting point. What I wanted to ask, was how we should structure the xine events. I made a list of them (using xine --keymap=lirc) but I'm not sure how we want to add the xine events to event.py. Aubin ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Freevo-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-devel
