vdr November 2006

vdr@linuxtv.org

61 participants
52 discussions

[Announce] LNB-sharing patch for VDR 1.4.0-3
by Matthias Lötzke 02 Jan '10

02 Jan '10

Hello! A new release of the configurable LNB-sharing patch for VDR 1.4 is available at: http://xn--ltzke-jua.de/dvb/VDR_LNB_sharing_patch/configurableLNBshare-VDR_… Changes: - added a missing "break" statement which froze vdr after pressing channel up/down buttons when the main menu was displayed. Thanks to Christian Jacobsen, "Horchi" and Anssi Hannula for reporting and analysing. - adapted to VDR 1.4.3 For general information about the LNB-sharing patch have a look at: http://xn--ltzke-jua.de/dvb/VDR_LNB_sharing_patch/Description.txt http://www.vdr-wiki.de/wiki/index.php/Lnbsharing-patch (german) Matthias.

2 1

EPG for Hotbird / russian programmes
by Harald Milz 23 Dec '08

23 Dec '08

Hi, now that my VDR works fine with 2 satellites thanks to the help of some kind folks here and the SourceCaps patch (did I mention it should be in the mainstream VDR?) I have now a couple of FTA programmes in russian language for my better half :-) The only problem is, none of these programmes carry any EPG information. The schedules are available on the web sites, mostly. Has somebody written a plugin that retrieves the schedules and creates proper EPG data from them? I might but not too soon... I understand this task can be a pain in <pick your favourite body part> because people use no SOA interfaces. TBNRussia provides an Excel file (yuck). TIA! -- Reader, suppose you were an idiot. And suppose you were a member of Congress. But I repeat myself. -- Mark Twain

4 7

FF card A/V sync suggestion
by C.Y.M 02 Feb '07

02 Feb '07

Since it has been several years now and I have never been able to solve the a/v desync issues with my Nexus-S FF card when playing back recordings, I was thinking about what could be done. As of now, I have been using xine with my FF card to fix the problem. But, if I use xine, then even live tv is played back over software. The problem was never with live tv, only playing back recordings. What if the mplayer plugin was modified to replace the default vdr playback for recordings. It currently works as is, but it has problems with split files (ie; 001.vdr, 002.vdr, etc.). Also, it would be nice if there was an option to replace the default playback in vdr for recordings (so we wouldnt have to select the mplayer plugin first every time). Just a suggestion, but using mplayer over mpegpes would definitely be a better solution for fixing the a/v desync instead of having to use xine for everything (since there never was a problem with live tv). Best Regards.

32 122

DVD plugin - sound jerky??
by Simon Baxter 31 Jan '07

31 Jan '07

I've had this problem for ages and never found any resolution to it as it's really only a problem with DVDs that have a lot of chapters. When it get towards the end of a chapter, the sound disappears. The video is still fine, but the sound stops. Are there any debugs I can run to get more info out of dvd-plugin?

4 10

flooded log when using status plugin
by Joachim Wilke 04 Jan '07

04 Jan '07

Hello everyone, when using the status plugin and tuning to a channel without an epg schedule, the syslog gets flooded with some hundreds of OsdProgramme messages: Nov 3 20:16:17 vdr vdr: [4676] status: cStatusTest::OsdChannel 2079 TechniSat Kanal 50 Nov 3 20:16:17 vdr vdr: [4676] status: cStatusTest::OsdProgramme Nov 3 20:16:17 vdr vdr: [4676] 01:00 (null) Nov 3 20:16:17 vdr vdr: [4676] (null) Nov 3 20:16:17 vdr vdr: [4676] 01:00 (null) Nov 3 20:16:17 vdr vdr: [4676] (null) Nov 3 20:16:17 vdr vdr: [4676] status: cStatusTest::OsdProgramme Nov 3 20:16:17 vdr vdr: [4676] 01:00 (null) Nov 3 20:16:17 vdr vdr: [4676] (null) Nov 3 20:16:17 vdr vdr: [4676] 01:00 (null) Nov 3 20:16:17 vdr vdr: [4676] (null) [...] These messages are caused by the else part in cDisplayChannel::DisplayInfo in menu.c: void cDisplayChannel::DisplayInfo(void) { if (withInfo && channel) { cSchedulesLock SchedulesLock; const cSchedules *Schedules = cSchedules::Schedules(SchedulesLock); if (Schedules) { const cSchedule *Schedule = Schedules->GetSchedule(channel); if (Schedule) { const cEvent *Present = Schedule->GetPresentEvent(); const cEvent *Following = Schedule->GetFollowingEvent(); if (Present != lastPresent || Following != lastFollowing) { SetTrackDescriptions(channel->Number()); displayChannel->SetEvents(Present, Following); cStatus::MsgOsdProgramme(Present ? Present->StartTime() : 0, Present ? Present->Title() : NULL, Present ? Present->ShortText() lastPresent = Present; lastFollowing = Following; } } else cStatus::MsgOsdProgramme(0, NULL, NULL, 0, NULL, NULL); } } } I would suggest removing the else part, because this MsgOsdProgramme call provides no information. As an alternative it should be limited to one call, similar to the check "(Present != lastPresent || Following != lastFollowing)" some lines above. Regards, Joachim.

2 1

Utf8-patch experiences, anyone?
by Petri Helin 31 Dec '06

31 Dec '06

Hi, I have been experimenting with increasing the resolution of the OSD with xineliboutput with at least some kind of success (see http://img79.imageshack.us/my.php?image=hdosdrx4.png and try to not get bothered about the other "images" you are forced to see, this was the first image sharing site I came across). Now there are some problems that have come up with the HD OSD. Font rendering and the way fonts and OSD are used by plugins are the main distractions. I bumped in to this Utf8-patch (http://www.vdr-wiki.de/wiki/index.php/Utf8-patch) which looks promising, but failed to find any more information than what is provided in the german wiki. And the latest adaptation is for VDR 1.4.0. Is the someone out there using this patch and could share his experiences? Maybe someone has adapted it to the current version of VDR... -Petri

7 12

Re: [vdr] [vdr bug]Shutdown during an active timer is broken
by vdr＠helmutauer.de 11 Dec '06

11 Dec '06

> > Then the message appears: "Next recording in -xx minutes - Shutdown > > anyway ?" > > When I now press ok the shutdown routine will be called and the timer > > given to the shutdown script is in the past, so the machine will shut > > down but never wake up again. > > Any easy solutions for this ? > > There's no simple solution to this, I think. I remember that this has > been discussed before, however without results. Using nvram-wakeup, the > nvram script will complain next and shutdown will not work, you have to > disable all running timers and all close timers, or nvram-wakeup wont > shut down. > And with acpi it will shutdown but never wake up, depending on the shutdown script. > The current solution just uses the remaining time to the next timer, and > thats the running one of course. > Thats not a solution - thats a bug :) The shutdown script should get the starttime of the next timer in the future, not a time in the past. > A proper solution would have to skip over the offending timers to get > the next timer that is at least xx minutes in the future. Probably the > easiest and most radical solution is to really disable (or skip) all > offending timers after each confirmation. > I've made some tries into this direction, but none of these are working correct with repeatable timers. The only solution which works reliable is to disallow shutdown when a recording is active. Bye Helmut

6 13

vdr shutdown handling / streamdev plugin
by Jörg Wendel 10 Dec '06

10 Dec '06

Hello, a question about the 'new' vdr shutdown handling implemented a few versions ago. Every time i connect a client to the streamdev plugin the log is full of these message: Nov 14 14:26:42 linvdr vdr: [8480] streamdev-server: no translation found for 'Streaming busy, can't shutdown' in language 1 (Deutsch) Nov 14 14:27:13 linvdr last message repeated 31 times Nov 14 14:27:19 linvdr last message repeated 6 times This is the code i found in the streamdev plugin: cString cPluginStreamdevServer::Active(void) { if (cStreamdevServer::Active()) return tr("Streaming busy, can't shutdown"); return 0; } I know, it's bescause of the missing translation ;) But why vdr call this so often, isn't it only required if the vdr is going to shutdown? Even without the log message, at first view it looks like unnecessary load? Regards Jörg

8 24

Segfault if cSkinDisplayMessage is replaced by another display object
by Udo Richter 05 Dec '06

05 Dec '06

Hi Klaus, I've isolated an null pointer dereferencing bug in cSkins::Message(): In the very rare case that a message is displayed using a cSkinDisplayMessage object, and the message is not removed before another cSkinDisplay object takes control, the next attempt to display a message while no cSkinDisplay::Current() object is available causes a segfault. The reason is that the cSkins::displayMessage pointer is not cleared if another cSkinDisplay object takes over. cSkins::Message() sees an existing displayMessage object, but accesses the non-existing cSkinDisplay::Current(), assuming they're both the same. The only way I know how to trigger this is to use mtStatus messages and allow user activity while the message is shown. I don't think that plain VDR can trigger this on its own. The attached patch changes cSkins::Message() by only checking the existence of cSkinDisplay::Current(). If no current cSkinDisplay exists, any old displayMessage object is deleted and a new one is created. Cheers, Udo --- skins.c.orig 2006-11-30 02:19:41.705523304 +0100 +++ skins.c 2006-11-30 02:33:28.269230960 +0100 @@ -226,8 +226,11 @@ } if (!Current()) return kNone; - if (!cSkinDisplay::Current() && !displayMessage) + if (!cSkinDisplay::Current()) { + if (displayMessage) + delete displayMessage; displayMessage = Current()->DisplayMessage(); + } cSkinDisplay::Current()->SetMessage(Type, s); cSkinDisplay::Current()->Flush(); cStatus::MsgOsdStatusMessage(s);

1 1

Problem to get vdr-to-vdr streaming working...
by Juha Pahkala 30 Nov '06

30 Nov '06

I've been trying to get vdr-to-vdr (both version 1.4.4) streaming working with streamdev (cvs from last sunday) for the past couple of days. I've tweaked the different settings but can't get the streaming to work. As a side note, http streaming is working without problems, so there's something I've done correctly. Anyhow, when trying to stream vdr-to-vdr, this is what I get on the server side: Nov 21 18:04:08 remote vdr: [7517] Streamdev: Accepted new client (VTP) 192.168.0.119:37794 Nov 21 18:04:19 remote vdr: [7517] Streamdev: Setting data connection to 192.168.0.119:44312 And this is on the client side: Nov 21 18:04:06 localhost vdr: [5870] VDR version 1.4.4 started Nov 21 18:04:06 localhost vdr: [5870] loading plugin: ./PLUGINS/lib/libvdr-softdevice.so.1.4.4 Nov 21 18:04:07 localhost vdr: [5870] loading plugin: ./PLUGINS/lib/libvdr-streamdev-client.so.1.4.4 Nov 21 18:04:07 localhost vdr: [5870] loading /home/user/.vdr/video/setup.conf Nov 21 18:04:07 localhost vdr: [5870] ERROR: unknown config parameter: softdevice.Postprocess Method = 0 Nov 21 18:04:07 localhost vdr: [5870] ERROR: unknown config parameter: softdevice.Postprocess Quality = 0 Nov 21 18:04:07 localhost vdr: [5870] loading /home/user/.vdr/video/sources.conf Nov 21 18:04:07 localhost vdr: [5870] loading /home/user/.vdr/video/channels.conf Nov 21 18:04:07 localhost vdr: [5870] loading /home/user/.vdr/video/remote.conf Nov 21 18:04:07 localhost vdr: [5870] reading EPG data from /home/user/.vdr/video/epg.data Nov 21 18:04:07 localhost vdr: [5871] video directory scanner thread started (pid=5870, tid=5871) Nov 21 18:04:07 localhost vdr: [5872] video directory scanner thread started (pid=5870, tid=5872) Nov 21 18:04:07 localhost vdr: [5871] video directory scanner thread ended (pid=5870, tid=5871) Nov 21 18:04:07 localhost vdr: [5872] video directory scanner thread ended (pid=5870, tid=5872) Nov 21 18:04:07 localhost vdr: [5870] no DVB device found Nov 21 18:04:07 localhost vdr: [5870] initializing plugin: softdevice (0.3.1): A software emulated MPEG2 device Nov 21 18:04:07 localhost vdr: [5870] [XvVideoOut]: patch version (2006-11-05) Nov 21 18:04:07 localhost vdr: [5870] [XvVideoOut]: Initialize XShmCreateImage Successful (0xb65bbcd0) Nov 21 18:04:07 localhost vdr: [5870] [XvVideoOut]: Initialize shmget Successful (2949120 bytes) Nov 21 18:04:07 localhost vdr: [5870] [XvVideoOut]: Initialize shmat Successful Nov 21 18:04:08 localhost vdr: [5870] [softdevice-xscreensaver]: xscreensaver not running Nov 21 18:04:08 localhost vdr: [5870] [XvVideoOut]: initialized OK Nov 21 18:04:08 localhost vdr: [5870] [XvVideoOut]: Intel(R) Video Overlay: available ports 73 - 73 Nov 21 18:04:08 localhost vdr: [5870] [XvVideoOut]: grabbed port 73 Nov 21 18:04:08 localhost vdr: [5870] [XvVideoOut]: max area size 1920 x 1080 Nov 21 18:04:08 localhost vdr: [5870] [XvVideoOut]: using area size 736 x 576 Nov 21 18:04:08 localhost vdr: [5870] [XvVideoOut]: XV_COLORKEY XvGettable XvSettable ( 0 [0x00000000] - 16777215 [0x00ffffff]) ( 66046 [0x000101fe] Nov 21 18:04:08 localhost vdr: [5870] [XvVideoOut]: XV_BRIGHTNESS XvGettable XvSettable ( -128 [0xffffff80] - 127 [0x0000007f]) ( 0 [0x00000000] Nov 21 18:04:08 localhost vdr: [5870] [XvVideoOut]: XV_CONTRAST XvGettable XvSettable ( 0 [0x00000000] - 255 [0x000000ff]) ( 64 [0x00000040] Nov 21 18:04:08 localhost vdr: [5870] [XvVideoOut]: XV_DOUBLE_BUFFER XvGettable XvSettable ( 0 [0x00000000] - 1 [0x00000001]) ( 1 [0x00000001] Nov 21 18:04:08 localhost vdr: [5870] [XvVideoOut]: XV_GAMMA0 XvGettable XvSettable ( 0 [0x00000000] - 16777215 [0x00ffffff]) ( 526344 [0x00080808] Nov 21 18:04:08 localhost vdr: [5870] [XvVideoOut]: XV_GAMMA1 XvGettable XvSettable ( 0 [0x00000000] - 16777215 [0x00ffffff]) ( 1052688 [0x00101010] Nov 21 18:04:08 localhost vdr: [5870] [XvVideoOut]: XV_GAMMA2 XvGettable XvSettable ( 0 [0x00000000] - 16777215 [0x00ffffff]) ( 2105376 [0x00202020] Nov 21 18:04:08 localhost vdr: [5870] [XvVideoOut]: XV_GAMMA3 XvGettable XvSettable ( 0 [0x00000000] - 16777215 [0x00ffffff]) ( 4210752 [0x00404040] Nov 21 18:04:08 localhost vdr: [5870] [XvVideoOut]: XV_GAMMA4 XvGettable XvSettable ( 0 [0x00000000] - 16777215 [0x00ffffff]) ( 8421504 [0x00808080] Nov 21 18:04:08 localhost vdr: [5870] [XvVideoOut]: XV_GAMMA5 XvGettable XvSettable ( 0 [0x00000000] - 16777215 [0x00ffffff]) (12632256 [0x00c0c0c0] Nov 21 18:04:08 localhost vdr: [5870] [XvVideoOut]: XvShmCreateImage Successful (0xb65bc5a8) Nov 21 18:04:08 localhost vdr: [5870] [XvVideoOut]: shmget Successful (0 bytes) Nov 21 18:04:08 localhost vdr: [5870] [XvVideoOut]: shmat Successful Nov 21 18:04:08 localhost vdr: [5870] [XvVideoOut]: XShmAttach rc = 1 (should be OK) Nov 21 18:04:08 localhost vdr: [5870] [softdevice] videoOut OK ! Nov 21 18:04:08 localhost vdr: [5870] [softdevice-audio] Opening alsa device default Nov 21 18:04:08 localhost vdr: [5870] [softdevice-audio] Using alsa AC3 device hw:0,1 Nov 21 18:04:08 localhost vdr: [5870] [softdevice-audio] Device opened! Ready to play Nov 21 18:04:08 localhost vdr: [5870] initializing plugin: streamdev-client (0.3.3-pre3-geni): VTP Streaming Client Nov 21 18:04:08 localhost vdr: [5870] setting primary device to 1 Nov 21 18:04:08 localhost vdr: [5870] SVDRP listening on port 2001 Nov 21 18:04:08 localhost vdr: [5870] setting current skin to "sttng" Nov 21 18:04:08 localhost vdr: [5870] loading /home/user/.vdr/video/themes/sttng-default.theme Nov 21 18:04:08 localhost vdr: [5870] starting plugin: softdevice Nov 21 18:04:08 localhost vdr: [5870] starting plugin: streamdev-client Nov 21 18:04:08 localhost vdr: [5870] reading EPG data from /home/user/.vdr/video/epg.data Nov 21 18:04:08 localhost vdr: [5877] section handler thread started (pid=5870, tid=5877) Nov 21 18:04:08 localhost vdr: [5876] streamdev-client: sections assembler thread started (pid=5870, tid=5876) Nov 21 18:04:08 localhost vdr: [5870] Streamdev: Connected to server 192.168.0.1:2004 using capabilities TSPIDS Nov 21 18:04:08 localhost vdr: [5870] Streamdev: Synchronizing EPG from server Nov 21 18:04:08 localhost vdr: [5873] [VideoOut]: 736x576 [0,0 736x576] -> 1024x576 [118,0 788x576] Nov 21 18:04:08 localhost vdr: [5873] [VideoOut]: 736x576 [0,0 736x576] -> 1024x576 [118,0 788x576] Nov 21 18:04:09 localhost vdr: [5870] remote control softdevice-xv - keys known Nov 21 18:04:09 localhost vdr: [5870] remote control KBD - learning keys Nov 21 18:04:09 localhost vdr: [5880] KBD remote control thread started (pid=5870, tid=5880) Nov 21 18:04:19 localhost vdr: [5870] switching to channel 27 Nov 21 18:04:19 localhost vdr: [5870] Streamdev: Filter 18, 78, 254 not available from 192.168.0.119:37794 Nov 21 18:04:19 localhost vdr: [5870] Streamdev: Filter 18, 80, 240 not available from 192.168.0.119:37794 Nov 21 18:04:19 localhost vdr: [5870] Streamdev: Filter 18, 96, 240 not available from 192.168.0.119:37794 Nov 21 18:04:19 localhost vdr: [5870] Streamdev: Filter 20, 112, 255 not available from 192.168.0.119:37794 Nov 21 18:04:19 localhost vdr: [5870] Streamdev: Filter 0, 0, 255 not available from 192.168.0.119:37794 Nov 21 18:04:19 localhost vdr: [5870] Streamdev: Filter 17, 66, 255 not available from 192.168.0.119:37794 Nov 21 18:04:19 localhost vdr: [5870] Streamdev: Filter 16, 64, 255 not available from 192.168.0.119:37794 Nov 21 18:04:19 localhost vdr: [5887] receiver on device 6 thread started (pid=5870, tid=5887) Nov 21 18:04:19 localhost vdr: [5886] transfer thread started (pid=5870, tid=5886) Nov 21 18:04:21 localhost vdr: [5887] Streamdev: Lost connection to 192.168.0.1:2004: Connection timed out Nov 21 18:04:21 localhost vdr: [5887] receiver on device 6 thread ended (pid=5870, tid=5887) Nov 21 18:04:31 localhost vdr: [5873] [VideoOut]: 736x576 [0,0 736x576] -> 1024x576 [118,0 788x576] Nov 21 18:04:31 localhost vdr: [5880] KBD remote control thread ended (pid=5870, tid=5880) Anybody able to tell from these, what's going wrong? The server side seems awfully quiet is syslog, maybe something wrong there? Anyway to debug this more closely? Thanks, Juhis

2 6

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr November 2006