[vdr] "noepg" plugin and vdr-2.4.1
Hello, I have an issue with noepg under vdr-2.4.1 (modifying channel yes/no is not stored). Do you know where I could find the last version for vdr-2.4.1, or a patch ? Thanks a lot. Karim ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr-2.4.1 and vaapi => issues audio and video
Hello, I continue to buid my new vdrbox : Mint 19.3 / Desktop Cinnamon 3840x2160 @ 60 Hz / intel gpu / vaapi plugin / vdr-2.4.1 Driver seems to be OK : vainfo libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_1 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.1 (libva 2.1.0) vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.1.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Simple : VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : VAEntrypointEncSliceLP VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileVP8Version0_3 : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain10 : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointEncSlice VAProfileVP9Profile0 : VAEntrypointVLD VAProfileVP9Profile0 : VAEntrypointEncSlice VAProfileVP9Profile2 : VAEntrypointVLD Running mpv from a terminal is OK : mpv -vo=vaapi --hwdec=vaapi /DATA/file1080p.mkv Playing: /DATA/file1080p.mkv (+) Video --vid=1 (*) (h264 1920x800 24.000fps) (+) Audio --aid=1 --alang=fre (*) (dts 6ch 48000Hz) (+) Subs --sid=1 --slang=fre (*) 'Forced' (subrip) AO: [pulse] 48000Hz 5.1(side) 6ch float Using hardware decoding (vaapi). VO: [vaapi] 1920x800 vaapi[nv12] AV: 00:00:09 / 01:27:44 (0%) A-V: 0.000 I have some issues with VDR and vaapi-plugin : - pictures are extremely slow on every channels (dvbt and dvbs) - no sound on dvbt (beause eac3 ?) , picture and sound out of sync on dvbs I found many errors in syslog (see below) , but I don't know what's wrong. Could you please help me to fix this isssue ? Thanks a lot. Karim syslog Jan 25 12:03:03 pctest vdr: [2546] VDR version 2.4.1 started Jan 25 12:03:03 pctest vdr: [2546] switched to user 'test' Jan 25 12:03:03 pctest vdr: [2546] codeset is 'UTF-8' - known Jan 25 12:03:03 pctest vdr: [2546] found 28 locales in /usr/local/src/vdr-2.4.1/locale Jan 25 12:03:03 pctest vdr: [2546] loading plugin: /usr/local/src/vdr/PLUGINS/lib/libvdr-femon.so.2.4.1 Jan 25 12:03:03 pctest vdr: [2546] loading plugin: /usr/local/src/vdr/PLUGINS/lib/libvdr-mpv.so.2.4.1 Jan 25 12:03:03 pctest vdr: [2546] loading plugin: /usr/local/src/vdr/PLUGINS/lib/libvdr-vaapidevice.so.2.4.1 Jan 25 12:03:03 pctest vdr: [2546] loading plugin: /usr/local/src/vdr/PLUGINS/lib/libvdr-skinsoppalusikka.so.2.4.1 Jan 25 12:03:03 pctest vdr: [2546] loading /DATA/configVDR/setup.conf ... Jan 25 12:03:05 pctest vdr: [2577] VAAPI-ERROR: video: display buffer empty, duping frame (1/0) 0 Jan 25 12:03:05 pctest vdr: [2577] VAAPI-ERROR: video: display buffer empty, duping frame (2/0) 0 Jan 25 12:03:05 pctest vdr: [2577] VAAPI-ERROR: video: display buffer empty, duping frame (3/0) 0 Jan 25 12:03:05 pctest vdr: [2577] VAAPI-ERROR: video: display buffer empty, duping frame (4/0) 0 Jan 25 12:03:05 pctest vdr: [2577] VAAPI-ERROR: video: display buffer empty, duping frame (5/0) 0 Jan 25 12:03:05 pctest vdr: [2577] VAAPI-ERROR: video: display buffer empty, duping frame (6/0) 0 Jan 25 12:03:05 pctest vdr: [2577] VAAPI-ERROR: video: display buffer empty, duping frame (7/0) 0 Jan 25 12:03:05 pctest vdr: [2577] VAAPI-ERROR: video: display buffer empty, duping frame (8/0) 0 Jan 25 12:03:05 pctest vdr: [2577] VAAPI
Re: [vdr] Need help for LIRC + remote on serial COM port on recent Linux distrib
Hi, Finally, I dropped Buster, and moved to Mint 19.3 Tricia. No problem with this version, lirc is working like a charm. Thanks for your support ! Karim Le 09/01/2020 à 22:59, Karim AFIFI a écrit : Hello, I finally managed to get working for the fist two steps : mode2 and irrecord are OK. There is only one problem left : lircd KO /sbin/lircd: symbol lookup error: /sbin/lircd: undefined symbol: release_map_remotes Could someone could help me to fix this problem ? Thanks a lot ! Karim Le 04/01/2020 à 23:02, Mikko Tuumanen a écrit : - lirc_serial move out of staging (is no longer part of the kernel) and/or rename to serial_ir. Here are my notes about those lirc changes from March 2019. You still need to release the serial port from normal serial driver: setserial /dev/ttyS0 uart none Load serial_ir module, no need for lirc_serial. serial_ir will create a /dev/lircN device, and also a /dev/input/eventM Load one of the ir_*_decoder modules too, for example ir_rc5_decoder or ir_rc6_decoder depending on the type of your remote. This way you'll probably don't need to teach remotes to lircd with irrecord, but can just read events from /dev/input/eventM Do a cat /sys/class/rc/rc*/protocols That will show you list(s) of supported remote models and you can change the model by writing your choice back to the protocols file. Before I knew all this, I tried to teach remote to lircd with irrecord, like irrecord -H default -d /dev/lircN This way I couldn't get irrecord to learn about a Technotrend remote I have. After I chose rc-5 with the protocols file, I started to get events from /dev/ input/eventM. This wasn't enough to get lircd to react to the events, so I had to teach them to lircd by running irrecord -H devinput -d /dev/input/eventM After that I ran lircd with lircd -e lirc -H devinput \ -d /dev/input/by-path/platform-serial_ir.0-event-ir \ /etc/lircd.conf And now lirc works again! Unfortunately I still couldn't figure out how I could use the Technotrend remote with built-in ir receiver of CT2-4400. There is a /dev/input/event- device for it, but no events come through. ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Need help for LIRC + remote on serial COM port on recent Linux distrib
Hello, I finally managed to get working for the fist two steps : mode2 and irrecord are OK. There is only one problem left : lircd KO /sbin/lircd: symbol lookup error: /sbin/lircd: undefined symbol: release_map_remotes Could someone could help me to fix this problem ? Thanks a lot ! Karim Le 04/01/2020 à 23:02, Mikko Tuumanen a écrit : - lirc_serial move out of staging (is no longer part of the kernel) and/or rename to serial_ir. Here are my notes about those lirc changes from March 2019. You still need to release the serial port from normal serial driver: setserial /dev/ttyS0 uart none Load serial_ir module, no need for lirc_serial. serial_ir will create a /dev/lircN device, and also a /dev/input/eventM Load one of the ir_*_decoder modules too, for example ir_rc5_decoder or ir_rc6_decoder depending on the type of your remote. This way you'll probably don't need to teach remotes to lircd with irrecord, but can just read events from /dev/input/eventM Do a cat /sys/class/rc/rc*/protocols That will show you list(s) of supported remote models and you can change the model by writing your choice back to the protocols file. Before I knew all this, I tried to teach remote to lircd with irrecord, like irrecord -H default -d /dev/lircN This way I couldn't get irrecord to learn about a Technotrend remote I have. After I chose rc-5 with the protocols file, I started to get events from /dev/ input/eventM. This wasn't enough to get lircd to react to the events, so I had to teach them to lircd by running irrecord -H devinput -d /dev/input/eventM After that I ran lircd with lircd -e lirc -H devinput \ -d /dev/input/by-path/platform-serial_ir.0-event-ir \ /etc/lircd.conf And now lirc works again! Unfortunately I still couldn't figure out how I could use the Technotrend remote with built-in ir receiver of CT2-4400. There is a /dev/input/event- device for it, but no events come through. ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Need help for LIRC + remote on serial COM port on recent Linux distrib
Thanks for helping ! Here is what I did following your advice : 1/ My lirc_options.conf : [lircd] driver = default device = /dev/lirc0 [modinit] code = /usr/bin/setserial /dev/ttyS0 uart none code1 = /usr/sbin/modprobe serial_ir 2/ Loading modules and check (my remote is an old Philips 8139, rc5): /sbin/modprobe ir_rc5_decoder /sbin/modprobe serial_ir lsmod | grep ir serial_ir 20480 0 ir_rc5_decoder 16384 0 ir_rc6_decoder 16384 0 irqbypass 16384 1 kvm rc_core 53248 9 budget_ci,ir_rc6_decoder,rc_rc6_mce,cx23885,ir_rc5_decoder,serial_ir,rc_tt_1500 cat /sys/class/rc/rc*/protocols rc-5 nec [rc-6] jvc sony rc-5-sz sanyo sharp mce_kbd xmp imon [lirc] ls /dev/lirc* -l crw-rw 1 root video 243, 0 janv. 5 10:14 /dev/lirc0 crw-rw 1 root video 243, 1 janv. 5 10:57 /dev/lirc1 3/ Modules are up, unfortunatelly, I can't run lircd : /etc/init.d/lircd start [] Starting lircd (via systemctl): lircd.serviceJob for lircd.service failed because the control process exited with error code. See "systemctl status lircd.service" and "journalctl -xe" for details. failed! 4/ journalctl -xe -- L'unité (unit) lircd.service a commencé à démarrer. janv. 05 10:57:11 pctest lircd[1997]: /usr/sbin/lircd: symbol lookup error: /usr/sbin/lircd: undefined symbol: release_map_remotes janv. 05 10:57:11 pctest systemd[1]: lircd.service: Main process exited, code=exited, status=127/n/a -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- An ExecStart= process belonging to unit lircd.service has exited. -- -- The process' exit code is 'exited' and its exit status is 127. janv. 05 10:57:11 pctest systemd[1]: lircd.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit lircd.service has entered the 'failed' state with result 'exit-code'. janv. 05 10:57:11 pctest systemd[1]: Failed to start Flexible IR remote input/output application support. -- Subject: L'unité (unit) lircd.service a échoué -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- L'unité (unit) lircd.service a échoué, avec le résultat failed. lines 2178-2274/2274 (END) 5/ I tried your command without succes : /usr/sbin/lircd -e lirc -H devinput -d /dev/input/by-path/platform-serial_ir.0-event-ir /etc/lircd.conf /usr/sbin/lircd: symbol lookup error: /usr/sbin/lircd: undefined symbol: release_map_remotes Did I missed something ? Regards. Karim My lircd.conf in /etc/lirc # Please make this file available to others # by sending it to # # this config file was automatically generated # using lirc-0.9.1-git(default) on Tue May 28 22:32:12 2013 # # contributed by # # brand: RT214 from VR8139 Philips # model no. of remote control: # devices being controlled by this remote: # begin remote name RT214 bits 13 flags RC5|CONST_LENGTH eps 30 aeps 100 one 960 816 zero 960 816 plead 997 gap 113915 toggle_bit_mask 0x800 begin codes KEY_PLAY 0x1175 KEY_PAUSE 0x1168 KEY_STOP 0x1176 KEY_RECORD 0x117D KEY_REWIND 0x116C KEY_FORWARD 0x116E KEY_MENU 0x0170 KEY_EXIT 0x0171 KEY_CHANNELUP 0x1160 KEY_CHANNELDOWN 0x1161 KEY_UP 0x1010 KEY_DOWN 0x1011 KEY_LEFT 0x116F KEY_RIGHT 0x116A KEY_OK 0x114A KEY_AUDIO 0x116B KEY_BACK 0x114B KEY_SUBTITLE 0x117C KEY_MACRO 0x1171 KEY_INFO 0x016F KEY_RED 0x016B KEY_GREEN 0x016C KEY_YELLOW 0x016D KEY_BLUE 0x016E KEY_EPG 0x014A KEY_DVD 0x016F KEY_F1 0x017A KEY_F2 0x116E KEY_F3 0x117A KEY_F4 0x017D KEY_F5 0x014A KEY_F6 0x114F KEY_0 0x1140 KEY_1 0x1141 KEY_2 0x1142 KEY_3 0x1143 KEY_4 0x1144 KEY_5 0x1145 KEY_6 0x1146 KEY_7 0x1147 KEY_8 0x1148 KEY_9 0x1149 end codes end remote
[vdr] Need help for LIRC + remote on serial COM port on recent Linux distrib
Hi all VDR users, I am upgrading my VDR box, using Debian Buster 10.2 (4.19 kernel). I've some difficulties for reinstalling LIRC [using remote on serial port] due to several changes : - new path / name of LIRC's configurations files. - lirc_serial move out of staging (is no longer part of the kernel) and/or rename to serial_ir. I am stuck :-( Could someone please explain to me how to install (ex. need to recompile kernel to add missing module ?) and/or point me to a howto on the Net ? Thanks ! Regards. Karim ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Index of /Developer/Patches/vdr-2.4
Perfect, thank you. Karim -Message d'origine- De : vdr [mailto:vdr-boun...@linuxtv.org] De la part de Klaus Schmidinger Envoyé : lundi 3 juin 2019 23:02 À : vdr@linuxtv.org Objet : Re: [vdr] Index of /Developer/Patches/vdr-2.4 On 03.06.19 21:18, Karim AFIFI wrote: > ... > Do you plan to provide soon a vdr-2.4.1 release with all of them ? Yes. There is one problem with the channel display on the Raspberry Pi that still needs to be solved, and after that I'm planning to release version 2.4.1. Klaus ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Index of /Developer/Patches/vdr-2.4
Hi Klaus, " This directory contains patches fixing bugs that have been detected after the official release of VDR version 2.4.0. Apply them to the original VDR source in alphabetical order. " I noticed many 2.4.0 patches. Do you plan to provide soon a vdr-2.4.1 release with all of them ? Thank you. Karim ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Questions about good hardware to view VDR 4K
Yes, PCI is on the way of extinction... But good news, I just found an ASUS "standard mb" which seems to be perfect : - DisplayPort (+ HDMI + DVI) - 2 x PCI - 4 x PCIE - 1 x COM port (I use a TSOPxx module for LIRC) https://www.asus.com/us/Motherboards/PRIME-H270-PRO/specifications/ If I buy it, I will test active DP > HDMI converter, and I will share the feedback here. Thanks again for your advices :-) Karim -Message d'origine- De : Frantisek Rysanek [mailto:frantisek.rysa...@post.cz] Envoyé : mercredi 8 mai 2019 23:41 À : VDR Mailing List Cc : Karim AFIFI Objet : Re: [vdr] Questions about good hardware to view VDR 4K Hello Karim, ...the parallel PCI slots really seem to have gone out of vogue... I work as a service techie for *industrial* PC's - a niche that is rather backward in its tastes :-) and if you take a look at e.g. the portfolio of Advantech, you may find ATX boards with LGA1151 with more than one PCI slot. But you definitely won't like the price tag. Other than that, the BIOS nowadays tends to be a pretty normal AMI APTIO, UEFI and legacy booting supported, but you won't find any overclocking features in the BIOS SETUP. Hmm... in the recent generation, only the AIMB-786 has two PCI slots, and that's full-size ATX. In the mATX format, if you go back to SkyLake/KabyLake, you may find a board with a single parallel PCI slot... Apparently the PCI slots are on their way to extinction, following the ISA slots :-) In the "industrial" segments you can find other formats that have parallel PCI, such as PICMG hardware or maybe an external expansion box, but I believe that's even further away from an HTPC budget and living-room aesthetics :-) Frank On 8 May 2019 at 22:39, Karim AFIFI wrote: > Dear Franck, > > Thanks a lot for all theses precisions ! I missed the 4k rate's difference > DP vs HDMI... > > For lowest consumption, I try to avoid external video card : the entry level > I found (fanless GT 1030 - 4K@60Hz HDMI 2.0) is about 30w !!! > > Active converter DP > HDMI 2.0 seems to be a good solution. Unfortunately, I > didn't found (yet) a motherboard with 2xPCI slots **AND** displayport or > HDMI 2.0. (I would like to avoid PCIE > PCI adapter). > > I will take a look to Atom CPU and Gemini Lake, but it seems there is no ATX > motherboards, only mini-ITX (not enough slots PCI/PCI-E for me). > > As you see, it's very complicated, I continue to search ... > > Best regards ! > Karim > > > > -Message d'origine- > De : Frantisek Rysanek [mailto:frantisek.rysa...@post.cz] > Envoyé : mercredi 8 mai 2019 21:21 > `A : VDR Mailing List > Cc : karim.af...@laposte.net > Objet : Re: [vdr] Questions about good hardware to view VDR 4K > > Dear Karim, > > thanks for raising that point... > > At first I thought that the i3 "T" edition was somehow limited in the > graphics output, to make people buy the i7 - but no, if I look at > some mainstream i7 CoffeeLake CPU, the set of outputs is the exact > same spec: the CPU can produce 4k at 24 Hz only on the HDMI output > (TMDS framing), but can produce 4k at 60 Hz in the DisplayPort > format. To me this is slightly funny, because the "universal digital > display" outputs can do either DP or TMDS on the same port (the > format is configurable in software). > > https://ark.intel.com/content/www/us/en/ark/products/129944/intel-core > -i3-8100t-processor-6m-cache-3-10-ghz.html > > https://ark.intel.com/content/www/us/en/ark/products/191792/intel-core > -i7-9700-processor-12m-cache-up-to-4-70-ghz.html > > Might be a "friendly stab in the back" to the HDMI Forum :-) > The DisplayPort is Intel's own standard. > > Note that there are DP 1.2 -> HDMI 2.0 active adapters that can do 4k > at 60 Hz. > > https://www.club-3d.com/en/detail/2366/displayportt-1.2-to-hdmit-2.0-uhd-act > ive-adapter/ > > You do need an active adapter, so that the PC GPU produces DP > framing, as only on DP it can reach 4k at 60 Hz. A passive DP-to-HDMI > adapter would be identical to the scenario where the HDMI connector > is onboard, driven by the IGP "directly" (through a level shifter) - > as in both cases, it is the IGP producing TMDS framing, and that's > where it is limited to 24 Hz... > > I've read a note that HDMI audio support might be a bit of a problem > in such a setup in Linux, i.e. DP output from the Intel IGP converted > to HDMI by an adapter... although I seem to recall that the report > was about "problem solved". > > I cannot advise you on discrete GPU's, or Nvidia vs. AMD. > If you're aiming for a low-power system, the Intel IGP might be your > best bet, as the lowest-power addon GPU's have a TDP of 30-40 Wa
Re: [vdr] Questions about good hardware to view VDR 4K
Dear Franck, Thanks a lot for all theses precisions ! I missed the 4k rate's difference DP vs HDMI... For lowest consumption, I try to avoid external video card : the entry level I found (fanless GT 1030 - 4K@60Hz HDMI 2.0) is about 30w !!! Active converter DP > HDMI 2.0 seems to be a good solution. Unfortunately, I didn't found (yet) a motherboard with 2xPCI slots **AND** displayport or HDMI 2.0. (I would like to avoid PCIE > PCI adapter). I will take a look to Atom CPU and Gemini Lake, but it seems there is no ATX motherboards, only mini-ITX (not enough slots PCI/PCI-E for me). As you see, it's very complicated, I continue to search ... Best regards ! Karim -Message d'origine- De : Frantisek Rysanek [mailto:frantisek.rysa...@post.cz] Envoyé : mercredi 8 mai 2019 21:21 À : VDR Mailing List Cc : karim.af...@laposte.net Objet : Re: [vdr] Questions about good hardware to view VDR 4K Dear Karim, thanks for raising that point... At first I thought that the i3 "T" edition was somehow limited in the graphics output, to make people buy the i7 - but no, if I look at some mainstream i7 CoffeeLake CPU, the set of outputs is the exact same spec: the CPU can produce 4k at 24 Hz only on the HDMI output (TMDS framing), but can produce 4k at 60 Hz in the DisplayPort format. To me this is slightly funny, because the "universal digital display" outputs can do either DP or TMDS on the same port (the format is configurable in software). https://ark.intel.com/content/www/us/en/ark/products/129944/intel-core -i3-8100t-processor-6m-cache-3-10-ghz.html https://ark.intel.com/content/www/us/en/ark/products/191792/intel-core -i7-9700-processor-12m-cache-up-to-4-70-ghz.html Might be a "friendly stab in the back" to the HDMI Forum :-) The DisplayPort is Intel's own standard. Note that there are DP 1.2 -> HDMI 2.0 active adapters that can do 4k at 60 Hz. https://www.club-3d.com/en/detail/2366/displayportt-1.2-to-hdmit-2.0-uhd-act ive-adapter/ You do need an active adapter, so that the PC GPU produces DP framing, as only on DP it can reach 4k at 60 Hz. A passive DP-to-HDMI adapter would be identical to the scenario where the HDMI connector is onboard, driven by the IGP "directly" (through a level shifter) - as in both cases, it is the IGP producing TMDS framing, and that's where it is limited to 24 Hz... I've read a note that HDMI audio support might be a bit of a problem in such a setup in Linux, i.e. DP output from the Intel IGP converted to HDMI by an adapter... although I seem to recall that the report was about "problem solved". I cannot advise you on discrete GPU's, or Nvidia vs. AMD. If you're aiming for a low-power system, the Intel IGP might be your best bet, as the lowest-power addon GPU's have a TDP of 30-40 Watt. As for CPU's, Ryzen is a very nice CPU, but low-power Ryzen is hard to find, especially if you're aiming for a passively cooled computer. You may also want to take a look at the Gemini Lake ATOM's (Pentia and Celerons): https://www.intel.com/content/dam/www/public/us/en/documents/product-b riefs/silver-celeron-datasheet-vol-1.pdf Available on some rare Mini-ITX motherboards. Note that their IGP can do 4k@60Hz on both DP and HDMI 2.0. And they can play back H.265 HEVC at 4k with hardware decoding in the GPU (IGP). Unfortunately I have no hands-on experience with VAAPI on this hardware. Theoretically it is supported. Allegedly it can decode source data with 10bit color depth (H.265 compressed video stream) but the DP/HDMI output is 8-bit only anyway :-) You might also want to take a look at the Apollo Lake ATOM = one generation older (I haven't checked the specs.) Frank > Am Mi., 8. Mai 2019 um 19:01 Uhr schrieb Karim AFIFI > : > Hi, > > I am looking for an ATX motherboard with PCI and PCIE slots, for > using with new VDR 4K (PCI S2-3200+CI and PCIE Hauppauge quad), and > ASTERISK (PCI Digium FXO/FXS card). > > At the beginning, I was thinking about an Intel 1151 socket (for best > vaapi support), like this one (*): > > https://www.asus.com/Motherboards/TUF-H310-PLUS-GAMING/HelpDesk_Manual > / > > Unfortunately, I noticed HDMI is v1.4, with 4k@24Hz only ! > > I am afraid that I need to add a PCI-E video card to achieve 4k@60Hz. > > Is it correct ? If so, I have two questions : > 1) could you advice about fanless + VAAPI compatible product ? > 2) any feedback about best plateform/chipset : AMD vs Intel ? > > Thanks a lot. > Karim > > > (*) using with low TDP quad core CPU, for example i3-8100T. ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Questions about good hardware to view VDR 4K
Hi, I am looking for an ATX motherboard with PCI and PCIE slots, for using with new VDR 4K (PCI S2-3200+CI and PCIE Hauppauge quad), and ASTERISK (PCI Digium FXO/FXS card). At the beginning, I was thinking about an Intel 1151 socket (for best vaapi support), like this one (*): https://www.asus.com/Motherboards/TUF-H310-PLUS-GAMING/HelpDesk_Manual/ Unfortunately, I noticed HDMI is v1.4, with 4k@24Hz only ! I am afraid that I need to add a PCI-E video card to achieve 4k@60Hz. Is it correct ? If so, I have two questions : 1) could you advice about fanless + VAAPI compatible product ? 2) any feedback about best plateform/chipset : AMD vs Intel ? Thanks a lot. Karim (*) using with low TDP quad core CPU, for example i3-8100T. ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Advice for best hardware and plugins to play MKV files and receive 4K channels
Hi, Thanks for sharing this. -Message d'origine- De : vdr [mailto:vdr-boun...@linuxtv.org] De la part de prelude Envoyé : mercredi 31 octobre 2018 13:46 À : VDR Mailing List Objet : Re: [vdr] Advice for best hardware and plugins to play MKV files and receive 4K channels Karim AFIFI kirjoitti 2018-10-30 01:16: > Could you share best hardware cpu/video/card,motherboard/..., & best > plugin/driver/... you advice at the moment? I do not know a best one but I faced same situation when my old good nvidia ion platform cannot handle hd channels properly. I tested different plugings with intel HD graphics (integrated in dell laptop via vaapi) but did not get any of those working as old systems. Facing problems with instability, splitted pictures, out of syck, and "jumping" fast forward modes (I look a lot of movies/series in 2-4 times speed up as in here we have subtitles). Shortly to say i did not manage to archive proper system with any of vdr plugins. Now im trying using VNSI & kodi in android tv and it still look promising. Just testing it currently inside on older laptop. Other great thing there is that i can move my server (including dvb sick) away from living room to garage and use only small and better looking device in living room. ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Advice for best hardware and plugins to play MKV files and receive 4K channels
Thanks a lot for the feedback ! -Message d'origine- De : vdr [mailto:vdr-boun...@linuxtv.org] De la part de VDR User Envoyé : mercredi 31 octobre 2018 00:03 À : mailing list: vdr Objet : Re: [vdr] Advice for best hardware and plugins to play MKV files and receive 4K channels > >xineliboutput and VDPAU so I assume what you actually mean by mkv is > >being able to play back HD or greater content using VDPAU for decoding > >and xineliboutput to get the decoded frames to your tv. > Correct, my 4K mkv files are using H.265 codecs, HD files are using H.264. Since dumping Nvidia I haven't kept up with what their current cards capabilities are so I can't advise on an Nvidia card that does HEVC/h265. My NUC handles it great though! ;) > I didn't understand which player/plugin you advise in VDR. > - MPlayer was very good but no longer works... > - Media Player in Xineliboutput is convenient but little buggy under VDPAU... I originally used mplayer, then mplayer2, and lastly mpv player. The vdr-mplayer plugin + mpv player has worked great. All you have to do to switch from mpv is just change your mplayer.sh (or whatever you call your player script) from using the mplayer bin to mpv bin. ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Advice for best hardware and plugins to play MKV files and receive 4K channels
-Message d'origine- De : vdr [mailto:vdr-boun...@linuxtv.org] De la part de VDR User Envoyé : mardi 30 octobre 2018 01:38 À : mailing list: vdr Objet : Re: [vdr] Advice for best hardware and plugins to play MKV files and receive 4K channels > I plan to upgrade my VDR box, with these two important features : > - reading mkv files => I am using xineliboutput and vdpau. >xineliboutput and VDPAU so I assume what you actually mean by mkv is >being able to play back HD or greater content using VDPAU for decoding >and xineliboutput to get the decoded frames to your tv. Correct, my 4K mkv files are using H.265 codecs, HD files are using H.264. >>VDPAU is EOL. Ok, I didn't know it. >>Nvidia currently has NVDEC but I can't speak to how well it's >> supported since I dumped VDPAU for VAAPI a while back. I just found informations here : https://wiki.archlinux.org/index.php/Hardware_video_acceleration > Could you share best hardware cpu/video/card,motherboard/..., & best > plugin/driver/... you advice at the moment? >When I switched from VDPAU to VAAPI I retired my old hardware and just >spent about $120 on an Intel NUC, and couldn't be happier. I'll never >bother with video cards again for htpc/media playing boxes. And also >non-usb tuners. Low power/low space is my theme now so my days of >building pc's for this purpose are over. You might want to look at >other options unless you actually want a pc tower. I am not looking for a very small pc case, because I have 3 x dvb PCIE cards and a Digium card (for Asterisk). I will probably keep my medium Silverstone aluminium case, and I will choose an ATX or mini ITX motherboard, depending power and efficiency. I didn't understand which player/plugin you advise in VDR. - MPlayer was very good but no longer works... - Media Player in Xineliboutput is convenient but little buggy under VDPAU... ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Advice for best hardware and plugins to play MKV files and receive 4K channels
Hello, I plan to upgrade my VDR box, with these two important features : - reading mkv files => I am using xineliboutput and vdpau. - receiving 4K channels => for HD, I am using old PCI/PCIE motherboard + TBS6928 (with CI). Could you share best hardware cpu/video/card,motherboard/..., & best plugin/driver/... you advice at the moment? Thanks for ther feedback. Karim ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR version 2.4.0 released
Hi Klaus, Many thanks for this new release, and all the job around it ! Regards. Karim -Message d'origine- De : vdr [mailto:vdr-boun...@linuxtv.org] De la part de Klaus Schmidinger Envoyé : dimanche 15 avril 2018 11:37 À : VDR mailing list Objet : [vdr] [ANNOUNCE] VDR version 2.4.0 released VDR version 2.4.0 is now available at ftp://ftp.tvdr.de/vdr/vdr-2.4.0.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-2.3.9-2.4.0.diff MD5 checksums: 12c6a3abeadfa915fcfe736bb047a3ab vdr-2.4.0.tar.bz2 6d98c2d619e82f3d4503146602fccde7 vdr-2.3.9-2.4.0.diff A summary of all the major changes since the last stable version 2.2.0 can be found at http://www.tvdr.de/changelog.htm When updating from an earlier version of VDR please make sure you read the INSTALL and MANUAL files that come with the VDR source _before_ doing so! Please make sure you have backup copies of all your configuration files, and verify carefully that your timers will be set to the correct channels after switching to this new version. Thanks to the many people who have contributed in the making, testing and debugging of this new version of VDR, and also to all users who just enjoy VDR! Please also visit the VDR homepage at http://www.tvdr.de and VDR's facebook page at https://www.facebook.com/VideoDiskRecorder Have fun! Klaus ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput '/usr/local/lib/vdr/' n'est pas un répertoire
Hi, I finally found the problem : I forgot to customize VDR's Make.config. I added LCLBLD=1 and modified the path, compilation is OK now. Thank's anyway Bruno ! Regards Karim -Message d'origine- De : vdr [mailto:vdr-boun...@linuxtv.org] De la part de g.bruno Envoyé : jeudi 28 décembre 2017 11:11 À : vdr@linuxtv.org Objet : Re: [vdr] xineliboutput '/usr/local/lib/vdr/' n'est pas un répertoire Hallo, I had the same problem some months ago. If I remember right, it was a question of permissions. Did you verify if you have all rights on the directory /usr/local/lib/vdr/ "read, write and execute -rwx-"? Regards GBruno Am 23.12.2017 um 22:53 schrieb Karim Afifi: > Hi ! > > I am trying to upgrade my VDR to 2.3.8, but I have a trouble... > > xine-lib 1.2.8 is installed, but xineliboutput doesn't compil. It seems to be > a "simple" directory problem, but I didn't find what's wrong. > > Could you please help me to fix this issue ? > > Thank you. > Regards. > > > ... > -fvisibility=hidden -shared -shared xineliboutput.o device.o > frontend.o osd.o config.o menu.o setup_menu.o menuitems.o > media_player.o equalizer.o frontend_local.o frontend_svr.o > tools/avahi.o tools/cxsocket.o tools/udp_pes_scheduler.o > tools/backgroundwriter.o tools/playlist.o tools/http.o > tools/vdrdiscovery.o tools/time_pts.o tools.o tools/metainfo_menu.o > logdefs.o tools/rle.o black_720x576.o nosignal_720x576.o > vdrlogo_720x576.o -lrt -L/lib64 -lcap -ldl -o > libvdr-xineliboutput.so.2.3.8 install libvdr-xineliboutput.so.2.3.8 > /usr/local/lib/vdr/ > install: la cible '/usr/local/lib/vdr/' n'est pas un répertoire: Aucun > fichier ou dossier de ce type > Makefile:341 : la recette pour la cible « > libvdr-xineliboutput.so.2.3.8 » a échouée > make[1]: *** [libvdr-xineliboutput.so.2.3.8] Erreur 1 > > *** failed plugins: xineliboutput > > Makefile:225 : la recette pour la cible « plugins » a échouée > make: *** [plugins] Erreur 1 > > > ___ > vdr mailing list > vdr@linuxtv.org > https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] xineliboutput '/usr/local/lib/vdr/' n'est pas un répertoire
Hi ! I am trying to upgrade my VDR to 2.3.8, but I have a trouble... xine-lib 1.2.8 is installed, but xineliboutput doesn't compil. It seems to be a "simple" directory problem, but I didn't find what's wrong. Could you please help me to fix this issue ? Thank you. Regards. ... -fvisibility=hidden -shared -shared xineliboutput.o device.o frontend.o osd.o config.o menu.o setup_menu.o menuitems.o media_player.o equalizer.o frontend_local.o frontend_svr.o tools/avahi.o tools/cxsocket.o tools/udp_pes_scheduler.o tools/backgroundwriter.o tools/playlist.o tools/http.o tools/vdrdiscovery.o tools/time_pts.o tools.o tools/metainfo_menu.o logdefs.o tools/rle.o black_720x576.o nosignal_720x576.o vdrlogo_720x576.o -lrt -L/lib64 -lcap -ldl -o libvdr-xineliboutput.so.2.3.8 install libvdr-xineliboutput.so.2.3.8 /usr/local/lib/vdr/ install: la cible '/usr/local/lib/vdr/' n'est pas un répertoire: Aucun fichier ou dossier de ce type Makefile:341 : la recette pour la cible « libvdr-xineliboutput.so.2.3.8 » a échouée make[1]: *** [libvdr-xineliboutput.so.2.3.8] Erreur 1 *** failed plugins: xineliboutput Makefile:225 : la recette pour la cible « plugins » a échouée make: *** [plugins] Erreur 1 ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 2.3.2
Hi Klaus, It's a good news to know that you will "come back on VDR" :-) Thank's a lot for this gift. Merry Christmas to you, and to all VDR users ! Best Regards. Karim -Message d'origine- De : vdr [mailto:vdr-boun...@linuxtv.org] De la part de Klaus Schmidinger Envoyé : samedi 24 décembre 2016 10:08 À : VDR mailing list Objet : [vdr] [ANNOUNCE] VDR developer version 2.3.2 Merry Christmas to all VDR users! It's been a very busy year for me, in which I was unable to spend as much time on VDR as I would have liked to. But now things are settled again and I managed to prepare a new developer version with the most important fixes and improvements. Please feel free to tell me if I missed something important - some things may well have slipped under my radar ;-). So here's my Christmas gift for you! VDR developer version 2.3.2 is now available at ftp://ftp.tvdr.de/vdr/Developer/vdr-2.3.2.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-2.3.1-2.3.2.diff MD5 checksums: 6dbb208ea3d59658a18912b49af175b3 vdr-2.3.2.tar.bz2 68a0ed9f01048026333939d30e0a6474 vdr-2.3.1-2.3.2.diff WARNING: This is a *developer* version. Even though *I* use it in my productive environment, I strongly recommend that you only use it under controlled conditions and for testing and debugging. The changes since version 2.3.1: - Fixed a crash when deleting a recording (reported by Oliver Endriss). - Fixed an overflow of PIDs in a receiver (thanks to Robert Hannebauer). - Updated the Italian OSD texts (thanks to Diego Pierotto). - Fixed initializing device specific parameters in cDvbTransponderParameters. - The function SetCurrentChannel(const cChannel *Channel) is now deprecated and may be removed in a future version. Use SetCurrentChannel(int ChannelNumber) instead. - The SVDRP command DELC now refuses to delete the very last channel in the list, to avoid ending up with an empty channel list. - The cRwLock class now allows nested read locks within a write lock from the same thread. This fixes possible crashes when moving or deleting channels in the menu or through SVDRP (as well as other operations that try to acquire a read lock within a write lock). - Fixed a crash when trying to delete a channel that is being used by a timer. - Fixed setting the current item and counter values in the Recordings menu after deleting the last recording in a subfolder. - Fixed a crash when deleting a recording that is currently being replayed. - Fixed a crash when moving a recording to a folder on a different volume. The cRecordingsHandler now performs its actual operations in a separate thread, thus avoiding locking problems and reducing the time between subsequent operations. - Added a note to the description of cFont::Size(), regarding possible differences between it and cFont::Height() (suggested to Thomas Reufer). - Made the cPlayer member functions FramesPerSecond, GetIndex and GetReplayMode 'const' (thanks to Thomas Reufer). - Fixed resuming replay at a given position, which was off by one frame (thanks to Thomas Reufer). - Improved handling frame numbers to have a smoother progress display during replay of recordings with B-frames (thanks to Thomas Reufer). - Fixed replaying recordings to their very end, if they don't end with an I-frame (thanks to Thomas Reufer). - Implemented a frame parser for H.265 (HEVC) recordings (thanks to Thomas Reufer). - Added cFont::Width(void) to get the default character width and allow stretched font drawing in high level OSDs (thanks to Thomas Reufer). - Fixed regenerating the index of audio recordings (thanks to Thomas Reufer). - Fixed building VDR with systemd >= 230 (thanks to Ville Skyttä). - Sorted sources.conf by continous azimuth (thanks to Lucian Muresan). - Added 'S58.5E Kazsat 3' to sources.conf (thanks to Aitugan Sarbassov). - Fixed truncated date/time strings in the skins on multi-byte UTF-8 systems (reported by Sergey Chernyavskiy). - Updated the Estonian OSD texts (thanks to Arthur Konovalov). - Added a 'const' version of cTimers::GetTimer() (thanks to Lars Hanisch). - Fixed a typo in the description of cTimers::GetTimersRead() (thanks to Lars Hanisch). - Fixed a possible buffer overflow in handling CA descriptors (suggested by Lars Hanisch). - Avoiding some duplicate code and unnecessary work in nit.c (thanks to Ville Skyttä). - Added support for the systemd watchdog (thanks to Marc Perrudin), - Added a short sleep to cTSBuffer::Action() to avoid high CPU usage (thanks to Sergey Chernyavskiy). Have fun! Klaus ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 2.3.2
Hi Klaus, It's a good news to know that you will "come back on VDR" :-) Thank's a lot for this gift. Merry Christmas to you, and to all VDR users ! Best Regards. Karim -Message d'origine- De : vdr [mailto:vdr-boun...@linuxtv.org] De la part de Klaus Schmidinger Envoyé : samedi 24 décembre 2016 10:08 À : VDR mailing list Objet : [vdr] [ANNOUNCE] VDR developer version 2.3.2 Merry Christmas to all VDR users! It's been a very busy year for me, in which I was unable to spend as much time on VDR as I would have liked to. But now things are settled again and I managed to prepare a new developer version with the most important fixes and improvements. Please feel free to tell me if I missed something important - some things may well have slipped under my radar ;-). So here's my Christmas gift for you! VDR developer version 2.3.2 is now available at ftp://ftp.tvdr.de/vdr/Developer/vdr-2.3.2.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-2.3.1-2.3.2.diff MD5 checksums: 6dbb208ea3d59658a18912b49af175b3 vdr-2.3.2.tar.bz2 68a0ed9f01048026333939d30e0a6474 vdr-2.3.1-2.3.2.diff WARNING: This is a *developer* version. Even though *I* use it in my productive environment, I strongly recommend that you only use it under controlled conditions and for testing and debugging. The changes since version 2.3.1: - Fixed a crash when deleting a recording (reported by Oliver Endriss). - Fixed an overflow of PIDs in a receiver (thanks to Robert Hannebauer). - Updated the Italian OSD texts (thanks to Diego Pierotto). - Fixed initializing device specific parameters in cDvbTransponderParameters. - The function SetCurrentChannel(const cChannel *Channel) is now deprecated and may be removed in a future version. Use SetCurrentChannel(int ChannelNumber) instead. - The SVDRP command DELC now refuses to delete the very last channel in the list, to avoid ending up with an empty channel list. - The cRwLock class now allows nested read locks within a write lock from the same thread. This fixes possible crashes when moving or deleting channels in the menu or through SVDRP (as well as other operations that try to acquire a read lock within a write lock). - Fixed a crash when trying to delete a channel that is being used by a timer. - Fixed setting the current item and counter values in the Recordings menu after deleting the last recording in a subfolder. - Fixed a crash when deleting a recording that is currently being replayed. - Fixed a crash when moving a recording to a folder on a different volume. The cRecordingsHandler now performs its actual operations in a separate thread, thus avoiding locking problems and reducing the time between subsequent operations. - Added a note to the description of cFont::Size(), regarding possible differences between it and cFont::Height() (suggested to Thomas Reufer). - Made the cPlayer member functions FramesPerSecond, GetIndex and GetReplayMode 'const' (thanks to Thomas Reufer). - Fixed resuming replay at a given position, which was off by one frame (thanks to Thomas Reufer). - Improved handling frame numbers to have a smoother progress display during replay of recordings with B-frames (thanks to Thomas Reufer). - Fixed replaying recordings to their very end, if they don't end with an I-frame (thanks to Thomas Reufer). - Implemented a frame parser for H.265 (HEVC) recordings (thanks to Thomas Reufer). - Added cFont::Width(void) to get the default character width and allow stretched font drawing in high level OSDs (thanks to Thomas Reufer). - Fixed regenerating the index of audio recordings (thanks to Thomas Reufer). - Fixed building VDR with systemd >= 230 (thanks to Ville Skyttä). - Sorted sources.conf by continous azimuth (thanks to Lucian Muresan). - Added 'S58.5E Kazsat 3' to sources.conf (thanks to Aitugan Sarbassov). - Fixed truncated date/time strings in the skins on multi-byte UTF-8 systems (reported by Sergey Chernyavskiy). - Updated the Estonian OSD texts (thanks to Arthur Konovalov). - Added a 'const' version of cTimers::GetTimer() (thanks to Lars Hanisch). - Fixed a typo in the description of cTimers::GetTimersRead() (thanks to Lars Hanisch). - Fixed a possible buffer overflow in handling CA descriptors (suggested by Lars Hanisch). - Avoiding some duplicate code and unnecessary work in nit.c (thanks to Ville Skyttä). - Added support for the systemd watchdog (thanks to Marc Perrudin), - Added a short sleep to cTSBuffer::Action() to avoid high CPU usage (thanks to Sergey Chernyavskiy). Have fun! Klaus ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] TBS driver breaks lirc_serial
Hi andreas, When I install TBS driver on my Debian, it breaks lirc_serial. It's a form of incompatibility ... Best regards. Karim -Message d'origine- De : vdr [mailto:vdr-boun...@linuxtv.org] De la part de Birgit & Andreas Böttger Envoyé : jeudi 26 mai 2016 23:09 À : VDR Mailing List Objet : Re: [vdr] TBS driver breaks lirc_serial Hi Karim, Karim schrieb am 26.05.2016 um 22:39: > I tried today with Jessie 8.4.0 x64, exactly same problem :-( I think > we tried all the ways. I opened a case at TBS support a few days ago. > They asked me to send them "lirc_serial.ko working" to check, it seems they > could integrate it in their driver. > If so, it should be great ! > > Many thanks for your help ! > Of course, if I have some good news from TBS, I will post here. You mean that the (current) TBS driver is incompatible to Debian? Maybe .. OK, let's check the TBS support :) Best regards Andreas Böttger ___ 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
Re: [vdr] TBS driver breaks lirc_serial
It's clear that TBS breaks lirc on Debian. It's a sort of incompatibility... Karim Le 26 mai 2016 23:08:37 GMT+02:00, "Birgit & Andreas Böttger" <fboett...@t-online.de> a écrit : >Hi Karim, > >Karim schrieb am 26.05.2016 um 22:39: >> I tried today with Jessie 8.4.0 x64, exactly same problem :-( >> I think we tried all the ways. I opened a case at TBS support a few >days ago. >> They asked me to send them "lirc_serial.ko working" to check, it >seems they could integrate it in their driver. >> If so, it should be great ! >> >> Many thanks for your help ! >> Of course, if I have some good news from TBS, I will post here. > >You mean that the (current) TBS driver is incompatible to Debian? >Maybe .. OK, let's check the TBS support :) > >Best regards >Andreas Böttger > >___ >vdr mailing list >vdr@linuxtv.org >http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -- Envoyé de mon téléphone Android avec K-9 Mail. Excusez la brièveté.___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] TBS driver breaks lirc_serial
Hi Andreas, You do not need journalctl, because your system is no systemd-system obviously. On my system there is no syslog or other logfile in directory /var/log :) ok... > This failed start should be visible in syslog... > > You've right. But curiously, I didnt find error : > > grep lirc /var/log/syslog > May 24 23:01:00 pctest lircd-0.9.0-pre1[4396]: lircd(default) ready, > using /var/run/lirc/lircd May 24 23:02:00 pctest > lircd-0.9.0-pre1[4396]: caught signal May 24 23:09:01 pctest > lircd-0.9.0-pre1[4414]: lircd(default) ready, using > /var/run/lirc/lircd May 24 23:09:09 pctest lircd-0.9.0-pre1[4414]: > caught signal May 24 23:35:51 pctest kernel: [ 4171.326315] > lirc_serial: Manually using active low receiver May 24 23:35:51 pctest > kernel: [ 4171.326409] lirc_serial lirc_serial.0: lirc_dev: driver > lirc_serial registered at minor = 2 > > grep lirc /var/log/user.log > nothing. Strange... Really ! Maybe it is a good idea to reinstall your Debian system to be sure, that all modules are clean. Than create a backup of the entire modules tree (/lib/modules/*) and install TBS stuff without deleting any directories. After that you are able to compare the mixed modules to the backup (diff -Nqr /lib/modules /your.backup) and find out, what you should delete before installing TBS. No mixed as I can see. Anyway I did many first install with clonezilla (I have an image of Debian fresh install without lirc, tbs, etc...). Same problem everytime => TBS problem. > In case I can't find/fix this, do you think it could be interesting to try > with a fresh install of Debian Jessie **8.4.0** which kernel 3.16 ? Debian and OpenSUSE are different. Logging is different, configuration is different, ... but both are linux :) Do you have an old system with running DVB and LIRC? If so, try to find the LIRC configuration... Unfortunately not ! I do not know Debian and which version is stable or not. But why not - "latest is greatest" :) I tried today with Jessie 8.4.0 x64, exactly same problem :-( I think we tried all the ways. I opened a case at TBS support a few days ago. They asked me to send them "lirc_serial.ko working" to check, it seems they could integrate it in their driver. If so, it should be great ! Best regards Andreas Böttger Many thanks for your help ! Of course, if I have somme good (news) from TBS, I will post here. Best regards. Karim ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] TBS driver breaks lirc_serial
Hi Andreas, > 2/ > I found a problem with lirc (I don't know if there is a relation with mode2 : > setserial /dev/ttyS0 uart none > /etc/init.d/lirc start > [ ok ] Loading LIRC modules:. > [FAIL] Starting remote control daemon(s) : LIRC : failed! > You mean lirc or lircd ? (I use lircd in my vdr) LIRC is a daemon (/usr/sbin/lircd on my system) and /etc/init.d/lirc is the script to start this daemon. If I restart LIRC I see the following in syslog (on my systemd system via journalctl -f): Unfortunately I don't have journalctl, and I didn't afford to install it on Debian Wheezy. Your line "[FAIL] Starting remote control..." means that LIRC has any problem. Please try to find any other entries in any logfiles that may be related with this problem. This failed start should be visible in syslog... You've right. But curiously, I didnt find error : grep lirc /var/log/syslog May 24 23:01:00 pctest lircd-0.9.0-pre1[4396]: lircd(default) ready, using /var/run/lirc/lircd May 24 23:02:00 pctest lircd-0.9.0-pre1[4396]: caught signal May 24 23:09:01 pctest lircd-0.9.0-pre1[4414]: lircd(default) ready, using /var/run/lirc/lircd May 24 23:09:09 pctest lircd-0.9.0-pre1[4414]: caught signal May 24 23:35:51 pctest kernel: [ 4171.326315] lirc_serial: Manually using active low receiver May 24 23:35:51 pctest kernel: [ 4171.326409] lirc_serial lirc_serial.0: lirc_dev: driver lirc_serial registered at minor = 2 grep lirc /var/log/user.log nothing. > 3/ > During workflow, theses commands returns "no file", I don't know if it's > normal : > mv /lib/modules/`uname -r`/kernel/drivers/media/* $SICDIR/media/ > mv /lib/modules/`uname -r`/kernel/drivers/staging/media/* > $SICDIR/staging/media/ On my system the package from TBS installs in different directories than the original modules are. This way I had a mixture of original modules and modules from TBS. After deleting the original "media" subdirs and reinstalling TBS stuff all was ok. But if it become necessary to restore the originals you need a backup... Maybe your system has a different directory structure? Yes, I think so. I see 2 path : /lib/modules/3.2.0-4-amd64/kernel/drivers/media/ /lib/modules/3.2.0-4-amd64/kernel/drivers/staging/media/ (I am afraid that if I restore media from backup it erase news modules from TBS).Theses points (path and need/or don't need to restore backup) are not very clear for me. > 4/ > I can't check this because "/etc/sysconfig" doesn't exist in my Debian 7.7.0. > Do you know the path for Debian ? > vdr:~ # grep '^[A-Z]' /etc/sysconfig/lirc LIRCD_DEV_PERMISSIONS="660" > LIRCD_DEV_OWNER="root:video" > LIRCD_DRIVER="default" > LIRCD_DEVICE="/dev/lirc0" > LIRC_MODULE="lirc_serial" > LIRCD_LISTENPORT= > LIRCD_CONNECT= vdr:~ # find /etc -name 'lirc*' /etc/lirc /etc/lirc/lircd.conf /etc/init.d/lirc /etc/sysconfig/lirc Try this on your system... Unfortunately I didn't find this file :-( > 5/ > /etc/lirc/hardware.conf > # /etc/lirc/hardware.conf > # > # Arguments which will be used when launching lircd LIRCD_ARGS="" > > #Don't start lircmd even if there seems to be a good config file > #START_LIRCMD=false > > #Don't start irexec, even if a good config file seems to exist. > #START_IREXEC=false > > #Try to load appropriate kernel modules LOAD_MODULES=true > > # Run "lircd --driver=help" for a list of supported drivers. > DRIVER="" > # If DEVICE is set to /dev/lirc and udev is in use /dev/lirc0 will be > # automatically used instead DEVICE="" > MODULES="lirc_serial" > > # Default configuration files for your hardware if any LIRCD_CONF="" > LIRCMD_CONF="" Your /etc/lirc/hardware.conf could be somewhat that /etc/sysconfig/lirc is on my system. Yes, that's why I did'nt find /etc/sysconfig. At this time, I think **the point** is to clarify is the configuration file : path, name and content. In case I can't find/fix this, do you think it could be interesting to try with a fresh install of Debian Jessie **8.4.0** which kernel 3.16 ? Thanks again for your support. Best regards. Karim ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] TBS driver breaks lirc_serial
ware.conf # /etc/lirc/hardware.conf # # Arguments which will be used when launching lircd LIRCD_ARGS="" #Don't start lircmd even if there seems to be a good config file #START_LIRCMD=false #Don't start irexec, even if a good config file seems to exist. #START_IREXEC=false #Try to load appropriate kernel modules LOAD_MODULES=true # Run "lircd --driver=help" for a list of supported drivers. DRIVER="" # If DEVICE is set to /dev/lirc and udev is in use /dev/lirc0 will be # automatically used instead DEVICE="" MODULES="lirc_serial" # Default configuration files for your hardware if any LIRCD_CONF="" LIRCMD_CONF="" Thanks ! Best regards. Karim ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] TBS driver breaks lirc_serial
Hi Andreas, Thanks a lot for the tip ! lirc_serial is now loading : dmesg [7.492111] lirc_serial: Manually using active low receiver [7.492378] lirc_serial lirc_serial.0: lirc_dev: driver lirc_serial registered at minor = 2 Unfortunately, remote doesn't work (tested with mode2). I noticed in ".config" file : # CONFIG_LIRC_SERIAL_TRANSMITTER is not set I changed to : CONFIG_LIRC_SERIAL_TRANSMITTER=y And I ran again the worflow, but it doesn't solve. Did I missed something ? Best regards Karim -Message d'origine- De : vdr [mailto:vdr-boun...@linuxtv.org] De la part de Birgit & Andreas Böttger Envoyé : jeudi 19 mai 2016 23:38 À : VDR Mailing List Objet : Re: [vdr] TBS driver breaks lirc_serial Hi Karim, Karim schrieb am 19.05.2016 um 22:36: > I have an issue with TBS drivers (even with last version from april 2016). > As soon as I install TBS Linux drivers and reboot, lirc_serial doesn't load > anymore. I use TBS drivers v160405 with OpenSuse 13.2 (kernel 3.16.7-35) but lirc from TBS driver package. My workflow to do this is: cd linux-tbs-drivers make distclean ./v4l/tbs-x86_64.sh make # but only some seconds to initialize build and generate v4l/.config vi v4l/.config # CONFIG_LIRC_STAGING=y and CONFIG_LIRC_SERIAL=m make # remove (with or without backup) original media SICDIR=/lib/modules/sic/`date +%Y-%m-%d_%H:%M`/`uname -r`/kernel/drivers/media/ mkdir -p $SICDIR/media $SICDIR/staging/media mv /lib/modules/`uname -r`/kernel/drivers/media/* $SICDIR/media/ mv /lib/modules/`uname -r`/kernel/drivers/staging/media/* $SICDIR/staging/media/ make install reboot Best regards. Andreas Böttger ___ 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] TBS driver breaks lirc_serial
Hi, I have an issue with TBS drivers (even with last version from april 2016). My remote is on serial COM1 and works fine, using Wheezy 7.7.0 x64 + lirc cvs from 2013. kernel : Linux 3.2.0-4-amd64 dmesg OK : [6.524401] lirc_serial: module is from the staging directory, the quality is unknown, you have been warned. [7.421128] lirc_serial: auto-detected active low receiver [7.421182] lirc_serial lirc_serial.0: lirc_dev: driver lirc_serial registered at minor = 0 As soon as I install TBS Linux drivers and reboot, lirc_serial doesn't load anymore. dmesg NOK : [7.650032] lirc_serial: module is from the staging directory, the quality is unknown, you have been warned. [7.650193] lirc_serial: disagrees about version of symbol lirc_register_driver [7.650197] lirc_serial: Unknown symbol lirc_register_driver (err -22) I need lirc_serial because I use Logitech Remote. Do you know how we could fix this issue ? Best regards. Karim -- modinfo lirc_serial filename: /lib/modules/3.2.0-4-amd64/kernel/drivers/staging/media/lirc/lirc_serial.ko license:GPL author: Ralph Metzler, Trent Piepho, Ben Pfaff, Christoph Bartelmus, Andrei Tanas description:Infra-red receiver driver for serial ports. depends:lirc_dev staging:Y intree: Y vermagic: 3.2.0-4-amd64 SMP mod_unload modversions parm: type:Hardware type (0 = home-brew, 1 = IRdeo, 2 = IRdeo Remote, 3 = AnimaX, 4 = IgorPlug, 5 = NSLU2 RX:CTS2/TX:GreenLED) (int) parm: io:I/O address base (0x3f8 or 0x2f8) (int) parm: iommap:physical base for memory mapped I/O (0 = no memory mapped io) (bool) parm: ioshift:shift I/O register offset (0 = no shift) (int) parm: irq:Interrupt (4 or 3) (int) parm: share_irq:Share interrupts (0 = off, 1 = on) (bool) parm: sense:Override autodetection of IR receiver circuit (0 = active high, 1 = active low ) (bool) parm: txsense:Sense of transmitter circuit (0 = active high, 1 = active low ) (bool) parm: softcarrier:Software carrier (0 = off, 1 = on, default on) (bool) parm: debug:Enable debugging messages (bool) -- modinfo lirc_dev filename: /lib/modules/3.2.0-4-amd64/kernel/drivers/media/rc/lirc_dev.ko license:GPL author: Artur Lipowski description:LIRC base driver module depends: intree: Y vermagic: 3.2.0-4-amd64 SMP mod_unload modversions parm: debug:Enable debugging messages (bool) -- RAS ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Looking for DVB-T and DVB-S2 CI tuners
Hi, I am using TBS PCI-E tuners (6922/6928/6280); hardware are OK, but drivers are very bad : they break my lirc_serial : [7.650032] lirc_serial: module is from the staging directory, the quality is unknown, you have been warned. [7.650193] lirc_serial: disagrees about version of symbol lirc_register_driver [7.650197] lirc_serial: Unknown symbol lirc_register_driver (err -22) So I am looking for tuners which are supported by vanilla Linux kernel, without patching or installing additional drivers : - For DVB-T : PCI, PCIE or USB, dual tuner **with high sensitivity**. - For DVB-S2 : PCI or PCIE, tuner with CI and another without, or a dual tuner with CI. I found a Digital Device "OctopusCI S2 PRO twin CI/DVBS2", but it seems that CI is buggy, and drivers are not in Linux kernel : http://www.digital-devices.eu/shop/en/professional-series/octopus-pcie-serie s/237/digital-devices-octopusci-s2-pro-twin-ci-and-twin-dvb-s2-tuner-forr-pc ie-slot Thanks for your advice. Regards. Karim ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] DVB-T2 device in France
I noticed than TBS680 is more sensitive than NOVA-T-500. I don't know if TBS6281 is even better, I don't have technical specifications. Regards. Thank you for your answers. Any information regarding the signal reception quality ? I was also pondering Digital Devices Octopus NET (rack version suits me) http://www.digital-devices.eu/shop/en/networktuner/sets-und-bundles/208/dd-octopus-net-rack-ct2-dvbip-networktuner This is expensive, but standalone with a webinterface, expandable (no kernel drivers on the VDR side, just the satip plugin which seems to be maintained). http://www.saunalahti.fi/~rahrenbe/vdr/satip/ DVB-T/T2 sensitivity is "-82.6 dBm at 16 - QAM & 3/4", which I can't compare to other cards (Nova-T-500 is only said to be "high sensitivity"). http://download.digital-devices.de/download/octopus_net/Handbuch-DD-ONet_V111eng.pdf Is Digital Devices worth the cost ? -- NH ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] DVB-T2 device in France
Hi, I use TBS6280 (dual tuner, pci-e) from Turbosight in dvb-t mode (no dvb-t2 signal here): good card, not expensive and great technical support. Newer model is TBS 6281 : http://www.linuxtv.org/wiki/index.php/TBS6281 I hope it helps. Regards. -Message d'origine- De : vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] De la part de Nicolas Huillard Envoyé : jeudi 17 septembre 2015 14:01 À : vdr@linuxtv.org Objet : [vdr] DVB-T2 device in France Hello all, My previous mail to this ML is apparently dated 2011 ;-) Everything was OK there since then... Except that my Hauppauge Nova-T-500 died recently, and my ancient PCI cards do not work in the 2013 server. I'm looking for advice for a new DVB-T2 device, which should : * have a good tuner, because some channels (transponders, ie. frequencies) are difficult to catch here ; the TV set (Panasonic) works perfectly well, and I've added an RF amplifier on the roof, so I guess the Nova-T-500 tuner was not good enough * have a PCI or preferably PCI-e bus, and dual tuner (I don't really like USB sticks, which tend to lead to a mess of cable) * be robustly supported with stock kernels in Debian (jessie and future), which does not seem to be a problem anymore... If there are some dual-tuner, DVB-T2 + S2 card out there which are well supported by VDR, that's OK too. I may prefer to add another DVB-S2 card later on though (there is no sat-dish on the roof yet). TIA ! -- NH ___ 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
Re: [vdr] [ANNOUNCE] VDR version 2.2.0 released - Celebrating 15 years of VDR!
@Klaus, Many thanks for all your job and this wonderful piece of software ! I use VDR since more than 10 years, I can't imagine using any commercial buggy machine :-) @All plugin's developpers, Thanks for adding features to VDR during all these years ! Regards. Karim -Message d'origine- De : vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] De la part de Klaus Schmidinger Envoyé : jeudi 19 février 2015 11:39 À : vdr@linuxtv.org Objet : [vdr] [ANNOUNCE] VDR version 2.2.0 released - Celebrating 15 years of VDR! VDR version 2.2.0 is now available at ftp://ftp.tvdr.de/vdr/vdr-2.2.0.tar.bz2 A 'diff' against the previous developer version is available at ftp://ftp.tvdr.de/vdr/vdr-2.1.10-2.2.0.diff MD5 checksums: 8853f64c0fc3d41ffd3b4bfc6f0a14b7 vdr-2.2.0.tar.bz2 2d75806f90a4f1c8b3e30d7568891dc6 vdr-2.1.10-2.2.0.diff A summary of all the major changes since the last stable version 2.0.0 can be found at http://www.tvdr.de/changelog.htm When updating from an earlier version of VDR please make sure you read the INSTALL and MANUAL files that come with the VDR source _before_ doing so! Please make sure you have backup copies of all your configuration files, and verify carefully that your timers will be set to the correct channels after switching to this new version. Thanks to the many people who have contributed in the making, testing and debugging of this new version of VDR, and also to all users who have been enjoying VDR over the past 15 years! Please also visit the VDR homepage at http://www.tvdr.de and VDR's facebook page at https://www.facebook.com/VideoDiskRecorder Have fun! Klaus ___ 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
Re: [vdr] MRE: TBS6285 slow onscreen menu
Hi, Sorry, I don't know. Karim -Message d'origine- De : vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] De la part de Mika Laitio Envoyé : jeudi 12 juin 2014 13:38 À : vdr@linuxtv.org Objet : Re: [vdr] MRE: TBS6285 slow onscreen menu At the beginning, drivers was buggy, and I could't use dvb-t *AND* dvb-s2 cards at the same time. I worked with TBS support during several weeks to fix the problem : they even sent to me USB card to check if problem was from PCI-E or from driver, etc...). At the end, they fixed their driver and all was OK. Technical support is really excellent ! Hi, do you know are the fixed drivers you have now been released somewhere or merged to upstream kernel? Mika ___ 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] MRE: TBS6285 slow onscreen menu
Hi Milos, I have 2 x VDR boxes using TBS6280, TBS6922 and TBS6928. - vdr-2.0.6 on Debian. - TBS drivers from 2013-09-01 - IR receiver not from TBS cards, but TSOP on com port with LIRC. At the beginning, drivers was buggy, and I could't use dvb-t *AND* dvb-s2 cards at the same time. I worked with TBS support during several weeks to fix the problem : they even sent to me USB card to check if problem was from PCI-E or from driver, etc...). At the end, they fixed their driver and all was OK. Technical support is really excellent ! The only restriction I have is from CAM, even if it's a dual : I can't register two channels at the same time, I don't know if limitation is from VDR or from CAM (I tried with Viaccess Secure from SMIT and NEOTION, same problem). You should contact TBS support, I am sure they could help you. =euro_supp...@tbsdtv.com Regards. Karim -Message d'origine- De : vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] De la part de Milos Kapoun Envoyé : mardi 10 juin 2014 17:17 À : VDR Mailing List Objet : Re: [vdr] TBS6285 slow onscreen menu I tested it with VLC, problem is definitely in the TBS drivers. Milos Dne 2014-06-10 11:09, Milos Kapoun napsal: Hi, I continued with investigation. I build new computer, there is only VDR and two TBS6285 cards. When I start VDR with one adapter CPU load rises to 2 and after 5 minutes drops to 0.03 . There is no streaming, no playing. In the syslog are not any bad messages. When I use all 8 adapters CPU load is between 4 and 12, never drops. There is no problem with signal quality. In the cannels.conf is only one multiplex. EPG scan take 2 seconds. How can I find what VDR doing with not used adapters? Maybe those adapters are not initialized and in the driver are bad defaults. Miloš CPU load debug, it is really strange. I tried to exclude IRQ storm, but it is difficult to confirm it. : # uname -a Linux streamer 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u2 x86_64 GNU/Linux TBS drivers tbs-linux-drivers_v140425.zip # top top - 21:24:54 up 8:51, 2 users, load average: 5.14, 3.02, 2.50 Tasks: 90 total, 1 running, 89 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.2 us, 0.7 sy, 0.0 ni, 98.3 id, 0.8 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 3931580 total, 250052 used, 3681528 free,16472 buffers KiB Swap: 9823740 total,0 used, 9823740 free, 110824 cached PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 9966 root 20 0 342m 28m 3332 S 2.3 0.7 0:05.46 vdr 4333 mika 20 0 71272 1820 1012 S 0.3 0.0 0:00.58 sshd 8290 root 20 0 000 S 0.3 0.0 0:00.34 kworker/0:1 # cat /proc/interrupts CPU0 CPU1 0: 41108 IO-APIC-edge timer 1: 0 2 IO-APIC-edge i8042 7: 1 0 IO-APIC-edge 8: 0 1 IO-APIC-edge rtc0 9: 0 0 IO-APIC-fasteoi acpi 12: 1 6 IO-APIC-edge i8042 14: 0 0 IO-APIC-edge pata_atiixp 15: 0 0 IO-APIC-edge pata_atiixp 16: 0 1 IO-APIC-fasteoi ohci_hcd:usb2 17: 0 2 IO-APIC-fasteoi ohci_hcd:usb3, ohci_hcd:usb5 18: 0 2 IO-APIC-fasteoi ohci_hcd:usb4, ohci_hcd:usb6 19: 0 0 IO-APIC-fasteoi ehci_hcd:usb1 22: 14 27576 IO-APIC-fasteoi ahci 43:183 391691 PCI-MSI-edge eth0 44:369 710371 PCI-MSI-edge SAA716x Core 45:251 566014 PCI-MSI-edge SAA716x Core NMI: 5 13 Non-maskable interrupts LOC: 396566 714959 Local timer interrupts SPU: 0 0 Spurious interrupts PMI: 5 13 Performance monitoring interrupts IWI: 0 0 IRQ work interrupts RES: 193929 146089 Rescheduling interrupts CAL:501262 Function call interrupts TLB: 3904 3155 TLB shootdowns TRM: 0 0 Thermal event interrupts THR: 0 0 Threshold APIC interrupts MCE: 0 0 Machine check exceptions MCP:108108 Machine check polls ERR: 1 MIS: 0 # vmstat procs ---memory-- ---swap-- -io -system-- cpu r b swpd free buff cache si sobibo in cs us sy id wa 0 0 0 3681288 16844 11083600 2 2 50 58 0 0 100 0 # iostat Linux 3.2.0-4-amd64 (streamer) 09/06/14_x86_64_(2 CPU) avg-cpu: %user %nice %system %iowait %steal %idle 0.080.030.150.050.00 99.70 Device:tpskB_read/skB_wrtn/skB_read kB_wrtn sda 0.31 2.05 3.21 66315
Re: [vdr] HD recording size
Hi, FYI, I noticed this behaviour here with vdr-2.0.6 and french HD channels. Karim Can you make a small sample (like a minute or so) of such a recording available? Klaus Of course. Please download sample from here : https://www.dropbox.com/sh/i9c732ukwl925md/AAC6J2H6RL6F5JIQNeouxPUIa I have tested this sample with both VDR 2.1.1 and 2.1.6, and in both cases 'vdr --genindex... creates an index file that is about twice the size of your file and thus appears to be correct. Was this sample taken from the very beginning of your recording or somewhere in the middle? Maybe the error is only caused by a specific sequence in the stream, which is not contained in the sample. If you can produce a sample where vdr's --genindex option generates a faulty index file, please let me know. Klaus I think that sample is from very beginning, what I am not totally sure. I will try to check again. Could you please tell me how I can detect a faulty index ? If you encounter a recording where the time shown in the progress display is not correct, the index is most likely wrong. In such a case please do as follows: - change into the *.rec directory of that recording - rename the file index to index.old (or whatever you like) - run the command vdr --genindex=`pwd` (`pwd` will be replaced by the name of the current directory) - do an ls -l index* and compare the size of the old and new index file. If they are the same, that means that --genindex produces the same index file as did the original recording, and thus I should be able to reproduce the problem here if you send me the first minute of that recording. Klaus It's clear, thank you. Karim ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] HD recording size
On 11.05.2014 15:13, Karim wrote: On 08.05.2014 23:14, Martin wrote: I'm having a small problem. Some HD recordings are 1/2 in time of the SD recording. Not every HD recording has this problem, but most of the time I record from RTL HD it has. Recording is completed but only the length is wrong. So when I play it back and jump in time, I must jump 60 sec to skip 120 sec etc. VDR 2.1.1 but had the same problem with other versions. Is the problem still present in version 2.1.6? Klaus Hi, FYI, I noticed this behaviour here with vdr-2.0.6 and french HD channels. Karim Can you make a small sample (like a minute or so) of such a recording available? Klaus Of course. Please download sample from here : https://www.dropbox.com/sh/i9c732ukwl925md/AAC6J2H6RL6F5JIQNeouxPUIa I have tested this sample with both VDR 2.1.1 and 2.1.6, and in both cases 'vdr --genindex... creates an index file that is about twice the size of your file and thus appears to be correct. Was this sample taken from the very beginning of your recording or somewhere in the middle? Maybe the error is only caused by a specific sequence in the stream, which is not contained in the sample. If you can produce a sample where vdr's --genindex option generates a faulty index file, please let me know. Klaus I think that sample is from very beginning, what I am not totally sure. I will try to check again. Could you please tell me how I can detect a faulty index ? Thank you. Karim ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] HD recording size
On 08.05.2014 23:14, Martin wrote: I'm having a small problem. Some HD recordings are 1/2 in time of the SD recording. Not every HD recording has this problem, but most of the time I record from RTL HD it has. Recording is completed but only the length is wrong. So when I play it back and jump in time, I must jump 60 sec to skip 120 sec etc. VDR 2.1.1 but had the same problem with other versions. Is the problem still present in version 2.1.6? Klaus Hi, FYI, I noticed this behaviour here with vdr-2.0.6 and french HD channels. Karim Can you make a small sample (like a minute or so) of such a recording available? Klaus Of course. Please download sample from here : https://www.dropbox.com/sh/i9c732ukwl925md/AAC6J2H6RL6F5JIQNeouxPUIa Regards. Karim ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] HD recording size
On 08.05.2014 23:14, Martin wrote: I'm having a small problem. Some HD recordings are 1/2 in time of the SD recording. Not every HD recording has this problem, but most of the time I record from RTL HD it has. Recording is completed but only the length is wrong. So when I play it back and jump in time, I must jump 60 sec to skip 120 sec etc. VDR 2.1.1 but had the same problem with other versions. Is the problem still present in version 2.1.6? Klaus Hi, FYI, I noticed this behaviour here with vdr-2.0.6 and french HD channels. Regards. Karim ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Issue with VDR-2.0.4 and IPTV-2.0.0 plugin
Hi, I've installed IPTV-2.0.0 on VDR-2.0.4 to view IP channels from my DSL provider. No problem on compilation and installation. Unfortunately, I've an issue : - when viewing channels via vdr = sound is OK but video freezes **every** seconds. - when viewing channels via vlc (outside vdr) = no problem. In vdr plugin menu, I tried to change buffer value and % prefill buffer without success. And filters are selected on NO. I can't determine if problem comes from vdr or from iptv-plugin. Did I missed something ? Is there any special patch to apply ? Could you please help me to fix this issue ? Regards. Karim ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-prefermenu and vdr 1.7.21
Hi, I tried to compil vdr-prefermenu-0.6.6 ant theses patches under vdr-2.0.3. Unfortunately, compilation failed. Is there any more recent patch, or could you help me to fix ? *** Plugin prefermenu: WARNING: plugin prefermenu is using an old Makefile! g++ -g -O3 -Wall -Werror=overloaded-virtual -Wno-parentheses -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -I/usr/include/linux/dvb -c -DPLUGIN_NAME_I18N='prefermenu' -D_GNU_SOURCE -I/usr/local/src/vdr-2.0.3/include prefermenu.c In file included from prefermenu.c:14:0: i18n.h:14:14: error: tI18nPhrase does not name a type prefermenu.c: In member function virtual bool cPluginPrefermenu::Start(): prefermenu.c:52:16: error: Phrases was not declared in this scope prefermenu.c:52:23: error: RegisterI18n was not declared in this scope make[1]: *** [prefermenu.o] Erreur 1 Thank you. Karim -Message d'origine- De : vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] De la part de Matti Lehtimäki Envoyé : mercredi 7 décembre 2011 17:01 À : vdr@linuxtv.org Objet : Re: [vdr] vdr-prefermenu and vdr 1.7.21 On 12/07/2011 01:01 PM, Arturo Martinez wrote: Is there a patch for vdr-prefermenu to work with vdr 1.7.21 ? If you prefer the small OSD of original prefermenu-plugin then there are 3 patches in debian unstable so it works also with new versions of vdr (I tested it with 1.7.22). The patches are attached. -- Matti Lehtimäki ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-prefermenu and vdr 1.7.21
Fixed. Thank you very much Matti ! -Message d'origine- De : vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] De la part de Matti Lehtimäki Envoyé : vendredi 27 septembre 2013 23:08 À : vdr@linuxtv.org Objet : Re: [vdr] vdr-prefermenu and vdr 1.7.21 Hi There is an additional patch for prefermenu plugin in debian unstable which should fix the problem your describe. The patch is attached. -Matti On 09/27/2013 09:54 PM, Karim wrote: Hi, I tried to compil vdr-prefermenu-0.6.6 ant theses patches under vdr-2.0.3. Unfortunately, compilation failed. Is there any more recent patch, or could you help me to fix ? *** Plugin prefermenu: WARNING: plugin prefermenu is using an old Makefile! g++ -g -O3 -Wall -Werror=overloaded-virtual -Wno-parentheses -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -I/usr/include/linux/dvb -c -DPLUGIN_NAME_I18N='prefermenu' -D_GNU_SOURCE -I/usr/local/src/vdr-2.0.3/include prefermenu.c In file included from prefermenu.c:14:0: i18n.h:14:14: error: tI18nPhrase does not name a type prefermenu.c: In member function virtual bool cPluginPrefermenu::Start(): prefermenu.c:52:16: error: Phrases was not declared in this scope prefermenu.c:52:23: error: RegisterI18n was not declared in this scope make[1]: *** [prefermenu.o] Erreur 1 Thank you. Karim -Message d'origine- De : vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] De la part de Matti Lehtimäki Envoyé : mercredi 7 décembre 2011 17:01 À : vdr@linuxtv.org Objet : Re: [vdr] vdr-prefermenu and vdr 1.7.21 On 12/07/2011 01:01 PM, Arturo Martinez wrote: Is there a patch for vdr-prefermenu to work with vdr 1.7.21 ? If you prefer the small OSD of original prefermenu-plugin then there are 3 patches in debian unstable so it works also with new versions of vdr (I tested it with 1.7.22). The patches are attached. -- Matti Lehtimäki ___ 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
Re: [vdr] Feature request for VDR = multi editing
OK ! I understood, sorry for the mismatch... Karim ... BTW: you should have started an all new thread for this, not reply to VDR needs some way to detect new tuners on runtime... and simply change the subject. Now these two threads are intertwinded... :-( Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Feature request for VDR = multi editing
Hi Klaus, I record many movies, shows and series with VDR = then I make a lot of editing. Unfortunately, VDR allows only one editing at a time. Is it possible to improve this feature ? I mean VDR could store all demands in a queue, and launch them one by one, until the last editing. This should improve greatly the usability of VDR ! Thank you ! Regards. Karim ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] noad : compilation issue
Hi, I can't compil noad on my vdrbox (Debian Wheezy x94). It could be a compatibility problem with new ffmpeg version, but I can't fix it :-( Here is the error logs : - NOAD - make -- make all-am make[1]: entrant dans le répertoire « /usr/local/src/noad-0.8.5 » CXX svdrpc.o svdrpc.cpp:21:19: warning: deprecated conversion from string constant to char* [-Wwrite-strings] AR libnoad.a CXX audiotools.o audiotools.cpp: In function void initAVCodec(): audiotools.cpp:105:39: error: avcodec_open was not declared in this scope audiotools.cpp:110:30: error: AVCODEC_MAX_AUDIO_FRAME_SIZE was not declared in this scope audiotools.cpp: In function int scan_audio_stream_0(unsigned char*, int): audiotools.cpp:166:16: error: AVCODEC_MAX_AUDIO_FRAME_SIZE was not declared in this scope audiotools.cpp:175:11: warning: int avcodec_decode_audio3(AVCodecContext*, int16_t*, int*, AVPacket*) is deprecated (declared at /usr/local/include/libavcodec/avcodec.h:3667) [-Wdeprecated-declarations] audiotools.cpp:176:39: warning: int avcodec_decode_audio3(AVCodecContext*, int16_t*, int*, AVPacket*) is deprecated (declared at /usr/local/include/libavcodec/avcodec.h:3667) [-Wdeprecated-declarations] make[1]: *** [audiotools.o] Erreur 1 make[1]: quittant le répertoire « /usr/local/src/noad-0.8.5 » make: *** [all] Erreur 2 -- NOAD - make install -- CXX audiotools.o audiotools.cpp: In function void initAVCodec(): audiotools.cpp:105:39: error: avcodec_open was not declared in this scope audiotools.cpp:110:30: error: AVCODEC_MAX_AUDIO_FRAME_SIZE was not declared in this scope audiotools.cpp: In function int scan_audio_stream_0(unsigned char*, int): audiotools.cpp:166:16: error: AVCODEC_MAX_AUDIO_FRAME_SIZE was not declared in this scope audiotools.cpp:175:11: warning: int avcodec_decode_audio3(AVCodecContext*, int16_t*, int*, AVPacket*) is deprecated (declared at /usr/local/include/libavcodec/avcodec.h:3667) [-Wdeprecated-declarations] audiotools.cpp:176:39: warning: int avcodec_decode_audio3(AVCodecContext*, int16_t*, int*, AVPacket*) is deprecated (declared at /usr/local/include/libavcodec/avcodec.h:3667) [-Wdeprecated-declarations] make: *** [audiotools.o] Erreur 1 -- Could you please help me to point on the problem ? Thanks a lot ! Regards. Karim ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] markad : compilation issue
Hi, I can't compil markad on my vdrbox (Debian Wheezy x94). It could be a compatibility problem with new ffmpeg version (lie my other post for noad), but I can't fix it :-( Here is the error log : *** Plugin markad: WARNING: plugin markad is using an old Makefile! for i in command plugin; do make -C $i; done g++ -g -O3 -Wall -Werror=overloaded-virtual -Wno-parentheses -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -I/usr/include/linux/dvb -c -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS -D__USE_XOPEN_EXTENDED -I/usr/local/include decoder.cpp decoder.cpp: In constructor cMarkAdDecoder::cMarkAdDecoder(bool, int): decoder.cpp:155:5: error: CodecID was not declared in this scope decoder.cpp:155:13: error: expected ; before video_codecid decoder.cpp:159:9: error: video_codecid was not declared in this scope decoder.cpp:163:9: error: video_codecid was not declared in this scope decoder.cpp:166:40: error: video_codecid was not declared in this scope decoder.cpp:176:47: error: avcodec_alloc_context was not declared in this scope decoder.cpp: In member function bool cMarkAdDecoder::Clear(): decoder.cpp:326:36: error: avcodec_alloc_context was not declared in this scope make[2]: *** [decoder.o] Erreur 1 make[2]: Rien à faire pour « all ». Could you please help me to point on the problem ? Thanks a lot ! Regards. Karim ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] HDMI 5.1 in VDR with Alsa : how ?
Hello, I am trying this connexion with vdr-2.0.1 + xineliboutput + nVidia 210 : VDR-hdmi-TV_with_internal_HP-Cinch_audio_num-ampli HC_external_HP With Debian Wheezy and alsa 0.1.25 : - PCM = OK on TV and on ampli HC speakers. - 5.1 = no sound in TV and ampli HC. Is there a special parameter I missed ? (Some hdmi passthrough like...) Any hint ? Greetings. Karim ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Xineliboutput doesn't compil under vdr-2.0.1
It works ! Thank you René for the tips... Regards. Karim -Message d'origine- De : vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] De la part de René Envoyé : lundi 6 mai 2013 16:50 À : VDR Mailing List Objet : Re: [vdr] Xineliboutput doesn't compil under vdr-2.0.1 I do the following in the vdr source-dir (vdr-2.0.1): make install-plugins With this my plugins end up in the plugin-dir. René On 04.05.2013 18:03 , Karim wrote: Hi Salim, I was looking for libvdr-xineliboutput.so.2.0.0.lib file, instead of libvdr-xineliboutput.so.2.0.0. After I copied it in vdr/PLUGINS/lib, problem solved. Thanks a lot ! Karim -Message d'origine- De : vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] De la part de Karim Envoyé : jeudi 2 mai 2013 19:24 À : 'VDR Mailing List' Objet : Re: [vdr] Xineliboutput doesn't compil under vdr-2.0.1 Hi Halim, I have double checked : there is no libvdr-xineliboutput.so.2.0.0 in vdr/PLUGINS/lib (or anywhere). I am afraid that compilation fails. Thanks Karim -Message d'origine- De : vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] De la part de Halim Sahin Envoyé : jeudi 2 mai 2013 05:39 À : vdr@linuxtv.org Objet : Re: [vdr] Xineliboutput doesn't compil under vdr-2.0.1 Hi, In the output you posted here are no error message (only warnings). The build was successfull but xineliboutput didn't copy the binaries to PLUGINS/lib because of the old Makefiles. You can do it yourself :-). cd PLUGINS/src/xineliboutput cp libvdr-xineliboutput* ../../lib cp libxineliboutput* ../../lib To install the frontends: sudo make install Thats it. HTH. Halim ___ 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 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 mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Xineliboutput doesn't compil under vdr-2.0.1
Hi Salim, I was looking for libvdr-xineliboutput.so.2.0.0.lib file, instead of libvdr-xineliboutput.so.2.0.0. After I copied it in vdr/PLUGINS/lib, problem solved. Thanks a lot ! Karim -Message d'origine- De : vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] De la part de Karim Envoyé : jeudi 2 mai 2013 19:24 À : 'VDR Mailing List' Objet : Re: [vdr] Xineliboutput doesn't compil under vdr-2.0.1 Hi Halim, I have double checked : there is no libvdr-xineliboutput.so.2.0.0 in vdr/PLUGINS/lib (or anywhere). I am afraid that compilation fails. Thanks Karim -Message d'origine- De : vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] De la part de Halim Sahin Envoyé : jeudi 2 mai 2013 05:39 À : vdr@linuxtv.org Objet : Re: [vdr] Xineliboutput doesn't compil under vdr-2.0.1 Hi, In the output you posted here are no error message (only warnings). The build was successfull but xineliboutput didn't copy the binaries to PLUGINS/lib because of the old Makefiles. You can do it yourself :-). cd PLUGINS/src/xineliboutput cp libvdr-xineliboutput* ../../lib cp libxineliboutput* ../../lib To install the frontends: sudo make install Thats it. HTH. Halim ___ 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 mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Xineliboutput doesn't compil under vdr-2.0.1
Hi Halim, I have double checked : there is no libvdr-xineliboutput.so.2.0.0 in vdr/PLUGINS/lib (or anywhere). I am afraid that compilation fails. Thanks Karim -Message d'origine- De : vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] De la part de Halim Sahin Envoyé : jeudi 2 mai 2013 05:39 À : vdr@linuxtv.org Objet : Re: [vdr] Xineliboutput doesn't compil under vdr-2.0.1 Hi, In the output you posted here are no error message (only warnings). The build was successfull but xineliboutput didn't copy the binaries to PLUGINS/lib because of the old Makefiles. You can do it yourself :-). cd PLUGINS/src/xineliboutput cp libvdr-xineliboutput* ../../lib cp libxineliboutput* ../../lib To install the frontends: sudo make install Thats it. HTH. Halim ___ 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
Re: [vdr] Xineliboutput doesn't compil under vdr-2.0.1
PS : I tried to run make install from vdr but xineliboutput doesn't see vdr. Please see below : root@pctest:/usr/local/src/vdr/PLUGINS/src/xineliboutput# make install sed: impossible de lire /config.h: Aucun fichier ou dossier de ce type Makefile:97: Makefile:98: VDR not detected ! VDR plugins will not be compiled. Makefile:99: sed: impossible de lire /config.h: Aucun fichier ou dossier de ce type sed: impossible de lire /config.h: Aucun fichier ou dossier de ce type sed: impossible de lire /config.h: Aucun fichier ou dossier de ce type sed: impossible de lire /config.h: Aucun fichier ou dossier de ce type sed: impossible de lire /config.h: Aucun fichier ou dossier de ce type sed: impossible de lire /config.h: Aucun fichier ou dossier de ce type Installing //usr/local/lib/xine/plugins/2.2/xineplug_inp_xvdr.so Installing //usr/local/lib/xine/plugins/2.2/post/xineplug_post_autocrop.so Installing //usr/local/lib/xine/plugins/2.2/post/xineplug_post_swscale.so Installing //usr/local/lib/xine/plugins/2.2/post/xineplug_post_audiochannel.so Installing ../../lib/libvdr-xineliboutput.so. Installing //usr/bin/vdr-fbfe Installing ../../lib/libxineliboutput-fbfe.so.1.0.90-cvs Installing //usr/bin/vdr-sxfe Installing ../../lib/libxineliboutput-sxfe.so.1.0.90-cvs If this log could help to point on the problem... Regards. Karim -Message d'origine- De : vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] De la part de Karim Envoyé : jeudi 2 mai 2013 19:24 À : 'VDR Mailing List' Objet : Re: [vdr] Xineliboutput doesn't compil under vdr-2.0.1 Hi Halim, I have double checked : there is no libvdr-xineliboutput.so.2.0.0 in vdr/PLUGINS/lib (or anywhere). I am afraid that compilation fails. Thanks Karim -Message d'origine- De : vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] De la part de Halim Sahin Envoyé : jeudi 2 mai 2013 05:39 À : vdr@linuxtv.org Objet : Re: [vdr] Xineliboutput doesn't compil under vdr-2.0.1 Hi, In the output you posted here are no error message (only warnings). The build was successfull but xineliboutput didn't copy the binaries to PLUGINS/lib because of the old Makefiles. You can do it yourself :-). cd PLUGINS/src/xineliboutput cp libvdr-xineliboutput* ../../lib cp libxineliboutput* ../../lib To install the frontends: sudo make install Thats it. HTH. Halim ___ 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 mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Viaccess CAM support in VDR
Hello, FYI, now TBS6928 + CAM Neotion Viaccess (*) is working with VDR 1.7.33. 1/ in dvb-s2 (TBS6928) - SD channels = OK - HD channels = a few artefacts and sometimes video isn't smooth enough. If anyone have an idea... 2/ in dvb-t (TBS6280) Working in SD ans HD channels, but as soon as I add this hardware, VDR doesn't decrypt anymore dvb-s/s2 channels. I've to try with vdr 2.0.1, in case problem persists, I will ask to Klaus. (*) after stability problem with SMIT, I sent this CAM to vendor for repair. Regards. Karim -Message d'origine- De : vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] De la part de hederic Envoyé : mardi 22 janvier 2013 12:25 À : vdr@linuxtv.org Objet : Re: [vdr] Viaccess CAM support in VDR Karim karim.afifi at laposte.net writes: Hello, I bought the same hardware a few weeks ago. It doesn't work with VDR at this time. 1/ I can reset the CAM from VDR but I can't access to the CAM menu. 2/ As soon as I plug the SMIT module in the CI slot a red led lights. (I dont' know what it's mean). Is it same with you ? I have to contact TBS support about this problem this week-end. To all vdr users, please give us your feedback about good CAM products. Regards. Karim Hi, I don't know if it's the same problem but i'm having errors in logfile : CAM tried to send a buffer larger than the ecount size! End all channels stop working even plain unencrypted channels. Bye. Hederic ___ 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] Xineliboutput doesn't compil under vdr-2.0.1
Hi, I am trying new vdr-2.0.1 with 2 plugins : - femon (v2.0.0) - Xineliboutput (cvs from today). = Xineliboutput doesn't compil (no problem with Femon). I compile VDR with theses options : make REMOTE=LIRC VFAT=1 LCLBLD=1 Here is the error message I always get : *** Plugin xineliboutput: WARNING: plugin xineliboutput is using an old Makefile! Makefile:112: Makefile:113: VDR source tree not detected ! Makefile:114: VDR plugins will not be installed. Makefile:115: make[1]: Rien à faire pour « all ». *** plugins with old Makefile: xineliboutput ** *** While this currently still works, it is strongly recommended *** that you convert old Makefiles to the new style used since *** VDR version 1.7.36. Support for old style Makefiles may be dropped *** in future versions of VDR. ** Here is my paths : /DATA/video /DATA/configVDR /usr/local/src/vdr Here is my VDR Make.config # # User defined Makefile options for the Video Disk Recorder # # Copy this file to 'Make.config' and change the parameters as necessary. # # See the main source file 'vdr.c' for copyright information and # how to reach the author. # # $Id: Make.config.template 2.19 2013/02/18 10:55:39 kls Exp $ ### The C compiler and options: CC = gcc CFLAGS = -g -O3 -Wall CXX = g++ CXXFLAGS = -g -O3 -Wall -Werror=overloaded-virtual -Wno-parentheses # Use 'make M32=1 ...' to build a 32-bit version of VDR on a 64-bit machine: ifdef M32 CFLAGS += -m32 CXXFLAGS += -m32 endif ### The directory environment: # Default directories (adjust as necessary or desired): #PREFIX= /usr/local #BINDIR= $(PREFIX)/bin #INCDIR= $(PREFIX)/include #LIBDIR= $(PREFIX)/lib/vdr Update perso #LOCDIR= $(PREFIX)/share/locale LOCDIR= /usr/local/src/vdr/locale #MANDIR= $(PREFIX)/share/man #PCDIR = $(PREFIX)/lib/pkgconfig #RESDIR= $(PREFIX)/share/vdr Update perso #DVBDIR= /usr/src/v4l-dvb/linux/include/uapi DVBDIR= /usr/include/linux/dvb Update perso #VIDEODIR = /srv/vdr/video VIDEODIR = /DATA/video0 Update perso #CONFDIR = /var/lib/vdr CONFDIR = /DATA/configVDR #CACHEDIR = /var/cache/vdr # Overrides for preset/legacy configurations: # Use 'make LCLBLD=1' to build locale and plugin files under the source directory: ifdef LCLBLD LOCDIR = $(CWD)/locale PLUGINDIR= $(CWD)/PLUGINS ifndef PLUGIN # don't overwrite for plugins with old makefiles LIBDIR = $(PLUGINDIR)/lib endif HDRDIR = $(CWD)/include endif # Use 'make ONEDIR=1' to have all data in one single directory: ifdef ONEDIR Update perso #VIDEODIR = /video VIDEODIR = /DATA/video0 CACHEDIR = $(VIDEODIR) Update perso #CONFDIR = $(VIDEODIR) CONFDIR = /DATA/configVDR RESDIR = $(VIDEODIR) endif # Use this if you want to have a central place where you configure compile time # parameters for plugins: #PLGCFG = $(CONFDIR)/plugins.mk ### The remote control: LIRC_DEVICE = /var/run/lirc/lircd ### Define if you want vdr to not run as root: #VDR_USER = vdr ### Fallback for plugins with old makefiles: ifdef PLUGIN CFLAGS += -fPIC CXXFLAGS += -fPIC endif Is there any patch I missed for Xineliboutput ? Perhaps I have to customize Xineliboutput's Makefile ? Could you help me to find the problem ? Regards. Karim ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Viaccess CAM support in VDR
Hello, I bought the same hardware a few weeks ago. It doesn't work with VDR at this time. 1/ I can reset the CAM from VDR but I can't access to the CAM menu. 2/ As soon as I plug the SMIT module in the CI slot a red led lights. (I dont' know what it's mean). Is it same with you ? I have to contact TBS support about this problem this week-end. To all vdr users, please give us your feedback about good CAM products. Regards. Karim Hi Karim, I'm using a TBS 6928 tuner from Turbosight and a SMIT Viaccess secure dual ACS3.0 CAM. Any luck you might have info on that hardware's compatibility ? Thanks. hederic Hi guys, I'd like to know if anyone has had some success lately using Viaccess CAM with VDR. I'm having error messages in /var/log/messages and nothing is working. I've only tried a Smit Viaccess CAM but if you know of any working Viaccess CAM i'd really appreciate the info. Thanks a lot. Hederic ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Viaccess CAM support in VDR
Hello, What hardware do you use (tuner and CAM) ? Karim -Message d'origine- De : vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] De la part de hederic Envoyé : lundi 14 janvier 2013 21:05 À : vdr@linuxtv.org Objet : [vdr] Viaccess CAM support in VDR Hi guys, I'd like to know if anyone has had some success lately using Viaccess CAM with VDR. I'm having error messages in /var/log/messages and nothing is working. I've only tried a Smit Viaccess CAM but if you know of any working Viaccess CAM i'd really appreciate the info. Thanks a lot. Hederic ___ 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
Re: [vdr] Problem with vdr-1.7.x and three DVB-T HD channels
Update. I just recorded France2HD and I played back with VLC without problem. It seems ther is a dialog problem between vdr and xlo for tree HD channels Any hint please ? Regards -Message d'origine- De : vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] De la part de kafifi Envoyé : dimanche 6 janvier 2013 20:40 À : 'VDR Mailing List' Objet : [vdr] Problem with vdr-1.7.x and three DVB-T HD channels Hi, Happy new year 2013 to Klaus and all vdr users !! Under vdr-1.7.x and xineliboutput, I have some trouble with **tree** dvb-t HD french channels (Eiffel Tower near Paris) : - SD channels : OK - HD channels : all OK except France2 HD, M6HD and 6ter (see below). Channels KO When I zap on one of them, image appears about one second, freezes, and then I get a black screen. Sometimes it's impossible to zap to another channel, vdr-sxfe can't drive vdr anymore, and I have to reload vdr. Sometimes, afert about 10s, image appears for one second, and freezes again, and then I get black screen. Here is latest tests performed on a Wheezy x64 fresh install. Same issues (signal strenght about 82%) : - with NOVA-T-500 tuner - with TBS6280 tuner - alternating vdr-1.7.27 (+ patch ppid) and vdr-7.1.33. - With parameter menu configuration DVB card update channels NO - With parameter menu configuration DVB card update channels name and pid Installation is OK, no problem under Win7. Could you please help me to find what's wrong ? Could it be a bad setting of config_xineliboutput ? Thanks a lot ! Karim channels.conf :@201 TF1 HD;MR5:53:B8C34G8M64S0T8Y0:T:27500:120=27:0;130=fra@122,131=qaa@122,132= qad@122:0;140=fra,141=fra:0:1281:8442:5:0 France 2 HD;MR5:53:B8S0Y0:T:27500:220=27:0;230=fra@122,231=qaa@122,232=qad@122:0; 240=fra,241=fra:0:1282:8442:5:0 :@206 M6HD;MR5:53:B8C23M2S0T8Y0:T:27500:320=27:0;330=fra@122,331=qaa@122,332=q ad@122:0;340=fra,341=fra:0:1283:8442:5:0 ARTE HD;Multi 4:546000:B8C23M64T8Y0:T:27500:720=27:731=qaa@3,732=deu@3,733=qad@3,730=fra@3 :0;740=fra,741=deu,742=fra:0:1031:8442:4:0 HD1;MHD7:642000:B8C23M64S0T8Y0:T:27500:120=27:0;130=fra@122,131=qaa@122,132= qad@122:0;150=fra,151=fra:0:2561:8442:10:0 RMC DECOUVERTE;R8:77:B8C23M64S0T8Y0:T:27500:320=27:0;330=fra@122,331=qaa@122 ,332=qad@122:0;340=fra,341=fra:0:2819:8442:11:0 Chérie 25;MHD7:642000:B8C23M64S0T8Y0:T:27500:320=27:0;330=fra@122,331=qaa@122,332=q ad@122:0;350=fra:0:2563:8442:10:0 NUMERO 23;R8:77:B8C23M64S0T8Y0:T:27500:220=27:0;230=fra@122,231=qaa@122,232=qad @122:0;240=fra,241=fra:0:2818:8442:11:0 6ter;R8:77:B8S0Y0:T:27500:120=27:0;130=fra@122,131=qaa@122,132=qad@122:0 ;140=fra,141=fra:0:2817:8442:11:0 L'Equipe 21;MHD7:642000:B8C23M64S0T8Y0:T:27500:220=27:0;230=fra@122,231=qad@122:0;250 =fra:0:2562:8442:10:0 vdr-sxfe Jan 6 20:29:56 pctest vdr: [4480] switching to channel 202 Jan 6 20:29:56 pctest vdr: [4792] TS buffer on device 3 thread ended (pid=4480, tid=4792) Jan 6 20:29:56 pctest vdr: [4791] buffer stats: 164688 (3%) used Jan 6 20:29:56 pctest vdr: [4791] receiver on device 3 thread ended (pid=4480, tid=4791) Jan 6 20:29:56 pctest vdr: [4802] receiver on device 3 thread started (pid=4480, tid=4802, prio=high) Jan 6 20:29:56 pctest vdr: [4803] TS buffer on device 3 thread started (pid=4480, tid=4803, prio=high) Jan 6 20:29:58 pctest vdr: [4802] [xine..put] H.264: Found NAL SPS at offset 8/152 Jan 6 20:29:58 pctest vdr: [4802] [xine..put] H.264 SPS: profile_idc 100 Jan 6 20:29:58 pctest vdr: [4802] [xine..put] H.264 SPS: pic_width: 120 mbs Jan 6 20:29:58 pctest vdr: [4802] [xine..put] H.264 SPS: pic_height: 34 mbs Jan 6 20:29:58 pctest vdr: [4802] [xine..put] H.264 SPS: frame only flag: 0 Jan 6 20:29:58 pctest vdr: [4802] [xine..put] H.264 SPS: MBAFF Jan 6 20:29:58 pctest vdr: [4802] [xine..put] H.264 SPS: cropping 0 0 0 2 Jan 6 20:29:58 pctest vdr: [4802] [xine..put] H.264 SPS: aspect_ratio_idc 1 Jan 6 20:29:58 pctest vdr: [4802] [xine..put] H.264 SPS: - aspect ratio 1 / 1 Jan 6 20:29:58 pctest vdr: [4802] [xine..put] H.264 SPS: - video size 1920x1080, aspect 1:1 Jan 6 20:29:58 pctest vdr: [4802] [xine..put] Detected video size 1920x1080 Jan 6 20:30:02 pctest vdr: [4501] [xine..put] Client connection 0 closed Jan 6 20:30:02 pctest vdr: [4786] [xine..put] cBackgroundWriter: TCP write error Jan 6 20:30:02 pctest vdr: [4786] [xine..put](ERROR (tools/backgroundwriter.c,247): Mauvais descripteur de fichier) Jan 6 20:30:02 pctest vdr: [4501] [xine..put] Closing connection 0 Jan 6 20:30:04 pctest vdr: [4501] [xine..put] Client 0 connected: 127.0.0.1:57549 Jan 6 20:30:04 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:30:04 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:30:04 pctest vdr: [4501] [xine..put] Client 1 connected: 127.0.0.1:57550 Jan 6 20:30:04 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:30:04 pctest vdr: [4501] [xine..put
Re: [vdr] vdr xine-lib eac3
Zaverel and Jose Alberto,
Thanks a lot for your explanations; I am going to try the recode ac3
solution with alsa.
Cheers.
Karim
-Message d'origine-
De : vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] De la part de
zaverel
Envoyé : jeudi 12 juillet 2012 13:12
À : VDR Mailing List
Objet : [vdr] vdr xine-lib eac3
@Zaverel,
What do you mean by It's not perfect but that work ?
it's cpu extensive because all audio is recoded in ac3.
You can try with this in /etc/asound.conf (for global user ) or ~/.asoundrc
(only user)
pcm.!default {
type plug
slave.pcm surroundaudio
}
ctl.!default {
type plug
slave.pcm surroundaudio
}
pcm.a52encode {
type a52
format S16_LE
channels 6
rate 48000
bitrate 448
}
pcm.surroundaudio {
type upmix
slave.pcm a52encode
channels 6
}
and start xine with --audio=alsa:surroundaudio
___
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
Re: [vdr] vdr xine-lib eac3
@Zaverel, What do you mean by It's not perfect but that work ? @Jose Alberto, What's the problem with the channel TVE-HD Pruebas. Could you please tell us about your hardware ? Are you using spdif output ? Thanks for your support which help us to understand the subject. Karim -Message d'origine- De : vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] De la part de Jose Alberto Reguero Envoyé : mercredi 11 juillet 2012 18:52 À : vdr@linuxtv.org Cc : zaverel Objet : Re: [vdr] vdr xine-lib eac3 On Miércoles, 11 de julio de 2012 14:00:47 zaverel escribió: / Is it the normal behaviour, or did I miss something ? // Is there a way to convert eac3 = ac3 for delivering 5.1 stream through the // spdif output ? // // Regards. // Karim // hello, with alsa-plugins and a52 you can have more than 2 channels on spdif sound is encoded in dolby on-the-fly and send to the spdif. configuration is in ~/.asoundrc There is many exemples on the net It's not perfect but that work./ Jose Alberto , what is the purpose to your patch ? The patch is for eac3 sound problems with the channel TVE-HD Pruebas. Jose Alberto ___ 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
Re: [vdr] Hardware for VDR and Viaccess Secure
Hello, It seems that Viaccess Secure is used only in France. Then I am still interested by your feedback about using CAM (even if different than Viaccess or Viaccess Secure) with the hardwares below. The main goal is to buy the good hardware for viewing one channel, and registering one (or more channels) with my subscriber card. Regards. Karim -Message d'origine- De : vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] De la part de Karim Afifi Envoyé : dimanche 8 juillet 2012 22:03 À : vdr@linuxtv.org Objet : [vdr] Hardware for VDR and Viaccess Secure Hello, Here in France, BISTV provider is using Viaccess Secure System. To view channels, we need a Viaccess compatible CAM like Viaccess SMIT SECURE DUAL. For VDR, to support this CAM, I plan to buy a dvb-s2 card and a CI interface card. I found couples of items which seems to be Linux/VDR compatibles : From Mystique http://www.dvbshop.net/product_info.php/info/p2318_Mystique-SaTiX-S2-V3-CI-D ual--2xDVB-S2-CI-HDTV-MPEG4-H-264.html http://www.dvbshop.net/product_info.php/info/p2319_Mystique-CI-Interface-f-- Mystique-SaTiX-S2-Dual.html From Digital Devices http://shop.digital-devices.de/epages/62357162.sf/secdcf4f6e155/?ObjectPath= /Shops/62357162/Products/091201 http://shop.digital-devices.de/epages/62357162.sf/de_DE/?ObjectPath=/Shops/6 2357162/Products/092003 It seems all theses items are able to register one channel when viewing another. I guess it's true. Do you have some experience with theses hardwares ? Could you please give me somme feedback ? Thanks a lot. ___ 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
Re: [vdr] vdr xine-lib eac3
Up please :-) Karim -Message d'origine- De : vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] De la part de Karim Afifi Envoyé : vendredi 18 mai 2012 21:32 À : 'VDR Mailing List' Objet : Re: [vdr] vdr xine-lib eac3 Hello, I am using vdr-1.7.27 and xineliboutput (with xine-lib from january 2012 and José Alberto's patch). All HD dvb-t french channels are deliver eac3, but vdr delivers only stereo pcm on the spdif output (instead of 5.1). Is it the normal behaviour, or did I miss something ? Is there a way to convert eac3 = ac3 for delivering 5.1 stream through the spdif output ? Regards. Karim -Message d'origine- De : vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] De la part de Jose Alberto Reguero Envoyé : dimanche 3 octobre 2010 23:56 À : VDR Mailing List Objet : Re: [vdr] vdr xine-lib eac3 Attached is a patch to fix xine-lib ts work with eac3. With this patch you can use xine-ui to play the records. Jose Alberto El Domingo 03 Octubre 2010, Jose Alberto Reguero escribió: Playing with xine-ui and demux ts don't work well. You must play it with vdr- xine. Jose Alberto ___ 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] Hardware for VDR and Viaccess Secure
Hello, Here in France, BISTV provider is using Viaccess Secure System. To view channels, we need a Viaccess compatible CAM like Viaccess SMIT SECURE DUAL. For VDR, to support this CAM, I plan to buy a dvb-s2 card and a CI interface card. I found couples of items which seems to be Linux/VDR compatibles : From Mystique http://www.dvbshop.net/product_info.php/info/p2318_Mystique-SaTiX-S2-V3-CI-D ual--2xDVB-S2-CI-HDTV-MPEG4-H-264.html http://www.dvbshop.net/product_info.php/info/p2319_Mystique-CI-Interface-f-- Mystique-SaTiX-S2-Dual.html From Digital Devices http://shop.digital-devices.de/epages/62357162.sf/secdcf4f6e155/?ObjectPath= /Shops/62357162/Products/091201 http://shop.digital-devices.de/epages/62357162.sf/de_DE/?ObjectPath=/Shops/6 2357162/Products/092003 It seems all theses items are able to register one channel when viewing another. I guess it's true. Do you have some experience with theses hardwares ? Could you please give me somme feedback ? Thanks a lot. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr xine-lib eac3
Hello, I am using vdr-1.7.27 and xineliboutput (with xine-lib from january 2012 and José Alberto's patch). All HD dvb-t french channels are deliver eac3, but vdr delivers only stereo pcm on the spdif output (instead of 5.1). Is it the normal behaviour, or did I miss something ? Is there a way to convert eac3 = ac3 for delivering 5.1 stream through the spdif output ? Regards. Karim -Message d'origine- De : vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] De la part de Jose Alberto Reguero Envoyé : dimanche 3 octobre 2010 23:56 À : VDR Mailing List Objet : Re: [vdr] vdr xine-lib eac3 Attached is a patch to fix xine-lib ts work with eac3. With this patch you can use xine-ui to play the records. Jose Alberto El Domingo 03 Octubre 2010, Jose Alberto Reguero escribió: Playing with xine-ui and demux ts don't work well. You must play it with vdr- xine. Jose Alberto ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] weatherng-0.0.10 and vdr-1.7.27 : compilation error
Hello, I am trying to compil weatherng-0.0.10 and vdr-1.7.27 without success. Adding #include vdr/config.h to i18n.h doesn't solve the problem. Is there any patch to fix this ? Regards. Here is the log : Plugin weatherng: make[1]: entrant dans le répertoire « /usr/local/src/vdr-1.7.27/PLUGINS/src/weatherng-0.0.10 » make[1]: quittant le répertoire « /usr/local/src/vdr-1.7.27/PLUGINS/src/weatherng-0.0.10 » make[1]: entrant dans le répertoire « /usr/local/src/vdr-1.7.27/PLUGINS/src/weatherng-0.0.10 » g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -fPIC -c -DHAVE_IMLIB2 -D_GNU_SOURCE -DPLUGIN_NAME_I18N='weatherng' -I/usr/local/src/media_build/linux/include -I../../../include -obitmap.o bitmap.c g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -fPIC -c -DHAVE_IMLIB2 -D_GNU_SOURCE -DPLUGIN_NAME_I18N='weatherng' -I/usr/local/src/media_build/linux/include -I../../../include -oquantize.o quantize.c g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -fPIC -c -DHAVE_IMLIB2 -D_GNU_SOURCE -DPLUGIN_NAME_I18N='weatherng' -I/usr/local/src/media_build/linux/include -I../../../include -oimagecache.o imagecache.c g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -fPIC -c -DHAVE_IMLIB2 -D_GNU_SOURCE -DPLUGIN_NAME_I18N='weatherng' -I/usr/local/src/media_build/linux/include -I../../../include -oweatherng.o weatherng.c In file included from weatherng.h:5, from weatherng.c:11: i18n.h:15: error: tI18nPhrase does not name a type weatherng.c: In member function virtual bool cPluginWetter::Start(): weatherng.c:124: error: Phrases was not declared in this scope weatherng.c:124: error: RegisterI18n was not declared in this scope make[1]: *** [weatherng.o] Erreur 1 make[1]: quittant le répertoire « /usr/local/src/vdr-1.7.27/PLUGINS/src/weatherng-0.0.10 » ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] noad-0.7.3 and HD ?
Hi, I've just installed noad 0.7.3 on vdr-1.7.27. Unfortunately, this version is doesn't work with HD recordings : __ . May 1 11:09:10 pctest vdr: [7651] timer 1 (202 1030-1130 'MØtØo 2~MØtØo.') stop May 1 11:09:10 pctest vdr: [7651] executing '/usr/local/src/noad/noad priority 5 --overlap --ac3 --jumplogo --OSD --savelogo after /DATA/video0/MØtØo_2/MØtØo./2012-05-01.10.30.202-0.rec' May 1 11:09:10 pctest noad[7965]: noad arg[0]: /usr/local/src/noad/noad May 1 11:09:10 pctest noad[7965]: noad arg[1]: priority May 1 11:09:10 pctest noad[7965]: noad arg[2]: 5 May 1 11:09:10 pctest noad[7965]: noad arg[3]: --overlap May 1 11:09:10 pctest noad[7965]: noad arg[4]: --ac3 May 1 11:09:10 pctest noad[7965]: noad arg[5]: --jumplogo May 1 11:09:10 pctest noad[7965]: noad arg[6]: --OSD May 1 11:09:10 pctest noad[7965]: noad arg[7]: --savelogo May 1 11:09:10 pctest noad[7965]: noad arg[8]: after May 1 11:09:10 pctest noad[7965]: noad arg[9]: /DATA/video0/MØtØo_2/MØtØo./2012-05-01.10.30.202-0.rec May 1 11:09:10 pctest noad[7965]: noad args done May 1 11:09:10 pctest noad[7965]: noad forked to pid 7966 May 1 11:09:10 pctest noad[7966]: Tuesday,01.05.2012 11:09:10 start noad-0.7.3 for /DATA/video0/MØtØo_2/MØtØo./2012-05-01.10.30.202-0.rec May 1 11:09:10 pctest noad[7966]: [7966] looks like HDTV, can't handle this file, give up ^^ May 1 11:09:10 pctest noad[7966]: Tuesday,01.05.2012 11:09:10 noad done for /DATA/video0/MØtØo_2/MØtØo./2012-05-01.10.30.202-0.rec (0:00:00) . __ Is there any version or any patch I missed ? Regards. Karim ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr-1.7.27 : compilation error with several plugins
Hello, I am building a new box with vdr-1.7.27. Several plugins don't compil anymore with this error msg : i18n.h:8: error: tI18nPhrase does not name a type Is there a solution to fix this ? Thanks a lot. Karim Plugin loadepg: make[1]: entrant dans le répertoire « /usr/local/src/vdr-1.7.27/PLUGINS/src/loadepg-0.2.3 » make[1]: quittant le répertoire « /usr/local/src/vdr-1.7.27/PLUGINS/src/loadepg-0.2.3 » make[1]: entrant dans le répertoire « /usr/local/src/vdr-1.7.27/PLUGINS/src/loadepg-0.2.3 » g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -fPIC -c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='loadepg' -I/usr/local/src/media_build/linux/include -I../../../include loadepg.c g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -fPIC -c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='loadepg' -I/usr/local/src/media_build/linux/include -I../../../include i18n.c In file included from i18n.c:1: i18n.h:8: error: tI18nPhrase does not name a type i18n.c:5: error: tI18nPhrase does not name a type make[1]: *** [i18n.o] Erreur 1 make[1]: quittant le répertoire « /usr/local/src/vdr-1.7.27/PLUGINS/src/loadepg-0.2.3 » Plugin osdpip: make[1]: entrant dans le répertoire « /usr/local/src/vdr-1.7.27/PLUGINS/src/osdpip-0.1.1 » make[1]: quittant le répertoire « /usr/local/src/vdr-1.7.27/PLUGINS/src/osdpip-0.1.1 » make[1]: entrant dans le répertoire « /usr/local/src/vdr-1.7.27/PLUGINS/src/osdpip-0.1.1 » g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -fPIC -c -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_GNU_SOURCE -DPLUGIN_NAME_I18N='osdpip' -D__STDC_CONSTANT_MACROS -DUSE_SWSCALE -DUSE_NEW_FFMPEG_HEADERS -I/usr/local/src/media_build/linux/include -I../../../include osdpip.c In file included from osdpip.c:24: ../../../include/vdr/status.h:33: warning: virtual void cStatus::ChannelSwitch(const cDevice*, int, bool) was hidden osd.h:79: warning: by virtual void cOsdPipObject::ChannelSwitch(const cDevice*, int) g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -fPIC -c -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_GNU_SOURCE -DPLUGIN_NAME_I18N='osdpip' -D__STDC_CONSTANT_MACROS -DUSE_SWSCALE -DUSE_NEW_FFMPEG_HEADERS -I/usr/local/src/media_build/linux/include -I../../../include osd_info.c In file included from osd_info.c:24: i18n.h:33: error: tI18nPhrase does not name a type make[1]: *** [osd_info.o] Erreur 1 make[1]: quittant le répertoire « /usr/local/src/vdr-1.7.27/PLUGINS/src/osdpip-0.1.1 » Plugin text2skin: make[1]: entrant dans le répertoire « /usr/local/src/vdr-1.7.27/PLUGINS/src/loadepg-0.2.3 » g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -fPIC -c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='loadepg' -I/usr/local/src/media_build/linux/include -I../../../include i18n.c In file included from i18n.c:1: i18n.h:8: error: tI18nPhrase does not name a type i18n.c:5: error: tI18nPhrase does not name a type make[1]: *** [i18n.o] Erreur 1 make[1]: quittant le répertoire « /usr/local/src/vdr-1.7.27/PLUGINS/src/loadepg-0.2.3 » ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] noad-0.7.3 and HD ?
Hi Franck, Thanks for the this, I didn't know this plugin ! The compilation goes well, but the plugin-markad prevents VDR launch by systematically crashes it ... Any idea please ? Thanks ! May 1 13:50:08 pctest vdr: [23994] found 4 DVB devices May 1 13:50:08 pctest vdr: [23994] initializing plugin: femon (1.7.17): Affiche les informations du signal DVB May 1 13:50:08 pctest vdr: [23994] initializing plugin: epgsearch (1.0.1): Recherche de répétition dans EPG May 1 13:50:08 pctest vdr: [23994] initializing plugin: xineliboutput (1.0.90-cvs): X11/xine-lib output plugin May 1 13:50:08 pctest vdr: [23994] new device number 9 May 1 13:50:08 pctest vdr: [23994] [xine..put] cTimePts: clock_gettime(CLOCK_MONOTONIC): clock resolution 0 us May 1 13:50:08 pctest vdr: [23994] [xine..put] cTimePts: using monotonic clock May 1 13:50:08 pctest vdr: [23994] [xine..put] RTP SSRC: 0x28bab902 May 1 13:50:08 pctest vdr: [23994] initializing plugin: markad (0.1.3): Mark advertisements May 1 13:50:08 pctest vdr: [23994] markad: cannot find /usr/bin/markad, please install May 1 13:50:08 pctest vdr: [24009] section handler thread started (pid=23994, tid=24009) May 1 13:50:08 pctest vdr: [24010] [xine..put] Have CAP_SYS_NICE capability May 1 13:50:09 pctest vdr: [24000] section handler thread ended (pid=23994, tid=24000) May 1 13:50:09 pctest vdr: [23999] tuner on frontend 0/0 thread ended (pid=23994, tid=23999) May 1 13:50:09 pctest vdr: [24003] section handler thread ended (pid=23994, tid=24003) May 1 13:50:09 pctest vdr: [24002] tuner on frontend 1/0 thread ended (pid=23994, tid=24002) May 1 13:50:09 pctest vdr: [24006] section handler thread ended (pid=23994, tid=24006) May 1 13:50:09 pctest vdr: [24005] tuner on frontend 2/0 thread ended (pid=23994, tid=24005) May 1 13:50:09 pctest vdr: [24009] section handler thread ended (pid=23994, tid=24009) May 1 13:50:09 pctest vdr: [24008] tuner on frontend 3/0 thread ended (pid=23994, tid=24008) May 1 13:50:09 pctest vdr: [23994] [xine..put] cXinelibDevice::StopDevice(): Stopping device ... May 1 13:50:09 pctest vdr: [23994] deleting plugin: markad May 1 13:50:09 pctest vdr: [23994] deleting plugin: xineliboutput May 1 13:50:09 pctest vdr: [23994] deleting plugin: epgsearch May 1 13:50:09 pctest vdr: [23994] deleting plugin: femon May 1 13:50:09 pctest vdr: [23994] max. latency time 0 seconds May 1 13:50:09 pctest vdr: [23994] exiting, exit code 2 ... If you want to have that funktionality, you need to look at vdr-plugin-markad. Regards fnu ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr-1.7.27 : compilation error with several plugins
Martin and Udo, Thanks, I am going to try to patch. nb : vdrportal is very interesting, but still difficult for me because I can't speak german. Regards. Karim ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] noad-0.7.3 and HD ?
You've right. Fixed, plugin-markad is working perfect now. Thanks a lot ! Karim -Message d'origine- De : vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] De la part de Dominic Evans Envoyé : mardi 1 mai 2012 14:09 À : VDR Mailing List Objet : Re: [vdr] noad-0.7.3 and HD ? On 1 May 2012 13:01, Karim Afifi karim.af...@laposte.net wrote: Hi Franck, Thanks for the this, I didn't know this plugin ! The compilation goes well, but the plugin-markad prevents VDR launch by systematically crashes it ... Any idea please ? Thanks ! There's a fairly clear message in your log: 23994] markad: cannot find /usr/bin/markad, please install ___ 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] vdr-1.7.x + TT S2-6400 + mkv
Hi, I dug up this old post ... I am still looking for a solution to view mkv files from vdr-1.7.x and Technotrend S2-6400. AFAIK, there is no evolution for mplayer at this time, and no vdr-plugin either :-( (I suppose that most of people are using Xineliboutpout and its own player). Do you know about a solution for Technotrend S2-6400 ? Dis I missed something ? Thanks. Karim -Message d'origine- De : vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] De la part de Steffen Barszus Envoyé : samedi 25 juin 2011 11:22 À : vdr@linuxtv.org Objet : Re: [vdr] vdr-1.7.x + TT S2-6400 + mkv On Sat, 25 Jun 2011 09:46:20 +0200 Karim karim.af...@laposte.net wrote: Hello, I am looking for a plugin to view hd file (mkv) with vdr-1.7.x and S2-6400. (MPlayer doesn't work here). Any hint please would be greatly appreciated ! As already mentioned. Such a thing does not exist. Your best bet would be to translate the mkv to ts and convert it to a recording. Then it MIGHT be possible to watch. But there is no media player which can output to your device. ___ 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
Re: [vdr] vdr-1.7.x : can't read correctly MKV = TS files
Up ! Your help would be greatly appreciated. I put two samples here : http://dl.free.fr/rKmDrD3qh 1/ ts_from_vdr.ts : record from VDR = Ok 2/ ts_from_mkv.ts : conversion from mkv = no sound with VDR. Thx ! -Message d'origine- De : vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] De la part de Karim Envoyé : lundi 4 juillet 2011 19:46 À : 'VDR Mailing List' Objet : [vdr] vdr-1.7.x : can't read correctly MKV = TS files Hello, MPlayer isn't compatible with my new hardware (Technotrend S2-6400), then I am looking for another solution to read my mkv files with vdr-1.7.x. I converted a mkv (HD+AC3) to ts with h264tobox tools, and I tried to read it from vanilla vdr. The picture is OK but there is no sound. vdr displays this message : no sound available. Could you please help me to find the problem or point to another solution? Thanks a lot. Karim ___ 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] vdr-1.7.x : can't read correctly MKV = TS files
Hello, MPlayer isn't compatible with my new hardware (Technotrend S2-6400), then I am looking for another solution to read my mkv files with vdr-1.7.x. I converted a mkv (HD+AC3) to ts with h264tobox tools, and I tried to read it from vanilla vdr. The picture is OK but there is no sound. vdr displays this message : no sound available. Could you please help me to find the problem or point to another solution? Thanks a lot. Karim ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr-1.7.x + TT S2-6400 + mkv
Hello, I am looking for a plugin to view hd file (mkv) with vdr-1.7.x and S2-6400. (MPlayer doesn't work here). Any hint please would be greatly appreciated ! Thanks a lot! Karim ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.7.x + TT S2-6400 + mkv
Thanks, I'll try this solution. Regards. Karim -Message d'origine- De : vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] De la part de Steffen Barszus Envoyé : samedi 25 juin 2011 11:22 À : vdr@linuxtv.org Objet : Re: [vdr] vdr-1.7.x + TT S2-6400 + mkv On Sat, 25 Jun 2011 09:46:20 +0200 Karim karim.af...@laposte.net wrote: Hello, I am looking for a plugin to view hd file (mkv) with vdr-1.7.x and S2-6400. (MPlayer doesn't work here). Any hint please would be greatly appreciated ! As already mentioned. Such a thing does not exist. Your best bet would be to translate the mkv to ts and convert it to a recording. Then it MIGHT be possible to watch. But there is no media player which can output to your device. ___ 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
Re: [vdr] Can' read mkv with vdr-1.7.18 + mplayer + TT S2-6400 !
On 20.06.2011 22:03, Karim Afifi wrote: Hello, Since I have upgraded my hardware from TT Nexus to TT S2-6400, I can't read any mkv file anymore from my vdr-1.7.18 and MPlayer. It seems that VDR can't share the device. This limitation is very very annoying : Is there any patch for VDR and/or for MPlayer ? Do you know any workaround or any other solution ? if that would be the case then all nexus (old ff card) users would have the same problem imho the tt s2 6400 is not supportet by mplayer You've right. Do you know if there is any patch for MPlayer ? Or any other plugin ? Thanks a lot. Karim ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Can' read mkv with vdr-1.7.18 + mplayer + TT S2-6400 !
Hello, Since I have upgraded my hardware from TT Nexus to TT S2-6400, I can't read any mkv file anymore from my vdr-1.7.18 and MPlayer. It seems that VDR can't share the device. This limitation is very very annoying : Is there any patch for VDR and/or for MPlayer ? Do you know any workaround or any other solution ? Regards. Karim ___ Here is the log : logger: *** DEBUG: MPLAYER_RETURN: 0 logger: *** DEBUG: parsed output for ORIG_X: 1280 logger: *** DEBUG: parsed output for ORIG_Y: 544 logger: *** DEBUG: parsed output for ORIG_FPS: 24.000 logger: *** DEBUG: parsed output for ORIG_ASPECT: 0. logger: *** DEBUG: parsed output for VIDEO_FORMAT: avc1 logger: *** DEBUG: parsed output for AUDIO_CODEC: ffdca logger: *** INFO: Source Video has Resolution of 1280 x 544 ... logger: *** DEBUG: Film logger: *** DEBUG: Variable MAX_X has value 1024 logger: *** DEBUG: Variable NEW_Y has value 435 logger: *** INFO: For Sqare Pixels we would scale to 1024 x 435 ... logger: *** DEBUG: Variable XResTEMP has value 352 480 528 544 688 704 720 logger: *** DEBUG: Variable AnzahlVonXResTEMP has value 7 logger: *** DEBUG: Variable NEW_X has value 720 logger: *** DEBUG: setting REAL_Y = FULL_Y logger: *** DEBUG: Variable CMDLINE has value /usr/bin/mplayer -vo mpegpes -ao mpegpes -vf scale=720:435,expand=720:576:-1:-1:1,lavc=5000:25 -speed 1.04 -framedrop -cache 8192 -slave -nolirc -subpos 80 -sub-bg-color 0 -sub-bg-alpha 30 -quiet MPlayer 1.0rc4-4.5.2 (C) 2000-2010 MPlayer Team PLAYING /VIDEO/DIVX/fichier.mkv Cache fill: 0.00% (0 bytes) [mkv] Track ID 1: video (V_MPEG4/ISO/AVC), -vid 0 [mkv] Track ID 2: audio (A_DTS) French DTS 1509kbps, -aid 0, -alang fre [mkv] Will play video track 1. Matroska file format detected. VIDEO: [avc1] 1280x544 24bpp 24.000 fps0.0 kbps ( 0.0 kbyte/s) Opening /dev/dvb/adapter0/video0+audio0 DVB VIDEO DEVICE: : Device or resource busy Error opening/initializing the selected video_out (-vo) device. === Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders AUDIO: 48000 Hz, 2 ch, s16le, 1536.0 kbit/100.00% (ratio: 192000-192000) Selected audio codec: [ffdca] afm: ffmpeg (FFmpeg DTS) === Opening /dev/dvb/adapter0/audio0 DVB AUDIO DEVICE: Device or resource busy Failed to initialize audio driver 'mpegpes' Could not open/initialize audio device - no sound. Audio: no sound Video: no video ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr xine-lib eac3
Jose, Sorry, I was related the issue *before* your last patches. I will test them this week-end. Regards. Karim -Message d'origine- De : vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] De la part de Jose Alberto Reguero Envoyé : jeudi 30 septembre 2010 20:11 À : VDR Mailing List Objet : Re: [vdr] vdr xine-lib eac3 I can change eac3 audio channel without problem. Perhaps you have additional patches that cause that. Jose Alberto El Miércoles 29 Septiembre 2010, Karim Afifi escribió: Hello, Just to confirm that I've the same crash that dplu is talking about, with xineliboutput here. It occurs : - **Every time** I try to change audio track on HD e-ac3 channel. - Many time when I zap from SD to on HD e-ac3 channel. - Many time when I zap from HD e-ac3 to on HD e-ac3 channel. - No problem when using SD and HD no e-ac3 channels. Guys, many thanks for your job, I hope vdr will soon remain as stable on HD e-ac3 that with SD and HD non e-ac3 channels. Karim -Message d'origine- De : vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] De la part de dplu Envoyé : mercredi 29 septembre 2010 15:05 À : VDR Mailing List Objet : Re: [vdr] vdr xine-lib eac3 Hi Thanks for the patch, works nice now. Did you try to change audio channel ? I have a strange error reported also by french colleague : ffmpeg_audio_dec: augmentation du buffer à 98304 pour éviter sa saturation. (translation) = Increasing buffer size to 98304 to prevent overflow ffmpeg_audio_dec: unknown header with buf type 0x341 and xine-ui crash ... error in xiTK It happen when switching from fra to qaa (both e-ac3) and also when switching from ac3 live channels (like Einfestival HD or ITV HD) to records having e-ac3 tracks. It is Ok when coming from a mpeg audio channel (SD broadcast) I don't know if it is a xine problem sending bad information to ffmpeg or a bug in ffmpeg ... changing audio track (with # key) do not crash mplayer when playing the TS file By the way, many thanks for your work ;o)) Best regards Le Wednesday 29 September 2010 02:07:11 Jose Alberto Reguero, vous avez écrit : Here is a new version of the patch. Now it works with the sample. There was a bug in the last patch. Jose Alberto El Lunes 27 Septiembre 2010, dplu escribió: Thanks for the test, In fact I am not in covered area so I work with sample given by a colleague who live in good area on our forum The sample is very fresh and works perfectly with xineliboutput + vdr-sxfe with patch xineliboutputeac3_4.diff plus patch ff_audio_decoder to downmix 5.1 to 2.0 Maybe is there something in TS who is different from your country. It should be also interesting to have report from Italian users who experiment this audio encoding (not all are xbmc user I hope) Have a nice evening Best regards Le Monday 27 September 2010 22:42:06 Jose Alberto Reguero, vous avez écrit : I try the sample and don't work. I look into it. But you must try live tv or samples made with the patches, to see if it work. I try here with a channel whith eac3 with spectral extention and it work well. Jose Alberto ___ 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 __ Information provenant d'ESET Smart Security, version de la base des signatures de virus 5488 (20100929) __ Le message a été vérifié par ESET Smart Security. http://www.eset.com ___ 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 __ Information provenant d'ESET Smart Security, version de la base des signatures de virus 5493 (20100930) __ Le message a été vérifié par ESET Smart Security. http://www.eset.com ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr xine-lib eac3
Hello, Just to confirm that I've the same crash that dplu is talking about, with xineliboutput here. It occurs : - **Every time** I try to change audio track on HD e-ac3 channel. - Many time when I zap from SD to on HD e-ac3 channel. - Many time when I zap from HD e-ac3 to on HD e-ac3 channel. - No problem when using SD and HD no e-ac3 channels. Guys, many thanks for your job, I hope vdr will soon remain as stable on HD e-ac3 that with SD and HD non e-ac3 channels. Karim -Message d'origine- De : vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] De la part de dplu Envoyé : mercredi 29 septembre 2010 15:05 À : VDR Mailing List Objet : Re: [vdr] vdr xine-lib eac3 Hi Thanks for the patch, works nice now. Did you try to change audio channel ? I have a strange error reported also by french colleague : ffmpeg_audio_dec: augmentation du buffer à 98304 pour éviter sa saturation. (translation) = Increasing buffer size to 98304 to prevent overflow ffmpeg_audio_dec: unknown header with buf type 0x341 and xine-ui crash ... error in xiTK It happen when switching from fra to qaa (both e-ac3) and also when switching from ac3 live channels (like Einfestival HD or ITV HD) to records having e-ac3 tracks. It is Ok when coming from a mpeg audio channel (SD broadcast) I don't know if it is a xine problem sending bad information to ffmpeg or a bug in ffmpeg ... changing audio track (with # key) do not crash mplayer when playing the TS file By the way, many thanks for your work ;o)) Best regards Le Wednesday 29 September 2010 02:07:11 Jose Alberto Reguero, vous avez écrit : Here is a new version of the patch. Now it works with the sample. There was a bug in the last patch. Jose Alberto El Lunes 27 Septiembre 2010, dplu escribió: Thanks for the test, In fact I am not in covered area so I work with sample given by a colleague who live in good area on our forum The sample is very fresh and works perfectly with xineliboutput + vdr-sxfe with patch xineliboutputeac3_4.diff plus patch ff_audio_decoder to downmix 5.1 to 2.0 Maybe is there something in TS who is different from your country. It should be also interesting to have report from Italian users who experiment this audio encoding (not all are xbmc user I hope) Have a nice evening Best regards Le Monday 27 September 2010 22:42:06 Jose Alberto Reguero, vous avez écrit : I try the sample and don't work. I look into it. But you must try live tv or samples made with the patches, to see if it work. I try here with a channel whith eac3 with spectral extention and it work well. Jose Alberto ___ 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 __ Information provenant d'ESET Smart Security, version de la base des signatures de virus 5488 (20100929) __ Le message a été vérifié par ESET Smart Security. http://www.eset.com ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Looking for DVB-T card (TVHD compatible) for vdr
@igor and @nico, Thanks for your responses. In France, MPEG4 HDTV DVB-T will begin shortly (several weeks). I don't know yet if we will swap to DVB-T2 around 2009-2010 :-( Since I need two DVB-T tuners by vdrbox, I won't buy WinTV-HVR-4000, it will be too much expensive (env 190 € each in France !). It's better for me to choose a double tuner PCI DVB-T card. As any budget can receive DVB-T, even in HDTV mode, I plan to buy one of theses items : Choice 1 : http://www.fusionhdtv.co.kr/ENG/products/DVBTdual4.aspx = unfortunately, I didn't find this hardware in Europe. Where to buy gives glowlounge techno in UK, FNAC and Surcouf in France, but none of theses has the card. Could you please confirm that there is no compatibility problem, with this model in France ? If someone know a reseller in Europe, please give as the link ! Choice 2 : http://www.hauppauge.fr/pages/products/data_nova-t-500.html = No problem to find this card in France, but I am not 100% shure that the hardware will be TVHD compliant. Hauppauge doesn't communicate about that, contrary to fusionhdtv. @all, As usually, any comment will be appreciate. Thanks. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Looking for DVB-T card (TVHD compatible) for vdr
Hello, My vdrbox currently running with 2 Nexus cards. I plan to upgrade the box, for receiving several TVHD FTA channels (from SAT and TNT). At the end, I hope vdr could run with : - 1 x Technotrend S2-3200 HD - 1 x Nexus DVB-S (or 1 x Technotrend S2-3200 HD) - 1 x DVB-T double-tuner, TVHD compatible I am very interested by PCI-E double-tuner cards, like Cinergy 2400i DT, unfortunately there is no Linux driver yet, because PCI-E format. Then I've to choose one TVHD compatible double-tuner DVB-T in PCI format. I found the Hauppauge WinTV Nova-T500 but I don't know if this card is TVHD compatible. Is it true that all budget DVB-T cards (ie without hardware MPEG2 or 4 embedded) are TVHD compatible (like S2-3200 HD for DVB-S) ? Thanks for clarify this, and help me to buy the good card. If you know any other good card, please give me the link. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] xineliboutput and vdr-1.5.12 compile problems
Hello, I am using vdr-1.5.12 under kernel 2.6.23.12 - UTF-8. I've tried to compile 2 versions of xineliboutput without success : Xineliboutput - 1.0.0rc2 grep: ../../../include/vdr/osd.h: Aucun fichier ou répertoire de ce type xineliboutput.c:39:6: error: #error VDR versions 1.3.31 are not supported ! equalizer.c:14:3: error: #error VDR 1.3.7 not supported grep: ../../../include/vdr/osd.h: Aucun fichier ou répertoire de ce type g++ -O3 -pipe -Wall -Woverloaded-virtual -fPIC -g -c -D_GNU_SOURCE g++ -DPLUGIN_NAME_I18N='xineliboutput' -D_REENTRANT g++ -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 g++ -DXINELIBOUTPUT_VERSION='1.0.0rc2' -DUSE_ICONV=1 -Wall g++ -I../../../include -o xineliboutput.o xineliboutput.c xineliboutput.c:28:24: error: vdr/plugin.h: Aucun fichier ou répertoire de ce type In file included from xineliboutput.c:31: Xineliboutput - cvs 22-12-07 grep: ../../../include/vdr/osd.h: Aucun fichier ou répertoire de ce type xineliboutput.c:38:3: error: #error VDR versions 1.4.0 are not supported ! g++ -O3 -pipe -Wall -Woverloaded-virtual -fPIC -g -c -D_GNU_SOURCE g++ -DPLUGIN_NAME_I18N='xineliboutput' -D_REENTRANT g++ -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 g++ -DXINELIBOUTPUT_VERSION='1.0.0rc2' -DUSE_ICONV=1 -Wall g++ -I../../../include -o xineliboutput.o xineliboutput.c xineliboutput.c:28:24: error: vdr/plugin.h: Aucun fichier ou répertoire de ce type In file included from xineliboutput.c:31: i18n.h:14:22: error: vdr/i18n.h: Aucun fichier ou répertoire de ce type In file included from xineliboutput.c:33: Could you please tell me which version I've to use with vdr-1.5.12, and if there is a special patch to apply ? My target is to build a box with vdr-1.5.12 + patch S2-2300 and h264 support + xineliboutput. Thanks. Merry Christmas Happy New Year ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] xineliboutput and vdr-1.5.12 compile problems
Hello, I tried this Makefile on the lastest cvs xineliboutput, unfortunately it doesn't solve the problem. Did I missed something, or is there anything I could check ? Thanks. Try to use xineliboutput's Makefile from cvs dated 21-12-07. There has been some changes to the Makefile on 22nd which could cause the problem you are seeing with the current cvs version. The direct link to the Makefile I mean is http://xineliboutput.cvs.sourceforge.net/*checkout*/xineliboutput/vdr-xineli boutput/Makefile?revision=1.24 -Petri karim wrote: Hello, I am using vdr-1.5.12 under kernel 2.6.23.12 - UTF-8. I've tried to compile 2 versions of xineliboutput without success : Xineliboutput - 1.0.0rc2 grep: ../../../include/vdr/osd.h: Aucun fichier ou répertoire de ce type Xineliboutput - cvs 22-12-07 grep: ../../../include/vdr/osd.h: Aucun fichier ou répertoire de ce type xineliboutput.c:38:3: error: #error VDR versions 1.4.0 are not supported ! g++ -O3 -pipe -Wall -Woverloaded-virtual -fPIC -g -c -D_GNU_SOURCE g++ -DPLUGIN_NAME_I18N='xineliboutput' -D_REENTRANT g++ -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 g++ -DXINELIBOUTPUT_VERSION='1.0.0rc2' -DUSE_ICONV=1 -Wall g++ -I../../../include -o xineliboutput.o xineliboutput.c xineliboutput.c:28:24: error: vdr/plugin.h: Aucun fichier ou répertoire de ce type In file included from xineliboutput.c:31: i18n.h:14:22: error: vdr/i18n.h: Aucun fichier ou répertoire de ce type In file included from xineliboutput.c:33: current cvs version. Could you please tell me which version I've to use with vdr-1.5.12, and if there is a special patch to apply ? My target is to build a box with vdr-1.5.12 + patch S2-2300 and h264 support + xineliboutput. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR, WAVEFRONTIER and MULTISWITCHES
Hi, I am using two vdrboxes (two FF cards inside each box), and I need to receive 4 satellites, then I plan to buy : - a multi-lnb dish wavefrontier T90 - 4 x lnb's (quad models) - 4 multiswitch 41 (one for each FF card). By adjusting disecq.conf, I know that vdr is able to manage a 4 ways multiswitches, but is it the same for 6 or 8 lnbs ? Is there any limit ? Because there is a lot of cables, multiswitches will be near the LNB, outdoor position. Could you please advise give me some good outdoor 41 and 81 FF nexus dvb compliant ? Feedback and remarks from vdr users, about wavefrontier / multil nbs / multi switches, are welcome. Regards. ***Merry Chrismas to all !!! *** attachment: winmail.dat___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
