Re: [vdr] [ANNOUNCE] VDR developer version 1.7.27
On 1 April 2012 00:54, VDR User wrote: >> Unfortunately, this doesn't seem to be working. I just upgraded to vdr >> 1.7.27 and the channel name is now only a single character for every >> channel. > > I had the same problem here as well. Klaus has fixed it, try the patch Thanks. Have submitted this to the yaVDR guys on github to add to their debian/patches. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] DVB-T Channels – ERROR: invalid value for parameter 'S'
I recently updated from 1.7.22 to the latest VDR developer snapshot 1.7.27 My DVB-S/DVB-S2 tuners all continued to work fine, but none of my DVB-T channels were accesible anymore. Checking the logs I noticed numerous "ERROR: invalid value for parameter 'S'" entries, whenever attempting to tune to a DVB-T channel. I presumed this was related to the changes introduced into 1.7.23 for not writing values to channels.conf that weren't valid for the given delivery system, but I couldn't find anything in the Changelog that indicated a channels.conf change was needed. I guessed the simplest way to fix this was to use VDR's channel editor to 'edit' and save my DVB-T channels, without modifying anything, and seeing what change was introduced in channels.conf - ITV1:64200:B8C23D12G32M64:T:0:520=2:521=eng@3,522=eng@3:0;523=eng:0:8271:9018:8207:0 + ITV1:64200:B8C23D12G32M64S0T8Y0:T:0:520=2:521=eng@3,522=eng@3:0;523=eng:0:8271:9018:8207:0 It is trivial for me to reproduce this for all my channels. However, I presume this means that scan / w_scan etc. all need to be updated to generate the new channels.conf format for VDR 1.7.23 and newer? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] DVB-T Channels – ERROR: invalid value for parameter 'S'
On 01.04.2012 11:27, Dominic Evans wrote: I recently updated from 1.7.22 to the latest VDR developer snapshot 1.7.27 My DVB-S/DVB-S2 tuners all continued to work fine, but none of my DVB-T channels were accesible anymore. Checking the logs I noticed numerous "ERROR: invalid value for parameter 'S'" entries, whenever attempting to tune to a DVB-T channel. I presumed this was related to the changes introduced into 1.7.23 for not writing values to channels.conf that weren't valid for the given delivery system, but I couldn't find anything in the Changelog that indicated a channels.conf change was needed. I guessed the simplest way to fix this was to use VDR's channel editor to 'edit' and save my DVB-T channels, without modifying anything, and seeing what change was introduced in channels.conf - ITV1:64200:B8C23D12G32M64:T:0:520=2:521=eng@3,522=eng@3:0;523=eng:0:8271:9018:8207:0 + ITV1:64200:B8C23D12G32M64S0T8Y0:T:0:520=2:521=eng@3,522=eng@3:0;523=eng:0:8271:9018:8207:0 It is trivial for me to reproduce this for all my channels. However, I presume this means that scan / w_scan etc. all need to be updated to generate the new channels.conf format for VDR 1.7.23 and newer? I'm getting the same here. Will look into it. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] DVB-T Channels – ERROR: invalid value for parameter 'S'
On 01.04.2012 11:53, Klaus Schmidinger wrote: On 01.04.2012 11:27, Dominic Evans wrote: I recently updated from 1.7.22 to the latest VDR developer snapshot 1.7.27 My DVB-S/DVB-S2 tuners all continued to work fine, but none of my DVB-T channels were accesible anymore. Checking the logs I noticed numerous "ERROR: invalid value for parameter 'S'" entries, whenever attempting to tune to a DVB-T channel. I presumed this was related to the changes introduced into 1.7.23 for not writing values to channels.conf that weren't valid for the given delivery system, but I couldn't find anything in the Changelog that indicated a channels.conf change was needed. I guessed the simplest way to fix this was to use VDR's channel editor to 'edit' and save my DVB-T channels, without modifying anything, and seeing what change was introduced in channels.conf - ITV1:64200:B8C23D12G32M64:T:0:520=2:521=eng@3,522=eng@3:0;523=eng:0:8271:9018:8207:0 + ITV1:64200:B8C23D12G32M64S0T8Y0:T:0:520=2:521=eng@3,522=eng@3:0;523=eng:0:8271:9018:8207:0 It is trivial for me to reproduce this for all my channels. However, I presume this means that scan / w_scan etc. all need to be updated to generate the new channels.conf format for VDR 1.7.23 and newer? I'm getting the same here. Will look into it. Sorry, that was a premature assessment. For testing I edited one of my DVB-T channel entries and changed it from B8C34D34G4M16S0T8Y0 to B8C34D34G4M16S, which was wrong - I should have stripped the 'S' as well. After correctly changing it to B8C34D34G4M16 the error did not occur any more: Apr 1 11:57:32 vdr2 vdr: [6861] switching to channel 21 Apr 1 11:57:52 vdr2 vdr: [6885] changing transponder data of channel 21 from 56200:B8C34D34G4M16:T to 56200:B8C34D34G4M16S0T8Y0:T Apr 1 11:57:53 vdr2 vdr: [6861] retuning due to modification of channel 21 Apr 1 11:57:53 vdr2 vdr: [6861] switching to channel 21 So I'm afraid I don't know why you are getting this error. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Recent breakage of DVB subtitles with dxr3
On Thu, Mar 29, 2012 at 01:47:06PM +0300, Mika Iisakkila wrote: > 28.3.2012 22:34, Pasi Kärkkäinen kirjoitti: >> The default audio mode of the em8300 device support utilities and kernel >> modules (em8300 and kmod-em8300-* packages) has changed from OSS to ALSA to >> follow upstream > > I googled your quote. Apparently it is from some Fedora release note > from 2007 and I don't think it will help me a bit with an Ubuntu > kernel from 2012, as the driver project has been forked, patched > and merged a number of times after that. > Yep, it was from Fedora. You could always check the Fedora src.rpm for any extra patches they might have there.. > I'll gladly receive a current, relevant reference that will tell > me how to use the em8300 drivers on current Ubuntu without > recompiling the kernel. It takes 18(!) hours of CPU time on my > VDR box. > I think your best bet is to post to dxr3-de...@lists.sourceforge.net mailinglist, I think all (most) the em8300 developers are there.. > Also, can we try and discuss the subtitling problem as well? > Sorry I can't really help with that.. -- Pasi ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Recent breakage of DVB subtitles with dxr3
1.4.2012 13:04, Pasi Kärkkäinen kirjoitti: Yep, it was from Fedora. You could always check the Fedora src.rpm for any extra patches they might have there.. I'll gladly receive a current, relevant reference that will tell me how to use the em8300 drivers on current Ubuntu without recompiling the kernel. It takes 18(!) hours of CPU time on my VDR box. I think your best bet is to post to dxr3-de...@lists.sourceforge.net mailinglist, I think all (most) the em8300 developers are there.. Well, I googled a bit more, and it seems the actual problem is in dxr3-plugin, not the drivers. The plugin is only able to use OSS (as of Dec.2008, anyway). I'm not willing to waste time fighting with semi-functional compatibility layers, so I'll just keep using my own kernel. Next time I'll configure out all the unneeded junk before compiling, though :D --mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Recent breakage of DVB subtitles with dxr3
On 01/04/2012 13:15, Mika Iisakkila wrote: Well, I googled a bit more, and it seems the actual problem is in dxr3-plugin, not the drivers. The plugin is only able to use OSS (as of Dec.2008, anyway). I'm not willing to waste time fighting with semi-functional compatibility layers, so I'll just keep using my own kernel. Next time I'll configure out all the unneeded junk before compiling, though :D Why don't you cross-compile your kernel on a faster computer ? Marc. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Recent breakage of DVB subtitles with dxr3
1.4.2012 15:22, Marc kirjoitti: Why don't you cross-compile your kernel on a faster computer ? Because I don't really have any with a suitable distribution installed. And once it takes more than 15 minutes, it's pretty much the same difference if it's two or six or ten hours... I'm not going to compile it again until I'm forced to. I ran 2.6.15 from 2006 until last October! --mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Recent breakage of DVB subtitles with dxr3
On Sun, Apr 01, 2012 at 02:15:39PM +0300, Mika Iisakkila wrote: > 1.4.2012 13:04, Pasi Kärkkäinen kirjoitti: >> Yep, it was from Fedora. You could always check the Fedora src.rpm >> for any extra patches they might have there.. >> >>> I'll gladly receive a current, relevant reference that will tell >>> me how to use the em8300 drivers on current Ubuntu without >>> recompiling the kernel. It takes 18(!) hours of CPU time on my >>> VDR box. >>> >> >> I think your best bet is to post to dxr3-de...@lists.sourceforge.net >> mailinglist, I think all (most) the em8300 developers are there.. > > Well, I googled a bit more, and it seems the actual problem is > in dxr3-plugin, not the drivers. The plugin is only able to > use OSS (as of Dec.2008, anyway). I'm not willing to waste time > fighting with semi-functional compatibility layers, so I'll just > keep using my own kernel. Next time I'll configure out all the > unneeded junk before compiling, though :D > I'm pretty sure there is drx3-plugin version with ALSA support aswell! -- Pasi ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Recent breakage of DVB subtitles with dxr3
On Sun, Apr 01, 2012 at 07:50:07PM +0300, Pasi Kärkkäinen wrote: > On Sun, Apr 01, 2012 at 02:15:39PM +0300, Mika Iisakkila wrote: > > 1.4.2012 13:04, Pasi Kärkkäinen kirjoitti: > >> Yep, it was from Fedora. You could always check the Fedora src.rpm > >> for any extra patches they might have there.. > >> > >>> I'll gladly receive a current, relevant reference that will tell > >>> me how to use the em8300 drivers on current Ubuntu without > >>> recompiling the kernel. It takes 18(!) hours of CPU time on my > >>> VDR box. > >>> > >> > >> I think your best bet is to post to dxr3-de...@lists.sourceforge.net > >> mailinglist, I think all (most) the em8300 developers are there.. > > > > Well, I googled a bit more, and it seems the actual problem is > > in dxr3-plugin, not the drivers. The plugin is only able to > > use OSS (as of Dec.2008, anyway). I'm not willing to waste time > > fighting with semi-functional compatibility layers, so I'll just > > keep using my own kernel. Next time I'll configure out all the > > unneeded junk before compiling, though :D > > > > I'm pretty sure there is drx3-plugin version with ALSA support aswell! > Yep, see dxr3plugin-users mailinglist archives for more information: "[Dxr3plugin-users] [PATCH] Switch to the ALSA audio interface": http://sourceforge.net/mailarchive/message.php?msg_id=21665465 -- Pasi ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
