vdr

vdr@linuxtv.org

1 participants
6750 discussions

Looking for DVB-C channels conf for Kabel DE München
by Harald Milz 01 Jan '22

01 Jan '22

Hi all, happy new year everyone! I would like to add my DVB-C channels to my existing setup but can't seem to find a working channels.conf for Kabel Deutschland München anywhere. There are only older versions around but I know that they changed their channel assignments considerably in the last few years. Any help is appreciated! -- This night methinks is but the daylight sick. -- William Shakespeare, "The Merchant of Venice"

1 1

PetShopBoys on BBC
by Reinhard Nißl 26 Dec '21

26 Dec '21

Hi, is anyone willing to record a couple of radio- and TV-broadcasts on BBC the next days? See http://view.e.wmg.com/?qs=5783d1cfd364e6f6d8d27a784af750a84bce302b7d9a37ba4… for schedules. Thanks in advance. Bye. -- Reinhard Nißl

3 3

Re: [vdr] VDR packages in Debian and e-tobi.net (Tobi)
by Richard F 23 Dec '21

23 Dec '21

Heroic work - thanks, and Merry Xmas Richard On 22/12/2021 12:00, vdr-request(a)linuxtv.org wrote: > > Today's Topics: > > 1. Re: VDR packages in Debian and e-tobi.net (Tobi) >

1 0

vdr not working in Raspbian 10
by Narcis Garcia 04 Jan '21

04 Jan '21

Hello, I've installed vdr from Raspbian packages, to use it with Kodi. I've updated channels.conf by using w_scan2 for a DVB-T2 dongle. TV channels are found. But I try to watch some channel and I get no data. Tried with two clients Kodi software with its VDR plugin (screen interface) and with vdradmin-am (web interface). What can I check to find the problem? Notes: - TV dongle works; if I stop vdr service and use GUI applicacion Kaffeine, I can watch all TV channels. - I see VDR service attending TCP ports 34890 (VNSI), 6419 and 2010 Thank you. -- Narcis Garcia __________ I'm using this dedicated address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should fix this against automated addresses collectors.

5 21

[ANNOUNCE] VDR version 2.4.6 released
by Klaus Schmidinger 22 Dec '20

22 Dec '20

VDR version 2.4.6 is now available at ftp://ftp.tvdr.de/vdr/vdr-2.4.6.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-2.4.4-2.4.6.diff MD5 checksums: aa91614159ae2db45655d35918e2c24e vdr-2.4.6.tar.bz2 b75cc737a5ea5fc059c2264b7ed21fa9 vdr-2.4.4-2.4.6.diff You can also get the latest stable version at the official VDR GIT archive with git clone --branch stable/2.4 git://git.tvdr.de/vdr.git This version fixes a few bugs that came up after the release of version 2.4.4. The changes since version 2.4.4: - Updated the Italian OSD texts (thanks to Diego Pierotto). - Fixed handling newline characters in ci.c's CopyString() (reported by Winfried Köhler). - Fixed checking the return value of the Open() call in cFileName::SetOffset() (reported by Winfried Köhler). - Fixed a possible invalid lock sequence in cMenuTimers::OnOff(). - Fixed several typos (reported by Jens Schleusener). - Implemented anti-aliasing for cPixmap::DrawSlope() and cPixmap::DrawEllipse() (thanks to Christoph Haubrich). The version numbers (both VDRVERSNUM and APIVERSNUM) have been bumped to 2.4.5 to indicate this change. - Fixed alignment of semi-circles in case of odd sizes. - Increased the size of the TS buffer to 16MB, to have more reserve when recording several HD programmes. - Added checking the symbol rate to cDvbTuner::IsTunedTo(), which apparently got lost in version 1.7.13 (thanks to Helmut Binder). - Now checking for an empty command in cDvbTuner::GetSignalStats() to avoid a possible error message (thanks to Helmut Binder). - Now initializing the status variable in cDvbTuner::GetFrontendStatus() and cDvbTuner::GetSignalStats() to avoid problems with drivers that don't do this (thanks to Helmut Binder). - Fixed multiple recording entries in case a recording is started during the initial reading of the video directory (reported by Claus Muus). - Fixed an unnecessary double call to Display() in cMenuRecording::RefreshRecording() (reported by Christoph Haubrich). - Fixed a crash in case an error occurs when setting a remote timer. - Fixed allocating memory for cImage (reported by Christoph Haubrich). - Fixed parsing the '-l' command line option (reported by Harald Milz). - Fixed possible compilation errors with libjpeg (thanks to Bernd Kuhls). - Fixed "read incomplete section" errors (thanks to Helmut Binder). - Fixed generating the HashId in cEIT::cEIT() (thanks to Helmut Binder). - Added initialization of cDvbFrontend::frontendInfo (thanks to Winfried Köhler). - Fixed a bug in handling shared PMTs, where after the first pass not all SIDs of a PMT pid were checked any more (thanks to Helmut Binder). - Fixed PMT handling in case locking the Channels list times out (reported by Helmut Binder). - Avoiding a lengthy lock on the Channels list when starting a recording (thanks to Helmut Binder). - Fixed error handling when loading a plugin (reported by Markus Ehrnsperger). - Improved handling missing VDRPluginDestroyer() (thanks to Winfried Köhler). - Fixed initializing tmpbuf in ExtendedEventDescriptors::getText() (thanks to Helmut Binder). - Fixed a compiler warning (thanks to Winfried Köhler). - Fixed convertCharacterTable() in case iconv_open() fails (thanks to Helmut Binder). - Official release. Have fun! Klaus

1 0

Re: [vdr] vdr not working in Raspbian 10
by Narcis Garcia 29 Nov '20

29 Nov '20

El 29/11/20 a les 14:16, André Weidemann ha escrit: > > > On 29.11.2020 11:33, Narcis Garcia wrote: >> de nov. 29 11:29:53 raspberrypi vdr[11391]: [11391] ERROR >> (dvbdevice.c,1650): /dev/dvb/adapter0/frontend1: El dispositiu o recurs >> es troba ocupat > > Looks like the dvb-adapter is already in use. > You can try to figure which process is holding on to it by running: > > sudo lsof |grep /dev/dvb/adap|awk '{print $2}'|uniq|xargs ps -fp > > André $ sudo lsof |grep /dev/dvb/adap|awk '{print $2}'|uniq|xargs ps -fp lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. UID PID PPID C STIME TTY TIME CMD vdr 11391 1 0 11:29 ? 00:01:10 /usr/bin/vdr *Narcís*

1 0

VDR do not show HD channels.
by prelude 22 Nov '20

22 Nov '20

Hello and thx for this great VDR software. Could someone help me at the start as I cannot get dvb-t2 channels visible in VDR? If I add HD channels manually in channels.conf then VDR mark those as OBSOLETE. Yesterday I even clean my channels.conf totally and just left one channel on it and put in setup "add new transponders". In the morning all DVB-T channels were in channels.conf file but not any DVB-T2. tvheadend works fine also in HD channels but i just like so much more VDR user experience that i don't want to change it.

3 6

Subtitle
by Alexander 20 Nov '20

20 Nov '20

Hi, my wife is hard of hearing and that is why we have permanently discontinued the subtitle in the vdr. But if she don't watch, I'll turn off the subtitle with the hotkey. When I switch channels, the subtitle is on again. Is there a possibility that the subtitles will not appear until the next restart of vdr? -- Greets Walter

3 2

option parsing for --log still broken
by Harald Milz 18 Nov '20

18 Nov '20

Hi Klaus and all, it appears that option parsing for the --log option is still broken, as described in this thread: https://www.vdr-portal.de/forum/index.php?thread/108924-gel%C3%B6st-logging… Short version: vdr stops parsing the remainder of the command line at the point of --log=2.6. Long version: The problem is in the getopt code in vdr.c: case 'l': { char *p = strchr(optarg, '.'); if (p) *p = 0; if (isnumber(optarg)) { int l = atoi(optarg); if (0 <= l && l <= 3) { SysLogLevel = l; if (!p) break; if (isnumber(p + 1)) { int l = atoi(p + 1); if (0 <= l && l <= 7) { int targets[] = { LOG_LOCAL0, LOG_LOCAL1, LOG_LOCAL2, LOG_LOCAL3, LOG_LOCAL4, LOG_LOCAL5, LOG_LOCAL6, LOG_LOCAL7 }; SysLogTarget = targets[l]; break; } } } } if (p) *p = '.'; fprintf(stderr, "vdr: invalid log level: %s\n", optarg); return 2; } Initially, the point is replaced by a NULL byte in order to be able to atoi() both numbers (if (p) *p = 0;). This replacing takes place _in place_. In theory, the replace should be reverted at the end of the code snippet (if (p) *p = '.';) BUT if one of the branches involving a break is executed, the revert is never invoked, and the original command line remains broken so that the remaining command line options are not getting evaluated. Consequently, what used to be vdr -w 60 -g -u vdr -l 2.6 -P plugin1 -P plugin2 becomes vdr -w 60 -g -u vdr -l 2 6 -P plugin1 -P plugin2 and the modules will not get loaded. The thread mentioned above speaks of upstart & co but I have the same issue in a docker container with explicit program start in a shell script whithout any upstart or anything. I now helped myself putting the -l at the end of the command line but I still cannot send the vdr log to a different facility because the dangling 6 is not getting evaluated. My suggestion would be to not evaluate the optarg string directly but create a copy of optarg first, and work with the copy. This way, the original command line is unchanged. Sample patch attached, untested but it should do the trick. -- You are as I am with You.

2 2

Re: [vdr] Many "Tuning timeout" messages and signal disruptions
by Richard F 17 Nov '20

17 Nov '20

I'd either use bare metal or maybe a container (LXC, not sure sure about docker) as that's as near as bare metal with few encumbrances. Why ? I've always used bare metal, and it seems VDR is working quite close to the hardware, adding layers adds complexity. But the other thing is that that sever looks quite ancient now and a replacement (somewhat newer, if not new) shouldn't cost much. I had a similar issue with a CCTV card unrecognised by the kernel and gave up fighting the FOXCONN mobo/BIOS, after some discussion and help on the kernel developers forum who tried but ultimately couldn't help in the end, and bought an-off-the shelf HP machine for only around 100 euro / used. There were other benefits, like super-efficient PSU giving power eduction which in the 4 or 5 years since may have paid for it ! The ugly bit is ideally you need a kind soul to let you test your card in whatever machine first, to be sure it works. On 13/11/2020 12:00 pm, vdr-request(a)linuxtv.org wrote: > potential solutions: > - run VDR in a docker container instead of in a VM and pass /dev/dvb to the > container > - replace the KVM host, thus get rid of the RMRR issue and continue to use PCI > passthrough > - run the VDR on bare metal > - others? > > What would you do if you were in my place, and why?

1 0

← Newer
1
...
4
5
6
7
8
9
10
...
675
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr