[vdr] VDR is the best program for DVB
Hello: VDR is the best program for DVB. I want to thank Klaus Schmidinger and staff for their fantastic work VDR and Plugins. You are the best! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR working with DVB-T Club 3D ZAP-TV240M?
On Tue, Nov 20, 2007 at 03:39:23PM +0200, Jere Malila wrote: > Hello, > > My friend asked if this product would work with VDR? Any ideas or anyone > using? > > http://www.club3d.nl/index.php/products/zaptv/item/14 > > -J- > > > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr Hello: VDR works perfectly with that card in the kernel have this driver: modinfo dvb_usb_dtt200u filename: /lib/modules/2.6.21.6/kernel/drivers/media/dvb/dvb-usb/dvb-usb-dtt200u.ko license:GPL version:1.0 description:Driver for the WideView/Yakumo/Hama/Typhoon/Club3D DVB-T USB2.0 devices <<-< author: Patrick Boettcher <[EMAIL PROTECTED]> srcversion: C0ECD158EB5AFBC4C741185 alias: usb:v14AAp0220d*dc*dsc*dp*ic*isc*ip* alias: usb:v14AAp0226d*dc*dsc*dp*ic*isc*ip* alias: usb:v14AAp0225d*dc*dsc*dp*ic*isc*ip* alias: usb:v14AAp022Bd*dc*dsc*dp*ic*isc*ip* alias: usb:v14AAp022Ad*dc*dsc*dp*ic*isc*ip* alias: usb:v14AAp0221d*dc*dsc*dp*ic*isc*ip* alias: usb:v14AAp0222d*dc*dsc*dp*ic*isc*ip* alias: usb:v14AAp0301d*dc*dsc*dp*ic*isc*ip* alias: usb:v14AAp0201d*dc*dsc*dp*ic*isc*ip* depends:dvb-usb vermagic: 2.6.21.6 SMP mod_unload parm: debug:set debugging level (1=info,xfer=2 (or-able)). (int) This firmware also need dvb-usb-wt220u-02.fw. You can download it from http://www.linuxtv.org/downloads/firmware/dvb-usb-wt220u-02.fw You have to put it in /usr/lib/hotplug/firmware/dvb-usb-wt220u-02.fw. You have more info in less /usr/src/linux/Documentation/dvb/README.dvb-usb. Good luck ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr xine-lib eac3
On Martes, 10 de julio de 2012 22:53:44 Karim Afifi escribió: > 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 > You can try latest vdr and latest xine-lib-1.2 without patches. I use also a patch(attached) for xine-lib-1.2 but perhaps you don't need it. But I don't know if spdif works because decoding eac3 is done via ffmpeg. Jose Alberto > > -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/vdrdiff -r 748c5603d2df src/combined/ffmpeg/ff_audio_decoder.c --- a/src/combined/ffmpeg/ff_audio_decoder.c Wed Feb 29 08:35:12 2012 +0200 +++ b/src/combined/ffmpeg/ff_audio_decoder.c Mon Jun 18 17:17:58 2012 +0200 @@ -448,7 +448,8 @@ /* pad input data */ memset(&this->buf[this->size], 0, FF_INPUT_BUFFER_PADDING_SIZE); - while (this->size>0) { + bytes_consumed = 0; + while (this->size>bytes_consumed) { decode_buffer_size = AVCODEC_MAX_AUDIO_FRAME_SIZE; bytes_consumed = @@ -555,8 +556,8 @@ offset += bytes_consumed; } - /* reset internal accumulation buffer */ - this->size = 0; + if (offset) +memmove(this->buf, &this->buf[offset], this->size); } } } ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
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
Re: [vdr] vdr xine-lib eac3
On Miércoles, 11 de julio de 2012 22:43:04 Karim Afifi escribió: > @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 > The patch is because ffmpeg eac3 takes whole eac3 frames, and the remaining part of the frames are lost without the patch. It is noticed by bad audio and lost audio parts. I have only one channel with eac3, and it only has two channels. I connect the computer with a hdmi cable to a tv. I am not using spdif. Jose Alberto > -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 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr and raspberry pi
I am trying to play vdr recordings with a raspberry pi and the not edited recording play well, but a edited recording don't play. Is there are any differences between a not edited recording and a edited one? The recordings are made with vdr 2.0. Thanks. Jose Alberto ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr and raspberry pi
On Martes, 28 de mayo de 2013 18:31:19 Klaus Schmidinger escribió: > On 28.05.2013 17:16, Jose Alberto Reguero wrote: > > I am trying to play vdr recordings with a raspberry pi and the not edited > > recording play well, but a edited recording don't play. Is there are any > > differences between a not edited recording and a edited one? > > The recordings are made with vdr 2.0. > > Do they not play at all (not even a single frame) or are there > disturbences at/after the editing points? > > Klaus > They not play at all. I get black screen and no audio. Thanks. Jose Alberto ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr and raspberry pi
On Jueves, 30 de mayo de 2013 06:47:00 JJussi escribió: > Maybe that file starts with edit.. You cut from start to point where > program starts.. > Yes, the edited program start some minutes after that the not edited one. Perhaps PAT,PMT o something with I-FRAME? Jose Alberto > On 30.5.2013 1.10, Klaus Schmidinger wrote: > > On 28.05.2013 19:00, Jose Alberto Reguero wrote: > >> On Martes, 28 de mayo de 2013 18:31:19 Klaus Schmidinger escribió: > >>> On 28.05.2013 17:16, Jose Alberto Reguero wrote: > >>>> I am trying to play vdr recordings with a raspberry pi and the not > >>>> edited > >>>> recording play well, but a edited recording don't play. Is there > >>>> are any > >>>> differences between a not edited recording and a edited one? > >>>> The recordings are made with vdr 2.0. > >>> > >>> Do they not play at all (not even a single frame) or are there > >>> disturbences at/after the editing points? > >>> > >>> Klaus > >> > >> They not play at all. I get black screen and no audio. > > > > Well, that's odd. > > I can think of no reason why at least the beginning of an edited > > recording shouldn't play... > > > > 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] vdr and raspberry pi
I am using xbmc to reproduce recordings of other computer, and I have also a vdr and vnsi plugin in the raspberry. Jose Alberto On Jueves, 30 de mayo de 2013 23:36:47 Torgeir Veimo escribió: > There's now experimental support for libxine, so you can use > xineliboutput with vdr-sxfe. See here; > http://www.vdr-portal.de/board18-vdr-hardware/board98-arm-co/118588-rasperry > -pi-xine-plugin/ > > Google translate should let get the gist of details required to try it out. > > On Thu, May 30, 2013 at 11:28 PM, André Weidemann > > wrote: > > On 28.05.2013 19:00, Jose Alberto Reguero wrote: > >> On Martes, 28 de mayo de 2013 18:31:19 Klaus Schmidinger escribió: > >>> On 28.05.2013 17:16, Jose Alberto Reguero wrote: > >>>> I am trying to play vdr recordings with a raspberry pi and the not > >>>> edited > >>>> recording play well, but a edited recording don't play. Is there are > >>>> any > >>>> differences between a not edited recording and a edited one? > >>>> The recordings are made with vdr 2.0. > >>> > >>> Do they not play at all (not even a single frame) or are there > >>> disturbences at/after the editing points? > >>> > >>> Klaus > >> > >> They not play at all. I get black screen and no audio. > > > > Which software do you use to play the VDR recordings? Proof me wrong, but > > as far as I know, there is no VDR-plugin which can output the video > > directly via HDMI on the Raspberry Pi. > > > > André > > > > ___ > > 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] vdr and raspberry pi
On Jueves, 30 de mayo de 2013 12:38:14 Jose Alberto Reguero escribió: > On Jueves, 30 de mayo de 2013 06:47:00 JJussi escribió: > > Maybe that file starts with edit.. You cut from start to point where > > program starts.. > > Yes, the edited program start some minutes after that the not edited one. > Perhaps PAT,PMT o something with I-FRAME? > > Jose Alberto > I made other test. I add manually two marks to a recording, edit the recording and the resulting recording play well. So the problem must be in the marks. I am using the plugin markad to make the marks, so the marks made with the plugin are not good. Thanks. Jose Alberto > > On 30.5.2013 1.10, Klaus Schmidinger wrote: > > > On 28.05.2013 19:00, Jose Alberto Reguero wrote: > > >> On Martes, 28 de mayo de 2013 18:31:19 Klaus Schmidinger escribió: > > >>> On 28.05.2013 17:16, Jose Alberto Reguero wrote: > > >>>> I am trying to play vdr recordings with a raspberry pi and the not > > >>>> edited > > >>>> recording play well, but a edited recording don't play. Is there > > >>>> are any > > >>>> differences between a not edited recording and a edited one? > > >>>> The recordings are made with vdr 2.0. > > >>> > > >>> Do they not play at all (not even a single frame) or are there > > >>> disturbences at/after the editing points? > > >>> > > >>> Klaus > > >> > > >> They not play at all. I get black screen and no audio. > > > > > > Well, that's odd. > > > I can think of no reason why at least the beginning of an edited > > > recording shouldn't play... > > > > > > 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 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] xineliboutput plugin with xine
I am using the xineliboutput plugin with xine program instead of vdr-sxfe. All work except rewind recordings. Anyone know how to fix this? Thanks. Jose Alberto Enviado desde mi dispositivo android. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] CAM questions
I have two usb cards, one with ci. I have a cam that can decrypt multiple streams, but if I am recording a encrypted channel and I tune to another encrypted channel, I get channel not available. It is possible to tune two encrypted channels with that setup? Jose Alberto Enviado desde mi dispositivo android. -Original Message- From: Kende To: VDR Mailing List Sent: mié, 07 may 2014 14:00 Subject: Re: [vdr] CAM questions On 05/07/2014 01:37 PM, Michal Novotny wrote: > Are CI somehow paired with a specific card or tuner? Let's say I have > DVB-S with CI (Hauppauge WinTV-NOVA-CI PCI) and DVB-C card without CI > (TerraTec Cinergy T PCIe dual). Would it work so that the encrypted > stream from DVB-C is decrypted by Conax CAM in CI that is attached to > DVB-S card? Pairing is between the CAM and the smartcard, it's not paired to the tuner or TV so you can place your CAM to any device and it still decrypts. I've never tried to use DVB-S card for decrypting DVB-C stream but I don't see why it wouldn't work. > How many channels can be typically decrypted at the same time? Is it > limited by the maximum number of pids or by the bandwidth that the CAM > is able to decrypt? VDR asks from the CAM how many streams it can decrypt so it depends on the CAM. > My goal is to be able to watch one channel and record at least other 2 > channels. So I'd like to buy TBS6680 dual tuner with dual CI (but I > would use just one CAM and the second CI slot would stay unused). I > would use this card together with the TerraTec Cinergy T. So there > would be 3 DVB-C tuners and one CAM. Would this combination work as I > wish? It should. I have two TDA10023 single tuner DVB-C PCI cards and one TBS6285 quad tuner DVB-C PCIe card with CI attached to one of the TDA10023 cards. Decryption works on any card but only one channel at the time with my Conax CAM. Please note that at least TBS6285 is still early development and it's not that reliable or error free. I have constant bit errors on one of the four tuners and occasional freezes that require kernel module reloading. -- Kende ___ 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] [PATCH] Add SubsystemId for usb cards
This patch add SubsystemId for usb cards, to be able to make changes to GetSignalQuality and GetSignalStrength functions. Jose Alberto--- vdr-2.1.6/dvbdevice.c 2014-03-16 11:38:31.0 +0100 +++ vdr-actual/dvbdevice.c 2014-05-24 13:06:25.358513231 +0200 @@ -1750,12 +1735,26 @@ uint32_t cDvbDeviceProbe::GetSubsystemId if (char *s = ReadLine.Read(f)) SubsystemId = strtoul(s, NULL, 0) << 16; fclose(f); + } else { +FileName = cString::sprintf("/sys/class/dvb/%s/device/idVendor", e->d_name); +if ((f = fopen(FileName, "r")) != NULL) { + if (char *s = ReadLine.Read(f)) + SubsystemId = strtoul(s, NULL, 16) << 16; + fclose(f); +} } FileName = cString::sprintf("/sys/class/dvb/%s/device/subsystem_device", e->d_name); if ((f = fopen(FileName, "r")) != NULL) { if (char *s = ReadLine.Read(f)) SubsystemId |= strtoul(s, NULL, 0); fclose(f); + } else { +FileName = cString::sprintf("/sys/class/dvb/%s/device/idProduct", e->d_name); +if ((f = fopen(FileName, "r")) != NULL) { + if (char *s = ReadLine.Read(f)) + SubsystemId |= strtoul(s, NULL, 16); + fclose(f); +} } break; } ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Diseqc question
I have a double LNB. I have a stb without diseqc capabilities and I want to use it with the default diseqc port A, and I want to use vdr with the diseqc port B. It is that possible? Jose Alberto ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Diseqc question
El Martes, 24 de junio de 2014 13:25:15 Klaus Schmidinger escribió: > On 24.06.2014 12:58, Jose Alberto Reguero wrote: > > I have a double LNB. I have a stb without diseqc capabilities and I want to > > use it with the default diseqc port A, and I want to use vdr with the > > diseqc port B. > > It is that possible? > > Does this LNB point to two neighboring sat positions and have one > cable connector, or does it point to only one sat position and > have two cable connectors? > > Klaus > > It is only one sat position and two cable connectors. Jose Alberto ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Diseqc question
El Martes, 24 de junio de 2014 15:38:14 Klaus Schmidinger escribió: > On 24.06.2014 13:45, Jose Alberto Reguero wrote: > > El Martes, 24 de junio de 2014 13:25:15 Klaus Schmidinger escribió: > >> On 24.06.2014 12:58, Jose Alberto Reguero wrote: > >>> I have a double LNB. I have a stb without diseqc capabilities and I want > >>> to use it with the default diseqc port A, and I want to use vdr with the > >>> diseqc port B. > >>> It is that possible? > >> > >> Does this LNB point to two neighboring sat positions and have one > >> cable connector, or does it point to only one sat position and > >> have two cable connectors? > >> > >> Klaus > >> > >> > > > > It is only one sat position and two cable connectors. > > Then the next question is whether these two connectors are for the (separate) > horizontal and vertical band, or whether they both provide all bands. In the > latter case it should just work. > > Klaus > Both provide all bands. They point to ASTRA 19.2E. I use this diseq.conf entries: S28.2E 11700 V 9750 t v W15 A W15 t S28.2E 9 V 10600 t v W15 A W15 T S28.2E 11700 H 9750 t V W15 A W15 t S28.2E 9 H 10600 t V W15 A W15 T S19.2E 11700 V 9750 t v W15 B W15 t S19.2E 9 V 10600 t v W15 B W15 T S19.2E 11700 H 9750 t V W15 B W15 t S19.2E 9 H 10600 t V W15 B W15 T (28.2E is just a fake entry) But when I tune a channel with vdr, the stb lost the signal. Jose Alberto ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Diseqc question
El Martes, 24 de junio de 2014 16:47:57 Klaus Schmidinger escribió: > On 24.06.2014 16:32, Jose Alberto Reguero wrote: > > El Martes, 24 de junio de 2014 15:38:14 Klaus Schmidinger escribió: > >> On 24.06.2014 13:45, Jose Alberto Reguero wrote: > >>> El Martes, 24 de junio de 2014 13:25:15 Klaus Schmidinger escribió: > >>>> On 24.06.2014 12:58, Jose Alberto Reguero wrote: > >>>>> I have a double LNB. I have a stb without diseqc capabilities and I > >>>>> want to use it with the default diseqc port A, and I want to use vdr > >>>>> with the diseqc port B. > >>>>> It is that possible? > >>>> > >>>> Does this LNB point to two neighboring sat positions and have one > >>>> cable connector, or does it point to only one sat position and > >>>> have two cable connectors? > >>>> > >>>> Klaus > >>>> > >>>> > >>> > >>> It is only one sat position and two cable connectors. > >> > >> Then the next question is whether these two connectors are for the > >> (separate) > >> horizontal and vertical band, or whether they both provide all bands. In > >> the > >> latter case it should just work. > >> > >> Klaus > >> > > Both provide all bands. They point to ASTRA 19.2E. > > > > I use this diseq.conf entries: > > > > S28.2E 11700 V 9750 t v W15 A W15 t > > S28.2E 9 V 10600 t v W15 A W15 T > > S28.2E 11700 H 9750 t V W15 A W15 t > > S28.2E 9 H 10600 t V W15 A W15 T > > > > S19.2E 11700 V 9750 t v W15 B W15 t > > S19.2E 9 V 10600 t v W15 B W15 T > > S19.2E 11700 H 9750 t V W15 B W15 t > > S19.2E 9 H 10600 t V W15 B W15 T > > > > (28.2E is just a fake entry) > > But when I tune a channel with vdr, the stb lost the signal. > > If both connectors provide all bands, you shouldn't need the 'A/B' > commands. > > Do you have a link to the specs of that LNB? > > Klaus > It is a Opticum. I buy it in amazon. http://www.dipolnet.com/twin_lnb_opticum-orton_ltp-04h_premium_0_1db_A9842.htm Jose Alberto ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Diseqc question
El Martes, 24 de junio de 2014 17:22:08 Jose Alberto Reguero escribió: > El Martes, 24 de junio de 2014 16:47:57 Klaus Schmidinger escribió: > > On 24.06.2014 16:32, Jose Alberto Reguero wrote: > > > El Martes, 24 de junio de 2014 15:38:14 Klaus Schmidinger escribió: > > >> On 24.06.2014 13:45, Jose Alberto Reguero wrote: > > >>> El Martes, 24 de junio de 2014 13:25:15 Klaus Schmidinger escribió: > > >>>> On 24.06.2014 12:58, Jose Alberto Reguero wrote: > > >>>>> I have a double LNB. I have a stb without diseqc capabilities and I > > >>>>> want to use it with the default diseqc port A, and I want to use > > >>>>> vdr with the diseqc port B. It is that possible? > > >>>> > > >>>> Does this LNB point to two neighboring sat positions and have one > > >>>> cable connector, or does it point to only one sat position and > > >>>> have two cable connectors? > > >>>> > > >>>> Klaus > > >>> > > >>> It is only one sat position and two cable connectors. > > >> > > >> Then the next question is whether these two connectors are for the > > >> (separate) horizontal and vertical band, or whether they both provide > > >> all bands. In the latter case it should just work. > > >> > > >> Klaus > > > > > > Both provide all bands. They point to ASTRA 19.2E. > > > > > > I use this diseq.conf entries: > > > > > > S28.2E 11700 V 9750 t v W15 A W15 t > > > S28.2E 9 V 10600 t v W15 A W15 T > > > S28.2E 11700 H 9750 t V W15 A W15 t > > > S28.2E 9 H 10600 t V W15 A W15 T > > > > > > S19.2E 11700 V 9750 t v W15 B W15 t > > > S19.2E 9 V 10600 t v W15 B W15 T > > > S19.2E 11700 H 9750 t V W15 B W15 t > > > S19.2E 9 H 10600 t V W15 B W15 T > > > > > > (28.2E is just a fake entry) > > > But when I tune a channel with vdr, the stb lost the signal. > > > > If both connectors provide all bands, you shouldn't need the 'A/B' > > commands. > > > > Do you have a link to the specs of that LNB? > > > > Klaus > > It is a Opticum. I buy it in amazon. > > http://www.dipolnet.com/twin_lnb_opticum-orton_ltp-04h_premium_0_1db_A9842.h > tm > > Jose Alberto > > I did another test, and if both channels are vertical there are not problems. But if the stb is in a vertical channel, and vdr is in a horizontal channel, the stb loose the signal. Jose Alberto ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Problem with rpihddevice OSD
I am using rpihddevice plugin with a raspberry pi in text mode, and if I start the plugin with -P "rpihddevice" I have the OSD, but the video is not played. If I start with -P "rpihddevice -d" I have the video, but I have not the OSD. There can be OSD and video with rpihddevice in text mode? Thanks. Jose Alberto ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Problem with rpihddevice OSD
Thanks that solve the problem. Jose Alberto El 11/03/2016 21:27, Thomas Reufer escribió: > > I guess you’re just running out of GPU memory - try adding "gpu_mem=128" to > /boot/config.txt. 64MB should be fine if you’re using VDR’s default skins, > increase the amount for more complex skins. > > Regards, > Thomas > > > Am 11.03.2016 um 18:42 schrieb Jose Alberto Reguero > > : > > > > I am using rpihddevice plugin with a raspberry pi in text mode, and if I > > start the plugin with -P "rpihddevice" I have the OSD, but the video is not > > played. If I start with -P "rpihddevice -d" I have the video, but I have > > not the OSD. > > There can be OSD and video with rpihddevice in text mode? > > > > Thanks. > > > > 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 mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Upnp plugin
I am trying to use the upnp plugin, but I can’t find documentation. Do you know the format of the config file directories.conf ? Or how I can add a multimedia directory? Jose Alberto ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Upnp plugin
El 01/10/2016 22:59, Lucian Muresan escribió: > > On 29.09.2016 14:59, Peer Oliver Schmidt wrote: > > Isn't the UPnP plugin solely for the purpose to use UPnP renderes with > > VDR recordings and stuff, and not outside media files?! > > The UPnP Plugin also has a "sub-plugin" for other media files, but I > never got that one working, maybe it isn't even finished. Accessing live > TV and recordings used to work, but I do not use it anymore due to > insanely heavy load it puts on my VDR machine... > > Greetings, > Lucian Thanks, for me it work with live tv, but don't work with the recordings. Jose Alberto. ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Upnp plugin
Thanks, I give it a try. Jose Alberto. El 02/10/2016 14:52, Richard F escribió: > > Have you looked at Minidlna? > I've been using it for a while now to provide upnp access to various media. > It's lightweight and doesn't slow the server down noticeably, once it's > scanned the directories. I normally access the VDR directory via SMB, but I > added it to the minidlna config to test, and it worked OK. > > HTH Richard > > - On 28 Sep, 2016, at 14:26, Jose Alberto Reguero > jaregu...@telefonica.net wrote: > > > I am trying to use the upnp plugin, but I can’t find documentation. Do you > > know > > the format of the config file directories.conf ? Or how I can add a > > multimedia > > directory? > > > > Jose Alberto > > ___ > 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 and vaapi
I upgrade to fedora 25, and now vaapi with xineliboutput don't work for h264 channels. Works well with softhddevice. Attached is a log from vdr-sxfe. Any hint? Jose Alberto log Description: ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput and vaapi
El 09/02/2017 11:02, Petri Hintukainen escribió: > > ti, 2017-01-31 kello 18:21 +0100, Jose Alberto Reguero kirjoitti: > > I upgrade to fedora 25, and now vaapi with xineliboutput don't work > > for h264 channels. Works well with softhddevice. Attached is a log > > from vdr-sxfe. > > > > Any hint? > > Please try upgrading xine-lib from hg. > > I've fixed one vaapi decoding issue today. It was causing video to > break every 1-2 seconds (and no video at all if guarded_render was > disabled in xine config). > The log doesn't look exactly the same, so this could be also different > issue. > Thank you. It seem to solve the problem. I did more tests later. Jose Alberto. ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Trouble with DVB-T2 on frontend 1
I have another card with the same problem, it has frontend0 and frontend1and I modify vdr to open always demux0 dvr0 and net0 instead of demux1, dvr1 and net1, and work well with my card.Jose AlbertoEnviado desde mi Huawei Mensaje original Asunto: Re: [vdr] Trouble with DVB-T2 on frontend 1De: Marko M鋕el� Para: VDR Mailing List CC: On Wed, Nov 29, 2017 at 11:13:24AM +0100, Klaus Schmidinger wrote:>>The second startup is for a tweak where I removed >>/dev/dvb/adapter0/frontend0 and renamed frontend1 to frontend0. On >>this startup, VDR will not complain anything, but it will not find any >>signal either. It properly detects the MN88473, but perhaps improperly >>claims that it provides DVB-T along with DVB-T2 and DVB-C.>>Well, from the information that VDR gets from the driver, it does >support DVB-T, -T2 and -C:>> frontend 0/0 provides DVB-T,DVB-T2,DVB-C with > QPSK,QAM16,QAM32,QAM64,QAM128,QAM256 ("Panasonic MN88473")>>If this is not correct, I assume it's a driver problem.I made some further experiments today. It turns out that frontend1 indeed supports both DVB-T and DVB-T2 (and presumably DVB-C).Furthermore, with the trick sudo mv /dev/dvb/adapter0/frontend1 /dev/dvb/adapter0/frontend0I got VDR to display both DVB-T and DVB-T2 programs. The only difference from my previous attempts was that this time, I did not rename the old frontend0 to frontend2. The only frontend device descriptor that existed in the file system was frontend0.The reception is not the best here (especially on windy or rainy days, in particular with DVB-T2), and it is possible that during my previous attempts, the DVB-T2 signal was too weak to get the tuner to lock on it in reasonable time. Also, the USB stick might not have the best analog signal path or the best tuner.So, the good news is that the device indeed works with this little tweak. It probably is not worth the effort to implement something in dvbdevice.c that would allow this device to work without tweaking /dev/dvb/.Now I will only have to figure out how to get the remote control to work.Best regards, Marko___vdr mailing listvdr@linuxtv.orghttps://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] diseq.conf
I have a lnb monoblock pointing to astra 19.2E hotbird, with a internal diseq 2x1 wich I use with diseq enabled and the default diseq.conf: S19.2E 11700 V 9750 t v W15 [E0 10 38 F0] W15 A W15 t S19.2E 9 V 10600 t v W15 [E0 10 38 F1] W15 A W15 T S19.2E 11700 H 9750 t V W15 [E0 10 38 F2] W15 A W15 t S19.2E 9 H 10600 t V W15 [E0 10 38 F3] W15 A W15 T S13.0E 11700 V 9750 t v W15 [E0 10 38 F4] W15 B W15 t S13.0E 9 V 10600 t v W15 [E0 10 38 F5] W15 B W15 T S13.0E 11700 H 9750 t V W15 [E0 10 38 F6] W15 B W15 t S13.0E 9 H 10600 t V W15 [E0 10 38 F7] W15 B W15 T I have another lnb that point to astra 28.2E. Can I use another diseq 2x1 to join this two lnbs? If it is posible, how must be the diseq.conf with these two diseq in cascade? Thanks. Jose Alberto Reguero Enviado desde mi Huawei ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDRAdmin-AM with UTF-8 support?
El Martes, 27 de Marzo de 2007, Harald Milz escribió: > Hi, > > is anyone working on a UTF-8 version of VDRadmin-AM? I'm using vdr with the > UTF8 patch (de and ru) and need to always select UTF8 manually in the > browser to avoid seeing the à stuff. Looking at the html files in > template/default/, I see everything is hardcoded in iso-8859-1, but that > should be a configuration option. Setting LANG=de_DE.utf8 doesn't help, it > is silently ignored. > > Anyone? > > THX. I run: sed -i -e s/ISO-8859-1/UTF-8/g *.html in the template/default/ directory. Jose Alberto ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Re: VDRAdmin-AM with UTF-8 support?
El Miércoles, 28 de Marzo de 2007, Lucian Muresan escribió: > Jose Alberto Reguero wrote: > > El Martes, 27 de Marzo de 2007, Harald Milz escribió: > >> Hi, > >> > >> is anyone working on a UTF-8 version of VDRadmin-AM? I'm using vdr with > >> the UTF8 patch (de and ru) and need to always select UTF8 manually in > >> the browser to avoid seeing the à stuff. Looking at the html files in > >> template/default/, I see everything is hardcoded in iso-8859-1, but that > >> should be a configuration option. Setting LANG=de_DE.utf8 doesn't help, > >> it is silently ignored. > >> > >> Anyone? > >> > >> THX. > > > > I run: > > > > sed -i -e s/ISO-8859-1/UTF-8/g *.html > > > > in the template/default/ directory. > > Andreas Mair already adopted my UTF-8 patch for the vdradmin locales, > months and versions ago. It patches the makefile and adds targets for > generating the UTF-8 locales out of the stock ones. For more info, check > this thread: http://www.linuxtv.org/pipermail/vdr/2006-July/010116.html > > Regards, > Lucian > I use make.sh utf8add and make.sh po but the html files in template/default/ still have references to ISO-8859-1, as Harald Milz says, and firefox put the encoding to ISO-8859-1. That is with vdradmin-am-3.5.3. Jose Alberto ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] plugin writing - need help with C
El Viernes, 13 de Abril de 2007, Simon Baxter escribió: > Hi. > > I'm modifying a non-published pvrinput variation which sends IR commands > to a set box box - specifically, the channel number stored in > channels.conf. > > 12345J2:6:C12:C:0:301:300:305:A1:62006:0:1009:0 > FOODJ2:63:C12:C:0:301:300:305:A1:62008:0:1019:0 >^^ - channel number to send to external digi-box > > It works fine, sending single-digit channel numbers but fails to send > double digit. i.e. channels 1-9 are ok, but 10+ fail. > > This fails because there are only codes in the lircd.conf for 0-9. > > Here's an excerpt from the plugin which sends the commands: > > redremote.h > > class cRedRemote : public cThread { > public: > cRedRemote(); > ~cRedRemote(); > > int Open(); > void Tune(int channel); > void Send(char *text); > > > > redremote.c > > void cRedRemote::Send(char *text) > { > > char buf[100]; > snprintf(buf,sizeof(buf), "SEND_ONCE ADB_ICAN3000 %s\n",text); > > write(fd,buf,strlen(buf)); > close(fd); > fd = -1; > } > > > > My question is this. I need to modify the channel sent, so that double > (or triple) channel numbers are sent as '6 3' or '1 1 7' rather than '63' > or '117'. i.e. put spaces between the letters. > > I'm really out of my depth - can anyone point me in the right direction? > > Thanks > > Simon > > You can try something like that: char txt2[strlen(txt) * 2]; int i = 0; int j = 0; while (i < strlen(txt) - 1) { txt2[j] = txt[i]; i++; j++; txt2[j] = ' '; j++; } txt2[j] = txt[i]; j++; txt2[j] = '\0'; Jose Alberto ___ vdr mailing list [EMAIL PROTECTED] http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] plugin writing - need help with C
El Viernes, 13 de Abril de 2007, Simon Baxter escribió: > > One more thing - how do I convert a %d variable to a %s string first? > > > > My 'txt' variable is currently an integer. > > Strike that - works a treat: > > > void cRedRemote::Tune(int channel) > { > char buf[10]; > sprintf(buf,"%d",channel); > log(1,"Setting digibox to channel %d",channel); > char *p = buf; > > /* SBB Fudge > */ > char txt2[strlen(buf) * 2]; > int i = 0; > int j = 0; > while (i < strlen(buf) - 1) { > txt2[j] = buf[i]; > i++; > j++; > txt2[j] = ' '; > j++; > } > txt2[j] = buf[i]; > j++; > txt2[j] = '\0'; > > log(0,"SBB Channel Produced by Fudge '%s'",txt2); > > Send(txt2); > > > If you like more compact code: char txt2[strlen(buf) * 2]; int i = 0; int j = 0; while (i < strlen(buf) - 1) { txt2[j++] = buf[i++]; txt2[j++] = ' '; } txt2[j++] = buf[i]; txt2[j] = '\0'; Jose Alberto ___ vdr mailing list [EMAIL PROTECTED] http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] H.264 updates for VDR-1.5.9
El Jueves, 30 de Agosto de 2007, Hannu Tirkkonen escribió: > On Thu, Aug 30, 2007 at 12:05:08AM +0300, Hannu Tirkkonen wrote: > > I did apply this h264 patch and streamdev patch from: > > http://www.vdr-developer.org/mantisbt/view.php?id=382 > > > > Now the load of the server is low when tuned to Canal+ HD and I can watch > > the stream using vlc. The recording at least outputs something to hard > > disk ;) > > Well... the video part of the recordings seems to be corrupted. > vlc cannot show any video; there's only audio. > > projectx says (hundreds of lines on 34MB recording): > !> error in pes_extension of pes-ID 0xBD @ pos: 112153 (1554 / 14 / 15 / > true / false) -> found PES-ID 0xBD (private stream 1) @ 112153 > !> error in pes_extension of pes-ID 0xE0 @ pos: 134640 (2048 / 14 / 15 / > true / false) !> error in pes_extension of pes-ID 0xE0 @ pos: 188715 (2048 > / 14 / 15 / true / false) !> error in pes_extension of pes-ID 0xE0 @ pos: > 247087 (2048 / 19 / 20 / true / false) I have this errors also with the ttxtsubs .They are not important in mpeg-2 streams. Perhaps ttxtsubs corupts the mpeg-4 stream. Jose Alberto > -> more than 500 warnings/errors, stop logging.. > -> dropping video data, GOP larger than 6MB > -> dropping video data, GOP larger than 6MB > > od does find 00 00 01 09 sequences from the file. > > The live stream can be watched with vlc, and saving > the stream with vlc creates a file that can be watched again with mplayer > or vlc. > > There is 34MB of the recording on http://hotel.hanu.com/~hanu/h264 > > ...hanu > > ___ > 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.5.11 & subtitling problems
El Sábado, 10 de Noviembre de 2007, Reinhard Nissl escribió: > Hi, > > Reinhard Nissl schrieb: > >>> Though, a cleaner solution would be to fix the result buffer to allow > >>> retrieving any packet as soon as it is completely available in the > >>> buffer (final subtitle packets are about 100 bytes in size). > >> > >> That sounds like the right thing to do. > >> Can you suggest a patch for this? > > > > I hope to get something ready till tomorrow 12:00. > > See attachment. Tested in transfer mode with audio packets only (= > radio), as there is no broadcast running which would provide subtitles. > > Bye. This patch fix problems with pvrinput radio an CRepacker. Thanks. Jose Alberto ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.5.11 & subtitling problems
El Domingo, 11 de Noviembre de 2007, Jose Alberto Reguero escribió: > El Sábado, 10 de Noviembre de 2007, Reinhard Nissl escribió: > > Hi, > > > > Reinhard Nissl schrieb: > > >>> Though, a cleaner solution would be to fix the result buffer to allow > > >>> retrieving any packet as soon as it is completely available in the > > >>> buffer (final subtitle packets are about 100 bytes in size). > > >> > > >> That sounds like the right thing to do. > > >> Can you suggest a patch for this? > > > > > > I hope to get something ready till tomorrow 12:00. > > > > See attachment. Tested in transfer mode with audio packets only (= > > radio), as there is no broadcast running which would provide subtitles. > > > > Bye. > > This patch fix problems with pvrinput radio an CRepacker. > Thanks. > Jose Alberto > I still have problems with this patch and pvrinput and live radio, with CRepacker. If I disable CRepacker, the live radio is ok. Any ideas why to debug it? Thanks. JHose Alberto ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.5.11 & subtitling problems
El Domingo, 18 de Noviembre de 2007, Reinhard Nissl escribió: > Hi, > > Jose Alberto Reguero schrieb: > > I still have problems with this patch and pvrinput and live radio, with > > CRepacker. If I disable CRepacker, the live radio is ok. Any ideas why to > > debug it? > > I need some more information. From what I guess, pvrinput provides a TS > stream, VDR runs in transfermode and outputs the remuxed stream via a FF > card. Is this correct? > Pvrinput is for analog hauppauge cards with harware encoder. Radio is a bit diferent, that tv because the card can't provide a mpeg audio only stream but a mpeg audio stream with a blank mpeg video. Audio channels have pid=0 so remux left only the audio part. If I put video pid in the radio channels in channels.conf then there is no problem with CRepacker. I use xineliboutput for the output. > What are the problems you are seeing with cAudioRepacker enabled? > The problems I have are that sometimes, the audio is not completely smooth, they have some breaks, in live radio. > Are there any problems when you replay a radio recording? > The recordings play without problems. > Are there any logfile entries mentioning a problem? > There are not any messages in the log files. > Bye. Thanks. Jose Alberto ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Fix Pid not available error in the streamdev plugin VDR-VDR connection
This patch fix the error "Pid xxx not available" in the streamdev plugin with VDR-VDR connection, that cause not tunning to the channel. The problem is that sometimes, when cConnectionVTP::CmdADDP is called, m_LiveStreamer is NULL, and then return an errorr. m_LiveStreamer became null in cConnectionVTP::CmdABRT that is called from cStreamdevDevice::CloseDvrInt called from cStreamdevDevice::CloseDvr. Jose Alberto Index: server/connectionVTP.c === RCS file: /var/cvsroot/streamdev/server/connectionVTP.c,v retrieving revision 1.15 diff -u -r1.15 connectionVTP.c --- server/connectionVTP.c 21 Sep 2007 12:45:31 - 1.15 +++ server/connectionVTP.c 15 Dec 2007 14:34:15 - @@ -840,7 +840,8 @@ switch (id) { case siLive: - DELETENULL(m_LiveStreamer); + m_LiveStreamer->Stop(); +// DELETENULL(m_LiveStreamer); DELETENULL(m_LiveSocket); break; ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Help - can't get dvd-plugin to compile!
El Miércoles, 19 de Diciembre de 2007, Simon Baxter escribió: > Can anyone please help? I had no response to my last posting - thought I'd > try again! > > I've now rebuilt (again) now with 2.6.23.1-49.fc8 (Fedora Core 8) > > I'm now getting a new error trying to build vdr-dvd (see below) > > I did find this error: > http://qa.mandriva.com/show_bug.cgi?id=35140 > > but I can't work out what I need to add the "#include " ? > > Can anyone help? > > > > > [EMAIL PROTECTED] vdr-1.5.12]# make plugins > Plugin dvd: > make[1]: Entering directory `/root/vdr-1.5.12/PLUGINS/src/dvd-cvs27.07.07' > In file included from /usr/include/dvdread/nav_types.h:33, > from /usr/include/dvdnav/dvdnav.h:41, > from player-dvd.h:14, > from dvd.h:20, > from dvd.c:15: > /usr/include/dvdread/ifo_types.h:32:2: error: #error "Must include > In file included from /usr/include/dvdread/nav_types.h:33, > from /usr/include/dvdnav/dvdnav.h:41, > from player-dvd.h:14, > from player-dvd.c:34: > /usr/include/dvdread/ifo_types.h:32:2: error: #error "Must include > In file included from /usr/include/dvdread/nav_types.h:33, > from /usr/include/dvdnav/dvdnav.h:41, > from player-dvd.h:14, > from control-dvd.c:21: > /usr/include/dvdread/ifo_types.h:32:2: error: #error "Must include > In file included from /usr/include/dvdread/nav_types.h:33, > from /usr/include/dvdnav/dvdnav.h:41, > from player-dvd.h:14, > from ca52.c:44: > /usr/include/dvdread/ifo_types.h:32:2: error: #error "Must include > g++ -g -O2 -Wall -Woverloaded-virtual -fPIC -O3 -c -D_GNU_SOURCE > -DPLUGIN_NAME_I18N='"dvd"' -I../../../include -I/usr/include/dvdnav dvd.c > In file included from /usr/include/dvdread/nav_types.h:33, > from /usr/include/dvdnav/dvdnav.h:41, > from player-dvd.h:14, > from dvd.h:20, > from dvd.c:15: > /usr/include/dvdread/ifo_types.h:32:2: error: #error "Must include > make[1]: *** [dvd.o] Error 1 > > You can try to include stdint.h instead of inttypes.h before the dvdread includes. Jose alberto ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Disappearing audio
El Domingo, 20 de Enero de 2008, JJussi escribió: > Hi! > > Do anybody have same problem what I nowadays have... > > I updated this week my Gentoo vdr system and now if I use fast forward (or > rewind) I loose audio. So after fast forward when I come back to normal > speed playback, there is no sound anymore. > After killing vdr-sxfe and starting it again, I have sound again. > Jumping backward or forward don't make audio to disappear. See this thread: http://sourceforge.net/mailarchive/forum.php?thread_name=620587.9617.qm%40web50409.mail.re2.yahoo.com&forum_name=xine-devel Jose Alberto ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Problem when playing radio recordings
When playing radio recordings there are a lot of lines in the logs: Mar 25 02:14:46 jar vdr: [32230] playing '/video/Música/Jazz/2008-01-12.22.00.50.99.rec/001.vdr' Mar 25 02:14:48 jar vdr:last message repeated 59 times Mar 25 02:14:48 jar vdr: [32192] [vdrmon] connect from 127.0.0.1, port -18951 - accepted Mar 25 02:14:48 jar vdr: [32230] playing '/video/Música/Jazz/2008-01-12.22.00.50.99.rec/001.vdr' Mar 25 02:15:12 jar vdr:last message repeated 497 times It is that normal? Jose Alberto ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR with S2API
El Sábado, 6 de Diciembre de 2008, Klaus Schmidinger escribió: > The attached patch is what I've gathered from various postings > regarding adapting VDR to the S2API driver API (thanks to > Igor M. Liplianin, Niels Wagenaar and Edgar Hucek - did I forget anybody?). > > Since the S2SAPI doesn't provide a way of determining whether > a DVB-S device supports DVB-S2 (at least I didn't find any), > you need to apply the second attached patch to the driver > in order to impelement a new capability flag that reports > the availability of DVB-S2 support. > > If you don't want to patch the driver, you can change the line > > case FE_QPSK: frontendType = (frontendInfo.caps & > FE_CAN_2ND_GEN_MODULATION) ? SYS_DVBS2 : SYS_DVBS; break; > > in dvbdevice.c to avoid FE_CAN_2ND_GEN_MODULATION. Either set frontendType > permanently to SYS_DVBS or SYS_DVBS2, depending on what you have. > > > So far DVB-S and DVB-S2 appears to tune fine. > DVB-C is completely untested. > With DVB-T tuning doesn't work, even though my TDA10046H based DVB-T card > does work with the S2API driver under VDR 1.6.0. > > So for the moment I would appreciate if people could test DVB-T > tuning and check whether maybe I made some silly mistake in the > DVB-T tuning code. > > Klaus For DVB-T in S2API the bandwidth must be in HZ. http://www.linuxtv.org/pipermail/linux-dvb/2008-October/029556.html Jose Alberto ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDRAdmin-AM with UTF-8 support?
El Viernes, 13 de Marzo de 2009, H. Langos escribió: > Hi, > > I just installed vdr and vdradmin-am on Debian lenny and it seems that two > years down the road the problem still exists. (Though in a more subtle way) > > I even tried the 3.6.4-1 from debian testing and still the pages have > this in the head section: > > meta http-equiv="content-type" content="text/html;charset=ISO-8859-1" > > My system default locale is en_US.UTF-8 > # cat /etc/default/locale > LANG="en_US.UTF-8" > > Only switching to something like de_DE.UTF-8 seems to fix the problem. > Seems like gettext('ISO-8859-1') is not the best way of handling > encodings after all. > > Anyway, isn't it time to make a move towards a default UTF-8? > > cheers > -henrik > > PS: I'm not subscribed to vdr or vdradmin-am. So please CC me. In my case the problem is that the directory where the UTF8 locale is stored is: /usr/share/locale/es_ES.utf8/ if I change to: /usr/share/locale/es_ES.UTF8 All work ok. Jose Alberto > > On Thu, Jan 01, 1970 at 12:00:00AM +, Jose Alberto Reguero wrote: > > El Mi?rcoles, 28 de Marzo de 2007, Lucian Muresan escribi?: > > > Jose Alberto Reguero wrote: > > > > El Martes, 27 de Marzo de 2007, Harald Milz escribi?: > > > >> Hi, > > > >> > > > >> is anyone working on a UTF-8 version of VDRadmin-AM? I'm using vdr > > > >> with the UTF8 patch (de and ru) and need to always select UTF8 > > > >> manually in the browser to avoid seeing the ? stuff. Looking at the > > > >> html files in template/default/, I see everything is hardcoded in > > > >> iso-8859-1, but that should be a configuration option. Setting > > > >> LANG=de_DE.utf8 doesn't help, it is silently ignored. > > > >> > > > >> Anyone? > > > >> > > > >> THX. > > > > > > > > I run: > > > > > > > > sed -i -e s/ISO-8859-1/UTF-8/g *.html > > > > > > > > in the template/default/ directory. > > > > > > Andreas Mair already adopted my UTF-8 patch for the vdradmin locales, > > > months and versions ago. It patches the makefile and adds targets for > > > generating the UTF-8 locales out of the stock ones. For more info, > > > check this thread: > > > http://www.linuxtv.org/pipermail/vdr/2006-July/010116.html > > > > > > Regards, > > > Lucian > > > > I use make.sh utf8add and make.sh po but the html files in > > template/default/ still have references to ISO-8859-1, as Harald Milz > > says, and firefox put the encoding to ISO-8859-1. That is with > > vdradmin-am-3.5.3. > > > > Jose Alberto ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Fix for recordings greater than 2 GB
The attached patch fix some problems when playing recordings greater than 2 GB. Jose Alberto --- vdr-1.7.4/dvbplayer.c 2009-01-25 12:11:39.0 +0100 +++ vdr-1.7.4.new/dvbplayer.c 2009-03-28 00:33:23.0 +0100 @@ -209,7 +209,7 @@ cFrame *playFrame; void TrickSpeed(int Increment); void Empty(void); - bool NextFile(uchar FileNumber = 0, int FileOffset = -1); + bool NextFile(uint16_t FileNumber = 0, off_t FileOffset = -1); int Resume(void); bool Save(void); protected: @@ -319,7 +319,7 @@ firstPacket = true; } -bool cDvbPlayer::NextFile(uchar FileNumber, int FileOffset) +bool cDvbPlayer::NextFile(uint16_t FileNumber, off_t FileOffset) { if (FileNumber > 0) replayFile = fileName->SetOffset(FileNumber, FileOffset); ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDRAdmin-AM with UTF-8 support?
El Sábado, 13 de Marzo de 2010, Andreas Mair escribió: > Hi, > > have you tried VDRAdmin-AM v3.6.6? UTF8 handling has been changed there. > > Best regards, > Andreas > There is still the problem with es_ES.utf8 and es_ES.UTF8. I think that the problem is that in the sources in the locale directory there are es_ES.utf8 instead of es_ES.UTF8. Jose Alberto > 2009/3/14 Jose Alberto Reguero : > > El Viernes, 13 de Marzo de 2009, H. Langos escribió: > >> Hi, > >> > >> I just installed vdr and vdradmin-am on Debian lenny and it seems that > >> two years down the road the problem still exists. (Though in a more > >> subtle way) > >> > >> I even tried the 3.6.4-1 from debian testing and still the pages have > >> this in the head section: > >> > >> meta http-equiv="content-type" content="text/html;charset=ISO-8859-1" > >> > >> My system default locale is en_US.UTF-8 > >> # cat /etc/default/locale > >> LANG="en_US.UTF-8" > >> > >> Only switching to something like de_DE.UTF-8 seems to fix the problem. > >> Seems like gettext('ISO-8859-1') is not the best way of handling > >> encodings after all. > >> > >> Anyway, isn't it time to make a move towards a default UTF-8? > >> > >> cheers > >> -henrik > >> > >> PS: I'm not subscribed to vdr or vdradmin-am. So please CC me. > > > > In my case the problem is that the directory where the UTF8 locale is > > stored is: > > > > /usr/share/locale/es_ES.utf8/ > > > > if I change to: > > > > /usr/share/locale/es_ES.UTF8 > > > > All work ok. > > > > Jose Alberto > > > >> On Thu, Jan 01, 1970 at 12:00:00AM +, Jose Alberto Reguero wrote: > >> > El Mi?rcoles, 28 de Marzo de 2007, Lucian Muresan escribi?: > >> > > Jose Alberto Reguero wrote: > >> > > > El Martes, 27 de Marzo de 2007, Harald Milz escribi?: > >> > > >> Hi, > >> > > >> > >> > > >> is anyone working on a UTF-8 version of VDRadmin-AM? I'm using > >> > > >> vdr with the UTF8 patch (de and ru) and need to always select > >> > > >> UTF8 manually in the browser to avoid seeing the ? stuff. > >> > > >> Looking at the html files in template/default/, I see everything > >> > > >> is hardcoded in iso-8859-1, but that should be a configuration > >> > > >> option. Setting LANG=de_DE.utf8 doesn't help, it is silently > >> > > >> ignored. > >> > > >> > >> > > >> Anyone? > >> > > >> > >> > > >> THX. > >> > > > > >> > > > I run: > >> > > > > >> > > > sed -i -e s/ISO-8859-1/UTF-8/g *.html > >> > > > > >> > > > in the template/default/ directory. > >> > > > >> > > Andreas Mair already adopted my UTF-8 patch for the vdradmin > >> > > locales, months and versions ago. It patches the makefile and adds > >> > > targets for generating the UTF-8 locales out of the stock ones. For > >> > > more info, check this thread: > >> > > http://www.linuxtv.org/pipermail/vdr/2006-July/010116.html > >> > > > >> > > Regards, > >> > > Lucian > >> > > >> > I use make.sh utf8add and make.sh po but the html files in > >> > template/default/ still have references to ISO-8859-1, as Harald Milz > >> > says, and firefox put the encoding to ISO-8859-1. That is with > >> > vdradmin-am-3.5.3. > >> > > >> > 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] VDRAdmin-AM with UTF-8 support?
El Domingo, 14 de Marzo de 2010, Tobi escribió: > Jose Alberto Reguero wrote: > > There is still the problem with es_ES.utf8 and es_ES.UTF8. I think that > > the problem is that in the sources in the locale directory there are > > es_ES.utf8 instead of es_ES.UTF8. > > With version 3.6.6 the *.utf8 locales shouldn't be required at all. The > charset encoding is handled by gettext. > > Please provide the following information: > > - Output of the `locale` command > - Output of the `locale charmap` command > - cat vdradmind.conf | grep LANG > - svdrpsend HELP | grep 220 > - Which encoding is detected by the browser and which encoding do you see > in the HTML source? > > You might need to change the LANG setting in vdradmind.conf to es_ES if it > is configured to es_ES.UTF8 or drop it altogether to automatically use the > systems default locale. > > Tobias > I delete vdradmin.mo from /usr/share/locale/es_ES.UTF-8/LC_MESSAGES/ and the program still work well, in spanish. I thought that it was using vdradmin.mo because the installation program still copy it to the locale directory. Jose Alberto ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Recording DVB-T HD infrance
El Miércoles, 17 de Marzo de 2010, Eric Valette escribió: > >> Still wonder why such a one liner patch is not integrated though. > > > > That forum is in French and apparently requires registration. > > > > Can you post that "one-liner" here? > > I just translate the instruction, into english (could do german too ;-)) > Could do a diff but for one trivial line no need for it. > > Just add the following line in pat.c > > case SI::AC3DescriptorTag: > + case SI::EnhancedAC3DescriptorTag: > dpid = stream.getPid(); > > > > I think for streamdev the same patch is required in > livestreamer.c > > case SI::AC3DescriptorTag: > + case SI::EnhancedAC3DescriptorTag: > Dprintf("cStreamdevPatFilter PMT scanner: adding PID %d (%s) %s\n", > > -- eric > > > I make a patch to use ffmpeg eac3 with xine. The patch is for the latest xine- lib-1.2 hg. If you use xineliboutput you also need the second patch attached. Jose Alberto diff -r a6a25ea3e2c8 src/combined/ffmpeg/ff_audio_decoder.c --- a/src/combined/ffmpeg/ff_audio_decoder.c Sun Mar 14 15:12:25 2010 + +++ b/src/combined/ffmpeg/ff_audio_decoder.c Thu Mar 18 21:56:24 2010 +0100 @@ -68,6 +68,8 @@ char *decode_buffer; int decoder_ok; + int sync; + int frame_size; } ff_audio_decoder_t; @@ -257,10 +259,46 @@ if( !this->decoder_ok ) { if ( ! this->context || ! this->codec ) { -xprintf (this->stream->xine, XINE_VERBOSITY_LOG, - _("ffmpeg_audio_dec: trying to open null codec\n")); - _x_stream_info_set(this->stream, XINE_STREAM_INFO_AUDIO_HANDLED, 0); - return; + if ( (buf->type & 0x) == BUF_AUDIO_A52 ) { + pthread_mutex_lock (&ffmpeg_lock); +this->codec = avcodec_find_decoder(CODEC_ID_AC3); + pthread_mutex_unlock (&ffmpeg_lock); +_x_meta_info_set(this->stream, XINE_META_INFO_AUDIOCODEC, + "AC3 coque (ffmpeg)"); + +if (!this->codec) { + xprintf (this->stream->xine, XINE_VERBOSITY_LOG, + _("ffmpeg_audio_dec: couldn't find ffmpeg decoder for buf type 0x%X\n"), + buf->type); + _x_stream_info_set(this->stream, XINE_STREAM_INFO_AUDIO_HANDLED, 0); + return; +} + +this->context = avcodec_alloc_context(); + +this->audio_bits = 16; +// this->audio_sample_rate = 48000; +// this->audio_channels = 6; +// this->frame_size = 768; +this->context->request_channels = 2; + +this->context->bits_per_sample = this->audio_bits; +this->context->sample_rate = this->audio_sample_rate; +this->context->channels= this->audio_channels; +this->context->codec_id= this->codec->id; +this->context->codec_type = this->codec->type; +this->context->codec_tag = _x_stream_info_get(this->stream, XINE_STREAM_INFO_AUDIO_FOURCC); + +this->size = 0; + this->sync = 0; + +this->decode_buffer = calloc(1, AVCODEC_MAX_AUDIO_FRAME_SIZE); + } else { + xprintf (this->stream->xine, XINE_VERBOSITY_LOG, + _("ffmpeg_audio_dec: trying to open null codec\n")); + _x_stream_info_set(this->stream, XINE_STREAM_INFO_AUDIO_HANDLED, 0); + return; + } } pthread_mutex_lock (&ffmpeg_lock); @@ -278,20 +316,32 @@ if( buf->decoder_flags & BUF_FLAG_PREVIEW ) return; +if (this->sync == 0) { + while ((buf->content[0] != 0x0b) || (buf->content[1] != 0x77)) { +buf->content++; + buf->size--; + } + this->sync = 1; +} ff_audio_ensure_buffer_size(this, this->size + buf->size); xine_fast_memcpy (&this->buf[this->size], buf->content, buf->size); this->size += buf->size; if (!this->output_open) { +// if ((!this->audio_bits || !this->audio_sample_rate || !this->audio_channels) || ( (buf->type & 0x) == BUF_AUDIO_A52 )) { if (!this->audio_bits || !this->audio_sample_rate || !this->audio_channels) { -avcodec_decode_audio2 (this->context, + decode_buffer_size = AVCODEC_MAX_AUDIO_FRAME_SIZE; +this->frame_size = avcodec_decode_audio2 (this->context, (int16_t *)this->decode_buffer, &decode_buffer_size, &this->buf[0], this->size); +// this->size -= this->frame_size; +// memmove(this->buf, &this->buf[this->frame_size], this->size); this->audio_bits = this->context->bits_per_sample; this->audio_sample_rate = t
Re: [vdr] vdr xine-lib eac3
El Miércoles, 24 de Marzo de 2010, zaverel escribió: > hello > > i try the patch from Jose Alberto to use ffmpeg eac3 with xine > http://www.linuxtv.org/pipermail/vdr/2010-March/022687.html > > The good things is that eac3 sound is now decoded with xine-lib > > But it's not stable at all when zapping frhom HD to HD channel or SD > channel > > vdr-sxfe doesn't work anymore with --video=xv on HD channels but only > with --video=vdpau > > vdr-sxfe --tcp --video=xv --verbose > > > [29976] [input_vdr] fifo_buffer_new... > [29976] [input_vdr] fifo_buffer_new done. > [29977] [demux_vdr] PMT changed > [29977] [demux_vdr] audio stream changed: -> 0300 > ffmpeg_audio_dec: increasing buffer to 98304 to avoid overflow. > Erreur de segmentation > > and dmesg said > > vdr-sxfe[29973] general protection ip:b06757c5 sp:b442a020 error:0 in > libavcodec.so.52.60.0[b01d7000+6e3000] > > with xine-ui it's almost the same > > xine "xvdr+tcp://miniq#nocache" --verbose --video=xv > > > > [1723] [input_vdr] wait_stream_sync: discard_index 5465954112 != curpos > 5471218488 ! (diff -5264376) > prebuffer=14400 pts > prebuffer=2000 pts > prebuffer=14400 pts > prebuffer=14400 pts > [1723] [demux_vdr] PMT changed > ffmpeg_audio_dec: augmentation du buffer à 98304 pour éviter sa saturation. > Last message repeated 3 times > [h264 @ 0x8fb2640]non-existing SPS 0 referenced in buffering period > [h264 @ 0x8fb2640]non-existing PPS 0 referenced > [h264 @ 0x8fb2640]decode_slice_header error > [h264 @ 0x8fb2640]non-existing PPS 0 referenced > [h264 @ 0x8fb2640]decode_slice_header error > [h264 @ 0x8fb2640]non-existing PPS 0 referenced > [h264 @ 0x8fb2640]decode_slice_header error > [h264 @ 0x8fb2640]non-existing PPS 0 referenced > [h264 @ 0x8fb2640]decode_slice_header error > [h264 @ 0x8fb2640]non-existing PPS 0 referenced > [h264 @ 0x8fb2640]decode_slice_header error > [h264 @ 0x8fb2640]non-existing PPS 0 referenced > [h264 @ 0x8fb2640]decode_slice_header error > [h264 @ 0x8fb2640]no frame! > xiTK received SIGSEGV signal, RIP. > Abandon > > but dmesg said nothing. > > > I do my test with vdr-1.7.12 , ffmpeg , xine-lib-1.2 , all patched for > eac3 and xineliboutput. > All are latest cvs > > > So what can i do ? > > thanks. > > I make some changes based on the patches posted by Petri Hintukainen yesterday in the xine-devel mailing list. Attached is a new version of the patch. I can not probe it now with tdt eac3 channel. You can try it. Jose Alberto diff -r a6a25ea3e2c8 include/xine/buffer.h --- a/include/xine/buffer.h Sun Mar 14 15:12:25 2010 + +++ b/include/xine/buffer.h Wed Mar 24 17:24:12 2010 +0100 @@ -266,6 +266,7 @@ #define BUF_AUDIO_MP3ADU 0x033E #define BUF_AUDIO_AMR_NB 0x033F #define BUF_AUDIO_AMR_WB 0x0340 +#define BUF_AUDIO_EAC3 0x0341 /*...@}*/ /** diff -r a6a25ea3e2c8 src/combined/ffmpeg/ff_audio_decoder.c --- a/src/combined/ffmpeg/ff_audio_decoder.c Sun Mar 14 15:12:25 2010 + +++ b/src/combined/ffmpeg/ff_audio_decoder.c Wed Mar 24 17:24:12 2010 +0100 @@ -257,10 +257,44 @@ if( !this->decoder_ok ) { if ( ! this->context || ! this->codec ) { -xprintf (this->stream->xine, XINE_VERBOSITY_LOG, - _("ffmpeg_audio_dec: trying to open null codec\n")); - _x_stream_info_set(this->stream, XINE_STREAM_INFO_AUDIO_HANDLED, 0); - return; + if ( (buf->type & 0x) == BUF_AUDIO_EAC3 ) { + pthread_mutex_lock (&ffmpeg_lock); +this->codec = avcodec_find_decoder(CODEC_ID_EAC3); + pthread_mutex_unlock (&ffmpeg_lock); +_x_meta_info_set(this->stream, XINE_META_INFO_AUDIOCODEC, + "AC3 coque (ffmpeg)"); + +if (!this->codec) { + xprintf (this->stream->xine, XINE_VERBOSITY_LOG, + _("ffmpeg_audio_dec: couldn't find ffmpeg decoder for buf type 0x%X\n"), + buf->type); + _x_stream_info_set(this->stream, XINE_STREAM_INFO_AUDIO_HANDLED, 0); + return; +} + +this->context = avcodec_alloc_context(); + +this->audio_bits = 16; +// this->audio_sample_rate = 48000; +// this->audio_channels = 6; +this->context->request_channels = 2; + +this->context->bits_per_sample = this->audio_bits; +this->context->sample_rate = this->audio_sample_rate; +this->context->channels= this->audio_channels; +this->context->codec_id= this->codec->id; +this->context->codec_type = this->codec->type; +this->context->codec_tag = _x_stream_info_get(this->stream, XINE_STREAM_INFO_AUDI
Re: [vdr] vdr xine-lib eac3
It works here with a old sample of tdt with eac3. Have you patch also remux.c? You need to change in line 533: case SI::AC3DescriptorTag: +case SI:EnhancedAC3DescriptorTag: and in line 191: -Target[i++] = SI::AC3DescriptorTag; +Target[i++] = SI::EnhancedAC3DescriptorTag Jose Alberto El Miércoles, 24 de Marzo de 2010, dplu escribió: > Hi > > I have made previous test with the version release by Petri Hintukainen > > And I notice this part is not working like it should > > -if((m->descriptor_tag == STREAM_AUDIO_AC3) ||/* ac3 - raw */ > +if(m->descriptor_tag == HDMV_AUDIO_84_EAC3) { > + m->content = p; > + m->size = packet_len; > + m->type |= BUF_AUDIO_EAC3; > + return 1; > + > +} else if((m->descriptor_tag == STREAM_AUDIO_AC3) ||/* ac3 - raw > */ > > unfortunaletly, in AC3 or E-AC3 , the descriptor tag is STREAM_AUDIO_AC3, > so the program never run the first if (installed a debug printf here) > > It seems that your first approach (at least what I understood) by forcing > the decoding of all AC-3 stream by ffmepg instead of internal lib was nice > but generate violent segfault on libavcodec > > Hope this help you > > Best regards > > PS : Sorry to pollute the vdr mailing list (not subscribed to ffmpeg or > xine-lib) > > Le Wednesday 24 March 2010 18:41:14 zaverel, vous avez écrit : > > hello > > > > your second patch doesn't work : no sound on eac3 channel > > > > if you want there is a sample of vdr hd-eac3 recording here: > > > > http://dl.free.fr/ew4rJddM8 > > > > 103mo > > > > else , i don't know what mailing-list is the more indicate for debuging > > > > the vdr or xine-dev mailing-list ? > > > > ___ > > 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] vdr xine-lib eac3
I attached a second version of the first patch. I make the same changes that in the second patch, but maintaining the logic of the first patch. Also I commented the line: +//this->context->request_channels = 2; because your example has 5 channels. If you have trouble with that you can comment the line again. Which typo error has the second patch? Jose Alberto El Miércoles, 24 de Marzo de 2010, zaverel escribió: > i 've patched pat.c and now remux.c > and with use xine-lib-1.2 with your second patch (who has typo error) > and that doesn't work. > > corrected remux.c > > line 533 > case SI::AC3DescriptorTag: > +case SI::EnhancedAC3DescriptorTag: > > > and in line 191: > > -Target[i++] = SI::AC3DescriptorTag; > +Target[i++] = SI::EnhancedAC3DescriptorTag; > > > > with your previously patch and just pat.c patched with > line 402 > > case SI::AC3DescriptorTag: > +case SI:EnhancedAC3DescriptorTag: > > that worked but not stable. > > Is your sample eac3 has |"Spectral extension" ? > because in france dvb-t with eac3 has it > and need a ffmpeg patched for that. > And i test with that sound. > > Le 24/03/2010 19:41, Jose Alberto Reguero a écrit : > > It works here with a old sample of tdt with eac3. Have you patch also > > remux.c? You need to change in line 533: > > > > case SI::AC3DescriptorTag: > > +case SI:EnhancedAC3DescriptorTag: > > > > and in line 191: > > > > -Target[i++] = SI::AC3DescriptorTag; > > +Target[i++] = SI::EnhancedAC3DescriptorTag > > > > Jose Alberto > > > > El Miércoles, 24 de Marzo de 2010, dplu escribió: > >> Hi > >> > >> I have made previous test with the version release by Petri Hintukainen > >> > >> And I notice this part is not working like it should > >> > >> -if((m->descriptor_tag == STREAM_AUDIO_AC3) ||/* ac3 - raw */ > >> +if(m->descriptor_tag == HDMV_AUDIO_84_EAC3) { > >> + m->content = p; > >> + m->size = packet_len; > >> + m->type |= BUF_AUDIO_EAC3; > >> + return 1; > >> + > >> +} else if((m->descriptor_tag == STREAM_AUDIO_AC3) ||/* ac3 - > >> raw */ > >> > >> unfortunaletly, in AC3 or E-AC3 , the descriptor tag is > >> STREAM_AUDIO_AC3, so the program never run the first if (installed a > >> debug printf here) > >> > >> It seems that your first approach (at least what I understood) by > >> forcing the decoding of all AC-3 stream by ffmepg instead of internal > >> lib was nice but generate violent segfault on libavcodec > >> > >> Hope this help you > >> > >> Best regards > >> > >> PS : Sorry to pollute the vdr mailing list (not subscribed to ffmpeg or > >> xine-lib) > >> > >> Le Wednesday 24 March 2010 18:41:14 zaverel, vous avez écrit : > >>> hello > >>> > >>> your second patch doesn't work : no sound on eac3 channel > >>> > >>> if you want there is a sample of vdr hd-eac3 recording here: > >>> > >>> http://dl.free.fr/ew4rJddM8 > >>> > >>> 103mo > >>> > >>> else , i don't know what mailing-list is the more indicate for debuging > >>> > >>> the vdr or xine-dev mailing-list ? > >>> > >>> ___ > >>> 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 diff -r a6a25ea3e2c8 src/combined/ffmpeg/ff_audio_decoder.c --- a/src/combined/ffmpeg/ff_audio_decoder.c Sun Mar 14 15:12:25 2010 + +++ b/src/combined/ffmpeg/ff_audio_decoder.c Wed Mar 24 22:44:29 2010 +0100 @@ -257,10 +257,44 @@ if( !this->decoder_ok ) { if ( ! this->context || ! this->codec ) { -xprintf (this->stream->xine, XINE_VERBOSITY_LOG, - _("ffmpeg_audio_dec: trying to open null codec\n")); - _x_stream_info_set(this->stream, XINE_STREAM_INFO_AUDIO_HANDLED, 0); - return; + if ( (buf->type & 0x) == BUF_AUDIO_A52 ) { + pthread_mutex_lock (&ffmpeg_lock); +this-&
Re: [vdr] vdr xine-lib eac3
Patch against latest xine-lib-1.2. New patch for xineliboutput. Now must work if you patch remux.c. You must have the latest xine-lib and xineliboutput. Yesterday both have changes about eac3. Jose Alberto El Jueves, 25 de Marzo de 2010, zaverel escribió: > The typo was on remux.c => lost : and ; > > Anyway xine-lib has been updated and your patch don't apply. > > Update is for eac3 with mkv > > i don't test it yet > > > > corrected remux.c > > line 533 > case SI::AC3DescriptorTag: > +case SI::EnhancedAC3DescriptorTag: > > > and in line 191: > > -Target[i++] = SI::AC3DescriptorTag; > +Target[i++] = SI::EnhancedAC3DescriptorTag; > > Le 24/03/2010 22:58, Jose Alberto Reguero a écrit : > > I attached a second version of the first patch. > > I make the same changes that in the second patch, but maintaining the > > logic of the first patch. Also I commented the line: > > +//this->context->request_channels = 2; > > because your example has 5 channels. If you have trouble with that you > > can comment the line again. > > Which typo error has the second patch? > > > > Jose Alberto > > > > El Miércoles, 24 de Marzo de 2010, zaverel escribió: > >> i 've patched pat.c and now remux.c > >> and with use xine-lib-1.2 with your second patch (who has typo error) > >> and that doesn't work. > >> > >> corrected remux.c > >> > >> line 533 > >> case SI::AC3DescriptorTag: > >> +case SI::EnhancedAC3DescriptorTag: > >> > >> > >> and in line 191: > >> > >> -Target[i++] = SI::AC3DescriptorTag; > >> +Target[i++] = SI::EnhancedAC3DescriptorTag; > >> > >> > >> > >> with your previously patch and just pat.c patched with > >> line 402 > >> > >> case SI::AC3DescriptorTag: > >> +case SI:EnhancedAC3DescriptorTag: > >> > >> that worked but not stable. > >> > >> Is your sample eac3 has |"Spectral extension" ? > >> because in france dvb-t with eac3 has it > >> and need a ffmpeg patched for that. > >> And i test with that sound. > >> > >> Le 24/03/2010 19:41, Jose Alberto Reguero a écrit : > >>> It works here with a old sample of tdt with eac3. Have you patch also > >>> remux.c? You need to change in line 533: > >>> > >>> case SI::AC3DescriptorTag: > >>> +case SI:EnhancedAC3DescriptorTag: > >>> > >>> and in line 191: > >>> > >>> -Target[i++] = SI::AC3DescriptorTag; > >>> +Target[i++] = SI::EnhancedAC3DescriptorTag > >>> > >>> Jose Alberto > >>> > >>> El Miércoles, 24 de Marzo de 2010, dplu escribió: > >>>> Hi > >>>> > >>>> I have made previous test with the version release by Petri > >>>> Hintukainen > >>>> > >>>> And I notice this part is not working like it should > >>>> > >>>> -if((m->descriptor_tag == STREAM_AUDIO_AC3) ||/* ac3 - raw */ > >>>> +if(m->descriptor_tag == HDMV_AUDIO_84_EAC3) { > >>>> + m->content = p; > >>>> + m->size = packet_len; > >>>> + m->type |= BUF_AUDIO_EAC3; > >>>> + return 1; > >>>> + > >>>> +} else if((m->descriptor_tag == STREAM_AUDIO_AC3) ||/* ac3 - > >>>> raw */ > >>>> > >>>> unfortunaletly, in AC3 or E-AC3 , the descriptor tag is > >>>> STREAM_AUDIO_AC3, so the program never run the first if (installed a > >>>> debug printf here) > >>>> > >>>> It seems that your first approach (at least what I understood) by > >>>> forcing the decoding of all AC-3 stream by ffmepg instead of internal > >>>> lib was nice but generate violent segfault on libavcodec > >>>> > >>>> Hope this help you > >>>> > >>>> Best regards > >>>> > >>>> PS : Sorry to pollute the vdr mailing list (not subscribed to ffmpeg > >>>> or xine-lib) > >>>> > >>>> Le Wednesday 24 March 2010 18:41:14 zaverel, vous avez écrit : > >>>>> hello > >>>>> > >>>>> your second patch doesn't work : no sound on eac3 channel > >>>>> > >>>>> if y
Re: [vdr] vdr xine-lib eac3
Patch for xine-lib that don't need to patch remux.c to work. Jose Alberto El Jueves, 25 de Marzo de 2010, Jose Alberto Reguero escribió: > Patch against latest xine-lib-1.2. New patch for xineliboutput. Now must > work if you patch remux.c. > You must have the latest xine-lib and xineliboutput. Yesterday both have > changes about eac3. > > Jose Alberto > > El Jueves, 25 de Marzo de 2010, zaverel escribió: > > The typo was on remux.c => lost : and ; > > > > Anyway xine-lib has been updated and your patch don't apply. > > > > Update is for eac3 with mkv > > > > i don't test it yet > > > > > > > > corrected remux.c > > > > line 533 > > case SI::AC3DescriptorTag: > > +case SI::EnhancedAC3DescriptorTag: > > > > > > and in line 191: > > > > -Target[i++] = SI::AC3DescriptorTag; > > +Target[i++] = SI::EnhancedAC3DescriptorTag; > > > > Le 24/03/2010 22:58, Jose Alberto Reguero a écrit : > > > I attached a second version of the first patch. > > > I make the same changes that in the second patch, but maintaining the > > > logic of the first patch. Also I commented the line: > > > +// this->context->request_channels = 2; > > > because your example has 5 channels. If you have trouble with that you > > > can comment the line again. > > > Which typo error has the second patch? > > > > > > Jose Alberto > > > > > > El Miércoles, 24 de Marzo de 2010, zaverel escribió: > > >> i 've patched pat.c and now remux.c > > >> and with use xine-lib-1.2 with your second patch (who has typo error) > > >> and that doesn't work. > > >> > > >> corrected remux.c > > >> > > >> line 533 > > >> case SI::AC3DescriptorTag: > > >> +case SI::EnhancedAC3DescriptorTag: > > >> > > >> > > >> and in line 191: > > >> > > >> -Target[i++] = SI::AC3DescriptorTag; > > >> +Target[i++] = SI::EnhancedAC3DescriptorTag; > > >> > > >> > > >> > > >> with your previously patch and just pat.c patched with > > >> line 402 > > >> > > >> case SI::AC3DescriptorTag: > > >> +case SI:EnhancedAC3DescriptorTag: > > >> > > >> that worked but not stable. > > >> > > >> Is your sample eac3 has |"Spectral extension" ? > > >> because in france dvb-t with eac3 has it > > >> and need a ffmpeg patched for that. > > >> And i test with that sound. > > >> > > >> Le 24/03/2010 19:41, Jose Alberto Reguero a écrit : > > >>> It works here with a old sample of tdt with eac3. Have you patch also > > >>> remux.c? You need to change in line 533: > > >>> > > >>> case SI::AC3DescriptorTag: > > >>> +case SI:EnhancedAC3DescriptorTag: > > >>> > > >>> and in line 191: > > >>> > > >>> -Target[i++] = SI::AC3DescriptorTag; > > >>> +Target[i++] = SI::EnhancedAC3DescriptorTag > > >>> > > >>> Jose Alberto > > >>> > > >>> El Miércoles, 24 de Marzo de 2010, dplu escribió: > > >>>> Hi > > >>>> > > >>>> I have made previous test with the version release by Petri > > >>>> Hintukainen > > >>>> > > >>>> And I notice this part is not working like it should > > >>>> > > >>>> -if((m->descriptor_tag == STREAM_AUDIO_AC3) ||/* ac3 - raw > > >>>> */ +if(m->descriptor_tag == HDMV_AUDIO_84_EAC3) { > > >>>> + m->content = p; > > >>>> + m->size = packet_len; > > >>>> + m->type |= BUF_AUDIO_EAC3; > > >>>> + return 1; > > >>>> + > > >>>> +} else if((m->descriptor_tag == STREAM_AUDIO_AC3) ||/* ac3 > > >>>> - raw */ > > >>>> > > >>>> unfortunaletly, in AC3 or E-AC3 , the descriptor tag is > > >>>> STREAM_AUDIO_AC3, so the program never run the first if (installed a > > >>>> debug printf here) > > >>>> > > >>>> It seems that your first approach (at least what I understood) by > > >>>> forcing the decoding o
Re: [vdr] vdr xine-lib eac3
You can add the line: this->context->request_channels = 2; in line 247 and 295. Then you have stereo sound. Joae Alberto El Viernes, 26 de Marzo de 2010, zaverel escribió: > After some test there are some issue: > ramdom crash at start up or without sound. > But the real probleme i think is with 5.0 sound. > > In the sample the 2.0 audio out is good > but the 5.0 has low volume and metallic sound > > just try xine > fra piste 5.0 > ffmpeg_audio_dec: unknown header with buf type 0x300 > > qaa 2.0 > is good > > ffmpeg -i 1.ts > ... > Input #0, mpegts, from '1.ts': > Duration: 00:02:10.51, start: 10461.634989, bitrate: 6905 kb/s > Program 132 > Stream #0.0[0x78]: Video: h264, yuv420p, 1440x1080 [PAR 4:3 DAR > 16:9], 50 fps, 50 tbr, 90k tbn, 50 tbc > Stream #0.1[0x82](fra): Audio: eac3, 48000 Hz, 5.0, s16, 256 kb/s > Stream #0.2[0x83](qaa): Audio: eac3, 48000 Hz, stereo, s16, 128 kb/s > Stream #0.3[0x8c](fra): Subtitle: dvbsub > Stream #0.4[0x8d](fra): Subtitle: dvbsub > > Le 25/03/2010 16:08, Jose Alberto Reguero a écrit : > > Patch for xine-lib that don't need to patch remux.c to work. > > > > Jose Alberto > > > > El Jueves, 25 de Marzo de 2010, Jose Alberto Reguero escribió: > >> Patch against latest xine-lib-1.2. New patch for xineliboutput. Now must > >> work if you patch remux.c. > >> You must have the latest xine-lib and xineliboutput. Yesterday both have > >> changes about eac3. > >> > >> Jose Alberto > >> > >> El Jueves, 25 de Marzo de 2010, zaverel escribió: > >>> The typo was on remux.c => lost : and ; > >>> > >>> Anyway xine-lib has been updated and your patch don't apply. > >>> > >>> Update is for eac3 with mkv > >>> > >>> i don't test it yet > >>> > >>> > >>> > >>> corrected remux.c > >>> > >>> line 533 > >>> case SI::AC3DescriptorTag: > >>> +case SI::EnhancedAC3DescriptorTag: > >>> > >>> > >>> and in line 191: > >>> > >>> -Target[i++] = SI::AC3DescriptorTag; > >>> +Target[i++] = SI::EnhancedAC3DescriptorTag; > >>> > >>> Le 24/03/2010 22:58, Jose Alberto Reguero a écrit : > >>>> I attached a second version of the first patch. > >>>> I make the same changes that in the second patch, but maintaining the > >>>> logic of the first patch. Also I commented the line: > >>>> +//this->context->request_channels = 2; > >>>> because your example has 5 channels. If you have trouble with that you > >>>> can comment the line again. > >>>> Which typo error has the second patch? > >>>> > >>>> Jose Alberto > >>>> > >>>> El Miércoles, 24 de Marzo de 2010, zaverel escribió: > >>>>> i 've patched pat.c and now remux.c > >>>>> and with use xine-lib-1.2 with your second patch (who has typo error) > >>>>> and that doesn't work. > >>>>> > >>>>> corrected remux.c > >>>>> > >>>>> line 533 > >>>>> case SI::AC3DescriptorTag: > >>>>> +case SI::EnhancedAC3DescriptorTag: > >>>>> > >>>>> > >>>>> and in line 191: > >>>>> > >>>>> -Target[i++] = SI::AC3DescriptorTag; > >>>>> +Target[i++] = SI::EnhancedAC3DescriptorTag; > >>>>> > >>>>> > >>>>> > >>>>> with your previously patch and just pat.c patched with > >>>>> line 402 > >>>>> > >>>>> case SI::AC3DescriptorTag: > >>>>> +case SI:EnhancedAC3DescriptorTag: > >>>>> > >>>>> that worked but not stable. > >>>>> > >>>>> Is your sample eac3 has |"Spectral extension" ? > >>>>> because in france dvb-t with eac3 has it > >>>>> and need a ffmpeg patched for that. > >>>>> And i test with that sound. > >>>>> > >>>>> Le 24/03/2010 19:41, Jose Alberto Reguero a écrit : > >>>>>> It works here with a old sample of tdt with eac3. Have you patch > >>>>>> also remux.c? You need to change in line 533: > >>>>>> > &
Re: [vdr] vdr xine-lib eac3
Yes, the file is ff_audio_decoder.c You must put the line this->context->request_channels = 2; after this->context->codec_tag = _x_stream_info_get(this->stream, XINE_STREAM_INFO_AUDIO_FOURCC); Jose Alberto El Sábado, 27 de Marzo de 2010, zaverel escribió: > Is ff_audio_decoder.c to patch ? > I try but that change nothing. > > Le 26/03/2010 13:12, Jose Alberto Reguero a écrit : > > You can add the line: > > > > this->context->request_channels = 2; > > > > in line 247 and 295. > > > > Then you have stereo sound. > > > > Joae Alberto > > > > El Viernes, 26 de Marzo de 2010, zaverel escribió: > >> After some test there are some issue: > >> ramdom crash at start up or without sound. > >> But the real probleme i think is with 5.0 sound. > >> > >> In the sample the 2.0 audio out is good > >> but the 5.0 has low volume and metallic sound > >> > >> just try xine > >> fra piste 5.0 > >> ffmpeg_audio_dec: unknown header with buf type 0x300 > >> > >> qaa 2.0 > >> is good > >> > >> ffmpeg -i 1.ts > >> ... > >> > >> Input #0, mpegts, from '1.ts': > >> Duration: 00:02:10.51, start: 10461.634989, bitrate: 6905 kb/s > >> Program 132 > >> > >> Stream #0.0[0x78]: Video: h264, yuv420p, 1440x1080 [PAR 4:3 DAR > >> > >> 16:9], 50 fps, 50 tbr, 90k tbn, 50 tbc > >> > >> Stream #0.1[0x82](fra): Audio: eac3, 48000 Hz, 5.0, s16, 256 kb/s > >> Stream #0.2[0x83](qaa): Audio: eac3, 48000 Hz, stereo, s16, 128 kb/s > >> Stream #0.3[0x8c](fra): Subtitle: dvbsub > >> Stream #0.4[0x8d](fra): Subtitle: dvbsub > >> > >> Le 25/03/2010 16:08, Jose Alberto Reguero a écrit : > >>> Patch for xine-lib that don't need to patch remux.c to work. > >>> > >>> Jose Alberto > >>> > >>> El Jueves, 25 de Marzo de 2010, Jose Alberto Reguero escribió: > >>>> Patch against latest xine-lib-1.2. New patch for xineliboutput. Now > >>>> must work if you patch remux.c. > >>>> You must have the latest xine-lib and xineliboutput. Yesterday both > >>>> have changes about eac3. > >>>> > >>>> Jose Alberto > >>>> > >>>> El Jueves, 25 de Marzo de 2010, zaverel escribió: > >>>>> The typo was on remux.c => lost : and ; > >>>>> > >>>>> Anyway xine-lib has been updated and your patch don't apply. > >>>>> > >>>>> Update is for eac3 with mkv > >>>>> > >>>>> i don't test it yet > >>>>> > >>>>> > >>>>> > >>>>> corrected remux.c > >>>>> > >>>>> line 533 > >>>>> case SI::AC3DescriptorTag: > >>>>> +case SI::EnhancedAC3DescriptorTag: > >>>>> > >>>>> > >>>>> and in line 191: > >>>>> > >>>>> -Target[i++] = SI::AC3DescriptorTag; > >>>>> +Target[i++] = SI::EnhancedAC3DescriptorTag; > >>>>> > >>>>> Le 24/03/2010 22:58, Jose Alberto Reguero a écrit : > >>>>>> I attached a second version of the first patch. > >>>>>> I make the same changes that in the second patch, but maintaining > >>>>>> the logic of the first patch. Also I commented the line: > >>>>>> +//this->context->request_channels = 2; > >>>>>> because your example has 5 channels. If you have trouble with that > >>>>>> you can comment the line again. > >>>>>> Which typo error has the second patch? > >>>>>> > >>>>>> Jose Alberto > >>>>>> > >>>>>> El Miércoles, 24 de Marzo de 2010, zaverel escribió: > >>>>>>> i 've patched pat.c and now remux.c > >>>>>>> and with use xine-lib-1.2 with your second patch (who has typo > >>>>>>> error) and that doesn't work. > >>>>>>> > >>>>>>> corrected remux.c > >>>>>>> > >>>>>>> line 533 > >>>>>>> case SI::AC3DescriptorTag: > >>>>>>> +case SI::EnhancedAC3DescriptorTag: &
Re: [vdr] vdr and aac support
El Martes, 18 de Mayo de 2010, Luca Olivetti escribió: > Al 18/05/10 21:43, En/na Luca Olivetti ha escrit: > > (i.e. it only adds SI::AACDescriptorTag) > > > > I must have missed some patch along the way :-/ > > Ok, they were in the "Recording DVB-T HD infrance" (sic). > It appears that spain is using the same standard. > > Bye Here is a patch based in Klaus aac pacth that add support for eac3 sound in vdr. Jose Alberto Sólo en vdr-1.7.14.new/: audio.o diff -ur vdr-1.7.14/channels.c vdr-1.7.14.new/channels.c --- vdr-1.7.14/channels.c 2010-02-21 14:36:04.0 +0100 +++ vdr-1.7.14.new/channels.c 2010-05-18 18:54:57.0 +0200 @@ -12,6 +12,7 @@ #include "device.h" #include "epg.h" #include "timers.h" +#include "libsi/si.h" // IMPORTANT NOTE: in the 'sscanf()' calls there is a blank after the '%d' // format characters in order to allow any number of blanks after a numeric @@ -270,14 +271,21 @@ return result; } -static int IntArrayToString(char *s, const int *a, int Base = 10, const char n[][MAXLANGCODE2] = NULL) +static int IntArrayToString(char *s, const int *a, int Base = 10, const char n[][MAXLANGCODE2] = NULL, const int *t = NULL) { char *q = s; int i = 0; while (a[i] || i == 0) { q += sprintf(q, Base == 16 ? "%s%X" : "%s%d", i ? "," : "", a[i]); -if (a[i] && n && *n[i]) - q += sprintf(q, "=%s", n[i]); +const char *Delim = "="; +if (a[i]) { + if (n && *n[i]) { + q += sprintf(q, "%s%s", Delim, n[i]); + Delim = ""; + } + if (t && t[i]) + q += sprintf(q, "%...@%d", Delim, t[i]); + } if (!a[i]) break; i++; @@ -286,32 +294,32 @@ return q - s; } -void cChannel::SetPids(int Vpid, int Ppid, int Vtype, int *Apids, char ALangs[][MAXLANGCODE2], int *Dpids, char DLangs[][MAXLANGCODE2], int *Spids, char SLangs[][MAXLANGCODE2], int Tpid) +void cChannel::SetPids(int Vpid, int Ppid, int Vtype, int *Apids, char ALangs[][MAXLANGCODE2], int *Dpids, int *Dtypes, char DLangs[][MAXLANGCODE2], int *Spids, char SLangs[][MAXLANGCODE2], int Tpid) { int mod = CHANNELMOD_NONE; if (vpid != Vpid || ppid != Ppid || vtype != Vtype || tpid != Tpid) mod |= CHANNELMOD_PIDS; - int m = IntArraysDiffer(apids, Apids, alangs, ALangs) | IntArraysDiffer(dpids, Dpids, dlangs, DLangs) | IntArraysDiffer(spids, Spids, slangs, SLangs); + int m = IntArraysDiffer(apids, Apids, alangs, ALangs) | IntArraysDiffer(dpids, Dpids, dlangs, DLangs) | IntArraysDiffer(dtypes, Dtypes) | IntArraysDiffer(spids, Spids, slangs, SLangs); if (m & STRDIFF) mod |= CHANNELMOD_LANGS; if (m & VALDIFF) mod |= CHANNELMOD_PIDS; if (mod) { - const int BufferSize = (MAXAPIDS + MAXDPIDS) * (5 + 1 + MAXLANGCODE2) + 10; // 5 digits plus delimiting ',' or ';' plus optional '=cod+cod', +10: paranoia + const int BufferSize = (MAXAPIDS + MAXDPIDS) * (5 + 1 + MAXLANGCODE2 + 5) + 10; // 5 digits plus delimiting ',' or ';' plus optional '=cod+...@type', +10: paranoia char OldApidsBuf[BufferSize]; char NewApidsBuf[BufferSize]; char *q = OldApidsBuf; q += IntArrayToString(q, apids, 10, alangs); if (dpids[0]) { *q++ = ';'; -q += IntArrayToString(q, dpids, 10, dlangs); +q += IntArrayToString(q, dpids, 10, dlangs, dtypes); } *q = 0; q = NewApidsBuf; q += IntArrayToString(q, Apids, 10, ALangs); if (Dpids[0]) { *q++ = ';'; -q += IntArrayToString(q, Dpids, 10, DLangs); +q += IntArrayToString(q, Dpids, 10, DLangs, Dtypes); } *q = 0; const int SBufferSize = MAXSPIDS * (5 + 1 + MAXLANGCODE2) + 10; // 5 digits plus delimiting ',' or ';' plus optional '=cod', +10: paranoia @@ -335,6 +343,7 @@ apids[MAXAPIDS] = 0; for (int i = 0; i < MAXDPIDS; i++) { dpids[i] = Dpids[i]; + dtypes[i] = Dtypes[i]; strn0cpy(dlangs[i], DLangs[i], MAXLANGCODE2); } dpids[MAXDPIDS] = 0; @@ -484,13 +493,13 @@ if (Channel->vpid && Channel->vtype) q += snprintf(q, sizeof(vpidbuf) - (q - vpidbuf), "=%d", Channel->vtype); *q = 0; - const int BufferSize = (MAXAPIDS + MAXDPIDS) * (5 + 1 + MAXLANGCODE2) + 10; // 5 digits plus delimiting ',' or ';' plus optional '=cod+cod', +10: paranoia + const int BufferSize = (MAXAPIDS + MAXDPIDS) * (5 + 1 + MAXLANGCODE2 + 5) + 10; // 5 digits plus delimiting ',' or ';' plus optional '=cod+...@type', +10: paranoia
Re: [vdr] vdr and aac support
El Viernes, 21 de Mayo de 2010, Eric Valette escribió: > On 18/05/2010 22:00, Jose Alberto Reguero wrote: > > Here is a patch based in Klaus aac pacth that add support for eac3 sound > > in vdr. > > Hi, > > I applied manually your patch on my own vdr-1.7.14 source tree. It seems > to work as far as vdr is concerened but it breaks other plugin such as > vdr live and vdr streamdev. > > Did I miss something (I will double check, as for some reason I had some > rejecst ad had to apply part of it manually). > > --eric > > I have the attached patch for streamdev. Jose Alberto Index: server/livestreamer.c === RCS file: /var/cvsroot/streamdev/server/livestreamer.c,v retrieving revision 1.29 diff -r1.29 livestreamer.c 174a175 > case SI::EnhancedAC3DescriptorTag: ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr and aac support
El Martes, 18 de Mayo de 2010, Jose Alberto Reguero escribió: > El Martes, 18 de Mayo de 2010, Luca Olivetti escribió: > > Al 18/05/10 21:43, En/na Luca Olivetti ha escrit: > > > (i.e. it only adds SI::AACDescriptorTag) > > > > > > I must have missed some patch along the way :-/ > > > > Ok, they were in the "Recording DVB-T HD infrance" (sic). > > It appears that spain is using the same standard. > > > > Bye > > Here is a patch based in Klaus aac pacth that add support for eac3 sound in > vdr. > > Jose Alberto Patch for xineliboutput to support eac3. With this patch you don't need to patch the latest xine-lib-1.2. Jose Alberto Index: xine/ts2es.c === RCS file: /cvsroot/xineliboutput/vdr-xineliboutput/xine/ts2es.c,v retrieving revision 1.11 diff -r1.11 ts2es.c 33a34 > intnumpreview; 78a80,85 > if (this->stream_type == STREAM_AUDIO_EAC3) { > this->xine_buf_type |= BUF_AUDIO_EAC3; > this->buf->type = this->xine_buf_type; > return; > } > 163c170,177 < this->buf->decoder_flags |= BUF_FLAG_FRAME_END; --- > if (this->numpreview<5) > this->numpreview++; > if (this->numpreview == 1) > this->buf->decoder_flags = BUF_FLAG_HEADER | BUF_FLAG_FRAME_END; > else if (this->numpreview < 5) > this->buf->decoder_flags = BUF_FLAG_PREVIEW; > else > this->buf->decoder_flags |= BUF_FLAG_FRAME_END; 310a325,326 > data->numpreview=0; > ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr xine-lib eac3
El Domingo, 13 de Junio de 2010, Luca Olivetti escribió: > Al 25/03/10 16:08, En/na Jose Alberto Reguero ha escrit: > > Patch for xine-lib that don't need to patch remux.c to work. > > Today I applied this patch (strange it isn't in xine-lib-1.2 yet) but > there's still no sound on tvehd (vdr 1.7.15, vdr-xine and playing the ts > directly through xine). > Do I need some special options to configure xine-lib for this patch to > take effect? > > Bye I use the latest xine-lib hg without patches and xineliboutput with the attached patch. Live TV are ok, but the recordings have drop outs. vdr-xine don't work with eac3. Jose Alberto Index: xine/ts2es.c === RCS file: /cvsroot/xineliboutput/vdr-xineliboutput/xine/ts2es.c,v retrieving revision 1.12 diff -r1.12 ts2es.c 33a34 > intnumpreview; 165,169c166,181 < < this->buf->decoder_flags |= BUF_FLAG_FRAME_END; < < result = this->buf; < this->buf = NULL; --- > if (!this->video) { > if (this->numpreview<5) > this->numpreview++; > if (this->numpreview == 1) > this->buf->decoder_flags = BUF_FLAG_HEADER | BUF_FLAG_FRAME_END; > else if (this->numpreview < 5) > this->buf->decoder_flags = BUF_FLAG_PREVIEW; > else > this->buf->decoder_flags |= BUF_FLAG_FRAME_END; > result = this->buf; > this->buf = NULL; > } else { > this->buf->decoder_flags |= BUF_FLAG_FRAME_END; > result = this->buf; > this->buf = NULL; > } 177d188 < 313a325,326 > data->numpreview=0; > ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr xine-lib eac3
El Domingo, 13 de Junio de 2010, Luca Olivetti escribió: > Al 25/03/10 16:08, En/na Jose Alberto Reguero ha escrit: > > Patch for xine-lib that don't need to patch remux.c to work. > > Today I applied this patch (strange it isn't in xine-lib-1.2 yet) but > there's still no sound on tvehd (vdr 1.7.15, vdr-xine and playing the ts > directly through xine). > Do I need some special options to configure xine-lib for this patch to > take effect? > > Bye With this two patches vdr-xine work with eac3. I can't test if it still work with normal ac3. One patch is for the plugin, and the other is for xine-lib 1.2. Jose Alberto diff -ur xine-0.9.3/vdr172remux.c xine-0.9.3.new/vdr172remux.c --- xine-0.9.3/vdr172remux.c 2009-04-12 13:52:32.0 +0200 +++ xine-0.9.3.new/vdr172remux.c 2010-09-20 23:49:10.19914 +0200 @@ -1703,8 +1703,17 @@ const uchar *Payload = Data + PesPayloadOffset; const int PayloadCount = Count - PesPayloadOffset; + bool ac3; + int framesize; - if (Data[3] == 0xBD && PayloadCount >= 9 && ((Payload[0] & 0xF0) == 0x80) && Payload[4] == 0x0B && Payload[5] == 0x77 && frameSizes[Payload[8]] > 0) { + if (PayloadCount < 10) + return -1; + ac3 = ((Payload[9] >> 3) & 0x1f) <= 10; + if ( ac3) + framesize = frameSizes[Payload[8]]; + else + framesize = (Payload[7] + 1) << 1; + if (Data[3] == 0xBD && ((Payload[0] & 0xF0) == 0x80) && Payload[4] == 0x0B && Payload[5] == 0x77 && framesize > 0) { if (TrackIndex) *TrackIndex = Payload[0] - 0x80; @@ -1906,7 +1915,10 @@ state++; continue; case get_length: - ac3todo = 2 * frameSizes[*data]; + if (((*(data + 1) >> 3) & 0x1f) <= 10) + ac3todo = 2 * frameSizes[*data]; + else + ac3todo = (*(data - 1) + 1) << 1; // frameSizeCode was invalid => restart searching if (ac3todo <= 0) { // reset PES header instead of using a wrong one @@ -1971,6 +1983,9 @@ int cDolbyRepacker::BreakAt(const uchar *Data, int Count) { + bool ac3; + int framesize; + if (initiallySyncing) return -1; // fill the packet buffer completely until we have synced once // enough data for test? @@ -1984,12 +1999,18 @@ if (ac3todo > 0) return headerLen + ac3todo; // enough data for test? - if (Count < headerLen + 5) + if (Count < headerLen + 6) return -1; const uchar *data = Data + headerLen; // break after ac3 frame? - if (data[0] == 0x0B && data[1] == 0x77 && frameSizes[data[4]] > 0) - return headerLen + 2 * frameSizes[data[4]]; + ac3 = ((data[5] >> 3) & 0x1f) <= 10; + if ( ac3) + framesize = 2 * frameSizes[data[4]]; + else + framesize = (data[3] + 1) << 1; + if (data[0] == 0x0B && data[1] == 0x77 && framesize > 0) + return headerLen + framesize; + return -1; } diff -r 9679028a161b src/demuxers/demux_mpeg_pes.c --- a/src/demuxers/demux_mpeg_pes.c Wed Jul 21 15:52:00 2010 + +++ b/src/demuxers/demux_mpeg_pes.c Tue Sep 21 00:54:22 2010 +0200 @@ -103,6 +103,7 @@ uint8_t preview_data[ MAX_PREVIEW_SIZE ]; off_t preview_size, preview_done; + uint8_t preview_eac3; } demux_mpeg_pes_t ; typedef struct { @@ -931,10 +932,21 @@ buf->content = p+4; buf->size = this->packet_len-4; - if (track & 0x8) { -buf->type = BUF_AUDIO_DTS + (track & 0x07); /* DVDs only have 8 tracks */ + if (((p[9] >> 3) & 0x1f) <= 10) { +if (track & 0x8) { + buf->type = BUF_AUDIO_DTS + (track & 0x07); /* DVDs only have 8 tracks */ +} else { + buf->type = BUF_AUDIO_A52 + track; +} } else { -buf->type = BUF_AUDIO_A52 + track; +buf->type = BUF_AUDIO_EAC3; +if (this->preview_eac3 < 2) + this->preview_eac3++; +if (this->preview_eac3 == 1) + buf->decoder_flags = BUF_FLAG_HEADER | BUF_FLAG_FRAME_END; +else { + buf->decoder_flags |= BUF_FLAG_FRAME_END; +} } buf->pts = this->pts; if( !this->preview_mode ) @@ -1548,6 +1560,7 @@ */ this->last_cell_time = 0; this->send_newpts = 1; + this->preview_eac3 = 0; if( !playing ) { this->buf_flag_seek = 0; ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr xine-lib eac3
El Domingo 26 Septiembre 2010, dplu escribió: > Hi > > I Just test your patch, thanks for it, it applied well but seems not > working, no e-ac3 sound on sample e-ac3 record for French DVB-T but AC3 > sound is still OK > > Which xine-lib 1.2 did you use ? this one : > http://hg.debian.org/hg/xine-lib/xine-lib-1.2/ > is not allways well synchronized, for example the patch for demux_ts on > 1.1.18 changeset a1ba73e0b475 (april 9) is not on 1.2 > > I will check another time to see if I made no error on patching > > Regards > You need a recent ffmpeg. I use latest hg xine-lib-1.2, and latest ffmpeg svn. Jose Alberto. > Le Tuesday 21 September 2010 00:57:39 Jose Alberto Reguero, vous avez écrit : > > El Domingo, 13 de Junio de 2010, Luca Olivetti escribió: > > > Al 25/03/10 16:08, En/na Jose Alberto Reguero ha escrit: > > > > Patch for xine-lib that don't need to patch remux.c to work. > > > > > > Today I applied this patch (strange it isn't in xine-lib-1.2 yet) but > > > there's still no sound on tvehd (vdr 1.7.15, vdr-xine and playing the > > > ts directly through xine). > > > Do I need some special options to configure xine-lib for this patch to > > > take effect? > > > > > > Bye > > > > With this two patches vdr-xine work with eac3. I can't test if it still > > work with normal ac3. One patch is for the plugin, and the other is for > > xine-lib 1.2. > > > > 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] vdr xine-lib eac3
El Lunes 27 Septiembre 2010, dplu escribió: > Hi > > @Darren Salt > Oupss you're right, I had another old patch for e-ac3 support auto applied > I clean all now > > @Jose Alberto > By the way, we are two person having made same test : not working with this > sample of french DVB-T HD , here is detail given by ffplay > > sample : http://dl.free.fr/cMNuFuG8X > > Stream #0.0[0xdc]: Video: h264, yuv420p, 1440x1080 [PAR 4:3 DAR 16:9], > 50 fps, 50 tbr, 90k tbn, 50 tbc > Stream #0.1[0xe7](qaa): Audio: eac3, 48000 Hz, 5.1, s16, 256 kb/s > Stream #0.2[0xe6](fra): Audio: eac3, 48000 Hz, stereo, s16, 128 kb/s > Stream #0.3[0xf0](fra): Subtitle: dvbsub > > Can you please test this small file (48 Mo) and tell us if OK or not, this > should be a good direction to go. I will rebuild a full new dev env on my > machine > > Many thanks for your help > > Best regards > 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 > Le Sunday 26 September 2010 20:56:32 Darren Salt, vous avez écrit : > > I demand that dplu may or may not have written... > > > > [snip] > > > > > http://hg.debian.org/hg/xine-lib/xine-lib-1.2/ > > > is not allways well synchronized, for example the patch for demux_ts on > > > 1.1.18 changeset a1ba73e0b475 (april 9) is not on 1.2 > > > > It is... > > > > [snip] > > ___ > 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
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 diff -ur xine-0.9.3/vdr172remux.c xine-0.9.3.new/vdr172remux.c --- xine-0.9.3/vdr172remux.c 2009-04-12 13:52:32.0 +0200 +++ xine-0.9.3.new/vdr172remux.c 2010-09-29 01:58:34.79803 +0200 @@ -1703,8 +1703,20 @@ const uchar *Payload = Data + PesPayloadOffset; const int PayloadCount = Count - PesPayloadOffset; + bool ac3; + int framesize; + unsigned short size; - if (Data[3] == 0xBD && PayloadCount >= 9 && ((Payload[0] & 0xF0) == 0x80) && Payload[4] == 0x0B && Payload[5] == 0x77 && frameSizes[Payload[8]] > 0) { + if (PayloadCount < 10) + return -1; + ac3 = ((Payload[9] >> 3) & 0x1f) <= 10; + if ( ac3) + framesize = frameSizes[Payload[8]]; + else { + size = Payload[7] + Payload[6] * 256; + framesize = ((size & 0x07FF) + 1) << 1; + } + if (Data[3] == 0xBD && ((Payload[0] & 0xF0) == 0x80) && Payload[4] == 0x0B && Payload[5] == 0x77 && framesize > 0) { if (TrackIndex) *TrackIndex = Payload[0] - 0x80; @@ -1860,6 +1872,7 @@ int done = 6 + 3 + Data[8]; int todo = Count - done; const uchar *data = Data + done; + unsigned short size; // look for 0x0B 0x77 while (todo > 0) { @@ -1906,7 +1919,12 @@ state++; continue; case get_length: - ac3todo = 2 * frameSizes[*data]; + if (((*(data + 1) >> 3) & 0x1f) <= 10) + ac3todo = 2 * frameSizes[*data]; + else { + size = chk2 + chk1 * 256; + ac3todo = ((size & 0x07FF) + 1) << 1; + } // frameSizeCode was invalid => restart searching if (ac3todo <= 0) { // reset PES header instead of using a wrong one @@ -1971,6 +1989,10 @@ int cDolbyRepacker::BreakAt(const uchar *Data, int Count) { + bool ac3; + int framesize; + unsigned short size; + if (initiallySyncing) return -1; // fill the packet buffer completely until we have synced once // enough data for test? @@ -1984,12 +2006,20 @@ if (ac3todo > 0) return headerLen + ac3todo; // enough data for test? - if (Count < headerLen + 5) + if (Count < headerLen + 6) return -1; const uchar *data = Data + headerLen; // break after ac3 frame? - if (data[0] == 0x0B && data[1] == 0x77 && frameSizes[data[4]] > 0) - return headerLen + 2 * frameSizes[data[4]]; + ac3 = ((data[5] >> 3) & 0x1f) <= 10; + if ( ac3) + framesize = 2 * frameSizes[data[4]]; + else { + size = data[3] + data[2] * 256; + framesize = ((size & 0x07FF) + 1) << 1; + } + if (data[0] == 0x0B && data[1] == 0x77 && framesize > 0) + return headerLen + framesize; + return -1; } ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
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
Re: [vdr] vdr xine-lib eac3
The error you report doesn't matter. It is because there is no case for EAC3. I have an additional patch to use only two channels, and I don't have this error. You can use the patch and comment the line: this->context->request_channels = 2; and then you don't have the error. I try with the sample you give to me. If you want you can give me another sample. Jose Alberto El Jueves 30 Septiembre 2010, dplu escribió: > Hi > > In fact, I use a very recent ffmpeg (less than one month) and the very > latest xine-lib 1.2 with no patch except yours > > I found my error message in combined/ffmpeg/ff_audio_decoder.c > > This is strange that you cannot reproduce as long we (my colleague + me) > are able to have it every time and other user report this problem using > xlo plugin + sxfe (on French DVB forum) > > I can update my ffmpeg to the very latest release but not sure it will > change something (ffplay or mplayer works fine) > > Nobody else can test our sample please ? > > Have a nive evening > > Le Thursday 30 September 2010 20:10:54 Jose Alberto Reguero, vous avez écrit : > > 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 &
Re: [vdr] vdr xine-lib eac3
Playing with xine-ui and demux ts don't work well. You must play it with vdr- xine. Jose Alberto El Sábado 02 Octubre 2010, dplu escribió: > Hi > > I play with your sample , it has only one audio track and strictly no sound > on it ... > > So I decide to replace my recent xine-ui by the very latest here > http://hg.debian.org/hg/xine-lib/xine-ui/ > > xine-lib is latest one with only your patch in mpeg-pes > ffmpeg is the full latest git with absolutely no patch > > the result is the same .. > > So I destroy the /.xine/config file and I can open the ts file and play > with audio track .. if I play too hard, I have the message saying : > > -load_plugins: plugin vdpau_h264 will be used for video streamtype 4d. > -Broken NAL, skip it. > -ffmpeg_audio_dec: augmentation du buffer à 98304 pour éviter sa > saturation. -load_plugins: plugin ffmpegaudio will be used for audio > streamtype 41. -ffmpeg_audio_dec: trying to open null codec > -audio_decoder: no plugin available to handle 'E-AC-3' > > no more sound available ... so it's better > > Back to vdr, I try to play with sound track and crash immediatly > I remark that when crashing, and running xine-ui to reconnect to vdr > playing my records, it has stop replay and fall back to live TV .. strange > !!! > > I was focusing on xine but on vdr log there is a message I didn't saw : > > -SetPlayMode: 0 > -SetPlayMode: 1 > -SetPlayMode: 0 > -SetPlayMode: 1 > -SetDigitalAudioDevice: 1 > -::write(2048) returned -1, error 32: Broken pipe > -vdr-xine: Client disconnected! > -SetPlayMode: 0 > -SetPlayMode: 1 > -SetDigitalAudioDevice: 0 > > I will report on our forum this event and ask my colleague to check also > this part if they have time. In a short way does it means that vdr-xine > ask xine-ui to break itself and stop replaying ? > > For myself, I will break for one week hoping somebody will continue to test > or find what can be wrong in our basis config > > Thanks for your help and sorry to not have enough skills to debug or > understand the source code > > Best regards > > Le Saturday 02 October 2010 12:54:07 Jose Alberto Reguero, vous avez écrit : > > I use latsest xine-ui hg. The problem may be ffmpeg or xine-lib or > > xine-ui. Are you sure that you have the latest versions and no aditional > > patches? You can do hg diff o svn diff to see the changes you have in > > the repositories. Here is a sample: > > http://dl.free.fr/pByrnmYwZ > > > > Jose Alberto > > > > El Viernes 01 Octubre 2010, dplu escribió: > > > Hi > > > > > > I continue to search why it fail ... with no luck, hope other people > > > will have time to make test > > > > > > basis test setup : > > > vdr 1.7.15 extention patch + patch e-ac3 for vdr-xine > > > xine-ui 0.99.6 > > > latest git ffmpeg > > > latest xine 1.2 with basic e-ac3 patch for only > > > > > > From vdr : crash every time I change audio track as described > > > previously > > > > > > Second test > > > Try opening the TS file from xine-ui directly, same behaviour > > > > > > op mode : > > > > > > At startup sound track is "0" (should be "fra"), play nice > > > track -- > > > display track "off" , no crash > > > track ++ > > > display "0" instead of "fra" , no crash > > > track ++ > > > display "qaa" , it's real name .. crash in couple of seconds > > > > > > Here is the log with high verbosity > > > http://pastebin.com/BvGKDk0v > > > > > > Hope this help you, I underline in yellow some strange thing > > > > > > By the way, if you have time, can you post a sample of recording made > > > at home so we can also test your sample with our configuration > > > > > > Many thanks for your help and have a nice week end > > > > > > Best regards > > > > > > Le Thursday 30 September 2010 22:51:34 dplu, vous avez écrit : > > > > Here is the result of my colleague using vdr-sxfe verbose and > > > > changing the audio track > > > > > > > > [9665] [demux_vdr] audio stream changed: 0341 -> 03410001 > > > > Erreur de segmentation (=segfault error) > > > > > > > > As you can see this is the same error , he use this patch > > > > > > > > diff -r cb99a1abe986 src/combined/ffmpeg/ff_audio_decoder.c > > > > --- a/src/combined/ffmpeg/ff_audi
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 > > El Sábado 02 Octubre 2010, dplu escribió: > > Hi > > > > I play with your sample , it has only one audio track and strictly no > > sound on it ... > > > > So I decide to replace my recent xine-ui by the very latest here > > http://hg.debian.org/hg/xine-lib/xine-ui/ > > > > xine-lib is latest one with only your patch in mpeg-pes > > ffmpeg is the full latest git with absolutely no patch > > > > the result is the same .. > > > > So I destroy the /.xine/config file and I can open the ts file and play > > with audio track .. if I play too hard, I have the message saying : > > > > -load_plugins: plugin vdpau_h264 will be used for video streamtype 4d. > > -Broken NAL, skip it. > > -ffmpeg_audio_dec: augmentation du buffer à 98304 pour éviter sa > > saturation. -load_plugins: plugin ffmpegaudio will be used for audio > > streamtype 41. -ffmpeg_audio_dec: trying to open null codec > > -audio_decoder: no plugin available to handle 'E-AC-3' > > > > no more sound available ... so it's better > > > > Back to vdr, I try to play with sound track and crash immediatly > > I remark that when crashing, and running xine-ui to reconnect to vdr > > playing my records, it has stop replay and fall back to live TV .. > > strange !!! > > > > I was focusing on xine but on vdr log there is a message I didn't saw : > > > > -SetPlayMode: 0 > > -SetPlayMode: 1 > > -SetPlayMode: 0 > > -SetPlayMode: 1 > > -SetDigitalAudioDevice: 1 > > -::write(2048) returned -1, error 32: Broken pipe > > -vdr-xine: Client disconnected! > > -SetPlayMode: 0 > > -SetPlayMode: 1 > > -SetDigitalAudioDevice: 0 > > > > I will report on our forum this event and ask my colleague to check also > > this part if they have time. In a short way does it means that vdr-xine > > ask xine-ui to break itself and stop replaying ? > > > > For myself, I will break for one week hoping somebody will continue to > > test or find what can be wrong in our basis config > > > > Thanks for your help and sorry to not have enough skills to debug or > > understand the source code > > > > Best regards > > > > Le Saturday 02 October 2010 12:54:07 Jose Alberto Reguero, vous avez écrit : > > > I use latsest xine-ui hg. The problem may be ffmpeg or xine-lib or > > > xine-ui. Are you sure that you have the latest versions and no > > > aditional patches? You can do hg diff o svn diff to see the changes > > > you have in the repositories. Here is a sample: > > > http://dl.free.fr/pByrnmYwZ > > > > > > Jose Alberto > > > > > > El Viernes 01 Octubre 2010, dplu escribió: > > > > Hi > > > > > > > > I continue to search why it fail ... with no luck, hope other people > > > > will have time to make test > > > > > > > > basis test setup : > > > > vdr 1.7.15 extention patch + patch e-ac3 for vdr-xine > > > > xine-ui 0.99.6 > > > > latest git ffmpeg > > > > latest xine 1.2 with basic e-ac3 patch for only > > > > > > > > From vdr : crash every time I change audio track as described > > > > previously > > > > > > > > Second test > > > > Try opening the TS file from xine-ui directly, same behaviour > > > > > > > > op mode : > > > > > > > > At startup sound track is "0" (should be "fra"), play nice > > > > track -- > > > > display track "off" , no crash > > > > track ++ > > > > display "0" instead of "fra" , no crash > > > > track ++ > > > > display "qaa" , it's real name .. crash in couple of seconds > > > > > > > > Here is the log with high verbosity > > > > http://pastebin.com/BvGKDk0v > > > > > > > > Hope this help you, I underline in yellow some strange thing > > > > > > > > By the way, if you have time, can you post a sample of recording made > > > > at home so we can also test your sample with our configuration > > > > > > > > Many
Re: [vdr] Collecting patches for vdr-xine-0.9.4
On Lunes, 17 de Enero de 2011 21:37:06 Reinhard Nissl escribió: > Hi, > > it looks like I can find more time this week to work on vdr-xine. > > I've seen some patches for vdr-xine-0.9.3 (and xine-lib) in the > mailing list which address so far unsupported audio formats if I > recall correctly, as vdr-xine still uses PES and my c*Repackers. > > I'd like to invite you to send them again to me (privately). A > sample recording would be appreciated too. > > Bye. Attached are two patches to play dolby digital plus audio with vdr-xine. One for vdr-xine and another for xine-lib. There is an aditional patch to play dolby digital plus audio with xine-lib and a ts file. Jose Alberto diff -ur xine-0.9.3/vdr172remux.c xine-0.9.3.new/vdr172remux.c --- xine-0.9.3/vdr172remux.c 2009-04-12 13:52:32.0 +0200 +++ xine-0.9.3.new/vdr172remux.c 2010-09-29 01:58:34.79803 +0200 @@ -1703,8 +1703,20 @@ const uchar *Payload = Data + PesPayloadOffset; const int PayloadCount = Count - PesPayloadOffset; + bool ac3; + int framesize; + unsigned short size; - if (Data[3] == 0xBD && PayloadCount >= 9 && ((Payload[0] & 0xF0) == 0x80) && Payload[4] == 0x0B && Payload[5] == 0x77 && frameSizes[Payload[8]] > 0) { + if (PayloadCount < 10) + return -1; + ac3 = ((Payload[9] >> 3) & 0x1f) <= 10; + if ( ac3) + framesize = frameSizes[Payload[8]]; + else { + size = Payload[7] + Payload[6] * 256; + framesize = ((size & 0x07FF) + 1) << 1; + } + if (Data[3] == 0xBD && ((Payload[0] & 0xF0) == 0x80) && Payload[4] == 0x0B && Payload[5] == 0x77 && framesize > 0) { if (TrackIndex) *TrackIndex = Payload[0] - 0x80; @@ -1860,6 +1872,7 @@ int done = 6 + 3 + Data[8]; int todo = Count - done; const uchar *data = Data + done; + unsigned short size; // look for 0x0B 0x77 while (todo > 0) { @@ -1906,7 +1919,12 @@ state++; continue; case get_length: - ac3todo = 2 * frameSizes[*data]; + if (((*(data + 1) >> 3) & 0x1f) <= 10) + ac3todo = 2 * frameSizes[*data]; + else { + size = chk2 + chk1 * 256; + ac3todo = ((size & 0x07FF) + 1) << 1; + } // frameSizeCode was invalid => restart searching if (ac3todo <= 0) { // reset PES header instead of using a wrong one @@ -1971,6 +1989,10 @@ int cDolbyRepacker::BreakAt(const uchar *Data, int Count) { + bool ac3; + int framesize; + unsigned short size; + if (initiallySyncing) return -1; // fill the packet buffer completely until we have synced once // enough data for test? @@ -1984,12 +2006,20 @@ if (ac3todo > 0) return headerLen + ac3todo; // enough data for test? - if (Count < headerLen + 5) + if (Count < headerLen + 6) return -1; const uchar *data = Data + headerLen; // break after ac3 frame? - if (data[0] == 0x0B && data[1] == 0x77 && frameSizes[data[4]] > 0) - return headerLen + 2 * frameSizes[data[4]]; + ac3 = ((data[5] >> 3) & 0x1f) <= 10; + if ( ac3) + framesize = 2 * frameSizes[data[4]]; + else { + size = data[3] + data[2] * 256; + framesize = ((size & 0x07FF) + 1) << 1; + } + if (data[0] == 0x0B && data[1] == 0x77 && framesize > 0) + return headerLen + framesize; + return -1; } diff -r 9679028a161b src/demuxers/demux_mpeg_pes.c --- a/src/demuxers/demux_mpeg_pes.c Wed Jul 21 15:52:00 2010 + +++ b/src/demuxers/demux_mpeg_pes.c Tue Sep 21 00:54:22 2010 +0200 @@ -103,6 +103,7 @@ uint8_t preview_data[ MAX_PREVIEW_SIZE ]; off_t preview_size, preview_done; + uint8_t preview_eac3; } demux_mpeg_pes_t ; typedef struct { @@ -931,10 +932,21 @@ buf->content = p+4; buf->size = this->packet_len-4; - if (track & 0x8) { -buf->type = BUF_AUDIO_DTS + (track & 0x07); /* DVDs only have 8 tracks */ + if (((p[9] >> 3) & 0x1f) <= 10) { +if (track & 0x8) { + buf->type = BUF_AUDIO_DTS + (track & 0x07); /* DVDs only have 8 tracks */ +} else { + buf->type = BUF_AUDIO_A52 + track; +} } else { -buf->type = BUF_AUDIO_A52 + track; +buf->type = BUF_AUDIO_EAC3; +if (this->preview_eac3 < 2) + this->preview_eac3++; +if (this->preview_eac3 == 1) + buf->decoder_flags = BUF_FLAG_HEADER | BUF_FLAG_FRAME_END; +else { + buf->decoder_flags |= BUF_FLAG_FRAME_END; +} } buf->pts = this->pts; i
[vdr] Re: [linux-dvb] Kernel bug using kernel 2.6.17
I have problems with kernels newer that 2.6.16 and vdr. With kernel 2.6.17.9 see atached log1. With kernel 2.6.18-rc4 with kernels drivers and with last mercurial drivers see log2. After that errors I need to reboot. Thanks. Jose Alberto El Lunes, 3 de Julio de 2006 18:44, Jose Alberto Reguero escribió: > I have this kernel bug when I update to kernel 2.6.17 > I have no problem with 2.6.16 > Thanks. > Jose Alberto Aug 21 16:16:32 jar kernel: general protection fault: [1] SMP Aug 21 16:16:32 jar kernel: CPU 0 Aug 21 16:16:32 jar kernel: Modules linked in: ppdev nfsd exportfs lockd nfs_acl ipv6 autofs4 w83627hf hwmon_vid hwmon i2c_isa hidp l2cap bluetooth sunrpc cpufreq_ondemand vfat fat dm_mirror dm_mod video button battery ac parport_pc lp parport saa7134_dvb mt352 video_buf_dvb dvb_core nxt200x dvb_pll tda1004x snd_via82xx_modem usblp snd_via82xx saa7134 gameport video_buf snd_ac97_codec compat_ioctl32 snd_ac97_bus v4l2_common snd_mpu401_uart snd_rawmidi v4l1_compat snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq ir_kbd_i2c nvidia snd_seq_device ir_common sg ide_cd i2c_viapro floppy skge i2c_core ehci_hcd snd_pcm_oss snd_mixer_oss cdrom serio_raw ohci1394 ieee1394 snd_pcm uhci_hcd videodev snd_timer snd soundcore snd_page_alloc ext3 jbd sata_promise sata_via libata sd_mod scsi_mod Aug 21 16:16:32 jar kernel: Pid: 25510, comm: vdr Tainted: P 2.6.17.9 #1 Aug 21 16:16:32 jar kernel: RIP: 0010:[] {try_to_wake_up+45} Aug 21 16:16:32 jar kernel: RSP: 0018:81002f4f58f8 EFLAGS: 00010092 Aug 21 16:16:32 jar kernel: RAX: 6b6b6b6b6b6b6b6b RBX: 8073a480 RCX: Aug 21 16:16:32 jar kernel: RDX: RSI: 000f RDI: 81001a6eb080 Aug 21 16:16:32 jar kernel: RBP: 81002f4f5978 R08: R09: 81002f4f5908 Aug 21 16:16:32 jar kernel: R10: 81003c77c3f8 R11: 81003c77c148 R12: 000f Aug 21 16:16:32 jar kernel: R13: R14: 81001a6eb080 R15: 8073a480 Aug 21 16:16:32 jar kernel: FS: 41001940(0063) GS:806d7000() knlGS:f732f6d0 Aug 21 16:16:32 jar kernel: CS: 0010 DS: ES: CR0: 8005003b Aug 21 16:16:32 jar kernel: CR2: 2aaac000 CR3: 3ddd3000 CR4: 06e0 Aug 21 16:16:32 jar kernel: Process vdr (pid: 25510, threadinfo 81002f4f4000, task 810031987810) Aug 21 16:16:32 jar kernel: Stack: 2f4f5908 81002f4f5918 81002f4f5968 0292 Aug 21 16:16:32 jar kernel: Aug 21 16:16:32 jar kernel: 802a2ee1 Aug 21 16:16:32 jar kernel: Call Trace: {debug_mutex_add_waiter+152} Aug 21 16:16:32 jar kernel:{wake_up_process+16} {kthread_stop_sem+129} Aug 21 16:16:32 jar kernel:{kthread_stop+11} {:video_buf_dvb:videobuf_dvb_stop_feed+77} Aug 21 16:16:32 jar kernel: {:dvb_core:dmx_section_feed_stop_filtering+86} Aug 21 16:16:32 jar kernel: {:dvb_core:dvb_dmxdev_feed_stop+96} Aug 21 16:16:32 jar kernel: {:dvb_core:dvb_dmxdev_filter_stop+52} Aug 21 16:16:32 jar kernel: {:dvb_core:dvb_demux_release+103} Aug 21 16:16:32 jar kernel:{__fput+196} {fput+20} Aug 21 16:16:32 jar kernel:{free_poll_entry+33} {poll_freewait+42} Aug 21 16:16:32 jar kernel:{do_sys_poll+1002} {__pollwait+0} Aug 21 16:16:32 jar kernel:{default_wake_function+0} {default_wake_function+0} Aug 21 16:16:32 jar last message repeated 2 times Aug 21 16:16:32 jar kernel:{default_wake_function+0} {:dvb_core:dvb_usercopy+309} Aug 21 16:16:32 jar kernel: {:dvb_core:dvb_demux_do_ioctl+0} {audit_syscall_entry+316} Aug 21 16:16:32 jar kernel:{sys_poll+59} {tracesys+209} Aug 21 16:16:32 jar kernel: Aug 21 16:16:32 jar kernel: Code: 8b 40 18 48 8b 04 c5 20 90 6f 80 4c 03 78 08 4c 89 ff e8 03 Aug 21 16:16:32 jar kernel: RIP {try_to_wake_up+45} RSP Aug 21 16:16:32 jar kernel: <3>BUG: sleeping function called from invalid context at include/linux/rwsem.h:43 Aug 21 16:16:32 jar kernel: in_atomic():0, irqs_disabled():1 Aug 21 16:16:32 jar kernel: Aug 21 16:16:32 jar kernel: Call Trace: {__might_sleep+178} {blocking_notifier_call_chain+39} Aug 21 16:16:32 jar kernel:{profile_task_exit+21} {do_exit+37} Aug 21 16:16:32 jar kernel:{kernel_math_error+0} {do_general_protection+261} Aug 21 16:16:32 jar kernel:{error_exit+0} {try_to_wake_up+45} Aug 21 16:16:32 jar kernel: {debug_mutex_add_waiter+152} {wake_up_process+16} Aug 21 16:16:32 jar kernel:{kthread_stop_sem+129} {kthread_stop+11} Aug 21 16:16:32 jar kernel: {:video_buf_dvb:videobuf_dvb_stop_feed+77} Aug 21 16:16:32 jar kernel: {:dvb_core:dmx_section_feed_stop_filtering+86} Aug 21 16:16:32 jar kernel: {:dvb_core:dvb_dmxdev_feed_stop+96} Aug 21 16:16:32 jar kernel: {:dvb_core:dvb_
Re: [vdr] Re: [linux-dvb] Kernel bug using kernel 2.6.17
El Lunes, 21 de Agosto de 2006 22:26, Darren Salt escribió: > I demand that Jose Alberto Reguero may or may not have written... > > > I have problems with kernels newer that 2.6.16 and vdr. > > With kernel 2.6.17.9 see atached log1. > > With kernel 2.6.18-rc4 with kernels drivers and with last mercurial > > drivers see log2. > > After that errors I need to reboot. > > [snip] > > Does this happen without the proprietary graphics card taintware? Yes. I atach the log. Thanks. Jose Alberto Aug 22 01:48:18 jar kernel: general protection fault: [1] SMP Aug 22 01:48:18 jar kernel: CPU 0 Aug 22 01:48:18 jar kernel: Modules linked in: nfsd exportfs lockd nfs_acl ipv6 autofs4 w83627hf hwmon_vid hwmon i2c_isa hidp l2cap bluetooth sunrpc cpufreq_ondemand vfat fat dm_mirror dm_mod video button battery ac parport_pc lp parport saa7134_dvb mt352 video_buf_dvb dvb_core nxt200x dvb_pll tda1004x usblp saa7134 snd_via82xx_modem video_buf compat_ioctl32 v4l2_common v4l1_compat ir_kbd_i2c sg snd_via82xx ir_common gameport ide_cd serio_raw snd_seq_dummy uhci_hcd snd_ac97_codec snd_ac97_bus snd_mpu401_uart floppy snd_seq_oss snd_seq_midi_event snd_seq ehci_hcd snd_pcm_oss snd_mixer_oss ohci1394 cdrom snd_pcm i2c_viapro i2c_core skge videodev snd_rawmidi snd_timer snd_page_alloc ieee1394 snd_seq_device snd soundcore ext3 jbd sata_promise sata_via libata sd_mod scsi_mod Aug 22 01:48:18 jar kernel: Pid: 2450, comm: vdr Not tainted 2.6.17.9 #1 Aug 22 01:48:18 jar kernel: RIP: 0010:[] {try_to_wake_up+45} Aug 22 01:48:18 jar kernel: RSP: :8100302878f8 EFLAGS: 00010092 Aug 22 01:48:18 jar kernel: RAX: 6b6b6b6b6b6b6b6b RBX: 8073a480 RCX: Aug 22 01:48:18 jar kernel: RDX: RSI: 000f RDI: 81002fcac0c0 Aug 22 01:48:18 jar kernel: RBP: 810030287978 R08: R09: 810030287908 Aug 22 01:48:18 jar kernel: R10: 81003cc8be18 R11: 81003cc8bb68 R12: 000f Aug 22 01:48:18 jar kernel: R13: R14: 81002fcac0c0 R15: 8073a480 Aug 22 01:48:18 jar kernel: FS: 43005940(0063) GS:806d7000() knlGS: Aug 22 01:48:18 jar kernel: CS: 0010 DS: ES: CR0: 8005003b Aug 22 01:48:18 jar kernel: CR2: 2aaac000 CR3: 30878000 CR4: 06e0 Aug 22 01:48:18 jar kernel: Process vdr (pid: 2450, threadinfo 810030286000, task 810030263100) Aug 22 01:48:18 jar kernel: Stack: 30287908 810030287918 810030287968 0292 Aug 22 01:48:18 jar kernel: Aug 22 01:48:18 jar kernel: 802a2ee1 Aug 22 01:48:18 jar kernel: Call Trace: {debug_mutex_add_waiter+152} Aug 22 01:48:18 jar kernel:{wake_up_process+16} {kthread_stop_sem+129} Aug 22 01:48:18 jar kernel:{kthread_stop+11} {:video_buf_dvb:videobuf_dvb_stop_feed+77} Aug 22 01:48:18 jar kernel: {:dvb_core:dmx_section_feed_stop_filtering+86} Aug 22 01:48:18 jar kernel: {:dvb_core:dvb_dmxdev_feed_stop+96} Aug 22 01:48:18 jar kernel: {:dvb_core:dvb_dmxdev_filter_stop+52} Aug 22 01:48:18 jar kernel: {:dvb_core:dvb_demux_release+103} Aug 22 01:48:18 jar kernel:{__fput+196} {fput+20} Aug 22 01:48:18 jar kernel:{free_poll_entry+33} {poll_freewait+42} Aug 22 01:48:18 jar kernel:{do_sys_poll+1002} {__pollwait+0} Aug 22 01:48:18 jar kernel:{default_wake_function+0} {default_wake_function+0} Aug 22 01:48:18 jar last message repeated 2 times Aug 22 01:48:18 jar kernel:{default_wake_function+0} {:dvb_core:dvb_usercopy+309} Aug 22 01:48:18 jar kernel: {:dvb_core:dvb_demux_do_ioctl+0} {audit_syscall_entry+316} Aug 22 01:48:18 jar kernel:{sys_poll+59} {tracesys+209} Aug 22 01:48:18 jar kernel: Aug 22 01:48:18 jar kernel: Code: 8b 40 18 48 8b 04 c5 20 90 6f 80 4c 03 78 08 4c 89 ff e8 03 Aug 22 01:48:18 jar kernel: RIP {try_to_wake_up+45} RSP Aug 22 01:48:18 jar kernel: <3>BUG: sleeping function called from invalid context at include/linux/rwsem.h:43 Aug 22 01:48:18 jar kernel: in_atomic():0, irqs_disabled():1 Aug 22 01:48:18 jar kernel: Aug 22 01:48:18 jar kernel: Call Trace: {__might_sleep+178} {blocking_notifier_call_chain+39} Aug 22 01:48:18 jar kernel:{profile_task_exit+21} {do_exit+37} Aug 22 01:48:18 jar kernel:{kernel_math_error+0} {do_general_protection+261} Aug 22 01:48:18 jar kernel:{error_exit+0} {try_to_wake_up+45} Aug 22 01:48:18 jar kernel: {debug_mutex_add_waiter+152} {wake_up_process+16} Aug 22 01:48:18 jar kernel:{kthread_stop_sem+129} {kthread_stop+11} Aug 22 01:48:18 jar kernel: {:video_buf_dvb:videobuf_dvb_stop_feed+77} Aug 22 01:48:18 jar kernel: {:dvb_core:dmx_section_feed_stop_filtering+86} Aug 22 01:48:18 jar kernel:
Re: [vdr] Re: [linux-dvb] Kernel bug using kernel 2.6.17
El Martes, 22 de Agosto de 2006 01:59, Jose Alberto Reguero escribió: > El Lunes, 21 de Agosto de 2006 22:26, Darren Salt escribió: > > I demand that Jose Alberto Reguero may or may not have written... > > > > > I have problems with kernels newer that 2.6.16 and vdr. > > > With kernel 2.6.17.9 see atached log1. > > > With kernel 2.6.18-rc4 with kernels drivers and with last mercurial > > > drivers see log2. > > > After that errors I need to reboot. > > > > [snip] > > > > Does this happen without the proprietary graphics card taintware? > > Yes. I atach the log. > Thanks. > Jose Alberto Another log with kernel 2.6.27.11 What poison_obj means? What can produce Slab corruption? How I can debug it? Thanks. Jose Alberto Aug 29 01:16:36 jar kernel: general protection fault: [1] SMP Aug 29 01:16:36 jar kernel: CPU 0 Aug 29 01:16:36 jar kernel: Modules linked in: nfsd exportfs lockd nfs_acl ipv6 autofs4 w83627hf hwmon_vid hwmon i2c_isa hidp l2cap bluetooth sunrpc cpufreq_ondemand vfat fat dm_mirror dm_mod video button battery ac parport_pc lp parport saa7134_dvb mt352 video_buf_dvb dvb_core nxt200x dvb_pll tda1004x snd_via82xx_modem snd_via82xx gameport snd_ac97_codec snd_ac97_bus snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq saa7134 snd_pcm_oss snd_mixer_oss video_buf snd_pcm compat_ioctl32 msp3400 saa7127 snd_timer usblp saa7115 nvidia tda9887 ir_kbd_i2c tuner snd_mpu401_uart snd_rawmidi snd_seq_device snd v4l2_common sg ivtv i2c_viapro ir_common uhci_hcd i2c_algo_bit v4l1_compat tveeprom soundcore ehci_hcd floppy i2c_core snd_page_alloc ide_cd serio_raw skge videodev cdrom ext3 jbd sata_promise sata_via libata sd_mod scsi_mod Aug 29 01:16:36 jar kernel: Pid: 2523, comm: vdr Tainted: P 2.6.17.11 #1 Aug 29 01:16:36 jar kernel: RIP: 0010:[] {try_to_wake_up+45} Aug 29 01:16:36 jar kernel: RSP: 0018:81002e78fb88 EFLAGS: 00010096 Aug 29 01:16:36 jar kernel: RAX: 6b6b6b6b6b6b6b6b RBX: 8073a480 RCX: Aug 29 01:16:36 jar kernel: RDX: RSI: 000f RDI: 81002cf4a080 Aug 29 01:16:36 jar kernel: RBP: 81002e78fc08 R08: R09: 81002e78fb98 Aug 29 01:16:36 jar kernel: R10: 44005f98 R11: 0206 R12: 000f Aug 29 01:16:36 jar kernel: R13: R14: 81002cf4a080 R15: 8073a480 Aug 29 01:16:36 jar kernel: FS: 43005940(0063) GS:806d7000() knlGS:f73d96d0 Aug 29 01:16:36 jar kernel: CS: 0010 DS: ES: CR0: 8005003b Aug 29 01:16:36 jar kernel: CR2: 00e1 CR3: 2eebb000 CR4: 06e0 Aug 29 01:16:36 jar kernel: Process vdr (pid: 2523, threadinfo 81002e78e000, task 81002e76e100) Aug 29 01:16:36 jar kernel: Stack: 2e78fb98 81002e78fba8 81002e78fbf8 0296 Aug 29 01:16:36 jar kernel: Aug 29 01:16:36 jar kernel: 802a2de1 Aug 29 01:16:36 jar kernel: Call Trace: {debug_mutex_add_waiter+152} Aug 29 01:16:36 jar kernel:{wake_up_process+16} {kthread_stop_sem+129} Aug 29 01:16:36 jar kernel:{kthread_stop+11} {:video_buf_dvb:videobuf_dvb_stop_feed+77} Aug 29 01:16:36 jar kernel: {:dvb_core:dmx_section_feed_stop_filtering+86} Aug 29 01:16:36 jar kernel: {:dvb_core:dvb_dmxdev_feed_stop+96} Aug 29 01:16:36 jar kernel: {:dvb_core:dvb_dmxdev_filter_start+386} Aug 29 01:16:36 jar kernel:{_spin_unlock+9} {:dvb_core:dvb_demux_do_ioctl+603} Aug 29 01:16:36 jar vdr: [3321] cAudioRepacker(0xC0): skipped 36 bytes to sync on next audio frame Aug 29 01:16:36 jar kernel: {:dvb_core:dvb_usercopy+228} {:dvb_core:dvb_demux_do_ioctl+0} Aug 29 01:16:37 jar kernel:{poison_obj+39} {cache_free_debugcheck+761} Aug 29 01:16:37 jar kernel: {:dvb_core:dvb_demux_ioctl+16} {do_ioctl+94} Aug 29 01:16:37 jar kernel:{vfs_ioctl+602} {sys_ioctl+95} Aug 29 01:16:37 jar kernel:{tracesys+209} Aug 29 01:16:37 jar kernel: Aug 29 01:16:37 jar kernel: Code: 8b 40 18 48 8b 04 c5 20 90 6f 80 4c 03 78 08 4c 89 ff e8 0a Aug 29 01:16:37 jar kernel: RIP {try_to_wake_up+45} RSP Aug 29 01:16:37 jar kernel: <3>BUG: sleeping function called from invalid context at include/linux/rwsem.h:43 Aug 29 01:16:37 jar kernel: in_atomic():0, irqs_disabled():1 Aug 29 01:16:37 jar kernel: Aug 29 01:16:37 jar kernel: Call Trace: {__might_sleep+178} {blocking_notifier_call_chain+39} Aug 29 01:16:37 jar kernel:{profile_task_exit+21} {do_exit+37} Aug 29 01:16:37 jar kernel:{kernel_math_error+0} {do_general_protection+261} Aug 29 01:16:37 jar kernel:{error_exit+0} {try_to_wake_up+45} Aug 29 01:16:37 jar kernel: {debug_mutex_add_waiter+152} {wake_up_process+16} A
[vdr] Problem with xineliboutput
I have a problem with xineliboutput (latest cvs). When the client vdr-sxfe crash, X freeze and I must to harware reset. It can be reproduce by presing control-c when playing vdr-sxfe. I dont now if it is a prolem of vdr-sxfe or of the X drivers(Xorg 7.1 + nvidia) Thanks Jose Alberto ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Problem with xineliboutput
El Martes, 5 de Septiembre de 2006 13:46, Jose Alberto Reguero escribió: > I have a problem with xineliboutput (latest cvs). > When the client vdr-sxfe crash, X freeze and I must to harware reset. > It can be reproduce by presing control-c when playing vdr-sxfe. > I dont now if it is a prolem of vdr-sxfe or of the X drivers(Xorg 7.1 + > nvidia) It is xineliboutput. I go back to version 1.0.0pre1 and no problems. Jose Alberto ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Problem with xineliboutput
El Martes, 5 de Septiembre de 2006 18:15, Jose Alberto Reguero escribió: > El Martes, 5 de Septiembre de 2006 13:46, Jose Alberto Reguero escribió: > > I have a problem with xineliboutput (latest cvs). > > When the client vdr-sxfe crash, X freeze and I must to harware reset. > > It can be reproduce by presing control-c when playing vdr-sxfe. > > I dont now if it is a prolem of vdr-sxfe or of the X drivers(Xorg 7.1 + > > nvidia) > > It is xineliboutput. I go back to version 1.0.0pre1 and no problems. > The change that cause the problem is this one made 24 Aug 2006: void cXinelibServer::Read_Control(int cli) { - int n = read(fd_control[cli], - &m_CtrlBuf[ cli ][ m_CtrlBufPos[cli] ], - 90 - m_CtrlBufPos[cli]); - if(n<=0) { -LOGMSG("Client connection %d closed", cli); -CloseConnection(cli); -return; - } + while(read(fd_control[cli], &m_CtrlBuf[ cli ][ m_CtrlBufPos[cli] ], 1) == 1) { - char *pt; - m_CtrlBufPos[cli] += n; - m_CtrlBuf[cli][m_CtrlBufPos[cli]] = 0; - while(NULL != (pt=strstr(m_CtrlBuf[cli], "\r\n"))) { -*pt = 0; -Handle_Control(cli, m_CtrlBuf[cli]); -strcpy(m_CtrlBuf[cli], pt + 2); - } - m_CtrlBufPos[cli] = strlen(m_CtrlBuf[cli]); +++m_CtrlBufPos[cli]; - if(m_CtrlBufPos[cli]>=80) { -LOGMSG("Received too long control message from client %d", cli); -CloseConnection(cli); +if( m_CtrlBufPos[cli] > 79) { + LOGMSG("Received too long control message from client %d (%d bytes)", +cli, m_CtrlBufPos[cli]); + LOGMSG("%81s",m_CtrlBuf[cli]); + CloseConnection(cli); + return; +} + +if( m_CtrlBufPos[cli] > 2 && + m_CtrlBuf[ cli ][ m_CtrlBufPos[cli] - 2 ] == '\r' && + m_CtrlBuf[ cli ][ m_CtrlBufPos[cli] - 1 ] == '\n') { + + m_CtrlBufPos[cli] -= 2; + m_CtrlBuf[ cli ][ m_CtrlBufPos[cli] ] = 0; + + Handle_Control(cli, m_CtrlBuf[cli]); + + m_CtrlBufPos[cli] = 0; +} } } Reverting this patch, last cvs code work well for me. Jose Alberto ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.4.4 / xineliboutput 1.0.0_pre6 causes complete system freeze
El Domingo, 3 de Diciembre de 2006 11:31, Matthias Dahl escribió: > Hi everyone. > > I am currently trying to get away from MythTV (which never lived up to my > expectations). So far, vdr has been nothing but great. Except for the > following which just drives me crazy: > > Whenever I am using vdr-sfxe or xine-ui to watch tv, switching channels > sometimes freezes my system hard... except for the Magic SysRq reboot key, > its totally dead. (no remote logging, no emergency umounting, ...) > > So far I have been able to come up with a testcase that reproduces the > problem or at least some problem... > > 1) start vdr as demon (with xineliboutput) > 2) fire up vdr-sxfe (use a local pipe or rtsp or whatever) or xine xvdr:// > 3) send a SIGKILL to the frontend process (so either vdr-sxfe or xine) > 4) system freezes hard immediately without any logs or whatsoever > > I believe this is the same problem I have been expierencing at random. I > guess what happened previously was that vdr-sxfe or xine died unexpectedly > and which naturally led to the same result. > > What's interesting though, starting vdr directly (not as demon) with the > xineliboutput, I am unable to reproduce the problem. I can kill the > process, zap around as much as I want... no problem. > > Here some more informations: > > - OS: Gentoo ~amd64 (64 bit -hicks-) > - KNC ONE DVB-C Plus with Cineview and Alphacrypt Light CAM > - fresh (a few days old) dvb tree from mercurial repository (linuxtv.org) > - 2.6.19rc6git10 (almost 100% identical to 2.6.19-final) > - xinelib 1.1.3_pre20061129 > - vdr 1.4.4 with bigpatch, setup plugin, jumpplay, dvbplayer, cmdsubmenu > dolby-record-switch, submenu and femon > - xineliboutput 1.0.0_pre6 > - gcc 4.1.1 (gentoo rev 2, meaning there are a lot of fixes included and > thus not vanilla) > - glibc 2.5 > > Naturally I also tried older kernels and older dvb checkouts but that > didn't change anything. I do believe now that the problem is somewhere > either in vdr or in xineliboutput because my system is normally rock solid > and I cannot force a total freeze with just some dvb apps even if I want > to. (believe me, I tried) > > Being an "computer scientist" myself, I know there is nothing more > important than debugging the whole thing. Unfortunately that's hard to do > when the whole system just takes a break. ;-) I tried getting getting some > infos out of this with gdb but so far nothing turned up. There is also no > kernel oops or anything like it reported. > > The strangest thing about this: vdr runs as vdr:vdr and vdr-sxfe is also > just a regular user. Actually user processes shouldn't be able to freeze > the system hard. ;-( > > By the way, I also opened up a post over at vdr-portal.de which turned up > that I am not the only one seeing this problem. > > (german) http://www.vdr-portal.de/board/thread.php?postid=548719 > > I also email Petri (author of xineliboutput) a few days ago with roughly > the same msg here but I haven't yet received an answer. > > Thanks for any help or advice in advance! If there is anything I can do to > help to get to the bottom of this, I'd be more than glad. > > Have a nice weekend, > matthew. > I have the same problem. See: http://linuxtv.org/pipermail/vdr/2006-September/010628.html The attached patch work for me. Jose Alberto Index: frontend_svr.c === RCS file: /cvsroot/xineliboutput/vdr-xineliboutput/frontend_svr.c,v retrieving revision 1.27 diff -r1.27 frontend_svr.c 1245c1245,1246 < while(read(fd_control[cli], &m_CtrlBuf[ cli ][ m_CtrlBufPos[cli] ], 1) == 1) { --- > int n; > while((n = read(fd_control[cli], &m_CtrlBuf[ cli ][ m_CtrlBufPos[cli] ], 1)) == 1) { 1268a1270,1273 > if (n == 0) { > LOGMSG("Client connection %d closed", cli); > CloseConnection(cli); > } ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] pvrinput radio - need analogradio??
I use this modified code in device.c (pvrinput): bool cPvrDevice::Tune(int freq) { struct v4l2_frequency vf; int freqaux = freq; memset(&vf, 0, sizeof(vf)); vf.tuner = 0; if (freq > 18) vf.type = V4L2_TUNER_ANALOG_TV; else { vf.type = V4L2_TUNER_RADIO; freqaux = freq * 1000; } vf.frequency = (int) ((double) freqaux * 16.0 / 1000.0 + 0.5); if (IOCTL(video_fd, VIDIOC_S_FREQUENCY, &vf) != 0) { log(0, "Error tuning to %d: %s", freq, strerror(errno)); return false; } frequency = freq; return true; } But I have some problems with radio(pvrinput), and xineliboutput. Jose Alberto El Martes, 13 de Febrero de 2007 11:01, Simon Baxter escribió: > It looks like this plugin does something wrong with the analog radio on > the OEM PVR-150 card. > > With channels.conf set to: > Radio 91ZM:90900:I999C0:C:0:0:300:305:A1:12003:1:1007:0 > > v4l2-ctl --all looks like this: > > Audio input : 0 (Tuner 1) > Frequency: 1454 (90.875000 MHz) > Video standard = 0x00ff > PAL-B/B1/G/H/I/D/D1/K > Tuner: > Capabilities : 62.5 kHz multi-standard > Frequency range : 44.0 MHz - 958.0 MHz > Signal strength : 0% > Current audio mode : mono > Available subchannels: > > > Where ivtv-radio -f90 looks like this: > > Audio input : 0 (Tuner 1) > Frequency: 1454400 (90.90 MHz) > Video standard = 0x00ff > PAL-B/B1/G/H/I/D/D1/K > Tuner: > Capabilities : 62.5 Hz stereo > Frequency range : 65.0 MHz - 108.0 MHz > Signal strength : 50% > Current audio mode : stereo > Available subchannels: stereo > > > it appears pvrinput isn't setting the right audio mode/sub channels etc?? > > > Any ideas? > > PS. It looks like analogradio plugin is no longer supported? Is also > doesn't support ALSA. > > ? > > > I've asked this before, last year, but never had a response. > > > > How do I configure radio channels in VDR. > > > > My channels.conf has: > > > > Classic Hits:9:I999C0:C:0:0:300:305:A1:12003:1:1006:0 > > > > But I think I'm picking up the wrong device, as I hear no audio. I have > > a single PVR-150 with ivtv and the following devices: > > > > /dev/video0 > > /dev/video24 > > /dev/video32 > > > > When I do a 'ivtv-radio -f9' I see: > > aplay -f dat < /dev/video24#which works > > > > Sowhat should my Parameters be?? > > > > C0 - Input 0 > > C12 - Input 1 > > C23 - Input 2 > > C34 - Input 3 > > C45 - Input 4 > > C56 - Input 5 > > C67 - Input 6 > > C78 - Input 7 > > C89 - Input 8 > > C999 - Input 9 > > > > > > Thanks - in advance! > > > > > > > > ___ > > 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] pvrinput radio - need analogradio??
El Martes, 13 de Febrero de 2007 12:16, Jose Alberto Reguero escribió: > I use this modified code in device.c (pvrinput): > > bool cPvrDevice::Tune(int freq) > { > struct v4l2_frequency vf; > int freqaux = freq; > > memset(&vf, 0, sizeof(vf)); > vf.tuner = 0; > if (freq > 18) > vf.type = V4L2_TUNER_ANALOG_TV; > else > { > vf.type = V4L2_TUNER_RADIO; > freqaux = freq * 1000; > } > vf.frequency = (int) ((double) freqaux * 16.0 / 1000.0 + 0.5); > > if (IOCTL(video_fd, VIDIOC_S_FREQUENCY, &vf) != 0) > { > log(0, "Error tuning to %d: %s", freq, strerror(errno)); > return false; > } > frequency = freq; > return true; > } > > But I have some problems with radio(pvrinput), and xineliboutput. The problem I have is that after a while sound is distorted an finally sound stop. There is not any messages in the log. I don't know if is pvrinput or xineliboutput fault. Jose Alberto > > Jose Alberto > > El Martes, 13 de Febrero de 2007 11:01, Simon Baxter escribió: > > It looks like this plugin does something wrong with the analog radio on > > the OEM PVR-150 card. > > > > With channels.conf set to: > > Radio 91ZM:90900:I999C0:C:0:0:300:305:A1:12003:1:1007:0 > > > > v4l2-ctl --all looks like this: > > > > Audio input : 0 (Tuner 1) > > Frequency: 1454 (90.875000 MHz) > > Video standard = 0x00ff > > PAL-B/B1/G/H/I/D/D1/K > > Tuner: > > Capabilities : 62.5 kHz multi-standard > > Frequency range : 44.0 MHz - 958.0 MHz > > Signal strength : 0% > > Current audio mode : mono > > Available subchannels: > > > > > > Where ivtv-radio -f90 looks like this: > > > > Audio input : 0 (Tuner 1) > > Frequency: 1454400 (90.90 MHz) > > Video standard = 0x00ff > > PAL-B/B1/G/H/I/D/D1/K > > Tuner: > > Capabilities : 62.5 Hz stereo > > Frequency range : 65.0 MHz - 108.0 MHz > > Signal strength : 50% > > Current audio mode : stereo > > Available subchannels: stereo > > > > > > it appears pvrinput isn't setting the right audio mode/sub channels etc?? > > > > > > Any ideas? > > > > PS. It looks like analogradio plugin is no longer supported? Is also > > doesn't support ALSA. > > > > ? > > > > > I've asked this before, last year, but never had a response. > > > > > > How do I configure radio channels in VDR. > > > > > > My channels.conf has: > > > > > > Classic Hits:9:I999C0:C:0:0:300:305:A1:12003:1:1006:0 > > > > > > But I think I'm picking up the wrong device, as I hear no audio. I > > > have a single PVR-150 with ivtv and the following devices: > > > > > > /dev/video0 > > > /dev/video24 > > > /dev/video32 > > > > > > When I do a 'ivtv-radio -f9' I see: > > > aplay -f dat < /dev/video24#which works > > > > > > Sowhat should my Parameters be?? > > > > > > C0 - Input 0 > > > C12 - Input 1 > > > C23 - Input 2 > > > C34 - Input 3 > > > C45 - Input 4 > > > C56 - Input 5 > > > C67 - Input 6 > > > C78 - Input 7 > > > C89 - Input 8 > > > C999 - Input 9 > > > > > > > > > Thanks - in advance! > > > > > > > > > > > > ___ > > > 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] pvrinput radio - need analogradio??
El Martes, 13 de Febrero de 2007, Simon Baxter escribió: > OK. > > In order to get the correct info from a v4l2-ctl --all: > Format: > Type: VBI Capture > Sampling Rate : 2700 Hz > Offset : 248 samples (9.18519e-06 secs after leading edge) > Samples per Line: 1440 > Sample Format : GREY > Start 1st Field : 6 > Count 1st Field : 18 > Start 2nd Field : 318 > Count 2nd Field : 18 > Video input : 0 (Tuner 1) > Audio input : 0 (Tuner 1) > Frequency: 144 (90.00 MHz) > Video standard = 0x00ff > PAL-B/B1/G/H/I/D/D1/K > Tuner: > Capabilities : @@ -881,12 +881,19 @@ > bool cPvrDevice::Tune(int freq) > { > struct v4l2_frequency vf; > +int freqaux = freq; > > memset(&vf, 0, sizeof(vf)); > vf.tuner = 0; > - vf.type = V4L2_TUNER_ANALOG_TV; > +if (freq < 8800) I think this don't work. I use freq >18 because 18 is the max range for FM. You can also use: if (radio_fd >= 0) radio else tv Jose Alberto > +vf.type = V4L2_TUNER_ANALOG_TV; > +else > +{ > + log(3, "Changing to RADIO"); > +vf.type = V4L2_TUNER_RADIO; > +freqaux = freq * 1000; > +} > vf.frequency = (int) ((double) freq * 16.0 / 1000.0 + 0.5); > - > if (IOCTL(video_fd, VIDIOC_S_FREQUENCY, &vf) != 0) > { > log(0, "Error tuning to %d: %s", freq, strerror(errno)); > 62.5 Hz stereo > Frequency range : 65.0 MHz - 108.0 MHz > Signal strength : 50% > Current audio mode : stereo > Available subchannels: stereo > > I patched as follows: > > Thanks Jose - that's a great help! > > > >> El Martes, 13 de Febrero de 2007 12:16, Jose Alberto Reguero escribió: > >>> I use this modified code in device.c (pvrinput): > >>> > >>> bool cPvrDevice::Tune(int freq) > >>> { > >>> struct v4l2_frequency vf; > >>> int freqaux = freq; > >>> > >>> memset(&vf, 0, sizeof(vf)); > >>> vf.tuner = 0; > >>> if (freq > 18) > >>> vf.type = V4L2_TUNER_ANALOG_TV; > >>> else > >>> { > >>> vf.type = V4L2_TUNER_RADIO; > >>> freqaux = freq * 1000; > >>> } > >>> vf.frequency = (int) ((double) freqaux * 16.0 / 1000.0 + 0.5); > >>> > >>> if (IOCTL(video_fd, VIDIOC_S_FREQUENCY, &vf) != 0) > >>> { > >>> log(0, "Error tuning to %d: %s", freq, > >>> strerror(errno)); > >>> return false; > >>> } > >>> frequency = freq; > >>> return true; > >>> } > >>> > >>> But I have some problems with radio(pvrinput), and xineliboutput. > >> > >> The problem I have is that after a while sound is distorted an finally > >> sound > >> stop. There is not any messages in the log. I don't know if is pvrinput > >> or > >> xineliboutput fault. > >> > >> Jose Alberto > >> > >>> Jose Alberto > >>> > >>> El Martes, 13 de Febrero de 2007 11:01, Simon Baxter escribió: > >>> > It looks like this plugin does something wrong with the analog radio > >>> > >>> on > >>> > >>> > the OEM PVR-150 card. > >>> > > >>> > With channels.conf set to: > >>> > Radio 91ZM:90900:I999C0:C:0:0:300:305:A1:12003:1:1007:0 > >>> > > >>> > v4l2-ctl --all looks like this: > >>> > > >>> > Audio input : 0 (Tuner 1) > >>> > Frequency: 1454 (90.875000 MHz) > >>> > Video standard = 0x00ff > >>> > PAL-B/B1/G/H/I/D/D1/K > >>> > Tuner: > >>> > Capabilities : 62.5 kHz multi-standard > >>> > Frequency range : 44.0 MHz - 958.0 MHz > >>> > Signal strength : 0% > >>> > Current audio mode : mono > >>> > Available subchannels: > >>> > > >>> > > >>> > Where ivtv-radio -f90 looks like this: > &
Re: [vdr] pvrinput radio - need analogradio??
El Miércoles, 14 de Febrero de 2007, Simon Baxter escribió: > >> In order to get the correct info from a v4l2-ctl --all: > >> Format: > >> Type: VBI Capture > >> Sampling Rate : 2700 Hz > >> Offset : 248 samples (9.18519e-06 secs after leading > >> edge) > >> Samples per Line: 1440 > >> Sample Format : GREY > >> Start 1st Field : 6 > >> Count 1st Field : 18 > >> Start 2nd Field : 318 > >> Count 2nd Field : 18 > >> Video input : 0 (Tuner 1) > >> Audio input : 0 (Tuner 1) > >> Frequency: 144 (90.00 MHz) > >> Video standard = 0x00ff > >> PAL-B/B1/G/H/I/D/D1/K > >> Tuner: > >> Capabilities : @@ -881,12 +881,19 @@ > >> bool cPvrDevice::Tune(int freq) > >> { > >> struct v4l2_frequency vf; > >> +int freqaux = freq; > >> > >> memset(&vf, 0, sizeof(vf)); > >> vf.tuner = 0; > >> - vf.type = V4L2_TUNER_ANALOG_TV; > >> +if (freq < 8800) > > > > I think this don't work. I use freq >18 because 18 is the max > > range > > for FM. > > You can also use: > > > > if (radio_fd >= 0) > > radio > > else > > tv > > > > Jose Alberto > > I've found some weird stuff. When vf.tuner is set to V4L2_TUNER_RADIO the > freq seems to be a factor smaller. In experimenting, I find if I set the > channels between 8800 & 10800 (for 88-108Mhz - looks like this is > set as Hz ???) monitoring what's been set on the PVR-150 with 'v4l2-ctl > --all', I see these values set the correct freq and I get a 50% or better > signal strength. What's more, the 'v4l2-ctl --all' matches what's set > with a 'ivtv-radio -f90.0'. > > Problem is, no audio is output!! It looks like the v4l2 tuner is set to > radio, the tuner is set to 90.9Mhz, but it's trying to play the stream > from /dev/video0 rather than /dev/video24. Does this make sense?? radio: /dev/video24->raw audio /dev/video0->compressed mp2 audio Jose Albeerto > > > ___ > 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