vdr December 2008

vdr@linuxtv.org

99 participants
88 discussions

HVR-4000, vdr-1.7.2 and v4l-dvb'hg ?
by Gregoire Favre 03 Jan '09

03 Jan '09

Hello, it took me some time to find out that my HVR-4000 don't work for DVB-S(2) with vdr-1.7.2. v4l-dvb gives this when I start the modules : saa7146: register extension 'budget_ci dvb'. budget_ci dvb 0000:04:00.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21 saa7146: found saa7146 @ mem ffffc20000f96c00 (revision 1, irq 21) (0x13c2,0x100f). saa7146 (0): dma buffer size 192512 DVB: registering new adapter (TT-Budget/WinTV-NOVA-CI PCI) adapter has MAC addr = 00:d0:5c:23:a3:9b input: Budget-CI dvb ir receiver saa7146 (0) as /devices/pci0000:00/0000:00:1e.0/0000:04:00.0/input/input13 DVB: registering adapter 0 frontend 0 (ST STV0299 DVB-S)... Linux video capture interface: v2.00 cx88/0: cx2388x v4l2 driver version 0.0.6 loaded cx8800 0000:04:02.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23 cx88[0]: subsystem: 0070:6902, board: Hauppauge WinTV-HVR4000 DVB-S/S2/T/Hybrid [card=68,autodetected], frontend(s): 2 cx88[0]: TV tuner type 63, Radio tuner type -1 cx88[0]: i2c init: enabling analog demod on HVR1300/3000/4000 tuner tuner' 8-0043: chip found @ 0x86 (cx88[0]) tda9887 8-0043: creating new instance tda9887 8-0043: tda988[5/6/7] found tuner' 8-0061: chip found @ 0xc2 (cx88[0]) tuner' 8-0063: chip found @ 0xc6 (cx88[0]) tveeprom 8-0050: Hauppauge model 69009, rev B2A0, serial# 1241151 tveeprom 8-0050: MAC address is 00-0D-FE-12-F0-3F tveeprom 8-0050: tuner model is Philips FMD1216ME (idx 100, type 63) tveeprom 8-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K) ATSC/DVB Digital (eeprom 0xf4) tveeprom 8-0050: audio processor is CX882 (idx 33) tveeprom 8-0050: decoder processor is CX882 (idx 25) tveeprom 8-0050: has radio, has IR receiver, has no IR transmitter cx88[0]: hauppauge eeprom: model=69009 tuner-simple 8-0061: creating new instance tuner-simple 8-0061: type set to 63 (Philips FMD1216ME MK3 Hybrid Tuner) input: cx88 IR (Hauppauge WinTV-HVR400 as /devices/pci0000:00/0000:00:1e.0/0000:04:02.0/input/input14 cx88[0]/0: found at 0000:04:02.0, rev: 5, irq: 23, latency: 64, mmio: 0xdb000000 wm8775' 8-001b: chip found @ 0x36 (cx88[0]) cx88[0]/0: registered device video0 [v4l2] cx88[0]/0: registered device vbi0 cx88[0]/0: registered device radio0 cx8800 0000:04:05.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20 cx88[1]: subsystem: 14f1:0084, board: Geniatech DVB-S [card=52,autodetected], frontend(s): 1 cx88[1]: TV tuner type 4, Radio tuner type -1 cx88[1]/0: found at 0000:04:05.0, rev: 3, irq: 20, latency: 64, mmio: 0xd9000000 cx88[1]/0: registered device video1 [v4l2] cx88[1]/0: registered device vbi1 cx2388x alsa driver version 0.0.6 loaded cx88_audio 0000:04:02.1: PCI INT A -> GSI 23 (level, low) -> IRQ 23 cx88[0]/1: CX88x/0: ALSA support for cx2388x boards cx88/2: cx2388x MPEG-TS Driver Manager version 0.0.6 loaded cx88[0]/2: cx2388x 8802 Driver Manager cx88-mpeg driver manager 0000:04:02.2: PCI INT A -> GSI 23 (level, low) -> IRQ 23 cx88[0]/2: found at 0000:04:02.2, rev: 5, irq: 23, latency: 64, mmio: 0xdd000000 cx8802_probe() allocating 2 frontend(s) cx88[1]/2: cx2388x 8802 Driver Manager cx88-mpeg driver manager 0000:04:05.2: PCI INT A -> GSI 20 (level, low) -> IRQ 20 cx88[1]/2: found at 0000:04:05.2, rev: 3, irq: 20, latency: 64, mmio: 0xda000000 cx8802_probe() allocating 1 frontend(s) cx88/2: cx2388x dvb driver version 0.0.6 loaded cx88/2: registering cx8802 driver, type: dvb access: shared cx88[0]/2: subsystem: 0070:6902, board: Hauppauge WinTV-HVR4000 DVB-S/S2/T/Hybrid [card=68] cx88[0]/2: cx2388x based DVB/ATSC card tuner-simple 8-0061: attaching existing instance tuner-simple 8-0061: type set to 63 (Philips FMD1216ME MK3 Hybrid Tuner) DVB: registering new adapter (cx88[0]) DVB: registering adapter 1 frontend 0 (Conexant CX24116/CX24118)... DVB: registering adapter 1 frontend 1 (Conexant CX22702 DVB-T)... cx88[1]/2: subsystem: 14f1:0084, board: Geniatech DVB-S [card=52] cx88[1]/2: cx2388x based DVB/ATSC card CX24123: detected CX24123 DVB: registering new adapter (cx88[1]) DVB: registering adapter 2 frontend 0 (Conexant CX24123/CX24109)... The problem is certainly in : DVB: registering adapter 1 frontend 0 (Conexant CX24116/CX24118)... DVB: registering adapter 1 frontend 1 (Conexant CX22702 DVB-T)... The card tune well for example with kaffeine to BBC HD. Any idea on how to use it with VDR (dvb-t is of second interest to me) ? -- Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org http://picasaweb.google.com/Gregoire.Favre

8 21

[Announce] vdr-fritzbox 1.1.4
by Joachim Wilke 31 Dec '08

31 Dec '08

For testing purposes, a new version of the plugins' development branch is available. Download as usual from http://www.joachim-wilke.de/vdr-fritz.htm --- 8< --- 2008-12-31: Version 1.1.4 - adapted to changes in libfritz++: * Added type "ALL" to CallList to retrieve complete list of calls at once. * Moved callType from CallList to CallEntry. * Implemented in-library msn filtering and reverse-lookups. * Renamed various methods in FonbookManager from *Fonbuch* to *Fonbook*. * Made CallList a singleton. * Replaced string tokenizer in Listener. * Refactored MSN-filter functionality. * Added "-fPIC" to Makefiles. * A call to Config::SetupFonbookIDs now deletes a previously instantiated FonbookManager to allow multiple calls to SetupFonbookIDs in case of configuration changes. * Introduced new method CallList::DeleteCallList() to explicitly delete the singleton instance. * Made Listener a singleton. A call to Listener::CreateListener() is used to activate this feature. * Introduced new method CallList::CreateCallList() to explicitly pre-fetch the call list before calling CallList::getCallList(). * Moved Config::SetupFonbookIDs to FonbookManager::CreateFonbookManager(). * Renamed Tools::GetPhoneSettings() to Tools::GetLocationSettings(). * Added resolving of SIP[0-9] to real provider names. - configuration changes of MSN filter, selected fonbooks, hostname and password are now considered immediately without a restart - plugin classes no longer hold own references to fonbook, listener and callList. They now use the static getter methods. - fixed a possible crash when using the plugin with showNumber = pauseOnCall = muteOnCall = false. (Patch provided by Andreas [26]) - using new library feature: resolving SIP provider names, instead of signalling SIP0, ... --- 8< --- Best regards, Joachim.

1 0

How to assign a multiplex (frequency) to a specific tuner in multi-tuner setup?
by Janusz Krzysztofik 30 Dec '08

30 Dec '08

Hello, Recently I have migrated my home network digital tv solution from getstream + mythtv to vdr with streamdev plugin. Since then I have problems with my dual tuner DVB-T card (Hauppauge WinTV Nova T-500). There are two multiplexes available in my area. Using getstream, both tuners were tuned permanently to one multiplex each, and both were streaming them continously to the network without any problems. With vdr, the first tuner is tuned to the multiplex providing the current channel, and the second one is switched periodicaly among both multiplexes (trying to read EIT, I guess). After several hours, the second tuner still seems to keep switching, but stops providing any stream. Using suspendoutput plugin it works better (longer), but after several more hours I can still see similiar problem with the first tuner this time. To get acceptable resultes, I have reverted one of the tuners to getstream, tuning it permanently to the multiplex that does not provide EIT yet. Now, my vdr has access the channels from this multiplex via iptv plugin, using the remainig tuner directly for permanent reception of the other multiplex only. This solution works for me without problems for several days now, so I think my hardware is still ok. I can realize that the problem could be related to dvb driver, not vdr itself, but maybe there is a better workaround available in vdr. Except for simplicity, I would prefere using EIT form both multiplexes when the secound one becomes available. So, is it possible to configure vdr to use the first tuner for one multiplex only and the second for the other one? Cheers, Janusz

1 0

vdr-1.7.2 and xine-vdpau ?
by Gregoire Favre 30 Dec '08

30 Dec '08

Hello, is someone able to use this combinaison ? In the affirmative, by which way ? xine-plugin gives lots of FIXME and I got about one frame every 3-4 seconds (0.25 fps) for regular mpeg2 channels... Thanks. -- Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org http://picasaweb.google.com/Gregoire.Favre

3 3

new project - xine-vdpau
by Goga777 29 Dec '08

29 Dec '08

Great news :) right now developers have announced new project - xine-vdpau Source repository: svn://jusst.de/xine-vdpau Mailing-list: http://lists.kafic.ba/mailman/listinfo/xine-vdpau (xine-vdpau(a)kafic.ba) irc channel #xine-vdpau on freenode.net Goga

4 4

1080p ready VDR
by Sascha Vogt 29 Dec '08

29 Dec '08

Hi all, I'm new to this list and VDR in general, so if I'm missing some points or habits of this list, please feel free to correct me. I'm on the way of building a VDR. At the moment I'm searching for hardware recommendations, but this seems to be a hard task. What I want my VDR to do: - Playback of 1080p videos (e.g. the big buck bunny) - Watching TV over DVB-S (normal and HD, e.g. AnixeHD) - Recording of TV (should not be too "difficult" *g*) - Playing music and films from my fileserver What I'm not sure about is: - Full-featured or budget DVB card - CPU requirements for HD playback There was a quite silent PC recommendation, in a recent c't (german computer magazine). They used an AMD Atholon X2 4850e on a GigaByte MA78G-DS3H mainboard and got the whole system to be not louder than 0.4 Sone. The graphic is an onboard ATI Radeon HD3200 with HDMI out. What do you think? Is this sufficient for HD playback? And what about the DVB card? Is a budget card ok? Greetings -Sascha-

6 11

Ich bin z.Z. nicht per E-Mail erreichbar.
by carsten.funke＠sparkasse-bremen.de 29 Dec '08

29 Dec '08

Ich werde ab 29.12.2008 nicht im Büro sein. Ich kehre zurück am 05.01.2009. Ich befinde mich im genannten Zeitraum nicht im Haus und werde Ihre Nachrichten nach meiner Rückkehr beantworten. Bei technischen Fragen wenden Sie sich bitte an die Hotline der Portavis unter der Telefonnummer 1800. In Fällen von ernsthafen Gefährdungen der Sicherheit wenden Sie sich bitte an Herrn Greve, 2916. Mit freundlichen Grüßen Carsten Funke Bremens starke Seite. Die Sparkasse Bremen AG Sitz Bremen / Amtsgericht Bremen HRB 21770 Vorsitzender des Aufsichtsrates: Gerhard Harder Vorstand: Jürgen Oltmann (Vorsitzender), Dr. Tim Nesemann (Stv. Vorsitzender), Klaus Schöniger, Dr. Heiko Staroßom Am Brill 1-3, 28195 Bremen / Postfach 10 78 80, 28078 Bremen / Telefon 0421/179-0 mailto:mail@sparkasse-bremen.de / http://www.sparkasse-bremen.de Bankleitzahl 29050101 / Swift: SBRE DE 22 / Ust-ID-Nr. DE 232135295 Wie Sie wissen, können über das Internet versandte E-Mails leicht unter fremden Namen erstellt oder manipuliert werden. Aus diesem Grunde bitten wir um Verständnis dafür, dass wir zu Ihrem und unserem Schutz die rechtliche Verbindlichkeit der vorstehenden Erklärungen und Äußerungen ausschließen. As you are aware, e-mails sent via Internet can easily be prepared or manipulated by third persons. For this reason we trust you will understand that, for your own and our protection, we rule out the legal validity of the foregoing statements and comments.

1 0

Bits from projects.vdr-developer.org - issue #1
by Tobi 29 Dec '08

29 Dec '08

This is issue #1 of a more or less regular newsletter about what is happening on projects.vdr-developer.org. How it all began ----------------- Half a month ago, on December 12'th, projects.vdr-developer.org has been launched [1]. The idea to start just another project platform, was born out of a discussion about the VDR Plug-in Survey results [2][3]. These results revealed, that some plug-ins, that haven't seen an update for years and therefore can be considered "orphaned", are still very popular. Such plug-ins were mostly hold together by patches circulating in forums, mailing lists or distribution packages. This way they were already virtually "community maintained". All that was needed, was a central point to coordinate this community effort somehow. Git seemed to perfectly fit the way these plug-ins were maintained in some kind of distributed patch driven development. And as a fan of Redmine the decision was quickly made, to host a Redmine project management with Git repositories. Luckily the Open Source Factory, a German software company using VDR in their product "Xeatre.TV" [4], was currently seeking ways to support the community and was happy to provide a root server. And to kind of "keep things together under one roof", Siegmar Dieser kindly provided the subdomain "projects.vdr-developer.org". The project is open for everyone, not just for orphaned plug-ins. At the moment, 10 projects and about 30 users are registered. What we have so far ------------------- It started with three orphaned plug ins, which now have a new home: - OSDTeletext [5] - TTxtSubs [6] - Text2Skin [7] They were officially "released" from their original authors, which were happy to see the development continue as a community project. New versions of OSDTeletext and TTxtSubs have already been released. Thanks to Marcel Wiesweg, Ragnar Sundblad and Sascha Volkenandt for inventing these plug-ins in the first place! The latest plug-in is TvTv which was taken over from Mario Gross and is now mainly maintained by monty35. But also some actively maintained projects have found projects.vdr-develper.org to be useful: - Live [8] - Muggle [9] - The VDR Git Tree [10] And some new projects have chosen projects.vdr-develper.org as well. Helmut Auer started vdr-channels.conf [11] - a project to manage various VDR channel configurations and distribute them in a nicely organized tarball. If you want to help, just post your channel settings with provider or region info to the projects issue tracker. Jochen Dolze started a project for the InfosatEPG plug-in [12] (without any activity yet). You want to start your own project? That's easy! ------------------------------------------------ Registering a new project is very easy. All you need to do is: 1. Choose a user name and register an account on projects.vdr-developer.org. In order to register a new project, I kindly ask you to also provide your real name. 2. Create a new issue on the "Project Management" project. Briefly describe, what project you want to be created and how it should be named. If you are adopting an orphaned VDR plug-in, please ask the original author first, if he is ok with this. In order to get write access to the GIT repository, please also attach your public SSH key, 3. As soon as your project is created (which is done manually, so give us at least 48 hour before complaining), you will have full access to it. Your help is needed: Translators! --------------------------------- Some plug-ins have incomplete or missing translations. If you want to see a plug-in in your language, clone the git tree or download the po file and create an issue in the issue tracker with the po file or a patch attached. If you want to keep track of changes to your translations, you can subscribe to an RSS feed of a single po file: Use the GitWeb interface [13] to browse the project tree, select the translation file and on the lower left you have two buttons that link to an RSS or ATOM feed to this translation. E.g. to subscribe to the RSS feed of the Spanish translation of the OSDTeletext plug-in, use this URL: http://projects.vdr-developer.org/git/?p=vdr-plugin-osdteletext.git;a=rss;f… Your help is needed: Users! --------------------------- Please report any problems, feature requests or suggestions to the projects issue tracker. There's no need to register as a user, you can very well create new issues anonymously (but then will not get email updates on your reported issues). Make sure, you verified any problems with the latest available version and try to give as much details as possible. The better your instructions to recreate a problem are, the more likely it will be fixed! You can attach files to your reports and you can come back any time to add additional comments. Your help is needed: Developers! -------------------------------- Although each project has a "Manager" which has certain responsibilities, it's up to *YOU* to get things fixed / implemented. The easiest way is to use Git to create patches and post them to the projects issue tracker or ask to become a member of the project with push access to the repository. Currently help is needed especially for the following issues: vdr-plugin-osdteletext [16] [17]: This is about OSDTeletext forcing VDR into transfer mode, even if this is not really necessary. Klaus pointed out, that this needs to be fixed in VDR and is related to a bugfix from VDR 1.3.8 for "Live TV freeze when recording starts normal" [14]. Udo Richter provided a small patch, which helps to analyse the problem [15]. A solution is needed, which fixes the problem with "Live TV freeze when recording starts normal" from VDR < 1.3.8 with out making OSDTeletext forcing VDR into transfer mode. vdr-plugin-text2skin: Currently no work has been done on vdr-plugin-text2kin. There's an issue for including the patch from chr13 [18], but there probably needs to be done a lot more to this plugin. If you have any patches / improvements / whatever, please just post them to the projects issue tracker. If you can dedicate some more time to this plug-in, you can become it's manager. A project managers responsibility is mainly to integrate patches, keep an eye on the reported issues, make new releases and "recruite" developers, if needed. vdr-plugin-ttxtsubs [19]; "If there's a two rows of subtitles, the upper row is corrupted with FF card when using antialiasing. Without antialiasing, both rows of text are just fine." Patches are welcome! That's it for today! I hope to see you contributing to projects.vdr-developer.org soon! Tobias [1] http://www.linuxtv.org/pipermail/vdr/2008-December/018767.html [2] http://e-tobi.net/blog/2008/11/18/vdr-plugin-survey-2008-results-part-1 [3] http://e-tobi.net/blog/2008/12/02/vdr-plugin-survey-2008-results-part-2 [4] http://www.xeatre.tv/ [5] http://projects.vdr-developer.org/projects/show/plg-osdteletext [6] http://projects.vdr-developer.org/projects/show/plg-ttxtsubs [7] http://projects.vdr-developer.org/projects/show/plg-text2skin [8] http://projects.vdr-developer.org/projects/show/plg-live [9] http://projects.vdr-developer.org/projects/show/plg-muggle [10] http://projects.vdr-developer.org/projects/show/vdr [11] http://projects.vdr-developer.org/projects/show/vdr-channels [12] http://projects.vdr-developer.org/projects/show/plg-infosatepg [13] http://projects.vdr-developer.org/git/ [14] http://linuxtv.org/mailinglists/vdr/2004/05-2004/msg00115.html [15] http://projects.vdr-developer.org/issues/show/10#note-5 [16] http://projects.vdr-developer.org/issues/show/9 [17] http://projects.vdr-developer.org/issues/show/10 [18] http://projects.vdr-developer.org/issues/show/39 [19] http://projects.vdr-developer.org/issues/show/24

1 0

Help with compiling vdr and selecting appropriate plugins
by Tomáš Skočdopole 28 Dec '08

28 Dec '08

Hello everybody, I have some freetime and I will start using vdr at my server. I am planing streaming channels over network with vdr. I have got two TT S2-3200 cards and phoenix card reader. Now I have sucessfully compiled modules for my cards (tested with getstream). I want to ask there about sort of plugins and patches for vdr which I need for this screnario. Thank you, best regards Tomas

1 0

[ANNOUNCE] H.264 support for VDR-1.7.2
by Reinhard Nissl 28 Dec '08

28 Dec '08

Hi, attached you'll find an updated patch for VDR-1.7.2. The patch includes the formerly released remux fix. Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:rnissl@gmx.de

3 2

← Newer
1
2
3
4
5
6
7
8
9
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr December 2008