Re: [vdr] UPnP/DLNA server plugin?
2008/4/29 Steffen Barszus [EMAIL PROTECTED]: There is a good UPnP server available for linux, called Fuppes: http://fuppes.ulrich-voelkel.de/ not tried that - found mediatomb to look more interesting I installed mediatomb now too. It is far easier to setup than fuppes, and has some extra features like http streaming.. But still doesn't work any better with PS3. :) I wonder why the http streaming doesn't work, PS3 just reports some server error but logs show that it has actually connected to the stream just fine. -- Teemu Suikki http://www.z-power.fi/ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] UPnP/DLNA server plugin?
Teemu Suikki schrieb: 2008/4/29 Steffen Barszus [EMAIL PROTECTED]: There is a good UPnP server available for linux, called Fuppes: http://fuppes.ulrich-voelkel.de/ not tried that - found mediatomb to look more interesting I installed mediatomb now too. It is far easier to setup than fuppes, and has some extra features like http streaming.. But still doesn't work any better with PS3. :) It could be that the mime type is flagged wrong ? Think its outside vdr not that usual to stream mpeg2-ts around ;) The TG100 is streaming it just fine, but every now and then it displays the TV stream like radio (with OSD :( ) Did you try to change the type in the webinterface of mediatomb allready ? I wonder why the http streaming doesn't work, PS3 just reports some server error but logs show that it has actually connected to the stream just fine. Maybe also the IRC of mediatomb might help ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] OT: ITV HD Testing on Eurobird but receivable with VDR
Great, it's working :) I have vdr-xine + ffmpeg. The sound is not perfect, I think the CPU is not enough (AMD 2350 BE). Here is a screenshot: http://www.tigercomp.ro/~ifuley/itvhd.jpg Thanks for the info, Morfsta. Istvan -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] lcdproc, utf-8 VDR
Hi! My VDR with utf-8 is working marvelously, except for a small cosmetic problem. The non-7-bit characters are not shown correctly on my LCD. The LCD expects characters (i.e. it is no a graphics-LCD, or at least the kernel module isn't), in a certain character set (iso-8859-15 probably but I can't be actually sure, something very similar though). The vdr-lcdproc outputs characters in utf-8 (since I want to use utf-8). So, a utf-8 to iso-8859-15 conversion is required in the chain VDR-lcdproc-LCDd-/dev/lcd0. Currently none of the aforementioned can do the conversion. I can do the wollowing: 'echo ä | iconv -f utf-8 -t iso8859-15 /dev/lcd0' To show a real ä on my LCD. So, I tried the following workaround on my box: - mkfifo fakelcd - tail fakelcd | iconv -f utf-8 -t iso8859-15 /dev/lcd0 - Point LCDd to fakelcd (this is as I recall I tried it, it was some weeks ago when I did the actual tests) The above would work otherwise, but iconv doesn't tail - i.e. it waits for EOF (or something). I could do 'cat somefile fakelcd', with somefile containing utf-8 characters and it was shown, but that won't work with VDR. Any other suggestions? Also, in your opinion, which one in the chain VDR-lcdproc-LCDd-/dev/lcd0 should be responsible of the conversion of the character set? I'm asking so I know which programs author should I point my whine to =) Cheers! - Ville -- -- Ville Aakko - [EMAIL PROTECTED] ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] lcdproc, utf-8 VDR
Ville Aakko wrote: Hi! Also, in your opinion, which one in the chain VDR-lcdproc-LCDd-/dev/lcd0 should be responsible of the conversion of the character set? I'm asking so I know which programs author should I point my whine to =) Well it depends of API and what support the hardware. In my opinion doing charset conversion in kernel is not a good thing. Matthieu ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.6.0 channel not available
On 05/02/08 19:26, Simon Baxter wrote:
You could add some debug outputs to
cDevice::GetDevice(const cChannel *Channel, int Priority, bool LiveView)
to find out why it thinks that channel 9 is not available.
Can someone help me out here?How do I do this?
Try the attached patch.
Klaus
--- device.c 2008/04/12 14:12:14 2.2
+++ device.c 2008/05/03 10:49:26
@@ -372,6 +372,7 @@
cDevice *cDevice::GetDevice(const cChannel *Channel, int Priority, bool LiveView)
{
+ printf(GetDevice %d %d %d %d\n, Channel-Number(), Priority, LiveView, avoidDevice ? avoidDevice-CardIndex() : -1);//XXX
cDevice *AvoidDevice = avoidDevice;
avoidDevice = NULL;
// Collect the current priorities of all CAM slots that can decrypt the channel:
@@ -391,7 +392,9 @@
}
}
if (!NumUsableSlots)
+{printf(no usable CAM slots!\n);//XXX
return NULL; // no CAM is able to decrypt this channel
+}//XXX
}
bool NeedsDetachReceivers = false;
@@ -432,6 +435,7 @@
imp = 1; imp |= NumUsableSlots ? 0 : device[i]-HasCi(); // avoid cards with Common Interface for FTA channels
imp = 1; imp |= device[i]-HasDecoder(); // avoid full featured cards
imp = 1; imp |= NumUsableSlots ? !ChannelCamRelations.CamDecrypt(Channel-GetChannelID(), j + 1) : 0; // prefer CAMs that are known to decrypt this channel
+ printf(j = %d, i = %d, imp = %08X, Impact = %08X\n, j, i, imp, Impact);//XXX
if (imp Impact) {
// This device has less impact than any previous one, so we take it.
Impact = imp;
@@ -446,6 +450,7 @@
break; // no CAM necessary, so just one loop over the devices
}
if (d) {
+ printf(device %d\n, d-CardIndex());//XXX
if (NeedsDetachReceivers)
d-DetachAllReceivers();
if (s) {
@@ -460,6 +465,7 @@
else if (d-CamSlot() !d-CamSlot()-IsDecrypting())
d-CamSlot()-Assign(NULL);
}
+ else printf(no device found\n);//XXX
return d;
}
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] cvs xineliboutput
Petri Helin [EMAIL PROTECTED] writes: cvs update -C -r 1.127 xine_input_vdr.c It has been reported to cure the kind of behaviour you have been experiencing. btw, vdr-sxfe is also affected. Reverting xine_input_vdr.c, recompiling (make plugins) and reinstalling vdr-sxfe should fix that. That's exactly what i did. /usr/src/vdr/vdr-1.6.0/PLUGINS/src/xineliboutput $ ls -lht |head -n 6 total 5.8M -rwxrwxr-x 1 laurent laurent 211K May 3 00:04 xineplug_inp_xvdr.so -rw-rw-r-- 1 laurent laurent 249K May 3 00:04 xine_input_vdr.o drwxrwxr-x 2 laurent laurent 48 May 3 00:04 CVS -rw-rw-r-- 1 laurent laurent 187K May 3 00:04 xine_input_vdr.c drwxrwxr-x 3 laurent laurent 4.0K May 1 12:28 po but vdr-sxfe wasn't recompiled. it seems there's no dependency to xine_input_vdr.c -- ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] cvs xineliboutput
[EMAIL PROTECTED] wrote: but vdr-sxfe wasn't recompiled. it seems there's no dependency to xine_input_vdr.c You may have to run make clean-plugins. ( cd /usr/src/vdr-1.6.0-1/ make clean-plugins make plugins cd /usr/src/vdr-1.6.0-1/PLUGINS/src/xineliboutput-1.0.0 make install cp /usr/src/vdr-1.6.0-1/PLUGINS/lib/libvdr-xineliboutput.so.1.6.0 \ /usr/lib/vdr/plugins/ cp /usr/src/vdr-1.6.0-1/PLUGINS/lib/libxineliboutput-sxfe.so.1.0.0 \ /usr/lib/vdr/plugins/ ) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] cvs xineliboutput
Simon Baxter [EMAIL PROTECTED] writes:
If you could share your modified plugin - that'd be great
freevo-vdr.tar.bz2
Description: Binary data
If I recall correctly it was based on freevo-vdr-0.5.
I copy the 2 files in
/usr/local/stow/freevo-1.x/lib/python2.5/site-packages/freevo/plugins/
and I use this in my local_conf.py:
plugin.activate('vdr_interface')
plugin.activate('vdrtv', level=5)
VDR_VIEWER_PLUGIN='sxfe'
#VDR_VIEWER_PLUGIN='xine'
VDR_USE_SVDRP=0
VDR_SVDRP_HOST='telly'
VDR_SVDRP_PORT=2001
VDR_SVDRP_ALWAYSCLOSE=0
#VDR_XINE_FIFO_PATH='xvdr:tcp://telly:37890#nocache;demux:mpeg_block'
VDR_XINE_FIFO_PATH='xvdr://telly:37890'
It's a bit hackish, I haven't taken the time make it clearer and cleaner.
--
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] cvs xineliboutput
Pertti Kosunen [EMAIL PROTECTED] writes:
[EMAIL PROTECTED] wrote:
but vdr-sxfe wasn't recompiled. it seems there's no dependency to
xine_input_vdr.c
You may have to run make clean-plugins.
what I meant is that it does not seem vdr-sxfe depends on
xine_input_vdr.c
And the modification made to xine_input_vdr.c won't affect vdr-sxfe.
And it can be verified by removing xine_input_vdr.{c,o} vdr-sxfe and
running make vdr-sxfe
--
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] cvs xineliboutput
[EMAIL PROTECTED] wrote:
Pertti Kosunen [EMAIL PROTECTED] writes:
[EMAIL PROTECTED] wrote:
but vdr-sxfe wasn't recompiled. it seems there's no dependency to
xine_input_vdr.c
You may have to run make clean-plugins.
what I meant is that it does not seem vdr-sxfe depends on
xine_input_vdr.c
And the modification made to xine_input_vdr.c won't affect vdr-sxfe.
And it can be verified by removing xine_input_vdr.{c,o} vdr-sxfe and
running make vdr-sxfe
It will affect in a sense since xine_input_vdr.c is used when building
xineplug_inp_xvdr.so (the xine VDR input plugin) which in turn is used
whether you use vdr-sxfe or xine-ui. So, the important thing is to
replace the xine plugin after recompile, which is done by make install.
Are you saying that you still see the same behaviour when using
vdr-sxfe? Even if you recompile and replace the xine plugin?
-Petri
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] cvs xineliboutput
Petri Helin [EMAIL PROTECTED] writes: It will affect in a sense since xine_input_vdr.c is used when building xineplug_inp_xvdr.so (the xine VDR input plugin) which in turn is used whether you use vdr-sxfe or xine-ui. So, the important thing is to replace the xine plugin after recompile, which is done by make install. ok, I was thinking only xine-ui was using the plugin. Are you saying that you still see the same behaviour when using vdr-sxfe? Even if you recompile and replace the xine plugin? Don't know, I haven't tried :) Going to try right now -- ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] cvs xineliboutput
[EMAIL PROTECTED] writes: Don't know, I haven't tried :) Going to try right now Seems ok now. Thanks again. -- ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.6.0 channel not available
Klaus Schmidinger kirjoitti 2.5.2008 kello 17.03: On 04/27/08 12:49, Tero Siironen wrote: ... I don't know if this is same problem or not but I'm having similar symptoms with one encrypted channel. With plain VDR 1.6.0 I cannot tune to that channel, while 1.4.7 works. As can be seen from the log, the receiving starts from couple of seconds but stops right after giving this channel not available message. My system has DVB-C 2.1 FF card and Satelco Easywatch budget card. All the other encrypted channels works ok, but this one channel has problems with VDR 1.6.0. Your CAM seems to come and go. Please try the 1.6.0-1 maintenance patch from ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.6.0-1.diff which increases the time between the CAM status checks. Doesn't help, log is pretty similar still and picture shows now and then for couple of seconds May 2 23:03:36 localhost vdr: [4340] VDR version 1.6.0-1 started May 2 23:03:36 localhost vdr: [4340] codeset is 'ISO-8859-1' - known May 2 23:03:36 localhost vdr: [4340] found 23 locales in ./locale May 2 23:03:36 localhost vdr: [4340] loading /video/setup.conf May 2 23:03:36 localhost vdr: [4340] loading /video/sources.conf May 2 23:03:36 localhost vdr: [4340] loading /video/channels.conf May 2 23:03:36 localhost vdr: [4340] loading /video/timers.conf May 2 23:03:36 localhost vdr: [4340] loading /video/svdrphosts.conf May 2 23:03:36 localhost vdr: [4340] loading /video/remote.conf May 2 23:03:36 localhost vdr: [4340] loading /video/keymacros.conf May 2 23:03:36 localhost vdr: [4340] reading EPG data from /video/ epg.data May 2 23:03:37 localhost vdr: [4341] video directory scanner thread started (pid=4340, tid=4341) May 2 23:03:37 localhost vdr: [4342] video directory scanner thread started (pid=4340, tid=4342) May 2 23:03:37 localhost vdr: [4340] probing /dev/dvb/adapter0/ frontend0 May 2 23:03:37 localhost vdr: [4344] CI adapter on device 0 thread started (pid=4340, tid=4344) May 2 23:03:37 localhost vdr: [4340] probing /dev/dvb/adapter1/ frontend0 May 2 23:03:37 localhost vdr: [4342] video directory scanner thread ended (pid=4340, tid=4342) May 2 23:03:37 localhost vdr: [4345] tuner on device 1 thread started (pid=4340, tid=4345) May 2 23:03:37 localhost vdr: [4346] section handler thread started (pid=4340, tid=4346) May 2 23:03:37 localhost vdr: [4348] CI adapter on device 1 thread started (pid=4340, tid=4348) May 2 23:03:37 localhost vdr: [4340] found 2 video devices May 2 23:03:37 localhost vdr: [4340] setting primary device to 1 May 2 23:03:37 localhost vdr: [4349] tuner on device 2 thread started (pid=4340, tid=4349) May 2 23:03:37 localhost vdr: [4350] section handler thread started (pid=4340, tid=4350) May 2 23:03:37 localhost vdr: [4340] assuming manual start of VDR May 2 23:03:37 localhost vdr: [4340] SVDRP listening on port 2001 May 2 23:03:37 localhost vdr: [4340] loading /video/themes/classic- default.theme May 2 23:03:37 localhost vdr: [4340] remote control LIRC - keys known May 2 23:03:37 localhost vdr: [4351] LIRC remote control thread started (pid=4340, tid=4351) May 2 23:03:37 localhost vdr: [4344] CAM 1: module present May 2 23:03:38 localhost vdr: [4341] video directory scanner thread ended (pid=4340, tid=4341) May 2 23:03:39 localhost vdr: [4340] switching to channel 1 May 2 23:03:39 localhost vdr: [4348] CAM 3: no module present May 2 23:03:39 localhost vdr: [4344] CAM 2: no module present May 2 23:03:39 localhost vdr: [4346] channel 4 (Nelonen) event Pe 02.05.2008 22:55-23:05 'IS Urheilu-uutiset' status 4 May 2 23:03:39 localhost vdr: [4346] channel 2 (YLE TV2) event Pe 02.05.2008 22:25-00:50 'Jääkiekon MM 2008: Kanada - Slovenia' status 4 May 2 23:03:39 localhost vdr: [4346] channel 6 (Sub) event Pe 02.05.2008 22:10-23:05 'Bones' status 4 May 2 23:03:39 localhost vdr: [4346] channel 3 (MTV3) event Pe 02.05.2008 22:36-01:10 'Windtalkers' status 4 May 2 23:03:39 localhost vdr: [4346] changing pids of channel 1 from 512+512:650=deu:0:2321 to 512+512:650=deu:1027=fin:2321 May 2 23:03:39 localhost vdr: [4340] retuning due to modification of channel 1 May 2 23:03:39 localhost vdr: [4340] switching to channel 1 May 2 23:03:39 localhost vdr: [4352] live subtitle thread started (pid=4340, tid=4352) May 2 23:03:39 localhost vdr: [4353] receiver on device 1 thread started (pid=4340, tid=4353) May 2 23:03:39 localhost vdr: [4354] TS buffer on device 1 thread started (pid=4340, tid=4354) May 2 23:03:40 localhost vdr: [4346] changing pids of channel 2 from 513+513:660=fin,661=sve:0:2321 to 513+513:660=fin,661=sve:2027=fin:2321 May 2 23:03:40 localhost vdr: [4346] changing pids of channel 3 from 305+305:561=fin:0:817 to 305+305:561=fin:1073=fin:817 May 2 23:03:40 localhost vdr: [4346] changing pids of channel 5 from 514+514:670=esl:0:2321 to 514+514:670=esl:3028=sve,3027=fin:2321 May 2 23:03:41 localhost vdr: [4346] changing pids
Re: [vdr] UPnP/DLNA server plugin?
2008/5/3 Steffen Barszus [EMAIL PROTECTED]: Teemu Suikki schrieb: 2008/4/29 Steffen Barszus [EMAIL PROTECTED]: There is a good UPnP server available for linux, called Fuppes: http://fuppes.ulrich-voelkel.de/ not tried that - found mediatomb to look more interesting I installed mediatomb now too. It is far easier to setup than fuppes, and has some extra features like http streaming.. But still doesn't work any better with PS3. :) It could be that the mime type is flagged wrong ? Think its outside vdr not that usual to stream mpeg2-ts around ;) The TG100 is streaming it just fine, but every now and then it displays the TV stream like radio (with OSD :( ) Did you try to change the type in the webinterface of mediatomb allready ? I have tried different mime types, it's not that.. I think I'll switch back to fuppes for now, because fuppes has internal transcoding. MediaTomb uses external program (ffmpeg, vlc, mencoder) which makes it impossible to do seeks on the streamed file. Really not very nice to watch some 2 hour recording if you can't fast forward over commercials etc.. -- Teemu Suikki http://www.z-power.fi/ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.6.0 channel not available
On 05/03/08 16:24, Tero Siironen wrote: Klaus Schmidinger kirjoitti 2.5.2008 kello 17.03: On 04/27/08 12:49, Tero Siironen wrote: ... I don't know if this is same problem or not but I'm having similar symptoms with one encrypted channel. With plain VDR 1.6.0 I cannot tune to that channel, while 1.4.7 works. As can be seen from the log, the receiving starts from couple of seconds but stops right after giving this channel not available message. My system has DVB-C 2.1 FF card and Satelco Easywatch budget card. All the other encrypted channels works ok, but this one channel has problems with VDR 1.6.0. Your CAM seems to come and go. Please try the 1.6.0-1 maintenance patch from ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.6.0-1.diff which increases the time between the CAM status checks. Doesn't help, log is pretty similar still and picture shows now and then for couple of seconds Looks like there are no more unexpected CAM resets, so the reason for the channel not available must be something else. Maybe the CAM doesn't decrypt? You could add some debug output to cDevice::Action() to see whether the TS packets are getting descrambled. Maybe the TS_SCRAMBLING_TIMEOUT needs to be increased. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.6.0 channel not available
Klaus Schmidinger kirjoitti 3.5.2008 kello 19.06: On 05/03/08 16:24, Tero Siironen wrote: Klaus Schmidinger kirjoitti 2.5.2008 kello 17.03: On 04/27/08 12:49, Tero Siironen wrote: ... I don't know if this is same problem or not but I'm having similar symptoms with one encrypted channel. With plain VDR 1.6.0 I cannot tune to that channel, while 1.4.7 works. As can be seen from the log, the receiving starts from couple of seconds but stops right after giving this channel not available message. My system has DVB-C 2.1 FF card and Satelco Easywatch budget card. All the other encrypted channels works ok, but this one channel has problems with VDR 1.6.0. Your CAM seems to come and go. Please try the 1.6.0-1 maintenance patch from ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.6.0-1.diff which increases the time between the CAM status checks. Doesn't help, log is pretty similar still and picture shows now and then for couple of seconds Looks like there are no more unexpected CAM resets, so the reason for the channel not available must be something else. Maybe the CAM doesn't decrypt? You could add some debug output to cDevice::Action() to see whether the TS packets are getting descrambled. Maybe the TS_SCRAMBLING_TIMEOUT needs to be increased. I will try to debug it more. The same channel works with VDR 1.4.7 so the CAM works. Also with 1.6.0-1 all other encrypted channels that I've access works with that CAM, so there is something in that one channel which causes problems with 1.6.0-1. But I will report again when I get some more data. -- Tero ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 multiproto hvr4000 - multiproto_plus
Have you replaced linux/include/linux/compiler.h with the one from your kernel ? (in multiproto_plus dir) if that's going to be included, this shouldn't be in of course. your patch included the compiler.h, after replacing it with the right one the drivers are build your patch also created a .config.old in v4l and the cx88 modules are not build (the .config created during make does only contain inaktive lines for cx88 modules), i modified the .config manual and started make again OK, here's one without compiler.h and without .config.old (by the way, I don't understand why make distclean didn't remove it...). Good new, such way the patch is even smaller, so it would be really good to have it included finally into the repo :-) Any objection to the inclusion ? with this patch I have the error May 3 22:42:15 localhost vdr: [3471] ERROR (dvbdevice.c,302): Invalid argument when I try to tune on dvb-s2 channels on VDR But with HVR-4000-multiproto_plus-2008-04-25.diff + HVR-4000-multiproto_plus-2008-04-25_inversion is OK for me Igor ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0
when I want to switch on dvb-s2 channels ( 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 Please post the channels.conf line of that channel. ASTRA HD+;BetaDigital:11914:hC910M2O35S1:S19.2E:27500:1279:0;1283=deu:0:0:131:133:6:0 but the problem was in bug inside cx24116 driver Gilmi has fixed it in HVR-4000-multiproto_plus-2008-04-25_inversion patch for cx24116.c Igor ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 multiproto hvr4000 - multiproto_plus
with this patch I could receive dvb-s2 channels on my VDR 170 I don't have the error May 3 22:42:15 localhost vdr: [3471] ERROR (dvbdevice.c,302): Invalid argument anymore @gilmi thanks Igor sorry, took a little bit longer to find time for made the patch. This patch is against multiproto_plus + HVR-4000-multiproto_plus-2008-04-25.diff. With this combination i'm able to tune all HDTV channels on Astra 19.2E. My Hardware is a WinTV Nova HD S2. cu Edgar (gimli) Hucek On Tue, Apr 29, 2008 at 10:18:30AM +0200, gimli wrote: Some postings before i read about multiproto + hvr4000 and tuning problems. I had that problems myselfe. The problem is the inversion setting in the driver. It's a driver bug. At the moment i do not have my modified driver by hand. Will post it in later today. I did a mixuup between : http://www.linuxtv.org/pipermail/linux-dvb/2008-March/024487.html and http://www.mail-archive.com/[EMAIL PROTECTED]/msg27438.html a patch i have done. c Edgar (gimli) Hucek Oh, nice one, could you correct my update on your work for multiproto_plus : http://linuxtv.org/pipermail/linux-dvb/2008-April/025655.html I must have different hardware because all works just fine here... Thanks, -- GrИgoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org http://picasaweb.google.com/Gregoire.Favre ATTACHMENT: application/octet-stream (HVR-4000-multiproto_plus-2008-04-25_inversion.diff) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [linux-dvb] VDR 1.7.0 multiproto hvr4000 - multiproto_plus
sorry, I was wrong with the latest cumulative hvr4000-patch from Gregoire HVR-4000-multiproto_plus-2008-05-02.diff.bz2 I can tune on dvb-s2 channels on my VDR 170 this patch is OK for me @Gregoire thank you very much Igor -Original Message- From: Igor [EMAIL PROTECTED] To: VDR Mailing List vdr@linuxtv.org Date: Sat, 03 May 2008 22:51:26 +0400 Subject: Re: [linux-dvb][vdr] VDR 1.7.0 multiproto hvr4000 - multiproto_plus Have you replaced linux/include/linux/compiler.h with the one from your kernel ? (in multiproto_plus dir) if that's going to be included, this shouldn't be in of course. your patch included the compiler.h, after replacing it with the right one the drivers are build your patch also created a .config.old in v4l and the cx88 modules are not build (the .config created during make does only contain inaktive lines for cx88 modules), i modified the .config manual and started make again OK, here's one without compiler.h and without .config.old (by the way, I don't understand why make distclean didn't remove it...). Good new, such way the patch is even smaller, so it would be really good to have it included finally into the repo :-) Any objection to the inclusion ? with this patch I have the error May 3 22:42:15 localhost vdr: [3471] ERROR (dvbdevice.c,302): Invalid argument when I try to tune on dvb-s2 channels on VDR But with HVR-4000-multiproto_plus-2008-04-25.diff + HVR-4000-multiproto_plus-2008-04-25_inversion is OK for me ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [ANNOUNCE]: osdpip-0.0.10
Hi, there is a new version 0.0.10 of the osdpip plugin available: http://home.arcor.de/andreas.regel/files/osdpip/vdr-osdpip-0.0.10.tgz Changes since 0.0.9: - support swscale functions of recent FFMPEG versions. Have a look at README to see how to deactivate it for older FFPMEG versions. - support changed header file structure of recent FFMPEG versions. Have a look at README to see how to activate this. - added zapping through PiP channel based on a patch by pinky666 from vdr-portal. You can activate it via the green button. Regards, Andreas ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] e-tobi ubuntu hardy
Hi, I'm trying to set vdr building the packages from the e-tobi source packages. I'm doing this because I want to run vdr as streamdev client, with no dvb card in the client system. The e-tobi source I'm using is: deb-src http://e-tobi.net/vdr-experimental etch base addons vdr-multipatch The problem I have is that if I do: sudo apt-get build-dep vdr-plugin-xineliboutput The system says me that any version of the libxine-dev package can satisfy the xineliboutput dependencies. If I ignore the message and try to build the .deb packages (satisfying manually the dependences) there is a moment that apt ask me to update the vdr package. At this point I am a bit confused because I understand that this is a conflict between my e-tobi installed vdr and the ubuntu hardy vdr package. My goal on this is get a streamdev client vdr box with xineliboutput output. Could anyone advise me to acquire my objective? Thank you. Leo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
