Re: [vdr] femon plugin doesn't work ERROR (femonosd.c, 504): Function not implemented
Why not state the real error which is not enough ram on device X for osd? with a hint message like: Require xyz KB, only have 2048KB. On 9/15/09, Oliver Endriss o.endr...@gmx.de wrote: Rolf Ahrenberg wrote: Sep 15 08:37:36 video vdr: [18526] ERROR (femonosd.c,504): Function not implemented Your DVB driver doesn't provide the FE_READ_UNCORRECTED_BLOCKS ioctl - it shouldn't be fatal. Hm, wouldn't it be better to display something like 'n/a' in the osd instead of logging an error? CU Oliver -- VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/ 4 MByte Mod: http://www.escape-edv.de/endriss/dvb-mem-mod/ Full-TS Mod: http://www.escape-edv.de/endriss/dvb-full-ts-mod/ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -- Sent from my mobile device ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] femon plugin doesn't work ERROR (femonosd.c, 504): Function not implemented
Would you care to write such a patch for vdr? In a way that Klaus could simply include in future releases. I think it would help a lot for end-users, trying figure out what possible causes are. On 9/16/09, Rolf Ahrenberg rahre...@cc.hut.fi wrote: On Wed, 16 Sep 2009, Theunis Potgieter wrote: Why not state the real error which is not enough ram on device X for osd? with a hint message like: Require xyz KB, only have 2048KB. The osOutOfMemory error comes from the VDR - not from the plugin. Of course you could log another more detailed error message in plugins, but it would be just redundant information to fill up your syslog. IMO, if you want more detailed error messages, you should modify VDR's cOsd::SetAreas() method rather than plugins. BR, -- rofa ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -- Sent from my mobile device ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Editing recordings and no instant video update when moving markers
Hello, When editing recordings I am struggling to fine tune marker placement as adjustments made with '4' and '6' keys while moving the marker as indicated by the time line do not update the video display with the corresponding position in the recording. Current setup: SW: VDR-1.7.9 (with freesat patch), NVIDIA driver 185-something, xineliboutput and xine as outptut plugins, ffmpeg-svn / xine-lib-1.2- hg from about two weeks ago, v4l-dvb-hg from about two weeks ago, slackware64-current OS HW: M2NPV-VM with onboard Nvidia 6150, Athlon something 64 bit dual core (at least 2.1GHz), a couple of SATA disks. - This problem only occurs with TS recordings, PES recordings made with vdr-1.7.0 with this setup work as expected. - With the xineliboutput plugin the display does not update at all when moving the marker. - With xine plugin the display updates but with seemingly random time intervals, from almost realtime as expected to delays of 1-5 seconds to sometimes not at all, depending on the recording and the position of the marker. I have a tedious workaround: set marker, play - If adjustment needed then - select marker, adjust with '4' or '6', play, repeat until no further adjustment needed. Does anyone have the same problem? Does anyone NOT have this problem? What can I do to fix this? Best wishes, Ian. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Editing recordings and no instant video update when moving markers
On 16/09/2009, Ian Bates ian_and_joa...@talktalk.net wrote: Hello, When editing recordings I am struggling to fine tune marker placement as adjustments made with '4' and '6' keys while moving the marker as indicated by the time line do not update the video display with the corresponding position in the recording. Current setup: SW: VDR-1.7.9 (with freesat patch), NVIDIA driver 185-something, xineliboutput and xine as outptut plugins, ffmpeg-svn / xine-lib-1.2-hg from about two weeks ago, v4l-dvb-hg from about two weeks ago, slackware64-current OS HW: M2NPV-VM with onboard Nvidia 6150, Athlon something 64 bit dual core (at least 2.1GHz), a couple of SATA disks. - This problem only occurs with TS recordings, PES recordings made with vdr-1.7.0 with this setup work as expected. - With the xineliboutput plugin the display does not update at all when moving the marker. - With xine plugin the display updates but with seemingly random time intervals, from almost realtime as expected to delays of 1-5 seconds to sometimes not at all, depending on the recording and the position of the marker. I have a tedious workaround: set marker, play - If adjustment needed then - select marker, adjust with '4' or '6', play, repeat until no further adjustment needed. Does anyone have the same problem? Does anyone NOT have this problem? What can I do to fix this? Best wishes, Ian. I downgraded my vdr-xineliboutput to 1.0.4 on gentoo because of that. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Jumping while replay causes video to halt
Doesn't anyone have any suggestions where to start looking? \\Kartsa Kartsa kirjoitti: Hi all I am having some problems with jumping using yellow/blue and 1/3 buttons. Not always but almost the picture stops after jump. Its not on pause because pushing play does nothing. Using fast forward gets video playing again and then pushing play resumes playback. There is nothing in the logs that would tell me what the problem might be. Or at least I can't find anything. I have ubuntu and vdr installed from packages. vdr -V gives: vdr (1.6.0-2/1.6.0) - The Video Disk Recorder extrecmenu (1.1) - Extended recordings menu streamdev-server (0.3.4) - VDR Streaming Server skinsoppalusikka (1.6.4) - Soppalusikka skin conflictcheckonly (0.0.1) - Direct access to epgsearch's conflict check menu epgsearch (0.9.24) - search the EPG for repeats and more iptv (0.2.5) - Experience the IPTV menuorg (0.4.4) - Reorganizes the main menu burn (0.1.0-pre22) - Versatile convert-and-burn plugin pvrinput (2008-10-04) - use Hauppauge PVR as input device vompserver (0.3.0) - VDR on MVP plugin by Chris Tallon quickepgsearch (0.0.1) - Quick search for broadcasts undelete (0.0.6) - undelete for recordings xineliboutput (1.0.4) - X11/xine-lib output plugin epgsearchonly (0.0.1) - Direct access to epgsearch's search menu ttxtsubs (0.0.9) - Teletext subtitles weatherng (0.0.7-pre2) - Weather.com: Weather forecast osdteletext (0.8.1) - Displays teletext on the OSD I use vdr-sxfe for playback as a remote client on the same host. I tried regenerating index file with genindex with no change. How do I fix this? \\Kartsa ___ 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] femon plugin doesn't work ERROR (femonosd.c, 504): Function not implemented
On Wed, Sep 16, 2009 at 3:58 AM, Theunis Potgieter theunis.potgie...@gmail.com wrote: Would you care to write such a patch for vdr? In a way that Klaus could simply include in future releases. I think it would help a lot for end-users, trying figure out what possible causes are. I agree. Detailed error messages are the only ones worth printing/logging, especially when it comes to end-users trying to figure out why their box isn't working properly. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] femon plugin doesn't work ERROR (femonosd.c, 504): Function not implemented
Hi, please re-read my message. I was not referring to the osd size stuff, but to this error message: | Sep 15 08:37:36 video vdr: [18526] ERROR (femonosd.c,504): Function not implemented femon must not assume that drivers support all ioctls... CU Oliver Theunis Potgieter wrote: Why not state the real error which is not enough ram on device X for osd? with a hint message like: Require xyz KB, only have 2048KB. On 9/15/09, Oliver Endriss o.endr...@gmx.de wrote: Rolf Ahrenberg wrote: Sep 15 08:37:36 video vdr: [18526] ERROR (femonosd.c,504): Function not implemented Your DVB driver doesn't provide the FE_READ_UNCORRECTED_BLOCKS ioctl - it shouldn't be fatal. Hm, wouldn't it be better to display something like 'n/a' in the osd instead of logging an error? -- VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/ 4 MByte Mod: http://www.escape-edv.de/endriss/dvb-mem-mod/ Full-TS Mod: http://www.escape-edv.de/endriss/dvb-full-ts-mod/ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr