vdr

vdr@linuxtv.org

6731 discussions

VDR 1.7.0 - Patched for S2-3200 - Diseqc.conf
by Jelle De Loecker 22 May '08

22 May '08

Hello everyone, I've finally gotten VDR to work with my Technotrend S2-3200 card, but I just can't seem to get this diseqc.conf file right! I'm trying to understand all the tutorials and howto's, but since they're in German ... S19.2E 11700 V 9750 [E0 10 38 F0] S19.2E 99999 V 10600 [E0 10 38 F1] S19.2E 11700 H 9750 [E0 10 38 F2] S19.2E 99999 H 10600 [E0 10 38 F3] S28.2E 11700 V 9750 [E0 10 38 F4] S28.2E 99999 V 10600 [E0 10 38 F5] S28.2E 11700 H 9750 [E0 10 38 F6] S28.2E 99999 H 10600 [E0 10 38 F7] I have a diseqc 2.0 switch, but since the S2-3200 card only supports Diseqc 1.2 I'm not really sure what to use! Thank you, Jelle De Loecker

1 1

Building VDR 1.7.0 - skincurses error?
by Jelle De Loecker 22 May '08

22 May '08

Good day everyone, I've decided to use VDR 1.7.0 on my linux box, together with my Technotrend S2-3200 DVB-S2 card. Now, it's quite hard to find a decent tutorial on how to compile VDR from source, but at least I found this in the wiki: http://www.vdr-wiki.de/wiki/index.php/OpenSUSE_VDR_DVB-S2_-_xine It's german, and I don't completely understand it, but I wrestled through it. Right up to the point where I need to compile the plugins! ... skincurses.c: In member function ‘virtual bool cPluginSkinCurses::Initialize()’: skincurses.c:793: error: ‘WINDOW’ was not declared in this scope skincurses.c:793: error: ‘w’ was not declared in this scope skincurses.c:793: error: ‘initscr’ was not declared in this scope make[1]: *** [skincurses.o] Error 1 make[1]: Leaving directory `/usr/local/src/vdr/PLUGINS/src/skincurses' ... make[1]: Entering directory `/usr/local/src/vdr/PLUGINS/src/svdrpdemo' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/usr/local/src/vdr/PLUGINS/src/svdrpdemo' *** failed plugins: skincurses make: *** [plugins] Error 1 What could be causing this and how can I fix it? I'm using LinuxMCE 0710 - Kernel 2.6.22-14-generic Thank you for your patience, Jelle De Loecker

4 5

Compiling VDR on Linuxmce 0710 using Multiproto march revision
by skerit＠kipdola.com 21 May '08

21 May '08

Hello everyone, I'm trying to install VDR on my linuxmce machine. There's a catch, though: I can only use the regular multiproto drivers from a few weeks ago since the new ones (and the multiproto plus driver) won't "detect" my DVB-S2 S2-3200 card. The multiproto drivers I'm trying to use are a few months old, from march, and they're the only ones who will work. (I can use szap with them, anyway) The problem is, when I try to compile VDR using this tutorial (http://www.vdr-wiki.de/wiki/index.php/OpenSUSE_VDR_DVB-S2_-_xine_-_Teil3) I get this error message: g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -c -DREMOTE_KBD -DLIRC_DEVICE=\"/dev/lircd\" -DRCU_DEVICE=\"/dev/ttyS1\" -D_GNU_SOURCE -DVIDEODIR=\"/video\" -DCONFDIR=\"/video\" -DPLUGINDIR=\"./PLUGINS/lib\" -DLOCDIR=\"./locale\" -I/usr/include/freetype2 -I/opt/dvb/multiproto/linux/include dvbdevice.c dvbdevice.c: In member function ?bool cDvbTuner::SetFrontend()?: dvbdevice.c:302: error: ?DVBFE_SET_DELSYS? was not declared in this scope make: *** [dvbdevice.o] Error 1 Which I think indicates it's some kind of problem between VDR and the old drivers, is this correct? I pointed to the correct DVBDIR in the Make.config file so ... How can I fix it? Thank you for your time, Jelle De Loecker ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

2 1

vdr-1.6.0 channel not available
by Simon Baxter 20 May '08

20 May '08

Hello I have 2x DVB-C cards with Alphacrypt multi-cams. A TT-1500-C budget card and a TT-2300-C FF card and run vdr-xine. When recording one channel and attempting to watch another in the same transport stream, or trying to switch to another transport stream (and hence card) I get "channel not available" messages. After switching back and forth to other transport streams, usually I can overcome this problem. But occasionally I it won't play any channels in one specific transport stream or another. What's the best way to diagnose this? How do I enable debugging to see more info than is displayed in messages: Apr 24 18:53:56 callin vdr: [7375] switching to channel 8 Apr 24 18:53:56 callin vdr: [30940] transfer thread started (pid=7375, tid=30940) Apr 24 18:53:57 callin vdr: [30939] femon receiver thread ended (pid=7375, tid=30939) Apr 24 18:53:57 callin vdr: [30941] femon receiver thread started (pid=7375, tid=30941) Apr 24 18:53:58 callin vdr: [30940] setting audio track to 1 (0) Apr 24 18:54:04 callin vdr: [7375] switching to channel 9 Apr 24 18:54:04 callin vdr: [30940] transfer thread ended (pid=7375, tid=30940) Apr 24 18:54:04 callin vdr: [7375] buffer stats: 47564 (2%) used Apr 24 18:54:04 callin vdr: [7375] info: Channel not available! Apr 24 18:54:04 callin vdr: [7375] ERROR: attempt to open OSD while it is already open - using dummy OSD! Apr 24 18:54:22 callin vdr: [7375] switching to channel 1 Apr 24 18:54:22 callin vdr: [30942] transfer thread started (pid=7375, tid=30942) Apr 24 18:54:22 callin vdr: [30936] TS buffer on device 2 thread ended (pid=7375, tid=30936) Apr 24 18:54:22 callin vdr: [30935] buffer stats: 84600 (4%) used Apr 24 18:54:22 callin vdr: [30935] receiver on device 2 thread ended (pid=7375, tid=30935) Apr 24 18:54:22 callin vdr: [30943] receiver on device 2 thread started (pid=7375, tid=30943) Apr 24 18:54:22 callin vdr: [30944] TS buffer on device 2 thread started (pid=7375, tid=30944) Apr 24 18:54:23 callin vdr: [30945] femon receiver thread started (pid=7375, tid=30945) Apr 24 18:54:23 callin vdr: [30942] setting audio track to 1 (0) Apr 24 18:54:26 callin vdr: [7375] switching to channel 9 Apr 24 18:54:26 callin vdr: [30942] transfer thread ended (pid=7375, tid=30942) Apr 24 18:54:26 callin vdr: [7375] buffer stats: 194204 (9%) used Apr 24 18:54:26 callin vdr: [7375] info: Channel not available! Apr 24 18:54:26 callin vdr: [7375] ERROR: attempt to open OSD while it is already open - using dummy OSD! Apr 24 18:54:42 callin vdr: [7375] switching to channel 21 Thanks

3 14

vdr-1.7.0 and reelchannelscan-1.6 plugin
by Mike Booth 20 May '08

20 May '08

I am unable to compile this plugin. It fails with csmenu.c:236: error: 'class cDevice' has no member named 'ProvidesS2'. Can anyone provide any info that might help. I've scanned everywhere for mention of "ProvidesS2" with no luck. I'm using vdr-1.7.0, multiproto_plus and the reelchannelscan plugin is from CVS Mike

3 3

Converting from UTF-8 to ISO-8859-1
by Joachim Wilke 20 May '08

20 May '08

Dear experts, I am currently trying to convert a string to ISO-8859-1 using the following code fragment: cCharSetConv conv(NULL, "ISO-8859-1"); const char *s_converted = conv.Convert(string); Running VDR with UTF-8, this conversion failes (i.e., s_converted == string). This is due to the fact, that cCharSetConv::SystemCharacterTable contains "NULL" instead of "UTF-8". This is because systemCharacterTable is never set: void cCharSetConv::SetSystemCharacterTable(const char *CharacterTable) { free(systemCharacterTable); systemCharacterTable = NULL; if (!strcasestr(CharacterTable, "UTF-8")) { .. systemCharacterTable = strdup(CharacterTable); } } Is there a reason for this? The conversion works fine, if I use "UTF-8" instead of "NULL": cCharSetConv conv("UTF-8", "ISO-8859-1"); Best Regards, Joachim.

2 4

VDR 1.7.0 & ERROR (dvbdevice.c,302): Invalid argument
by Igor 20 May '08

20 May '08

Hi when I want to switch on dvb-s2 channel ASTRA HD+;BetaDigital:11914:hC910I1M2O35S1:S19.2E:27500:1279:0;1283=deu:0:0:131:133:6:0 I receive this error Apr 28 09:18:32 localhost vdr: [4188] switching to channel 2782 Apr 28 09:18:32 localhost vdr: [4535] transfer thread ended (pid=4188, tid=4535) Apr 28 09:18:32 localhost vdr: [4188] buffer stats: 0 (0%) used Apr 28 09:18:32 localhost vdr: [4756] transfer thread started (pid=4188, tid=4756) Apr 28 09:18:32 localhost vdr: [4537] TS buffer on device 1 thread ended (pid=4188, tid=4537) Apr 28 09:18:32 localhost vdr: [4536] buffer stats: 0 (0%) used Apr 28 09:18:32 localhost vdr: [4536] receiver on device 1 thread ended (pid=4188, tid=4536) Apr 28 09:18:32 localhost vdr: [4757] receiver on device 1 thread started (pid=4188, tid=4757) Apr 28 09:18:32 localhost vdr: [4758] TS buffer on device 1 thread started (pid=4188, tid=4758) Apr 28 09:18:40 localhost vdr: [4197] frontend 0 timed out while tuning to channel 2782, tp 111914 Apr 28 09:18:40 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:18:40 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv->state=2 Apr 28 09:18:50 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:18:50 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv->state=2 Apr 28 09:19:00 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:19:00 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv->state=2 Apr 28 09:19:10 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:19:10 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv->state=2 Apr 28 09:19:20 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:19:20 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv->state=2 Apr 28 09:19:30 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:19:30 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv->state=2 Apr 28 09:19:41 localhost vdr: [4197] frontend 0 timed out while tuning to channel 2782, tp 111914 in attachment you can find my dvbdevice.c Igor

4 7

vdr keeps forgetting the CAM
by Hanno Zulla 19 May '08

19 May '08

Hi, my e-tobi-based vdr 1.6 setup keeps forgetting that it has a valid CAM installed. When I go to the CAM setup menu and use "reset", vdr finds it again. Is this is a known issue? If not, how can I help debugging it? Thanks, Hanno

1 0

segmentation fault with Skins.QueueMessage
by lukkinosat 18 May '08

18 May '08

Hello I use the function Skins.QueueMessage from a background thread. Example: Skins.QueueMessage( mtInfo, "TEST", 40 ); I set a time of 40 seconds, but if time watchdog is less than 40 seconds, vdr exit with a segmentation fault. Is this normal? Is possible set a message with a time greater of time watchdog? Luca P.S. Sorry for my English ___________________________________ Scopri il Blog di Yahoo! Mail: trucchi, novità, consigli... e la tua opinione! http://www.ymailblogit.com/blog/

3 2

coreavc for Linux (coreavc 1.7.0 + xine patches)
by Igor 17 May '08

17 May '08

Hi today was opened Google's discussions groups about coreavc for Linux to subscribe you can send the mail to coreavc-for-linux-subscribe(a)googlegroups.com or visit a home page http://groups.google.com/group/coreavc-for-linux?hl=en here you can find a new patches for xine 1.1.12 h264_pes.patch demux_ts_fixes.patch coreavc-xine-1.1.12_more.patch coreavc-xine-1.1.11.patch Igor

5 7

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr