Re: [vdr] about the hvr-4000 tuning problems
I have following in my channel conf for dvb-t and dvb-s channels: YLE TV1;YLE:546000:B8C23G8M64T8Y0:T:27500:512=2:650=fin:2321:0:17:8438:4097:0 arte;ARD:10743:hC56M5O0S0:S19.2E:22000:401=2:402=deu,403=fra:404:0:28724:1:1051:0 Concerning Arte, I've got that same setting in my channels.conf. And I'm able to see that channel instantly. Klaus, do you have any idea from which functions I should try to track more for finding the problem? I use a Hauppauge NOVA-HD-S2 and I've updated to the latest S2API drivers on the s2-liplianin repository. It uses the same kernel-driver as the HVR-4000. And I don't have any tuning problems at all on Hotbird 13.0, Astra 19.2, Astra 23.5 and Astra 28.2. This is with VDR 1.7.0 and my own S2API patch as well as with VDR 1.7.3. I have tried both with the s2-liblianin and v4l-dvb versions of the drivers and I do not see any differences. scan,szap,szap-s2,scan-s2 and vdr-1.6.0 works ok with all of them. It's just that neither vdr-1.7.0 with your patches or vdr-1.7.2 or vdr-1.7.3 without patches are working. By any chance, did you try disabling diseqc? Because I had tuning problems when I used standard diseqc values with no retries with my diseqc 1.0 switch. I had to use the following safe diseqc commands for my diseqc 1.0 configuration: I do not have diseqc in my system and I checked that at least the cDvbTuner::SetFrontEnd() method from dvbdevice.c detected that correctly and went to else part of the block. (=no diseqcs) When I try to change to a (not previously tuned with szap) dvb-s/s2 channel, vdr will just notice that the tunerStatus variable in Action() method is = 2, which means that tuned. It will never go to state 3 which means locked. With szap-s2,szap or vdr-1.6.0 I can however get the locks immediately. So I am wondering that what could be the most potential places in vdr code where I should try to make some changes to tuning/locking code for testing. Is it the cDvbTuner::SetFrontEnd method or is there also some other methods that are really interfacing with S2API and could affect to the tuning or locking? Mika # # port 1 S19.2E 11700 V 9750 t v W15 [E0 10 38 F0] W100 [E0 10 38 F0] W100 [E0 11 00] W100 A W15 t S19.2E 9 V 10600 t v W15 [E0 10 38 F1] W100 [E0 10 38 F1] W100 [E0 11 00] W100 A W15 T S19.2E 11700 H 9750 t V W15 [E0 10 38 F2] W100 [E0 10 38 F2] W100 [E0 11 00] W100 A W15 t S19.2E 9 H 10600 t V W15 [E0 10 38 F3] W100 [E0 10 38 F3] W100 [E0 11 00] W100 A W15 T # port 2 S13.0E 11700 V 9750 t v W15 [E0 10 38 F4] W100 [E0 10 38 F4] W100 [E0 11 00] W100 B W15 t S13.0E 9 V 10600 t v W15 [E0 10 38 F5] W100 [E0 10 38 F5] W100 [E0 11 00] W100 B W15 T S13.0E 11700 H 9750 t V W15 [E0 10 38 F6] W100 [E0 10 38 F6] W100 [E0 11 00] W100 B W15 t S13.0E 9 H 10600 t V W15 [E0 10 38 F7] W100 [E0 10 38 F7] W100 [E0 11 00] W100 B W15 T # port 3 S23.5E 11700 V 9750 t v W15 [E0 10 38 F8] W100 [E0 10 38 F8] W100 [E0 11 00] W100 A W15 t S23.5E 9 V 10600 t v W15 [E0 10 38 F9] W100 [E0 10 38 F9] W100 [E0 11 00] W100 A W15 T S23.5E 11700 H 9750 t V W15 [E0 10 38 FA] W100 [E0 10 38 FA] W100 [E0 11 00] W100 A W15 t S23.5E 9 H 10600 t V W15 [E0 10 38 FB] W100 [E0 10 38 FB] W100 [E0 11 00] W100 A W15 T # port 4 S28.2E 11700 V 9750 t v W15 [E0 10 38 FC] W100 [E0 10 38 FC] W100 [E0 11 00] W100 B W15 t S28.2E 9 V 10600 t v W15 [E0 10 38 FD] W100 [E0 10 38 FD] W100 [E0 11 00] W100 B W15 T S28.2E 11700 H 9750 t V W15 [E0 10 38 FE] W100 [E0 10 38 FE] W100 [E0 11 00] W100 B W15 t S28.2E 9 H 10600 t V W15 [E0 10 38 FF] W100 [E0 10 38 FF] W100 [E0 11 00] W100 B W15 T S28.5E 11700 V 9750 t v W15 [E0 10 38 FC] W100 [E0 10 38 FC] W100 [E0 11 00] W100 B W15 t S28.5E 9 V 10600 t v W15 [E0 10 38 FD] W100 [E0 10 38 FD] W100 [E0 11 00] W100 B W15 T S28.5E 11700 H 9750 t V W15 [E0 10 38 FE] W100 [E0 10 38 FE] W100 [E0 11 00] W100 B W15 t S28.5E 9 H 10600 t V W15 [E0 10 38 FF] W100 [E0 10 38 FF] W100 [E0 11 00] W100 B W15 T Mika Regards, Niels Wagenaar ___ 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] 1.7.3
Hello.
I've tried to play the new ts recordings with vlc and it seems that
there is a typo in remux.c.
--- remux.c.orig2009-01-16 12:22:43.0 +0200
+++ remux.c 2009-01-16 12:23:39.0 +0200
@@ -320,7 +320,7 @@
uchar *cPatPmtGenerator::GetPmt(int Index)
{
if (Index numPmtPackets) {
- IncCounter(patCounter, pmt[Index]);
+ IncCounter(pmtCounter, pmt[Index]);
return pmt[Index++];
}
return NULL;
Good news is that vlc does show dvb subtitles from the ts recordings.
BTW, here is a quick and ugly hack to get streamdev to compile with
1.7.3.
http://users.utu.fi/mijutu/digitv/vdr/streamdev-pes_commented_out_for_vdr-1.7.3.diff
This is not worth merging anywhere, but works if you want to try to
record with 1.7.3 in a computer without actual dvb adapters.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.3
On 08.01.2009 07:32, gimli wrote: Hi, on playback old HDTV recordings the timline is wrong. From a first look it seems to show the double length of the recording. I assume those old HDTV recordings were done in PES. VDR 1.7.3 and up is probably not compatible with such recordings. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Lost and regained locks
On 08.01.2009 07:10, Jan Ekholm wrote: Hi folks, Should I worry when my syslog fills up with stuff like this: Jan 8 06:30:51 hex vdr: [2965] frontend 0 regained lock on channel 33, tp 322 Jan 8 06:30:52 hex vdr: [2965] frontend 0 lost lock on channel 33, tp 322 Jan 8 06:30:52 hex vdr: [2965] frontend 0 regained lock on channel 33, tp 322 Jan 8 06:30:53 hex vdr: [2965] frontend 0 lost lock on channel 33, tp 322 Jan 8 06:30:53 hex vdr: [2965] frontend 0 regained lock on channel 33, tp 322 Jan 8 06:30:54 hex vdr: [2965] frontend 0 lost lock on channel 33, tp 322 Jan 8 06:30:54 hex vdr: [2965] frontend 0 regained lock on channel 33, tp 322 Jan 8 06:30:56 hex vdr: [2965] frontend 0 lost lock on channel 33, tp 322 Jan 8 06:30:56 hex vdr: [2965] frontend 0 regained lock on channel 33, tp 322 Jan 8 06:30:57 hex vdr: [2965] frontend 0 lost lock on channel 33, tp 322 Jan 8 06:30:57 hex vdr: [2965] frontend 0 regained lock on channel 33, tp 322 Jan 8 06:30:59 hex vdr: [2965] frontend 0 lost lock on channel 33, tp 322 Jan 8 06:30:59 hex vdr: [2965] frontend 0 regained lock on channel 33, tp 322 Jan 8 06:36:15 hex vdr: [2965] frontend 0 lost lock on channel 33, tp 322 My VDR is 1.6.0 and the kernel is what's stock on a stable Debian, ie. 2.6.18-6-amd64. Everything seems to work ok and I think frontend 0 is the one that's only used for recording, frontend 1 is the one with the CI and which supplies the image (two FF DVB-c cards in use (does anyone still use those?)). Anyway, should I worry and/or is this something I could fix by upgrading something? This means that either the signal is actually so weak that the lock is lost over and over again, or there is a flaw in the driver that makes VDR think the lock has been lost. What happens if you switch both devices to that transponder? Do both frontends behave the same then? Does it also happen with other transponders, or only with this one? Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.3
On Fri, 16 Jan 2009 15:53:36 +0100 Klaus Schmidinger klaus.schmidin...@cadsoft.de wrote: I assume those old HDTV recordings were done in PES. VDR 1.7.3 and up is probably not compatible with such recordings. Are you planning to add backwards compatibility or will we need to convert our old recordings? -- TH * http://www.realh.co.uk ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.3
On 16.01.2009 16:07, Tony Houghton wrote: On Fri, 16 Jan 2009 15:53:36 +0100 Klaus Schmidinger klaus.schmidin...@cadsoft.de wrote: I assume those old HDTV recordings were done in PES. VDR 1.7.3 and up is probably not compatible with such recordings. Are you planning to add backwards compatibility or will we need to convert our old recordings? The official VDR never recorded any HDTV PES data, so there will be no backwards compatibility. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.3
On Fri, 16 Jan 2009 16:19:27 +0100 Klaus Schmidinger klaus.schmidin...@cadsoft.de wrote: On 16.01.2009 16:07, Tony Houghton wrote: On Fri, 16 Jan 2009 15:53:36 +0100 Klaus Schmidinger klaus.schmidin...@cadsoft.de wrote: I assume those old HDTV recordings were done in PES. VDR 1.7.3 and up is probably not compatible with such recordings. Are you planning to add backwards compatibility or will we need to convert our old recordings? The official VDR never recorded any HDTV PES data, so there will be no backwards compatibility. Oh, I missed the bit about HDTV. PES SD recordings are still supported then? -- TH * http://www.realh.co.uk ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.3
On 16.01.2009 18:14, Tony Houghton wrote: On Fri, 16 Jan 2009 16:19:27 +0100 Klaus Schmidinger klaus.schmidin...@cadsoft.de wrote: On 16.01.2009 16:07, Tony Houghton wrote: On Fri, 16 Jan 2009 15:53:36 +0100 Klaus Schmidinger klaus.schmidin...@cadsoft.de wrote: I assume those old HDTV recordings were done in PES. VDR 1.7.3 and up is probably not compatible with such recordings. Are you planning to add backwards compatibility or will we need to convert our old recordings? The official VDR never recorded any HDTV PES data, so there will be no backwards compatibility. Oh, I missed the bit about HDTV. PES SD recordings are still supported then? Of course - and always will be. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.7.3 + reelbox plugin
I've made some patch for reelbox plugin, but I was not able to get sound as well as from eHD as from PC soundcard. Same here. I just tried it, and the eHD does indeed give no sound. I allready posted it in the Reel forum. Hopefully a fix will popup some day. So now I'm back at vdr-1.7.0 and last multiproto from Igor. Same here. I'm back to 1.7.0 until the sound-problem has been fixed :) Have you had any replies on the Reel forum? Regards, Josce ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] ATSC a good primers guide? (Moving from Italy to the US with my VDR setup)
I'm looking at moving from Italy to the US in the summer and am trying to spend my time (while not highly preoccupied about health insurance, jobs, houses, shipping etc) trying to think through taking my VDR setup and Dreambox over to the US. I currently have a couple of Hauppauge DVB-S cards (a Nexus and a Nova) and a Hauppauge DVB-T card in the setup for digital terrestrial. I am wondering in the US if I should go with ATSC or Dish/Direct TV (or both). I'm aiming for Rockford, Illinois which has ATSC coverage. I have three vomp boxes hanging off the VDR server which I was planning to take with me. These currently connect with RGB Scart to my TV's. Then the dreambox 800 connects with HDMI. So, would the DVB-T card just work with ATSC or is it fundamentally different (like DVB-C is different to DVB-S). In which case should I get a USB ATSC dongle or two? How do you connect an RGB Vomp box to an American TV or should I get a couple of Scarted LCD's before I leave here? Is anything available with Scart in the US? My cousin says that a hotel near here is selling off it's 20 TV's for $25 each, is it worth it (I'm guessing thanks to the digital switch off)? If I go down the sat route, can I just stick a dish or direct tv card in the phoenix reader I use for Sky Italia and decode it with vdr-sc / CCcam? (Whatever happen I would be wanting a valid sub to watch what I want to.) The dreambox should display HD, as long as I have the rights to view it? Should I stick with Sat with that or go on the search for an ATSC card? Am I just overcomplicating life? Would I be better off just buying some ATSC set top boxes when I get there. Vomp/VDR was the only satisfying way of watching UK tv in Italy in any quality for us. Thanks for your ideas.. -- Latest news on http://www.stpixels.com/view_blog.cgi?user=66685 Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Serial IR receiver + wakeup from suspend
Hello all, I wonder if anybody here is using IR receiver that is connected to the PC with 9-pin serial cable and is able to wake the machine from suspend mode? Thanks. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
