Re: [vdr] Request for rotor integration to vdr
On Wed, Jun 23, 2010 at 2:04 PM, Timothy D. Lenz wrote: > The rotor plugin doesn't seem to be maintained anymore and was always > somewhat of a hack to vdr. Seems to me rotor control should really be a part > of vdr diseqc control code. Just about every sat box out there includes > rotor control function. I've seen numerous people make the same request and although I don't use a rotor myself, I do agree support for it should be included in vanilla VDR as it's a basic common function & equipment. I'll guess that if enough people reply to this thread that Klaus may add it to his TODO list (assuming it isn't there already). > I would also like to see it be able to handle a rotor per card. Not much > point in having several sat tuners if they all have to look at the same sat. I'm sure if Klaus decides to implement this, he'll do it in such a way that makes the most sense & flexibile usability to maximize the benefit of adding it. No point in adding more functionality if you leave it crippled. :) Cheers ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Request for rotor integration to vdr
The rotor plugin doesn't seem to be maintained anymore and was always somewhat of a hack to vdr. Seems to me rotor control should really be a part of vdr diseqc control code. Just about every sat box out there includes rotor control function. I also looked at the Actuator plugin because I am interested in getting something going with c-band and thought maybe it included rotor commands. Don't it does, doesn't look like it's been updated since vdr-1.6.0, and requires a custom kernel module. I don't mind building custom electronics and was planing to anyway. But I don't want to have to hack code into the kernel. I think they have boxes that provide actuator control from rotor diseqc commands anyway which brings us back to including it. I would also like to see it be able to handle a rotor per card. Not much point in having several sat tuners if they all have to look at the same sat. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Xine plugins and LATM AAC audio (was Re: vdr 1.7.15 & eHD & French HD DTV)
On Wed, 23 Jun 2010, Luis Fernandes wrote: and yes Femon 1.7.7 does not detect this audio codec, this one must be I've added a preliminary LATM parser to femon-1.7.8 that will be hopefully released tonight. BR, -- rofa ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Xine plugins and LATM AAC audio (was Re: vdr 1.7.15 & eHD & French HD DTV)
2010/6/23 Jonas Bardino : > Bjørnar Nilsen wrote: >> Den 22.06.2010 07:21, skrev ECLiPSE: >>> I know that is not directly related to vdr, as my problem should come >>> from the reel src and not vdr. >>> I know there is here a good community of developpers and perhaps >>> someone can look at the src of the hdplayer and see if it could be >>> possible to add the detection of e-ac3 audio format , (and perhaps >>> finding the way to decode it or at least enable the ac3 compatibility?). >> >> I have this problem on norwegian terrestrial channels, getting no audio. >> I have just upgraded to vdr-1.7.15(yavdr 0.2.0). Im using xineliboutput. >> Have used this ppa https://launchpad.net/~yavdr/+archive/unstable-vdr . >> >> Here are the stats: >> -Audio through xineliboutput doesnt work >> -Audio through streamdev to vlc(windows 7) works. >> -Recording plays fine in vlc(windows 7), but not wiht xineliboutput. >> -Femon 1.7.7 does not detect this audio codec. >> >> I have made a recording, here is a sample http://www.nilux.com/2.ts . >> >> Dunno if its xineliboutput or vdr. >> >> Regards >> Bjørnar Nilsen > > Hi Bjørnar > > (I changed the subject as I do not think it is directly related to the > original issue). > > I'm no expert when it comes to the audio formats, but I have the same > experience here in Denmark. AFAICT the problem is missing LATM AAC[1] > decoding support in xine/ffmpeg/libfaad itself. > Neither xineliboutput or xine plugins provide audio for our MPEG4 > channels, but I can connect mplayer or vlc to xineliboutput on port > 37890 and get audio, so the core VDR components are not to blame. My > ffmpeg says something about missing LATM support when playing your > recording and my own: > $ ffmpeg -i 2.ts > FFmpeg version SVN-r23019-4:0.6~svn20100505-2yavdr1, Copyright (c) > 2000-2010 the FFmpeg developers > built on Jun 14 2010 12:58:34 with gcc 4.4.3 > configuration: --extra-version='4:0.6~svn20100505-2yavdr1' > --prefix=/usr --enable-avfilter --enable-avfilter-lavf --enable-vdpau > --enable-bzlib --enable-libgsm --enable-libschroedinger > --enable-libspeex --enable-libtheora --enable-libvorbis > --enable-pthreads --enable-zlib --disable-stripping > --enable-runtime-cpudetect --enable-gpl --enable-postproc > --enable-x11grab --enable-libdc1394 --enable-shared --disable-static > libavutil 50.15. 0 / 50.15. 0 > libavcodec 52.66. 0 / 52.66. 0 > libavformat 52.62. 0 / 52.62. 0 > libavdevice 52. 2. 0 / 52. 2. 0 > libavfilter 1.19. 0 / 1.19. 0 > libswscale 0.10. 0 / 0.10. 0 > libpostproc 51. 2. 0 / 51. 2. 0 > [mpegts @ 0x14a7420]AAC LATM not currently supported, patch welcome > [h264 @ 0x14abae0]number of reference frames exceeds max (probably > corrupt input), discarding one > Last message repeated 361 times > [mpegts @ 0x14a7420]max_analyze_duration reached > Input #0, mpegts, from '2.ts': > Duration: 00:00:22.22, start: 14142.519600, bitrate: 7256 kb/s > Program 132 > Stream #0.0[0x200]: Video: h264, yuv420p, 1280x720 [PAR 1:1 DAR > 16:9], 50 fps, 50 tbr, 90k tbn, 100 tbc > Stream #0.1[0x280](nor): Data: 0x0011 > Stream #0.2[0x258](nor): Subtitle: dvbsub > Stream #0.3[0x259](nor): Subtitle: dvbsub > Stream #0.4[0x240]: Data: 0x0006 > > If you run xine --verbose=2 on the recording or on the xineliboutput > stream you will similarly see libfaad errors from the failed audio decoding. > > I have experimented with a Personal Package Archive at Launchpad[2] to > do some further testing but my conclusion so far is that no combination > of recent ffmpeg and xine versions support LATM. Other players like vlc, > xbmc, mythtv and mplayer apparently include their own LATM > parser/decoder before handing of the decoding of the raw AAC stream to > libfaad. > > I also commented on the issue at the VDR portal[3], but with no solution > so far. > I anyone knows more about this issue I'm all ears! > > Cheers, Jonas > > [1] http://wiki.multimedia.cx/index.php?title=Understanding_AAC > [2] https://launchpad.net/~jonas-bardino > [3] http://www.vdr-portal.de/board/thread.php?postid=912115 > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > hello, try to do as I did with svn xine-lib 1.2 read this http://hg.debian.org/hg/xine-lib/xine-lib-1.2-vdpau/file/57d31b4ca5e0/contrib/README.contrib and compile xine-lib with new sources of libfaad2 on contrib folder http://www.audiocoding.com/faad2.html download from this site is working with me to Portugal. only on vdr-xineliboutput. and yes Femon 1.7.7 does not detect this audio codec, this one must be update like vdr-xine hope that helps, best regards. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] rotor screen missing stuff
The plugin has been downgraded. There are people who use a patched and patched 0.1.4 rather than the official 0.1.5 The situation with the rotor plugin is so bad (so much patching needed to get it to work and then I found it makes vdr unstable) I've resorted to having two parallel installations of vdr one I use just for the rotor plugin when I need to use it to align the dish and store the positions. In my 'normal' vdr installation I don't use the rotor plugin but rather diseq commands 'Go to position X' Here is my diseqc.conf if it helps you: S19.2E 11700 V 9750 t v W15 [E0 31 6B 13] W25 [E0 31 6B 13] W15 t S19.2E 9 V 10600 t v W15 [E0 31 6B 13] W25 [E0 31 6B 13] W15 T S19.2E 11700 H 9750 t V W15 [E0 31 6B 13] W25 [E0 31 6B 13] W15 t S19.2E 9 H 10600 t V W15 [E0 31 6B 13] W25 [E0 31 6B 13] W15 T S13.0E 11700 V 9750 t v W15 [E0 31 6B 0D] W25 [E0 31 6B 0D] W15 t S13.0E 9 V 10600 t v W15 [E0 31 6B 0D] W25 [E0 31 6B 0D] W15 T S13.0E 11700 H 9750 t V W15 [E0 31 6B 0D] W25 [E0 31 6B 0D] W15 t S13.0E 9 H 10600 t V W15 [E0 31 6B 0D] W25 [E0 31 6B 0D] W15 T S28.2E 11700 V 9750 t v W15 [E0 31 6B 1C] W25 [E0 31 6B 1C] W15 t S28.2E 9 V 10600 t v W15 [E0 31 6B 1C] W25 [E0 31 6B 1C] W15 T S28.2E 11700 H 9750 t V W15 [E0 31 6B 1C] W25 [E0 31 6B 1C] W15 t S28.2E 9 H 10600 t V W15 [E0 31 6B 1C] W25 [E0 31 6B 1C] W15 T S28.5E 11700 V 9750 t v W15 [E0 31 6B 1D] W25 [E0 31 6B 1D] W15 t S28.5E 9 V 10600 t v W15 [E0 31 6B 1D] W25 [E0 31 6B 1D] W15 T S28.5E 11700 H 9750 t V W15 [E0 31 6B 1D] W25 [E0 31 6B 1D] W15 t S28.5E 9 H 10600 t V W15 [E0 31 6B 1D] W25 [E0 31 6B 1D] W15 T I guess it comes down to the hard truth that there is no vdr 1.7.x user with C programming skills using a rotor who needs something more than USALS 1.2 Message: 5 Date: Tue, 22 Jun 2010 19:12:16 -0700 From: "Timothy D. Lenz" Subject: [vdr] rotor screen missing stuff To: vdr@linuxtv.org Message-ID: <4c216d80.2090...@vorgon.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed I am trying to get my rotor working again. I had been using v0.1.4 with vdr-1.6.0. Now I'm trying to get v.0.1.5 working with vdr-1.7.15. On the rotor page, Postion information no longer shows the sat it matches to, the option to do a scan on the current TP is gone, and the lock and other indicators are gone. Was that all part of the text2skin plugin which I'm not using now? or has the plugin been down graded? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Xine plugins and LATM AAC audio (was Re: vdr 1.7.15 & eHD & French HD DTV)
Bjørnar Nilsen wrote: > Den 22.06.2010 07:21, skrev ECLiPSE: >> I know that is not directly related to vdr, as my problem should come >> from the reel src and not vdr. >> I know there is here a good community of developpers and perhaps >> someone can look at the src of the hdplayer and see if it could be >> possible to add the detection of e-ac3 audio format , (and perhaps >> finding the way to decode it or at least enable the ac3 compatibility?). > > I have this problem on norwegian terrestrial channels, getting no audio. > I have just upgraded to vdr-1.7.15(yavdr 0.2.0). Im using xineliboutput. > Have used this ppa https://launchpad.net/~yavdr/+archive/unstable-vdr . > > Here are the stats: > -Audio through xineliboutput doesnt work > -Audio through streamdev to vlc(windows 7) works. > -Recording plays fine in vlc(windows 7), but not wiht xineliboutput. > -Femon 1.7.7 does not detect this audio codec. > > I have made a recording, here is a sample http://www.nilux.com/2.ts . > > Dunno if its xineliboutput or vdr. > > Regards > Bjørnar Nilsen Hi Bjørnar (I changed the subject as I do not think it is directly related to the original issue). I'm no expert when it comes to the audio formats, but I have the same experience here in Denmark. AFAICT the problem is missing LATM AAC[1] decoding support in xine/ffmpeg/libfaad itself. Neither xineliboutput or xine plugins provide audio for our MPEG4 channels, but I can connect mplayer or vlc to xineliboutput on port 37890 and get audio, so the core VDR components are not to blame. My ffmpeg says something about missing LATM support when playing your recording and my own: $ ffmpeg -i 2.ts FFmpeg version SVN-r23019-4:0.6~svn20100505-2yavdr1, Copyright (c) 2000-2010 the FFmpeg developers built on Jun 14 2010 12:58:34 with gcc 4.4.3 configuration: --extra-version='4:0.6~svn20100505-2yavdr1' --prefix=/usr --enable-avfilter --enable-avfilter-lavf --enable-vdpau --enable-bzlib --enable-libgsm --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-libvorbis --enable-pthreads --enable-zlib --disable-stripping --enable-runtime-cpudetect --enable-gpl --enable-postproc --enable-x11grab --enable-libdc1394 --enable-shared --disable-static libavutil 50.15. 0 / 50.15. 0 libavcodec52.66. 0 / 52.66. 0 libavformat 52.62. 0 / 52.62. 0 libavdevice 52. 2. 0 / 52. 2. 0 libavfilter1.19. 0 / 1.19. 0 libswscale 0.10. 0 / 0.10. 0 libpostproc 51. 2. 0 / 51. 2. 0 [mpegts @ 0x14a7420]AAC LATM not currently supported, patch welcome [h264 @ 0x14abae0]number of reference frames exceeds max (probably corrupt input), discarding one Last message repeated 361 times [mpegts @ 0x14a7420]max_analyze_duration reached Input #0, mpegts, from '2.ts': Duration: 00:00:22.22, start: 14142.519600, bitrate: 7256 kb/s Program 132 Stream #0.0[0x200]: Video: h264, yuv420p, 1280x720 [PAR 1:1 DAR 16:9], 50 fps, 50 tbr, 90k tbn, 100 tbc Stream #0.1[0x280](nor): Data: 0x0011 Stream #0.2[0x258](nor): Subtitle: dvbsub Stream #0.3[0x259](nor): Subtitle: dvbsub Stream #0.4[0x240]: Data: 0x0006 If you run xine --verbose=2 on the recording or on the xineliboutput stream you will similarly see libfaad errors from the failed audio decoding. I have experimented with a Personal Package Archive at Launchpad[2] to do some further testing but my conclusion so far is that no combination of recent ffmpeg and xine versions support LATM. Other players like vlc, xbmc, mythtv and mplayer apparently include their own LATM parser/decoder before handing of the decoding of the raw AAC stream to libfaad. I also commented on the issue at the VDR portal[3], but with no solution so far. I anyone knows more about this issue I'm all ears! Cheers, Jonas [1] http://wiki.multimedia.cx/index.php?title=Understanding_AAC [2] https://launchpad.net/~jonas-bardino [3] http://www.vdr-portal.de/board/thread.php?postid=912115 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.7.15 & eHD & French HD DTV
2010/6/22 Bjørnar Nilsen : > Den 22.06.2010 07:21, skrev ECLiPSE: >> >> I know that is not directly related to vdr, as my problem should come from >> the reel src and not vdr. >> I know there is here a good community of developpers and perhaps someone >> can look at the src of the hdplayer and see if it could be possible to add >> the detection of e-ac3 audio format , (and perhaps finding the way to decode >> it or at least enable the ac3 compatibility?). > > I have this problem on norwegian terrestrial channels, getting no audio. I > have just upgraded to vdr-1.7.15(yavdr 0.2.0). Im using xineliboutput. Have > used this ppa https://launchpad.net/~yavdr/+archive/unstable-vdr . > > Here are the stats: > -Audio through xineliboutput doesnt work > -Audio through streamdev to vlc(windows 7) works. > -Recording plays fine in vlc(windows 7), but not wiht xineliboutput. > -Femon 1.7.7 does not detect this audio codec. > > I have made a recording, here is a sample http://www.nilux.com/2.ts . > > Dunno if its xineliboutput or vdr. > This is a xine problem, and not a vdr problem. Linux mplayer plays that stream's audio so the audio is OK. The latest development version of xine might work better. Kind Regards James ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
