vdr

vdr@linuxtv.org

6731 discussions

Welcome to Linux DVB VDR voice chat
by Goga777 06 Jan '09

06 Jan '09

Dears for discussion about any Linux DVB VDR questions you can join to voice Linux DVB VDR chat. You have to install the Mumble client aptitude install mumble or http://mumble.sourceforge.net/Installing_Mumble server address is vdr-settings.com port 64738 currently there are Russian, German, English chat-rooms. we have already spoken with gimli about some interesting questions :) Goga

1 0

Re: [vdr] Which extension for TS files?
by reinhard.buchner＠rw-buchner.de 06 Jan '09

06 Jan '09

Hi guys, Klaus wrote: > I've already dropped them. > Besides, these files are just auxiliary internal files for VDR's > very own purposes. There should normally be no need to edit them at all. I'm writing from work (webmail), so sorry if the email format gets fudged up. I never really liked the "name all files .vdr" terminology. However, totally dropping them is an EQUALLY bad idea, since, unlike Linux, Windows programs depend on the extension for association. I would like to propose using the following: Video / Audio container files: xyz.ts Index files: index.vdr Info files: info.txt Cutter marks: marks.dat Resume files: resume.vdr or resume.dat Klaus says there is no need to edit them (not quite true ;o)), but I would like at least to be able to read them easily. Here are my reasons for asking this: xyz.ts: Sometimes it is nice to able to edit or even just watching them externally. With an extension that is common to all video editors or players, it makes it much easier. index.vdr: Index contains no valuable info for external programs and it doesn't need editing, so we can leave this or even remove the extension all together. Info.txt: The info file esp. is a good thing to have since you can simply copy the info on a Windows PC (for title or contents) when burn them to a CD or DVD. It saves time, just being able to copy and paste via keyboard. If I have to tell the program to "open with" and associate a programm EVERY time I burn a video file to DVD it becomes much too time consuming. Marks.dat: To me it has happend a couple of times (esp if vdr runs out of disk space) that you are not able to jump forward or backward in a video file or even move the placed marks. Being able to edit the marks file or even deleting the preset times makes it easy to correct this problem. I can either place the marks where I need them (if known) or delete all of them if the video file is totally unresponsive. Resume files: resume.vdr or resume.dat: I don't use this file, so to me it makes no difference what is done with the extension. However, for others, esp. multi-user VDR setups it might be handy to able to edit these (making the .vdr a better decision to be able to differiantiate it from the marks.dat file) >> any extension at all. If they are in a .rec-directory it should be >> pretty clear what a file named "index" contains. Not quite sure who wrote this, but this argument isn't vaild, since external editors or programs have no knowledge of VDR's data structure or hierarchy. Naming (or just deleting ;o)) all the extensions the same doesn't change the situation. kind regards, Reinhard

1 0

Which extension for TS files?
by Klaus Schmidinger 06 Jan '09

06 Jan '09

Up to now VDR has used names like 001.vdr for its recording files. While moving to Transport Stream as the recording format, I need to use a different file name extension, and so was wondering which one to use. My first idea was *.ts, for "Transport Stream", but when I point, for instance, Konqueror to such a file, it thinks it is a "Qt Translation Source". So I was wondering if I should use *.mpg instead. This one is identified by Konqueror as an MPEG file and will make it launch a proper player. What do you think about this? Is *.mpg also appropriate for h.264 encoded files? Klaus

14 19

Re: [vdr] Which extension for TS files?
by Martin Dauskardt 04 Jan '09

04 Jan '09

> From: Klaus Schmidinger <Klaus.Schmidinger(a)cadsoft.de> > Up to now VDR has used names like 001.vdr for its recording files. > While moving to Transport Stream as the recording format, I need to > use a different file name extension, and so was wondering which one > to use. My first idea was *.ts, for "Transport Stream", but when I > point, for instance, Konqueror to such a file, it thinks it is a > "Qt Translation Source". So I was wondering if I should use *.mpg > instead. This one is identified by Konqueror as an MPEG file and > will make it launch a proper player. > > What do you think about this? I am strongly against this. *.ts may conflict with KDE, but it is a usual ending for transport stream. Several mpeg-tools can handle this. I think the dreambox is also using *.ts for its recordings. *.mpg would give much more problems with applications. A TS is not an mpeg-file. Applications which can play mpg but not TS may even crash. Greets, Martin

3 2

[ANNOUNCE] vdr-dxr3 0.2.9
by Ville Skyttä 03 Jan '09

03 Jan '09

vdr-dxr3 0.2.9 is available at https://sourceforge.net/projects/dxr3plugin 2009-01-02: Version 0.2.9 - Update Italian translation (Diego Pierotto) - Error handling improvements (Ville Skyttä) - Add SVDRP commands for device release/reopen, audio output settings, brightness/contrast/saturation (Krzysztof Parma, Ville Skyttä) - Switch to VDR 1.6's i18n system (Ville Skyttä) - Drop support for VDR < 1.6.0 (Ville Skyttä)

2 3

Frequent use of femon leads to "Too many open files", frontend0 file handles aren't closed
by Brendon Higgins 03 Jan '09

03 Jan '09

Hi, I've encountered a problem with the femon plugin opening /dev/dvb/adapter0/frontend0 and not closing it. While tracking down a different issue I wrote a small script that would periodically (every 30 seconds, say) use svdrp and the femon plugin to grab some information about the current status of my DVB signal. After some hours of this running I discovered VDR would have some weird problems, and I've since narrowed it down to the fact that for whatever reason each loop of my script causes a new opening of /dev/dvb/adapter0/frontend0, which is never closed (even though I do send the femon quit command). I can keep track of how many open file handles there are using "lsof | grep frontend0 | wc", which goes from one open instance at startup to several hundred after hours of running. Ultimately, this causes VDR to stop working since the kernel won't allow it to open any more files beyond a limit. syslog says, as an example vdr: [14876] ERROR (svdrp.c,126): Too many open files last message repeated 175 times Does anyone else see this behaviour, or is it just my setup? VDR 1.6.0, femon 1.6.5, Debian Testing (mostly), Linux 2.6.28. Peace, Brendon

2 1

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

1.7.2 xine plugin FIXMEs
by Scott 01 Jan '09

01 Jan '09

3 2

[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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr