Re: [vdr] Few more questions about xinelibout
On Fri, Dec 5, 2008 at 12:25 AM, Petri Helin [EMAIL PROTECTED] wrote: On Thu, Dec 4, 2008 at 11:43 PM, Alex Betis [EMAIL PROTECTED] wrote: Hi all, Few more questions about xinelibout. I've run the frontend now as a separate task and looks like it doesn't crash now except when I try to open a picture, I'll try to debug it later. Perhaps your pictures a too big for xv? Try to reduce their size. I would expect the software to do it... The questions are probably very simple: - When I playback a file, how can I move back? When replaying a live stream my and keys act as backward and forward buttons. In file playback forward runs the movie forward indeed, but backward button slows the playback until its fully stopped. This is a standard feature/restriction of many software players. You can jump backwards a given number of seconds, but a true rewind is not possible. Jump back is good enough, the question is how can I do it in xinelibout frontend? - Does deinterlacing settings from VDR menu apply also to movie playback? Sometimes I can see effects of picture is not sync with the screen, I mean that the picture is shown as its 2 halfs (top and bottom) that are moving in very little difference. Thats mostly seen when the whole picture is moved. Sounds like tearing to me. Usually caused by difference in the output refresh rate and the video being played back, or just crappy drivers (like Intel with certain hardware combined with Textured video). I was looking for the right word... tearing... I have nVidia 177.82 driver. Again, mplayer has no such problem. Thanks. -Petri ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Few more questions about xinelibout
On Fri, Dec 5, 2008 at 10:48 AM, Alex Betis [EMAIL PROTECTED] wrote: On Fri, Dec 5, 2008 at 12:25 AM, Petri Helin [EMAIL PROTECTED] wrote: On Thu, Dec 4, 2008 at 11:43 PM, Alex Betis [EMAIL PROTECTED] wrote: Hi all, Few more questions about xinelibout. I've run the frontend now as a separate task and looks like it doesn't crash now except when I try to open a picture, I'll try to debug it later. Perhaps your pictures a too big for xv? Try to reduce their size. I would expect the software to do it... You need to patch xine-lib to do that. But first I suggest you try out with smaller pictures to confirm the reason. What is the resolution of the pictures? The questions are probably very simple: - When I playback a file, how can I move back? When replaying a live stream my and keys act as backward and forward buttons. In file playback forward runs the movie forward indeed, but backward button slows the playback until its fully stopped. This is a standard feature/restriction of many software players. You can jump backwards a given number of seconds, but a true rewind is not possible. Jump back is good enough, the question is how can I do it in xinelibout frontend? See the README file under Media player key bindings for video files: GreenJump 1 min back Yellow Jump 1 min forward 1, User8 Jump 20 s back 3, User9 Jump 20 s forward - Does deinterlacing settings from VDR menu apply also to movie playback? Sometimes I can see effects of picture is not sync with the screen, I mean that the picture is shown as its 2 halfs (top and bottom) that are moving in very little difference. Thats mostly seen when the whole picture is moved. Sounds like tearing to me. Usually caused by difference in the output refresh rate and the video being played back, or just crappy drivers (like Intel with certain hardware combined with Textured video). I was looking for the right word... tearing... I have nVidia 177.82 driver. Again, mplayer has no such problem. Try xine-ui with the same file. If that works, compare files ~/.xine/config and ~/.xine/config_xineliboutput for any differences. -Petri ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Few more questions about xinelibout
On Fri, Dec 5, 2008 at 10:59 AM, Petri Helin [EMAIL PROTECTED] wrote: I've run the frontend now as a separate task and looks like it doesn't crash now except when I try to open a picture, I'll try to debug it later. Perhaps your pictures a too big for xv? Try to reduce their size. I would expect the software to do it... You need to patch xine-lib to do that. But first I suggest you try out with smaller pictures to confirm the reason. What is the resolution of the pictures? You're right! Small sized pictures (640x480) do not crash it, while the ones from my camera without conversion (3072x2304) crash it. Could you point me to a patch xine-lib to scale automatically? The questions are probably very simple: - When I playback a file, how can I move back? When replaying a live stream my and keys act as backward and forward buttons. In file playback forward runs the movie forward indeed, but backward button slows the playback until its fully stopped. This is a standard feature/restriction of many software players. You can jump backwards a given number of seconds, but a true rewind is not possible. Jump back is good enough, the question is how can I do it in xinelibout frontend? See the README file under Media player key bindings for video files: GreenJump 1 min back Yellow Jump 1 min forward 1, User8 Jump 20 s back 3, User9 Jump 20 s forward Thanks! I've read it long ago and forgot that part already. - Does deinterlacing settings from VDR menu apply also to movie playback? Sometimes I can see effects of picture is not sync with the screen, I mean that the picture is shown as its 2 halfs (top and bottom) that are moving in very little difference. Thats mostly seen when the whole picture is moved. Sounds like tearing to me. Usually caused by difference in the output refresh rate and the video being played back, or just crappy drivers (like Intel with certain hardware combined with Textured video). I was looking for the right word... tearing... I have nVidia 177.82 driver. Again, mplayer has no such problem. Try xine-ui with the same file. If that works, compare files ~/.xine/config and ~/.xine/config_xineliboutput for any differences. Strange thing is that I don't see tearing any more. But I'll know where to look in case it comes back. By the way, I assume the configuration is overwritten by frontend somehow since the config_xineliboutput says there is no deinterlacing, while frontend settings include deinterlacing. Do you know where the frontend configuration is stored? The plugins\xineliboutput in VDR config is empty. Thanks again! -Petri ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Few more questions about xinelibout
On Fri, Dec 5, 2008 at 11:06 AM, Gerald Dachs [EMAIL PROTECTED] wrote: Quoting Alex Betis [EMAIL PROTECTED]: I was looking for the right word... tearing... I have nVidia 177.82 driver. Again, mplayer has no such problem. You could try to activate all sync to vblank irqs with nvidia-settings. I've checked it now, its set to Sync to VBlank already in XVideo setting tab. It's not set in OpenGL, but I don't use it for playback. As I wrote, the problem is gone somehow. Thanks. Gerald This message was sent using IMP, the Internet Messaging Program. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Switching time
Hi all, Another question to bother you... How long does it takes to switch a FTA channel on your system? In my case DVB-S. I wonder if this timing sounds ok to you (I think its kind of slow): 1.7.1 + ext64-livebuffer + xinelibout 2 channels on the same transponder - about 2 seconds - video and sound playing right after the switch. 2 channels on different transponders - about 4 seconds - sound is playing right after the switch, image is shown, but start moving about 1 more second later. Please let me know what is your status on that (including version you're using). Thanks. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR ERROR: can't set filter every 20 seconds
Hi My cable provider recently made a number of changes to channel allocations, and since then I'm getting the following errors every 20 seconds or so: Dec 6 10:57:14 callin vdr: [20844] ERROR: can't set filter (pid=16, tid=40, mask=FF): Device or resource busy Dec 6 10:57:35 callin vdr: [20844] ERROR: can't set filter (pid=0, tid=00, mask=FF): Device or resource busy Dec 6 10:57:35 callin vdr: [20844] ERROR: can't set filter (pid=17, tid=42, mask=FF): Device or resource busy Dec 6 10:57:35 callin vdr: [20844] ERROR: can't set filter (pid=16, tid=40, mask=FF): Device or resource busy Dec 6 10:57:57 callin vdr: [20844] ERROR: can't set filter (pid=0, tid=00, mask=FF): Device or resource busy Dec 6 10:57:57 callin vdr: [20844] ERROR: can't set filter (pid=17, tid=42, mask=FF): Device or resource busy Dec 6 10:57:57 callin vdr: [20844] ERROR: can't set filter (pid=16, tid=40, mask=FF): Device or resource busy Dec 6 10:58:17 callin vdr: [20844] ERROR: can't set filter (pid=0, tid=00, mask=FF): Device or resource busy There seems to be the same repeating pid/tid numbers: pid=16, tid=40 pid=0, tid=00 pid=17, tid=42 pid=18, tid=60 pid=20, tid=70 pid=18, tid=4E pid=18, tid=50 I have FF-2300 and budget C1500 TTcards. It seems to be affecting both. Symptoms are intermittant no lock on channels? Any ideas what this is?? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Switching time
On Fri, Dec 5, 2008 at 11:34 AM, Morfsta [EMAIL PROTECTED] wrote: On Fri, Dec 5, 2008 at 11:05 AM, Alex Betis [EMAIL PROTECTED] wrote: 2 channels on the same transponder - about 2 seconds - video and sound playing right after the switch. 2 channels on different transponders - about 4 seconds - sound is playing right after the switch, image is shown, but start moving about 1 more second later. Sounds long, I can channel change on DVB-T and DVB-S almost instantaneously. You can normally fix this by recompiling your kernel with low latency settings (timer frequency, kernel queuing methods etc) - normally selecting the best settings for a desktop helps. I agree. My channel changes are about 1 second regardless if I'm switching on different transponders or lnbs. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Switching time
On Sat, Dec 6, 2008 at 12:58 AM, VDR User [EMAIL PROTECTED] wrote: On Fri, Dec 5, 2008 at 11:34 AM, Morfsta [EMAIL PROTECTED] wrote: On Fri, Dec 5, 2008 at 11:05 AM, Alex Betis [EMAIL PROTECTED] wrote: 2 channels on the same transponder - about 2 seconds - video and sound playing right after the switch. 2 channels on different transponders - about 4 seconds - sound is playing right after the switch, image is shown, but start moving about 1 more second later. Sounds long, I can channel change on DVB-T and DVB-S almost instantaneously. You can normally fix this by recompiling your kernel with low latency settings (timer frequency, kernel queuing methods etc) - normally selecting the best settings for a desktop helps. I agree. My channel changes are about 1 second regardless if I'm switching on different transponders or lnbs. You're saying that kernel provided by distributors (Fedora 10 in my case) is not tuned for desktops? Interesting... Will try that after I'll try moving back to 1.7.0. Thanks. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
