Re: [vdr] VDR and folders
Sounds interesting, if I copy a video off my phone will I be able to see it in vdr without editing folders.conf? I currently switch to xbmc to watch stuff recorded or copied outside of vdr . -Original Message- From: Klaus Schmidinger klaus.schmidin...@tvdr.de Sent: 04/11/2013 11:09 To: vdr@linuxtv.org vdr@linuxtv.org Subject: Re: [vdr] VDR and folders On 19.10.2013 19:38, Thomas Maass wrote: Hi! I like the new editing functions coming with version 2.1.2. Thank you for that Klaus! It would be nice, if VDR could recognize existing subfolders and add them to folders.conf automatically. Sometimes I edited my videodir manually, created some subfolders to sort some recordings. VDR does not know about these folders. I tried mixing existing recording directories into the entries in folders.conf. However, this pretty soon gets rather complex. Should recording directories only appear in the menu or should they actually be written into folders.conf? What if they are only in the menu, and you create a new subfolder in one of them? I'd really like to keep things simple here... With the new possibility of renaming entire folders and moving around recordings from within VDR's menu there shouldn't be the need for messing around with the actual disk files/directories any more. Klaus ___ 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] Which epg for Sky UK
Cant help with Italia, but ITV2-4 have full schedules here using that patch (vdr.eepg-patch-1.7.35) On 23/04/2013 19:48, Teemu Suikki wrote: Hi! Is anyone using this patch with Sky Italia? It doesn't work for me. Also with Sky UK, I have full epg for many channels, but missing for some. For example ITV1 has 7 days epg, but ITV2-4 have none. This patch looked so promising at first, but now I'm thinking of changing back to LoadEPG plugin.. 14.4.2013 11.35 André Weidemann andre.weidem...@web.de mailto:andre.weidem...@web.de kirjoitti: On 14.04.2013 00:38, Lucian Muresan wrote: The current git version of eepg tends to crash on me at least one if not twice a day with vdr-2.0.0, after it used to work well for several weeks. I do not know what changed the behaviour, since I cannot find any useful crash dump... Same problem here. I dumped the plugin in favor to the patch, which worked flawlessly ever since. BTW, where is the most current freeview patch? Ever since vdr-1.7.35 I've used this patch (see attachment). It should apply cleanly to the most recent vdr version. I think I originally downloaded it from here: http://www.vdr-portal.de/board16-video-disk-recorder/board55-vdr-plugins/p1082416-eepg-und-vdr-1-7-28/#skipPoint1082422 André ___ vdr mailing list vdr@linuxtv.org mailto: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 mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Which epg for Sky UK
Hi, I used to use freesat diff patch to get the 10 day schedule from UK Freesat (BSkyB 28.2E), but seems its not been supported much for a while so I wonder what others are using? -- Scott ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR version 2.0.0 released
Thanks Klaus for a really nice piece of software. -- Scott On 31/03/2013 04:48, Klaus Schmidinger wrote: VDR version 2.0.0 is now available at ftp://ftp.tvdr.de/vdr/vdr-2.0.0.tar.bz2 A 'diff' against the previous developer version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.42-2.0.0.diff MD5 checksums: fd7f481b996e03fae3c00e80b6b0d301 vdr-2.0.0.tar.bz2 db1fc075c567bf75c566de6ce3cb4a0b vdr-1.7.42-2.0.0.diff A summary of all the major changes since the last stable version 1.6.0 can be found at http://www.tvdr.de/changelog.htm When updating from an earlier version of VDR please make sure you read the INSTALL and MANUAL files that come with the VDR source _before_ doing so! Please make sure you have backup copies of all your configuration files, and verify carefully that your timers will be set to the correct channels after switching to this new version. Thanks to the many people who have contributed in the making, testing and debugging of this new version of VDR. Please also visit the newly refurbished VDR homepage at http://www.tvdr.de and VDR's new facebook page at https://www.facebook.com/VideoDiskRecorder Have fun! Klaus ___ 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] Does anyone see this or is the VDR mailing list broken?
Received ok here. -Original Message- From: VDR User user@gmail.com Sent: 06/02/2013 23:43 To: mailing list: vdr vdr@linuxtv.org Subject: [vdr] Does anyone see this or is the VDR mailing list broken? A few people have expressed concern now so I'm sending a test posting out. ___ 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] vdr-sxfe OSD transparency
Hi, Upgraded a bunch of stuff (vdr - 1.7.28, xinelib - latest from hg) and I've lost my transparent OSD (ST:TNG) when using vdr-sxfe. What is it that controls the transparency of the OSD? Does vdr overlay the OSD onto the video, or is it sent as a separate layer somehow to the output device and the output device decides how to merge? I would like to know if I need to concentrate on vdr config or xine config. vdr command: vdr -v /data/video -c /var/lib/vdr --lib=/usr/lib/vdr/plugins -r /usr/lib/vdr/vdr-recordingaction -s /usr/lib/vdr/vdr-shutdown-message -E /var/cache/vdr/epg.data -u vdr -g /tmp --port 2001 --lirc -P \streamdev-server -r /usr/bin/externremux.sh\ -P \xineliboutput --local=none --primary\ -P vnsiserver --vfat -w 60 vdr-sxfe: /usr/bin/vdr-sxfe xvdr+tcp://192.168.2.33 --video=xv --post=tvtime:method=Greedy2Frame,enabled=1 --fullscreen --syslog --verbose --reconnect Thanks, Scott ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] xineliboutput problem
Hi,
I upgraded my xinelib-1.2 to the latest from hg, recompiled
xineliboutput and its frontends and now vdr-sxfe will not start. I get
this in the log:
Nov 17 22:56:26 giradot vdr-sxfe[6256]: [6256] [scrnsaver] Error: The
name org.gnome.ScreenSaver was not provided by any .service files
Nov 17 22:56:26 giradot vdr-sxfe[6256]: [6256] [xine-vo ]
wire_video_driver() FAILED (vo_driver != vos_driver)
Nov 17 22:56:26 giradot kernel: vdr-sxfe[6256]: segfault at 0 ip (null)
sp 7fffa201d2b8 error 14 in vdr-sxfe[40+22000]
Nov 17 22:56:26 giradot vdr-sxfe[6256]: [6256] [vdr-fe]
wire_video_driver() for osdscaler failed
Looking at the code for wire_video_driver, I dont understand how this is
meant to work. It seems to take the driver element from the
xine_video_port_t (or xine_video_port_s) and compare it to the same
variable but cast to a vos_t and its -driver:
typedef struct {
xine_video_port_t vo; /* public part */
vo_driver_t *driver;
/* ... */
} vos_t;
int wire_video_driver(xine_video_port_t *video_port, vo_driver_t *hook)
{
vo_driver_t *vos_driver = ((vos_t*)video_port)-driver;
if (video_port-driver != vos_driver) {
LOGMSG(wire_video_driver() FAILED (vo_driver != vos_driver));
return 0;
}
...
But how is this meant to work as in xine_video_port_t the driver is the
last element, but in vos_t driver is after the xine_video_port, so
wouldn't that be 4 bytes later (on a 32 bit system)?
Obviously my C is not up to scratch :-(
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Pausing live video with xineliboutput
Hi, Most of my vdr/xineliboutput/vdr-sxfe setup works well, except for pausing live tv. When the pause button is pressed there is quite a long pause before the video and audio are stopped - 5 seconds is typical. Once paused, pressing Play does nothing, and eventually it looks like vdr-sxfe restarts itself and writes messages like this: Connection to server lost. Reconnecting after two seconds... Reconnecting... xine: found input plugin : VDR (Video Disk Recorder) input plugin xine: input plugin cannot open MRL [xvdr://192.168.2.33#nocache] xine: cannot find input plugin for MRL [xvdr://192.168.2.33#nocache] Error opening xvdr://192.168.2.33 Connection to server lost. Reconnecting after two seconds... Reconnecting... xine: found input plugin : VDR (Video Disk Recorder) input plugin xine: input plugin cannot open MRL [xvdr://192.168.2.33#nocache] xine: cannot find input plugin for MRL [xvdr://192.168.2.33#nocache] Error opening xvdr://192.168.2.33 Connection to server lost. Reconnecting after two seconds... and eventually goes back to showing the current live broadcast, not resuming from where it was paused, or it will crash writing this: xv_set_property: property=0, value=0 input cache plugin disabled xine: found demuxer plugin: XVDR demux plugin abort: audio_alsa_out.c:852: ao_alsa_write: Aborting. vdr itself seems to be running fine - the live recording is started and continues to record regardless of the vdr-sxfe client. Is anyone using vdr-sxfe with alsa and has pausing live tv working? vdr version 1.7.18, vdr-sxfe command line: /usr/bin/vdr-sxfe 192.168.2.33 --video=xv --post=tvtime:method=Greedy2Frame,enabled=1 --fullscreen --syslog --verbose --reconnect /tmp/xinelib_log 21 Thanks, -- Scott ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Email problem - who is the postmaster?
Thanks for the replies. I too believe the problem is at my end. I will dig out some more detailed logs of examples (Paul Menzel reply to my question is an example that I received many times, but Stefan and VDR User's I received only once), and then post them here if that's ok and I'm still stuck. I didn't want to post SMTP conversations here if there was a better place, but maybe this is the best place. Funny thing is, mail from other mailing lists I'm on (and from individuals) is ok and never repeated. Paul, I think you asked for some headers: This is the original (snipped to show the relevant section which is different on the repeats): Received: (qmail 8120 invoked from network); 16 Feb 2011 15:06:42 - Received: from localhost (HELO ASSP-nospam) (127.0.0.1) by localhost with ESMTPS (DHE-RSA-AES256-SHA encrypted); 16 Feb 2011 15:06:42 - Received: from www.linuxtv.org ([130.149.80.248] helo=www.linuxtv.org) with IPv4:25 by ASSP-nospam; 16 Feb 2011 15:06:41 + Received: from localhost ([127.0.0.1] helo=www.linuxtv.org) by www.linuxtv.org with esmtp (Exim 4.69) (envelope-from vdr-boun...@linuxtv.org) id 1Ppix0-0008VU-St; Wed, 16 Feb 2011 16:05:54 +0100 And this is the repeat: Received: (qmail 8482 invoked from network); 16 Feb 2011 15:25:54 - Received: from localhost (HELO ASSP-nospam) (127.0.0.1) by localhost with ESMTPS (DHE-RSA-AES256-SHA encrypted); 16 Feb 2011 15:25:54 - Received: from www.linuxtv.org ([130.149.80.248] helo=www.linuxtv.org) with IPv4:25 by ASSP-nospam; 16 Feb 2011 15:25:53 + Received: from localhost ([127.0.0.1] helo=www.linuxtv.org) by www.linuxtv.org with esmtp (Exim 4.69) (envelope-from vdr-boun...@linuxtv.org) id 1Ppix0-0008VU-St; Wed, 16 Feb 2011 16:05:54 +0100 From this you can see that www.linuxtv.org is responsible for resending to my MTA (ASSP-nospam) as the received time is changing, but the question is why it thinks it needs to resend. I'll get the SMTP conversation logged for next time. Thanks, Scott On 16/02/2011 16:28, VDR User wrote: On Wed, Feb 16, 2011 at 8:25 AM, Stefan Tafernertafer...@kde.org wrote: Am Mittwoch, 16. Februar 2011, um 16:05:44 schrieb Paul Menzel: Dear Scott, Am Montag, den 14.02.2011, 19:54 + schrieb Scott Waye: What is the postmaster email address for this list? sorry, I do not know. I get some of the messages 7 times 20 minutes apart. I do not experience this problem. No problem here too. I honestly think the problem is on Scott's end. I've been here for years and never had that problem either. I would make sure your issues aren't being caused locally first. ___ 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] Email problem - who is the postmaster?
Hi, What is the postmaster email address for this list? I get some of the messages 7 times 20 minutes apart. -- Scott ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr segfaults with glibc 2.12.2
Thanks a lot. I used: --enable-kernel=2.6.36 and it works fine now. -- Scott On 12/01/2011 00:11, David Spicer wrote: It turns out that the problem was known already. The fix is to rebuild Arch's x86_64 glibc 2.12.2 package with the --enable-kernel configure option set to one of the Good kernel versions listed in the post at http://www.cygwin.com/ml/libc-help/2010-12/msg00017.html. On 06/01/11 21:25, gimli wrote: I'm on Archlinux 32bit and there it works fine. Am 06.01.2011 um 22:19 schrieb sc...@waye.co.uk: Funny, I tried to change my system to Archlinux last weekend and had the same problem. I gave up in the end and will try Opensuse 11.3 now. I also tried recompiling glibc from source but it gave the same error. Would be to have a test suite for pthread. Could be a 64bit problem... if I was going to pursue it I would create a test program that made the same call as vdr to submit to the Archlinux guys. Sent from my HTC - Reply message - From: David Spicerazlei...@googlemail.com Date: Thu, Jan 6, 2011 20:53 Subject: [vdr] vdr segfaults with glibc 2.12.2 To:vdr@linuxtv.org Hi, I'm not a programmer and I'm not sure where to go with this but I thought that I'd try here first. I'm running vdr 1.6.0-2 on Arch Linux x86_64. The Arch glibc package was upgraded from 2.12.1 to 2.12.2 recently, with associated toolchain package updates. After the upgrade, vdr started segfaulting when it was run so I recompiled it with debugging symbols and got the following backtrace from gdb: (gdb) bt #0 0x0001 in ?? () #1 0x004f2d06 in ?? () #2 0x7fff1bb0269f in ?? () #3 0x004c2775 in cRwLock::Lock (this=0x72bb40, Write=true, TimeoutMs=value optimized out) at thread.c:163 #4 0x0047d382 in cSchedulesLock::cSchedulesLock (this=0x7fff1bb0269f, WriteLock=value optimized out, TimeoutMs=value optimized out) at epg.c:911 #5 0x0047dd06 in cSchedules::Read (f=0x0) at epg.c:1014 #6 0x004cc304 in main (argc=value optimized out, argv=value optimized out) at vdr.c:604 If I've done this properly then problem seems to be with the glibc, specifically pthread, functions that vdr uses to lock the epg data file for reading and writing but I have no idea whether the problem is with the vdr code or with glibc. The only workaround I have at the moment is to downgrade to glibc 2.12.1, after which vdr works again. Can anybody help please? TIA, David Spicer ___ 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 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] Trouble with picture Lost lock/regained lock
I've recently started having problems with my picture (breaks up/stops altogether). In trying to diagnose the problem I see this from vdr (1.7.15) when starting vdr-sxfe (remote) from xineliboutput (cvs from 4/9/10): Sep 5 21:23:29 giradot vdr-sxfe[10886]: [10903] [demux_vdr] PMT changed, resetting demuxer Sep 5 21:23:29 giradot vdr: [10370] frontend 0/0 lost lock on channel 6, tp 110773 Sep 5 21:23:30 giradot vdr-sxfe[10886]: [10903] [demux_vdr] ts2es: no payload, size 184 Sep 5 21:23:30 giradot vdr: [10370] frontend 0/0 regained lock on channel 6, tp 110773 Sep 5 21:23:30 giradot vdr-sxfe[10886]: [10903] [demux_vdr] ts2es: transport error Sep 5 21:23:30 giradot vdr-sxfe[10886]: [10903] [demux_vdr] ts2es: transport error Sep 5 21:23:30 giradot vdr-sxfe[10886]: [10903] [demux_vdr] ts2es: no payload, size 120 Sep 5 21:23:31 giradot vdr-sxfe[10886]: [10903] [demux_vdr] ts2es: no payload, size 131 Sep 5 21:23:31 giradot vdr-sxfe[10886]: [10903] [demux_vdr] ts2es: transport error Sep 5 21:23:31 giradot vdr-sxfe[10886]: [10903] [demux_vdr] ts2es: no payload, size 68 Sep 5 21:23:31 giradot vdr-sxfe[10886]: [10903] [demux_vdr] ts2es: transport error Sep 5 21:23:31 giradot vdr-sxfe[10886]: [10903] [demux_vdr] ts2es: transport error Sep 5 21:23:31 giradot vdr-sxfe[10886]: [10903] [demux_vdr] ts2es: no payload, size 37 Sep 5 21:23:31 giradot vdr-sxfe[10886]: [10903] [demux_vdr] ts2es: no payload, size 40 Sep 5 21:23:31 giradot vdr-sxfe[10886]: [10903] [demux_vdr] ts2es: no payload, size 184 In particular the lost lock/regained lock looks strange. Searching through the archives suggests this could be due to a weak signal. I ran femon and got this: FE: Conexant CX24116/CX24118 (DVBS) status SCVYL | signal d840 | snr d800 | ber | unc | FE_HAS_LOCK status SCVYL | signal d8c0 | snr d999 | ber | unc | FE_HAS_LOCK status SCVYL | signal d840 | snr d666 | ber | unc | FE_HAS_LOCK status SCVYL | signal d840 | snr d999 | ber 3e71 | unc 00a6 | FE_HAS_LOCK status SCVYL | signal d840 | snr d999 | ber 3e71 | unc 00a6 | FE_HAS_LOCK status SCVYL | signal d8c0 | snr db33 | ber 3e71 | unc 00a6 | FE_HAS_LOCK status SCVYL | signal d8c0 | snr d800 | ber 0081 | unc | FE_HAS_LOCK status SCVYL | signal d840 | snr db33 | ber | unc | FE_HAS_LOCK Which looks ok, the snr value seems high enough, so any other reason why the lock would be lost. I also see this in my dmesg which looks odd: DVB: adapter 0 frontend 0 frequency 89399000 out of range (95..215) DVB: adapter 0 frontend 0 frequency 89399000 out of range (95..215) DVB: adapter 0 frontend 0 frequency 89399000 out of range (95..215) DVB: adapter 0 frontend 0 frequency 89399000 out of range (95..215) -- Scott ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput - pausing playback takes time
Yes, I have same symptoms, no vdpau here. I put it down to the client clearing through its buffer, but that's just a guess. Sent from my HTC - Reply message - From: JJussi v...@jjussi.com Date: Wed, Aug 11, 2010 12:47 Subject: [vdr] xineliboutput - pausing playback takes time To: VDR list vdr@linuxtv.org Hi! I have vdr (1.7.14/1.7.14) - The Video Disk Recorder skinsoppalusikka (1.7.1) - Soppalusikka skin xineliboutput (1.0.90-cvs) - X11/xine-lib output plugin problem is when I'm watching recording and press 'pause' -key, playback is paused for about 1/10:th of second, then it countinues about 2-3 seconds before pausing totally. This happens most of time when I press pause.. Some times (rarely) it really pauses right away. I have tested different (data) transfer methods (pipe, tcp, udp..) and parameters when starting vdr-sxfe.. No luck! Have anybody else have same kind of problems? These came when I changed from version 1.6.x to current 1.7.x.. OH, one thing I have not yet tested.. What happen if I take vdpau off.. Vdpau was reason why I changend to 1.7.x versions. -- JJussi ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] How to pause live TV
Hi, Pausing live tv with the pause button has never worked for me, must be something stupid but I can't see it. I use vdr 1.7.14, with vdr-xine 0.9.3 and xine-lib 1.1 When I press Pause I get 00.00.00 in the top right corner of the screen, the picture freezes and these messages appear in the log: Jun 5 18:28:12 giradot vdr: [31452] buffer usage: 60% (tid=31451) Jun 5 18:28:12 giradot vdr: [31452] buffer usage: 70% (tid=31451) Jun 5 18:28:12 giradot vdr: [31452] buffer usage: 60% (tid=31451) Jun 5 18:28:12 giradot vdr: [31452] buffer usage: 70% (tid=31451) Jun 5 18:28:13 giradot vdr: [31452] buffer usage: 80% (tid=31451) Jun 5 18:28:15 giradot vdr: [31452] buffer usage: 90% (tid=31451) Jun 5 18:28:15 giradot vdr: [31452] buffer usage: 100% (tid=31451) Pressing pause again resumes the playback but shortly after it skips to the current live position omitting a chunk of the program. These messages appear in the log: Jun 5 18:28:40 giradot vdr: [31452] ERROR: driver buffer overflow on device 1 Jun 5 18:28:44 giradot vdr: [31451] ERROR: skipped 11 bytes to sync on TS packe t on device 1 Jun 5 18:28:44 giradot vdr: [31451] TS continuity error (14) Jun 5 18:28:44 giradot vdr: [31451] TS continuity error (7) Jun 5 18:28:44 giradot vdr: [31451] cAudioRepacker(0xC0): skipped 552 bytes to sync on next audio frame Jun 5 18:28:47 giradot vdr: [31452] buffer usage: 60% (tid=31451) I thiink maybe xine is trying to do all the pausing itself instead of handing it off to VDR, but that's just a guess. The key binding for lirc and the pause button look ok, and the pause button works fine when playing back recordings. -- Scott ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput - choppy problem
Have you tried with the CPU governor turned off? I know you said the CPU is not busy, but worth elimninating. Scott Sent from my HTC - Reply message - From: Jiri Jansky jans...@fel.cvut.cz Date: Sat, May 15, 2010 22:12 Subject: [vdr] xineliboutput - choppy problem To: VDR Mailing List vdr@linuxtv.org My problem isn't VDPAU related, because I have same no smooth playing with XV output too. (I tested pal mpeg2 television stations without postprocessing and i used about 20% on my pentium4). Halim Sahin napsal(a): hi, Make sure that your vdpau is working. Have installed the xinelib-1.2-vdpau branch? To check if you have vdpau run vdr-xfe --video you have the right info and the last two lines: Available video drivers: dxr3 aadxr3 xv raw opengl xshm none sdl fb Available audio drivers: pulseaudio alsa oss esd none file Your machine should list vdpau as well (I dont have it). You can download the right xinelib with vdpau support from hg with this command: hg clone http://hg.debian.org/hg/xine-lib/xine-lib-1.2-vdpau HTH. Halim ___ 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] XBMC with vdr-1.6.0 ??
Sorry for the delay. vdr is set to run all the time, I start mine with this line in inittab but anyway will do: vdr:35:once:/usr/local/bin/runvdr This is the while loop in my .xinitrc. This has to go before any exec lines that you might have which would be present to start window managers etc: ### bash script excerpt start while [ 1 -eq 1 ] do XINE=/data/downloads/xine-ui/src/xitk/xine $XINE -A alsa --video vdpau --post tvtime:method=use_vo_driver -f vdr://tmp/vdr-xine/stream#demux:mpeg_pes --no-gui --no-mouse --hide-gui --no-logo --no-splash --verbose=2 21 /tmp/xine_log #run xbmc export SDL_AUDIODRIVER=null # I use this to workaround an issue I had with navigation sounds in xbmc /usr/local/bin/xbmc --fullscreen 21 /tmp/xbmc done ### bash script excerpt end So this loop will just cycle between xine and xbmc unti the X session is killed. To stop xine I use the Music button on my Hauppauge remote, so I have this in the my .lircrc begin remote = Hauppauge button = Music prog = xine repeat = 0 config = Quit end This will close xine, causing the while loop to move on and start xbmc. I use MediaStream as my xbmc skin and this next bit is specific to that skin, if you use a different skin then you will have to look up how to add menu items for that skin. Also I think I read recently that xbmc has changed the way skins are handled so if you are on a new svn build, or maybe the latest release then things might have changed. I am using a SVN build from 8 Sep 2009. From the same home directory as the above .xinitrc, in .xbmc/skin/MediaStream/720p (That's the resolution I'm using, I don't think MediaStream has any other) you should have a file, Home.xml. Near the end there is a section which defines the main menu, normally preceded by the comment !-- Main Menu --. About 30 lines lower you should find a section which describes the buttons available in the top level menu, something like: content item id=7 descriptionPower Button/description label $LOCALIZE[31007] /label label2 $LOCALIZE[31017] /label2 onclickXBMC.ActivateWindow(ShutdownMenu)/onclick /item item id=6 descriptionMy System Menu/description label $LOCALIZE[31006] /label label2 $LOCALIZE[31016] /label2 onclickSetFocus(506)/onclick /item At a location of your choosing, but at the right xml indentation, you can add a button with the following xml: item id=11 descriptionMy VDR Button/description label $LOCALIZE[31905] /label label2 $LOCALIZE[31906] /label2 visible!Skin.HasSetting(HideTVShows)/visible onclickXBMC.Quit()/onclick /item The id of 11 must be unique in this list, my last one was 10, so I picked 11. The significant bits are the 2 numbers 31905 and 31906, plus the XBMC.Quit() which tells XBMC to close down when the menu item is clicked, and due to the bash while loop, xine will start up. Finally to get the right text for your new menu button, you need to define values for 31905 and 31906 in .xbmc/skin/MediaStream/language/English/strings.xml. Something like this before /strings will do: string id=31905TV/string string id=31906Watch/string As already mentioned you can achieve the same thing with less changes by using irexec, I guess the only advantage of the technique above is that you get a nice button in xbmc. Apologies for putting all this xbmc specific stuff in the vdr list, but its probably good to have the whole solution in one message. Its not exactly what you are after but it may give you some clues. -- Scott On Wed, 10 Mar 2010 10:12:30 +1300, Simon Baxter linu...@nzbaxters.com wrote: - Original Message - From: scott sc...@waye.co.uk To: VDR Mailing List vdr@linuxtv.org Sent: Monday, March 08, 2010 9:45 PM Subject: Re: [vdr] XBMC with vdr-1.6.0 ?? One way thats been suggested before, and which I use, is to put xbmc and vdr-xine in a while loop inside a bash shell script and set up a button to stop vdr-xine, and a menu option in xbmc to close it down. If you search this thread you should find some info, if not I can post my stuff. -- Scott Thanks Scott. Yes please, would like to see how you've implemeted it. I found a number of threads and have achieved the following: * added a script (vdr.py) under the My Scripts which calls the xine frontend. But this flags an error Errors in system config or similar, launches xine but closes xbmc at the back end http://forum.xbmc.org/showthread.php?t=42205 * added a phantom button on the main menu, which I'd hoped would launch vdr-py (lower in the above thread). But this just crashes xmbc What I want to achieve is a main menu button which
Re: [vdr] XBMC with vdr-1.6.0 ??
One way thats been suggested before, and which I use, is to put xbmc and vdr-xine in a while loop inside a bash shell script and set up a button to stop vdr-xine, and a menu option in xbmc to close it down. If you search this thread you should find some info, if not I can post my stuff. -- Scott On Mon, 8 Mar 2010 19:53:15 +1300, Simon Baxter linu...@nzbaxters.com wrote: Hi Has anyone got XBMC working with vdr-1.6.0? I want to run XBMC, but am not ready to move to a .ts file format yet. So I was thinking I'd just get XMBC to call a script and run vdr-xine (ie not integrate with streamdev etc). This should be easy yes? Any pointers or experience? Thanks Simon ___ 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] vdr and xbox 360
Have you looked at XBMC? -- Scott - Reply message - From: martinez marti...@embl.de Date: Fri, Feb 5, 2010 12:30 Subject: [vdr] vdr and xbox 360 To: vdr@linuxtv.org I have an xbox 360 able to run unsigned code and to interact (as all xbox 360s) with a microsoft media center. I have no microsoft media center, nor any interest in setting up one. Is there some way I can get the xbox 360 to stream video and/or recordings from my linux htpc which is running vdr 1.7.11 Cheers, Art Martinez ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] frontend 0 timed out.... Was working fine last night.
Hi, Last night my system (DVB-S2 Hauppauge card/Liplianin driver/Kerner2.6.27.10 (64bit OpenSuse) /l vdr 1.7.9/xine-ui with vdpau) was working fine, but this morning I cannot watch TV and get these errors. It wasn't very windy last night, but I am wondering what the symptons are if the dish becomes misaligned, or the LNB fails? Unfortunately I don't have another receiver to test it. Jan 24 14:33:39 giradot vdr: [4216] probing /dev/dvb/adapter0/frontend0 Jan 24 14:33:39 giradot vdr: [4216] device 1 provides DVB-S2 (Conexant CX24116/CX24118) Jan 24 14:33:39 giradot vdr: [4221] section handler thread started (pid=4216, tid=4221) Jan 24 14:33:39 giradot vdr: [4220] tuner on device 1 thread started (pid=4216, tid=4220) Jan 24 14:33:39 giradot vdr: [4216] found 1 video device Jan 24 14:33:39 giradot vdr: [4216] initializing plugin: xine (0.9.3): Software based playback using xine Jan 24 14:33:39 giradot vdr: [4222] XineRemote control thread started (pid=4216, tid=4222) Jan 24 14:33:39 giradot vdr: [4222] Entering cXineRemote thread Jan 24 14:33:39 giradot vdr: [4216] setting primary device to 2 Jan 24 14:33:39 giradot vdr: [4216] assuming manual start of VDR Jan 24 14:33:39 giradot vdr: [4216] SVDRP listening on port 2001 Jan 24 14:33:39 giradot vdr: [4216] setting current skin to sttng Jan 24 14:33:39 giradot vdr: [4216] loading /etc/vdr/themes/sttng-default.theme Jan 24 14:33:39 giradot vdr: [4216] starting plugin: xine Jan 24 14:33:39 giradot vdr: [4216] ERROR: remote control XineRemote not ready! Jan 24 14:33:39 giradot vdr: [4225] KBD remote control thread started (pid=4216, tid=4225) Jan 24 14:33:39 giradot vdr: [4216] remote control KBD - keys known Jan 24 14:33:39 giradot vdr: [4216] switching to channel 10 Jan 24 14:33:39 giradot vdr: [4227] receiver on device 1 thread started (pid=4216, tid=4227) Jan 24 14:33:39 giradot vdr: [4228] TS buffer on device 1 thread started (pid=4216, tid=4228) Jan 24 14:33:39 giradot vdr: [4216] setting watchdog timer to 60 seconds Jan 24 14:33:39 giradot vdr: [4216] OSD size changed to 720x576 @ 1.06667 Jan 24 14:33:39 giradot vdr: [4216] timer 1 (3 1120-1210 'Click') set to event Sat 30.01.2010 11:30-12:00 'Click' Jan 24 14:33:39 giradot vdr: [4216] timer 2 (15 0005-0055 'The IT Crowd') set to event Mon 25.01.2010 00:15-00:50 'The IT Crowd' Jan 24 14:33:39 giradot vdr: [4216] timer 3 (9 1258-1520 'Secondhand Lions') set to event Sun 24.01.2010 13:00-15:10 'Secondhand Lions' Jan 24 14:33:39 giradot vdr: [4216] switching device 1 to channel 9 Jan 24 14:33:39 giradot vdr: [4216] timer 3 (9 1258-1520 'Secondhand Lions') start Jan 24 14:33:39 giradot vdr: [4216] Title: 'Secondhand Lions' Subtitle: '(null)' Jan 24 14:33:39 giradot vdr: [4216] record /data/video/Secondhand_Lions/2010-01-24.12.58.9-0.rec Jan 24 14:33:39 giradot vdr: [4216] cFileName::SetOffset: removing zero-sized file /data/video/Secondhand_Lions/2010-01-24.12.58.9-0.rec/1.ts Jan 24 14:33:39 giradot vdr: [4216] recording to '/data/video/Secondhand_Lions/2010-01-24.12.58.9-0.rec/1.ts' Jan 24 14:33:39 giradot vdr: [4229] recording thread started (pid=4216, tid=4229) Jan 24 14:33:45 giradot vdr: [4216] max. latency time 1 seconds Jan 24 14:33:48 giradot vdr: [4220] frontend 0 timed out while tuning to channel 9, tp 110714 Jan 24 14:34:10 giradot vdr: [4229] ERROR: video data stream broken Jan 24 14:34:10 giradot vdr: [4229] initiating emergency exit Jan 24 14:34:10 giradot vdr: [4216] emergency exit requested - shutting down Jan 24 14:34:10 giradot vdr: [4216] stopping plugin: xine Jan 24 14:34:10 giradot vdr: [4229] recording thread ended (pid=4216, tid=4229) Jan 24 14:34:10 giradot vdr: [4216] buffer stats: 0 (0%) used Jan 24 14:34:10 giradot vdr: [4216] timer 3 (9 1258-1520 'Secondhand Lions') stop Jan 24 14:34:11 giradot vdr: [4222] Leaving cXineRemote thread Jan 24 14:34:11 giradot vdr: [4222] XineRemote control thread ended (pid=4216, tid=4222) Jan 24 14:34:11 giradot vdr: [4225] KBD remote control thread ended (pid=4216, tid=4225) Jan 24 14:34:11 giradot vdr: [4216] saved setup to /etc/vdr/setup.conf Jan 24 14:34:11 giradot vdr: [4228] TS buffer on device 1 thread ended (pid=4216, tid=4228) Jan 24 14:34:11 giradot vdr: [4227] buffer stats: 0 (0%) used Jan 24 14:34:11 giradot vdr: [4227] receiver on device 1 thread ended (pid=4216, tid=4227) Jan 24 14:34:11 giradot vdr: [4221] section handler thread ended (pid=4216, tid=4221) Jan 24 14:34:12 giradot vdr: [4220] tuner on device 1 thread ended (pid=4216, tid=4220) Jan 24 14:34:12 giradot vdr: [4216] deleting plugin: xine Jan 24 14:34:13 giradot vdr: [4216] max. latency time 1 seconds Jan 24 14:34:13 giradot vdr: [4216] emergency exit! Jan 24 14:34:13 giradot vdr: [4216] exiting, exit code 1 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] livebuffer patch improvements suggestions.
VDR User wrote: On Wed, Nov 18, 2009 at 8:46 AM, Tommi Lundell prel...@kapsi.fi wrote: Hello. 1) RAM is cheap now days. Can I use RAM to keep buffer data? (System running from USB stick so only reason to start Hard Disk is when i use recordings) 2) Patch only record current channel. It would be nice if i can select channels from lists where buffers are active. Example. i change channel and noticing that program what i want to look is already running so i simply press jump backward button and start to look program from beginning. (2GB can keep about 100 minutes in buffers. If i select 5 different channels that i got 20mins buffer in every channel) There was some talk a while back about implementing a live tv buffer into VDR. Many users don't like the idea of their harddrive recording 24/7 so it was mentioned to be able to buffer to ram just as you're asking about. I personally do NOT want to buffer to harddrive, especially non-stop. However, I'm all for buffering to RAM since it _is_ very cheap these days for 2-4GB. I don't know how much of a priority this is to Klaus but I'd recommend searching the mailing list for that thread because he did participate in the discussion. I agree, if the buffer was a configurable FIFO file (location and size), then the user could choose if the location was on a hard disk or a RAM disk. -- Scott ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] How do I listen to a channel's soundtrack and i t's audio description at the same time?
On Sat, 05 Sep 2009 18:39:27 +0200, Udo Richter udo_rich...@gmx.de wrote: On 02.09.2009 07:49, John Robinson wrote: I would very much like to hear the main programme's soundtrack and the audio description track at the same time, but at the moment, I can only hear one or the other - not both. Hmmm, interesting task. However, I don't think that this is possible currently. Output devices are currently designed to handle one audio channel, not multiple at the same time. Mixing them to one would require decompressing and re-compressing them and would probably introduce timing issues. There may be a quirked solution like playing back the second channel externally, like connecting to it using mplayer+streamdev, however thats not very comfortable. The best solution is probably a dedicated plugin that connects to live view and plays the secondary audio track in parallel. However I don't think that such a plugin exists currently. Not sure this helps, but mplayer manages to do this with vdr recordings. Isn't there a script somewhere that uses mplayer as the playback device? -- Scott ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Fast compact distro for vdr
On Fri, 28 Aug 2009 22:51:15 +0200, Diego Pierotto vdr_ml...@tiscali.it wrote: Damien Bally ha scritto: gimli a écrit : A start point : http://sourceforge.net/apps/trac/archvdr/ Sounds good. Is it superior to slackware in term of boot time compared to slackware (which I'm using) ? I'd like a system booting in a few seconds. A few years back when I built my car pc, one of the things that got my boot time down significantly was using LinuxBios. If you are counting seconds it might be worth a look. -- Scott ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdpau patches
On Mon, 24 Aug 2009 18:48:21 +0200, Malte Schröder malte...@gmx.de wrote: On Mon, 24 Aug 2009 12:49:18 +0100 scott sc...@waye.co.uk wrote: I was thinking of giving xine/vdpau/xineliboutput another try after failing earlier in the year. I came across these patches: http://www.nfvdr.net/bbs/thread-5856-1-1.html Is anyone using these? Looks like this: http://vdrportal.de/board/thread.php?threadid=86804 And yes, I use the patches and they improved playback considerably. Oh, yes its just a translation, thanks. I take it you are using them on xinelib 1.2, are you using xineliboutput 1.0.4 or cvs? -- Scott ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdpau patches
I was thinking of giving xine/vdpau/xineliboutput another try after failing earlier in the year. I came across these patches: http://www.nfvdr.net/bbs/thread-5856-1-1.html Is anyone using these? -- Scott ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] No audio with recordings, XBMC frontend, LATM AAC
On Tue, 2009-08-11 at 09:35 +1200, Alex Fazzari wrote: Hi, I'm setting up VDR using xbmc as a frontend as described here: http://xbmc.org/forum/showthread.php?t=45314highlight=audio I've got live streaming working well but have an issue with recordings where no audio comes through. I am using mirak's VDR 1.7.7 from the repository here: https://launchpad.net/~mirak-mirak/+ppa-packages Could this have something to to do with the audio used for NZ tv which broadcasts in LATM encapsulated AAC? I'm not sure why the streamed live tv would work fine and the recordings don't though. Any pointers much appreciated. Thanks, Alex Anything in the xbmc log? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xine-lib-1.2-vdpau-yaepghd-window
On Sat, 27 Jun 2009 16:31:24 -0400, hu_emulator hu_emula...@hotmail.com wrote: Any suggestions? Anyone?? Thanks, - Original Message - From: hu_emulator hu_emula...@hotmail.com To: VDR Mailing List vdr@linuxtv.org Sent: Wednesday, June 24, 2009 6:20 AM Subject: [vdr] xine-lib-1.2-vdpau-yaepghd-window Before last weeks xine-lib-1.2 enhancement for yaepghd's preview window my vdr system worked flawlessly on both hd and non hd live tv channels. Since I upgraded to the most current xine-lib-1.2 patched for yaepghd's preview window I have many live tv playback errors. Xine's gui comes up and is complaining of my settings. What setting must I change in either vdr-xine-9.3 or xine's config to accomodate for the yaepghd's changes? Current xine/config settings different than default settings: video.processing.ffmpeg_choose_speed_over_accuracy:1 video.processing.ffmpeg_pp_quality:0 video.processing.ffmpeg_skip_loop_filter:all video.processing.ffmpeg_thread_count:2 engine.buffers.video_num_buffers:1500 engine.buffers.video_num_frames:30 Thank you! I can't help I'm afraid except to say that I couldn't get a usable configuration either (onboard Nvidia 8300) so I've put it on hold for the moment and gone back to xv. I tried xine-ui and xineliboutput with xinelib 1.1 and 1.2 and the latest, at the time, nvidia and xine-vdpau versions. I might try again if I can get a 9xxx micro atx motherboard at a reasonable price as people seem to have less problems with the higher end chipsets. Sorry. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xine settings for VDPAU SD and HD
On Mon, 15 Jun 2009 19:30:59 +0200, Luca Olivetti l...@ventoso.org wrote: En/na scott ha escrit: With live TV on SD material (e.g. BBC News), I get a lot of dropped frames ( around 5 %) (HD is worse, around 20%): video_out: throwing away image with pts 2405183661 because it's too old [...] # number of video buffers # numeric, default: 500 - tried 500, 800, 900, 1000, and 1500. 900 seems to give the best results #engine.buffers.video_num_buffers:500 I have it set to 2500 (don't ask me why, I don't remember). I only see dropped frames when I'm resizing the window. Bye Thanks, thats helped quite a bit. I'm now down to around 1% dropped for live tv which is a big improvement. -- Scott ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xine settings for VDPAU SD and HD
On Mon, 15 Jun 2009 18:20:20 +0300, Pertti Kosunen pertti.kosu...@pp.nic.fi wrote: scott wrote: With live TV on SD material (e.g. BBC News), I get a lot of dropped frames ( around 5 %) (HD is worse, around 20%): Same here. What xine-lib-1.2 hg revision works with xine-lib-1.2-vdpau-r262? Sorry, don't know about 1.2, I'm using 1.1. If you are refering to the 1.2 vdpau patches from http://www.jusst.de/vdpau/files/xine-lib-1.2/ then I believe the r??? number refers to the subversion version number of xine-vdpau from svn://jusst.de/xine-vdpau. In other words, the patch takes the xine-lib 1.1 vdpau code and moves it to 1.2. Please correct me if I'm wrong. -- Scott ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xine settings for VDPAU SD and HD
On Sun, 14 Jun 2009 10:39:57 +0200, Luca Olivetti l...@ventoso.org wrote: En/na Scott Waye ha escrit: Thanks for that. I upgraded to r266 for xine-vdpau and 185.18.14 for the driver and changed my start command to match yours. The deinterlacing now looks good, but I have a more serious problem, as soon as I try to change channel with up or down, xine freezes. It does not crash, but the picture is frozen and the sound gone. I cannot tell if it's the same problem I had, but try uncommenting #define LOCKDISPLAY around line 55 in video_out_vdpau.c Thanks for those that suggested this. It has fixed the freezing. At the risk of getting annoying I have another question: With live TV on SD material (e.g. BBC News), I get a lot of dropped frames ( around 5 %) (HD is worse, around 20%): video_out: throwing away image with pts 2405183661 because it's too old (diff : 4067). video_out: throwing away image with pts 2405223261 because it's too old (diff : 4081). video_out: throwing away image with pts 2405475261 because it's too old (diff : 4037). video_out: throwing away image with pts 2405612061 because it's too old (diff : 4042). video_out: throwing away image with pts 2405658861 because it's too old (diff : 4099). video_out: throwing away image with pts 2405698461 because it's too old (diff : 4068). video_out: throwing away image with pts 2405734461 because it's too old (diff : 4076). video_out: throwing away image with pts 2405784861 because it's too old (diff : 4072). video_out: throwing away image with pts 2405828061 because it's too old (diff : 4080). video_out: throwing away image with pts 2405874861 because it's too old (diff : 4078). 200 frames delivered, 0 frames skipped, 10 frames discarded If I record the channel and play it back it is fine. Most of my xine settings are the default, except for video_num_frames: # number of audio buffers # numeric, default: 230 #engine.buffers.audio_num_buffers:230 # number of video buffers # numeric, default: 500 - tried 500, 800, 900, 1000, and 1500. 900 seems to give the best results #engine.buffers.video_num_buffers:500 # default number of video frames # numeric, default: 15 engine.buffers.video_num_frames:22 I have for the xine-ui plugin, the defaults, although I've also tried setting Live-TV buffer and Buffer hysteresis to 5 and 8 with no noticeable difference. Any ideas, sounds like there is not enough buffer for live tv? Many thanks, Scott vdr 1.7.7 vdr xine 0.9.2 xine-vdpau r266 (with xine-vdr patch) xine-ui cvs (14 June 09) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] xine settings for VDPAU SD and HD
I'm trying to get VDPAU working so I can watch HD TV, but I'm having trouble getting a good picture. My question is should I be using the xine options: --post vdr_video --post_audio or --post tvtime:method=use_vo_driver I dont understand what the difference is and whether one is preferred over the other for interlaced and/or HD/SD. My setup: Asus M3N78-EM (onboard Nvidia 8300) Athlon Dual Core (set to 2Ghz for now) HDMI output to Samsung Plasma Hauppauge Nova SD2 OpenSuse: kernel 2.6.27.10 Nvidia driver180.51 ffmpeg from svn on 8 June xine-lib-1.2 from hg on 8 June with r262 patch xine-ui-cvs-2009041220 vdr-1.7.7 vdr-xine 0.9.2 I have the buffer settings from a previous mail to this list: engine.buffers.video_num_buffers:2000 engine.buffers.video_num_frames:30 Thanks, Scott ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] sysinfo 0.1.0a
On Mon, 01 Jun 2009 23:09:38 +0200, Diego Pierotto vdr_ml...@tiscali.it wrote: Scott Waye ha scritto: Hi, I am trying to get this plugin working with vdr 1.7.7. When I bring it up from the menu it segmentation faults. The relevant sections from the backtrace are : snipped I'm using systeminfo-0.1.1 cause the version you use has some problems with VDR 1.6.x. I don't know if with 1.7.x is running well. Thanks I tried this with 1.7.7 and it seems to work fine. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] sysinfo 0.1.0a
= 366}, {
name = 0x504ee7 plugin, has_arg = 1, flag = 0x0, val = 80}, {
name = 0x504eee port, has_arg = 1, flag = 0x0, val = 112}, {
name = 0x504ef3 rcu, has_arg = 2, flag = 0x0, val = 370}, {
name = 0x504ef7 record, has_arg = 1, flag = 0x0, val = 114}, {
name = 0x504efe shutdown, has_arg = 1, flag = 0x0, val = 115}, {
name = 0x504f07 terminal, has_arg = 1, flag = 0x0, val = 116}, {
name = 0x504f10 user, has_arg = 1, flag = 0x0, val = 117}, {
name = 0x504f15 userdump, has_arg = 0, flag = 0x0, val = 373}, {
name = 0x4f65cc version, has_arg = 0, flag = 0x0, val = 86}, {
name = 0x504f1e vfat, has_arg = 0, flag = 0x0, val = 374}, {
name = 0x504c92 video, has_arg = 1, flag = 0x0, val = 118}, {
name = 0x504f23 watchdog, has_arg = 1, flag = 0x0, val = 119}, {
name = 0x0, has_arg = 0, flag = 0x0, val = 0}}
lastTime = 0
ChannelSaveTimeout = 1243888290
TimerState = 0
---Type return to continue, or q return to quit---#
LastTimerCheck = 1243887920
DeviceUsed = {0 repeats 16 times}
to me this looks like the Font passed into DrawText is invalid. This is
set up in sysinfoosd.h thus:
static const cFont *font = cFont::GetFont(fontOsd);
Is there something obvious here that someone with more experience of the
code can spot?
Thanks,
Scott
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Running multiple instances of vdr 1.7.7 with streamdev
On Fri, 15 May 2009 16:44:37 +0200, Frank Schmirler v...@schmirler.de wrote: Hi Scott, On Thu, 14 May 2009 18:02:22 +0100, scott wrote I have on the streamdev server, the behaviour to Offer Suspend and Client may suspend to yes, I was hoping that with this setup I would get last one wins, except for recordings which always win. Is there something wrong with my setup? I have no patches applied. xineliboutput v1.0.4. Your client VDR keeps begging for channel STREAM-0 as the server's DVB card is obviously tuned to an other transponder and due to Offer Suspend the client is not allowed to tune to a different one. This however doesn't explain why live view on the server gets interrupted. Please send me a mail off-list if you're interested in debugging this. Have you tried Always Suspended? That should be closer to last one wins. I'd expect a transponder change on the client to switch live view on the server, too. Changing transponder on the server, I'd expect that the picture on the client freezes. Best regards, Frank Hi, I've upgraded to the cvs version of libxineoutput and changed my output device on the server instance of vdr to libxineoutput and things are better. vdr-sxfe on the server instance no longer experiences no signal when the second instance of vdr is started. It does however switch channel when the second instance of vdr is started even though the second instance has no client connected. After it has switched channel I am only able to zap to channels on the same transponder until I kill the second instance of vdr. I notice that this error is reported: vdr: [23426] ERROR: device 10 reported an invalid number (0) of supported delivery systems - assuming 1 Is that significant? Server instance of vdr started with: VDRCMD='$VDRPRG -c /etc/vdr -v /data/video --lib=/etc/vdr/plugins/lib -P xineliboutput --primary --local=none --remote=37890 -Pstreamdev-server -w 60 $*' Streamdev set to Always suspend as suggested. Second instance started with: VDRCMD='$VDRPRG -c /etc/vdr2 -v /data/video --lib=/etc/vdr2/plugins/lib -D 10 -p 2102 -P xineliboutput --local=none --remote=37892 -P streamdev-client' Full log when starting the second instance: May 19 18:51:41 giradot vdr: [23426] VDR version 1.7.7 started May 19 18:51:41 giradot vdr: [23426] codeset is 'UTF-8' - known May 19 18:51:41 giradot vdr: [23426] ERROR: ./locale: No such file or directory May 19 18:51:41 giradot vdr: [23426] no locale for language code 'deu,ger' May 19 18:51:41 giradot vdr: [23426] no locale for language code 'slv,slo' May 19 18:51:41 giradot vdr: [23426] no locale for language code 'ita' May 19 18:51:41 giradot vdr: [23426] no locale for language code 'dut,nla,nld' May 19 18:51:41 giradot vdr: [23426] no locale for language code 'por' May 19 18:51:41 giradot vdr: [23426] no locale for language code 'fra,fre' May 19 18:51:41 giradot vdr: [23426] no locale for language code 'nor' May 19 18:51:41 giradot vdr: [23426] no locale for language code 'fin,suo' May 19 18:51:41 giradot vdr: [23426] no locale for language code 'pol' May 19 18:51:41 giradot vdr: [23426] no locale for language code 'esl,spa' May 19 18:51:41 giradot vdr: [23426] no locale for language code 'ell,gre' May 19 18:51:41 giradot vdr: [23426] no locale for language code 'sve,swe' May 19 18:51:41 giradot vdr: [23426] no locale for language code 'rom,rum' May 19 18:51:41 giradot vdr: [23426] no locale for language code 'hun' May 19 18:51:41 giradot vdr: [23426] no locale for language code 'cat,cln' May 19 18:51:41 giradot vdr: [23426] no locale for language code 'rus' May 19 18:51:41 giradot vdr: [23426] no locale for language code 'hrv' May 19 18:51:41 giradot vdr: [23426] no locale for language code 'est' May 19 18:51:41 giradot vdr: [23426] no locale for language code 'dan' May 19 18:51:41 giradot vdr: [23426] no locale for language code 'cze,ces' May 19 18:51:41 giradot vdr: [23426] no locale for language code 'tur' May 19 18:51:41 giradot vdr: [23426] no locale for language code 'ukr' May 19 18:51:41 giradot vdr: [23426] loading plugin: /etc/vdr2/plugins/lib/libvdr-xineliboutput.so.1.7.7 May 19 18:51:42 giradot vdr: [23426] loading plugin: /etc/vdr2/plugins/lib/libvdr-streamdev-client.so.1.7.7 May 19 18:51:42 giradot vdr: [23426] loading /etc/vdr2/setup.conf May 19 18:51:42 giradot vdr: [23426] [xine..put] Skipping configuration entry Remote.ListenPort=37890 (overridden in command line) May 19 18:51:42 giradot vdr: [23426] [xine..put] Skipping configuration entry RemoteMode=1 (overridden in command line) May 19 18:51:42 giradot vdr: [23426] loading /etc/vdr2/sources.conf May 19 18:51:42 giradot vdr: [23426] loading /etc/vdr2/diseqc.conf May 19 18:51:42 giradot vdr: [23426] loading /etc/vdr2/channels.conf May 19 18:51:42 giradot vdr: [23426] loading /etc/vdr2/timers.conf May 19 18:51:42 giradot vdr: [23426] loading /etc/vdr2/svdrphosts.conf May 19 18:51:42 giradot vdr: [23426] loading /etc/vdr2/remote.conf May 19 18:51:42
Re: [vdr] [OT] NVidia ION mini-ITX arriving
On Sat, 16 May 2009 14:11:55 +0200, Magnus Hörlin mag...@alefors.se wrote: Torgeir Veimo wrote: 2009/5/16 Magnus Hörlin mag...@alefors.se: Well, my first imressions of the ION platform (Acer Revo) are very good. It does the vdpau deinterlacing without problems and so far the video decoding has not exceeded 1% cpu load for ANY 1080p clip I've tried. This is the best VDR frontend/XBMC machine I've ever tried. I don't know why, but it works better than my Intel E7200/Nvidia 9400 uATX board. For those interested it uses 34W from 220V with the hdd still attached. I don't know if it's using any power though, since I've disabled SATA in the bios because I boot it off the network. With an N230 or 330 processor? That's a 230 with 2GB RAM. Don't see any need for a 330 for this application. Bit off topic but which XBMC skin are you using? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Running multiple instances of vdr 1.7.7 with streamdev
Hi, I have an not uncommon arrangement: 1 vdr machine in the living room with a budget card connect to a TV, a streamdev server (ip 192.168.2.33). I start it with: $VDRPRG -c /etc/vdr -v /data/video --lib=/etc/vdr/plugins/lib -P xine -r -Pstreamdev-server -w 60 $*' and that works fine. I have another pc/tv in the bedroom, so I run another instance of vdr on the living room machine with: $VDRPRG -c /etc/vdr2 -v /data/video --lib=/etc/vdr2/plugins/lib -D 10 -p 2102 -P xineliboutput --local=none --remote=37892 -P streamdev-client and I propose to connect to this using vdr-sxfe. I know I could run just one instance of vdr and use multiple vdr-sxfes, but I want multiple independend OSDs . My problem is that when I start the second instance of vdr (with no xineliboutput client) it seems to compete for the channel on the server. Every 30 seconds or so I get a no signal picture on the living room tv for a few seconds before the picture comes back (usually). The log at that time is: May 14 17:49:21 giradot vdr: [28489] streamdev-server: Detaching current receive r May 14 17:49:21 giradot vdr: [13530] ERROR: Streamdev: Couldn't tune 192.168.2.3 3:2004 to channel STREAM-0 May 14 17:49:21 giradot vdr: [13530] retrying May 14 17:49:21 giradot vdr: [28489] streamdev-server: Detaching current receiver May 14 17:49:21 giradot vdr: [13530] ERROR: Streamdev: Couldn't tune 192.168.2.33:2004 to channel STREAM-0 May 14 17:49:21 giradot vdr: [13530] retrying May 14 17:49:21 giradot vdr: [28489] streamdev-server: Detaching current receiver May 14 17:49:21 giradot vdr: [13530] ERROR: Streamdev: Couldn't tune 192.168.2.33:2004 to channel STREAM-0 May 14 17:49:21 giradot vdr: [13530] retrying May 14 17:49:21 giradot vdr: [2226] TS buffer on device 1 thread ended (pid=28480, tid=2226) May 14 17:49:21 giradot vdr: [2225] buffer stats: 69748 (3%) used May 14 17:49:21 giradot vdr: [2225] receiver on device 1 thread ended (pid=28480, tid=2225) May 14 17:49:22 giradot vdr: [28480] switching to channel 7 May 14 17:49:22 giradot vdr: [2269] receiver on device 1 thread started (pid=28480, tid=2269) May 14 17:49:22 giradot vdr: [2270] TS buffer on device 1 thread started (pid=28480, tid=2270) May 14 17:49:23 giradot vdr: [2269] cVideoRepacker: switching to MPEG1/2 mode May 14 17:49:23 giradot vdr: [2269] cVideoRepacker: operating in MPEG1/2 mode I have on the streamdev server, the behaviour to Offer Suspend and Client may suspend to yes, I was hoping that with this setup I would get last one wins, except for recordings which always win. Is there something wrong with my setup? I have no patches applied. xineliboutput v1.0.4. -- Scott___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] xineliboutput/vdr-sxfe and lirc (vdr 1.7.5)
I'm getting xineliboutput with vdr-sxfe going after a few months successfully running xineui. So far so good, but some of my remote keys do not work. In particular the Backup key. For xineui I have this (which works) in my .lircrc begin remote = Hauppauge button = Back/Exit prog = xine repeat = 0 config = VDRBack end but I suppose xine is not the right value for vdr-sxfe ? I have tried vdr-sxfe and had a look in xine_frontend_lirc.c but I'm none the wiser. -- Scott___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Best practices for running vdr-xine
On Wed, 29 Apr 2009 22:27:00 +0300, Seppo Ingalsuo seppo.ingal...@iki.fi wrote: Jan Ekholm wrote: So xineliboutput can't be what budget card people use, so I guess it's time to test vdr-xine. My initial gut feeling is that VDR isn't meant for X11 output at all, and it just happens to be possible to kludge it somehow. Bad luck? Obsolete xine libraries? I'm running three vdr-sxfe clients at home with nice 50 Hz progressive 720p/1080p output to DVI with close to perfect vertical blanking sync (or in other words the horizontal text scrolls are smooth and sharp). I didn't get that working with on-board AMD780G graphics in my newest PC but a cheapo Nvidia card fixed that. Now I'm looking forward to eventually switch to VDPAU. BR, Seppo How did you get the smooth scrolling, mine is jerky? I have on board nvidia HDMI connected to a plasma. I have a 50 Hz setting in xorg.conf and the Xorg.0.log and nvidia-settings both report a 50hz rate, the TV however reports 60 Hz so may be down to a duff TV (Samsung). -- Scott ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Streaming recordings
Hi, I was thinking of hacking in some more support to streamdev to support playback of recordings. Early days though. VTP seems easiest to get some playback with the PORT and PROV commands, although SVDRP has some support with the LSTR. Dont want to step on anyones toes, but any thoughts/suggestions? -- Scott___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Possibly corrupt stream for VDR frontends in 1. 7.4?
For what its worth, and its not worth much. I was watching live TV using Mplayer (on a Nintendo Wii) to streamdev on 1.7.4. the PES (http://xxx:3000/PES/1) stream worked quite well, whereas the TS stream only worked for a few seconds and then crashed. It was not corrupt though and the problem is no doubt due to the Mplayer port. -- Scott On Sun, 5 Apr 2009 10:26:05 +0200, Artem Makhutov ar...@makhutov.org wrote: Hello, currently watching HDTV channels using a VDR frontend (streamdev and xineliboutput - current CVS builds) is impossible for me. Watching the recordings (1.ts) using xine (with VDPAU) works like a charm. I am wondering if there could be a bug in how VDR is presenting the TS data to the frontends. I have just a corrupt video and audio using both plugins. I have also glitches in MPEG2 streams some times, which do not occour when watching the .ts recording directly. Can somebody validate this? Thanks, Artem PS: I saw similar problems while testing the multicast output of streamdev. The STBs I have used for playback did not liked 1500 bytes large packets which streamdev had send out (Xine had no problems in playing them back). When streamdev was changed to send 1316 (7*188) bytes packets the problem was solved for the STBs. Maybe there is something similar with VDR 1.7.4? ___ 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] Help with dvd plugin!
Doesn't look like a problem with gcc to me. It complains that it can't find FRAMESPERSEC in player-dvd.c on line 2031. I don't know where that should come from, you could try: grep -R FRAMESPERSEC * from the vdr top directory, where you normally run make. On Thu, 2 Apr 2009 02:03:27 -0700 (PDT), lucian orasanu o_luc...@yahoo.com wrote: Hy all, I'm trayng to compile dvd plugin but it fails! this is build log http://pastebin.com/m67dab49c. i tested it with vdr-1.7.4, gcc-4.3.3, x86 Can some one help me, ?I think is something with gcc. ___ 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] OpenTV and multiscreen
Hi, I've googled around and from some old discussions it would seem that the news multiscreens on Astra 28.2 (BBC News and Sky News) use a properiatory OpenTV format and are not viewable with VDR (or any other non-OpenTV STB). Is that still the case? I have a channel which displays the 6 BBC news videos in 6 boxes, but I only seem to get the audio for the first one. -- Scott ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.7.4 S2API and DVB-C ??
On 04/02/2009 19:26, Simon Baxter wrote: Hi Does vdr-1.7.4, ts recordings and and the S2API work under DVB-C? I can't see why it wouldn't? Dum question - where can I find the S2API repository? I just pulled the latest v4l-dvb from linuxtv.org, but I get vdr compiling errors requesting version 5. I think it should compile with that but you need to make sure it is using those headers. I changed line 24 of my Makefile to this: INCLUDES = -I/data/downloads/v4l-dvb/linux/include -I/usr/src/linux/include -I/usr/include/freetype2 Where /data/downloads/v4l-dvb is where you got the latest v4l-dvb tree. -- Scott ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Rewind and Skip buttons
Hi, These buttons, the ones with the diode like pictures on them, dont seem to have enum entries in keys.h, is that correct? I see that green/yellow can be used for these functions, but what is the philosophy for what goes in the enum. Just curious. -- Scott ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Options for deinterlacing (or not)
I want to replace my UK Sky digital box with VDR (I only want the free to air channels) for watching/recording TV over HDMI on my plasma. So far everything is working OK, I have vdr 1.7.3 and xine running on an ASUS M2N VM-HDMI (nvidia) mobo with the s2-liplianin drivers for my Nova SD2 card. My problem is interlacing. I've googled back through the archives and got a lot of info from there, however I still have one question and one request. If X is put into an interlaced mode (1920x1080i @ 50Hz), and I do not do any de interlacing in xine, why is this not the same as what my digibox does? I'm guessing it has something to do with xine outputting a complete frame when the broadcast sends each field? What I'd hope happen (for interlaced material) is that xine receives a field from VDR, scales it to the X resolution (halfed vertically of course) and sends it to the the graphics card which just passes it on to the TV which draws that field. That doesn't seem to happen so where have I gone wrong? There's a lot of options for tvtime in xine, TomsMoComp and full framerate seem popular. What settings are others using? -- Scott ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] 1:1 pixel mapping - a waste of time?
As Im just starting to get vdr working, I was wondering if 1:1 pixel mapping between the video card (nvidia onboard HDMI output) and my flat panel (Samsung plasma) is a waste of time. When looking at a computer generated image like the desktop, its going to make a difference, but with broadcast material (SD mostly), I imagine that the material is scaled anyway to fit the resolution of the panel (which in my case I think is 1024x720, but that has a bit of overscan). So it wont be 1:1 anyway, or am I wrong here? I know this is a bit off topic, but there seems to be a fair bit of experience here. -- Scott ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] 1.7.2 xine plugin FIXMEs
Hi, Newbie alert!! I'm trying to get started with vdr and dvb-s (and s2 hopefully) and xine. I've downloaded v4l-dvb (30/12), and patched it with v4l-dvb-s2api-add-s2-capability.diff. That builds and installs fine. Modules load fine (for Nova HD-S2) and I can record (and playback) streams using gnutv so I guess the card and its module are ok. I then run vdr (1.7.2) from the command line like this and I get a bunch of FIXMEs: ./vdr -c /etc/vdr -L ./PLUGINS/lib -v /data/video -E/data/video -Pxine -r - MakePrimaryDevice: 1 = SetVideoFormat: 0 SetVolumeDevice: 255 SetAudioChannelDevice: 0 SetVolumeDevice: 255 SetPlayMode: 1 SetAudioChannelDevice: 0 SetDigitalAudioDevice: 0 SetAudioChannelDevice: 0 SetDigitalAudioDevice: 0 SetAudioChannelDevice: 0 frame: (0, 0)-(-1, -1), zoom: (1.00, 1.00) GrabImage ... GrabImage failed. FIXME: xineDevice.c:3178 FIXME: xineDevice.c:1654 [FIXME: xineDevice.c:648 a] FIXME: xineDevice.c:1400 FIXME: xineDevice.c:3178 FIXME: xineDevice.c:1654 FIXME: xineDevice.c:1400 FIXME: xineDevice.c:3178 which seem to indicate that the stream does not begin 0 0 1. GrabImage is there as I had VDRAdmin-AM running, it also seems to have a problem, hopefully the same one. Any ideas where I go with this? Also is there a cvs/hg repository for vdr, I got mine from ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.7.2.tar.bz2? -- Scott ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
