Hi all,
I recently got a USB adapter "Astrometa DVB-T2" that I would like to use
with VDR. It comprises two frontends:
/dev/dvb/adapter0/frontend0: Realtek RTL2832 (DVB-T)
/dev/dvb/adapter0/frontend1: Panasonic MN88473 (DVB-T2 and DVB-C)
I guess it is similar to this one; just a slightly different plastic
case with some more ventilation holes:
http://blog.palosaari.fi/2014/09/naked-hardware-18-astrometa-amdvb-t2-v2.ht…
The hardware appears to work fine, once I copied the
/lib/firmware/…
[View More]dvb-demod-mn88473-01.fw from somewhere. The firmware
upload has failed at least once on the Raspberry Pi 2 (using Linux
4.9.59), but never on another machine that runs a 4.13.0 kernel.
I did not yet get the infrared remote control to produce anything in
evtest.
With dvbv5-zap (after running dvbv5-scan), I can tune into DVB-T2
channels like this:
dvbv5-zap -a 0 -f 1 -c dvb_channel.conf 'Yle TV1 HD' -r
After this, I can play the video and audio stream on the Raspberry Pi 2:
omxplayer /dev/dvb/adapter0/dvr0
Unless I explicitly specify the options -a 0 -f 1, then dvbv5-zap will
fail to find any DVB-T2 senders, because it apparently defaults to
frontend0, which is DVB-T only.
In VDR 2.3.8, I have only been able to view DVB-T from the first
frontend.
When I did a trick and renamed /dev/dvb/adapter0/frontend1 to frontend0
before starting VDR, VDR no longer complained that the DVB-T2 channels
(which I converted from the dvb_channel.conf to channels.conf with
dvb-format-convert) not being available, but it did not seem to receive
anything from these channels either.
Also, after using dvbv5-scan or dvbv5-zap, I sometimes have to invoke
w_scan to "reset" the hardware so that VDR can receive DVB-T channels.
I would like to receive and record DVB-T and DVB-T2 on this setup. I am
willing to try patches or do some programming myself, but I would
appreciate some hints to get started.
Marko
[View Less]
Hello everyone! I'm from Argentina, and up to last month I've been using
VDR 1.7.262 with an ISDB-T USB adapter. It works really good, but the
last week I've been trying to upgrade to VDR 2.2 and I've found a
problem with ISDB-T cards: they are not supported.
As I'm really interested in using VDR, I was digging inside the code and
found a partial solution for this problem: as ISDBT is the same as DVBT,
I've changed the way delivery system is queried. My changes are applied
in a cloned repo at …
[View More]github:
https://github.com/chrodriguez/vdr/commit/dadbca57c2dc55c1c53b4fa8f68b56728…
That's the only change I've made. Now I can enjoy my fresh upgraded VDR
installation!!
I think a better refactor should be made, but for now it's working
perfectly deployed as a docker container:
https://registry.hub.docker.com/u/chrodriguez/vdr
Thanks for this wonderfull project!
--
Lic. Christian A. Rodriguez
@car_unlp
[View Less]
Hi,
I just experienced weird problem. My hard drive became 100% full.
But I noticed that there are tons of .del directories, some dating
from months ago.. VDR hasn't removed them! What could cause this?
I see entries in log:
low disk space while recording, trying to remove a deleted recording...
Jan 16 08:23:06 puucee vdr: [30504] removing recording xxx.del
And these recordings ARE removed really. But the normal background
cleaning does not happen.
This is somehow related to the fact that …
[View More]I now have Plex Media Server
sitting on the VDR recordings directory. But still I could remove the
.del directories easily from the command line. After manually deleting
them, disk is now only 85% full.. And that's 4TB drive. :) So there
were quite a bit of .del directories.
--
Teemu Suikki
http://www.z-power.fi/
[View Less]
Hi,
I'm struggling a bit with the semantics of OsdItem and OsdCurrentItem in
VDR 2.2.0. My initial assumption was that all items in a menu would
first be announced by OsdItem and later calls to OsdCurrentItem would
then identify the current selection or change its text.
This is true for VDR's main menu and the Settings submenu. When I open
Settings -> OSD, OsdItem is not called anymore. Rather, I get multiple
calls to OsdCurrentItem. The argument of some of the calls are not even
valid …
[View More]menu entries: 'Language:#0110', 'Language:#011English',
'Skin:#0113', 'Skin:#011Text mode', 'Left (%):#0118', ...
I also noticed that in submenus of the Settings menu (e.g. the OSD
menu), the call to OsdCurrentItem is repeated about every second with
the same argument. This does not happen in the main menu or the Settings
submenu.
Note: In the standard implementation of VDR's own status plugin, OsdItem
will not produce any log messages, the call to dsyslog is commented out.
What am I missing?
Thanks,
Malte
[View Less]
hey folks, i'm having some trouble with technotrend s2-3200 dvb-s card [ https://www.linuxtv.org/wiki/index.php/TechnoTrend_TT-budget_S2-3200 ] Card is being recognized:05:04.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)
Subsystem: Technotrend Systemtechnik GmbH S2-3200
Flags: bus master, medium devsel, latency 32, IRQ 20
Memory at fdcfe000 (32-bit, non-prefetchable) [size=512]
Kernel driver in use: budget_ci dvb
Kernel …
[View More]modules: budget_ciMy Kernel: 4.14.11-1-ARCH.It works fine with w_scan or tvheadend I can watch many stations on multiple satelites without any problems, however when trying to tune anything with a symbol rate lower then 5000 (5 Msymbols/s) the driver does not seem to support it, see below messages from w_scan when trying. This makes me miss many stations I'd like to receive.
However, the manufacturer clearly indicates the card supports symbol rates starting as low as 2000 (2 Msymbols/s), [ http://www.tt-downloads.de/Update/engl/techspec_tt-budget_s2-3200_en.pdf ] so the driver needs to be adjusted I guess? How can I make it work or adjust the driver for this?trying 'S2 f = 12138 kHz H SR = 14580 2/3 0,AUTO 8PSK (0:0:0)'
(time: 02:59.734)
trying 'S f = 12515 kHz H SR = 8888 3/4 0,35 QPSK (0:0:0)'
(time: 03:02.894)
trying 'S f = 12525 kHz V SR = 30000 5/6 0,35 QPSK (0:0:0)'
(time: 03:05.424)
trying 'S f = 12544 kHz H SR = 24000 5/6 0,35 QPSK (0:0:0)'
(time: 03:09.274)
trying 'S f = 12562 kHz V SR = 25000 5/6 0,35 QPSK (0:0:0)'
(time: 03:12.394)
trying 'S f = 12571 kHz H SR = 2800 3/4 0,35 QPSK (0:0:0)'
(time: 03:15.933) skipped: (srate 2800000 unsupported by driver)
initial_tune:2813: Setting frontend failed S f = 12571 kHz H SR = 2800 3/4 0,35 QPSK (0:0:0)
trying 'S f = 12577 kHz H SR = 2590 5/6 0,35 QPSK (0:0:0)'
(time: 03:16.447) skipped: (srate 2590000 unsupported by driver)
initial_tune:2813: Setting frontend failed S f = 12577 kHz H SR = 2590 5/6 0,35 QPSK (0:0:0)
trying 'S f = 12588 kHz V SR = 2260 5/6 0,35 QPSK (0:0:0)'
(time: 03:17.660) skipped: (srate 2260000 unsupported by driver)
initial_tune:2813: Setting frontend failed S f = 12588 kHz V SR = 2260 5/6 0,35 QPSK (0:0:0)
trying 'S f = 12592 kHz H SR = 8888 3/4 0,35 QPSK (0:0:0)'
(time: 03:18.893)
trying 'S f = 12592 kHz V SR = 2220 5/6 0,35 QPSK (0:0:0)'
(time: 03:23.487) skipped: (srate 2220000 unsupported by driver)
initial_tune:2813: Setting frontend failed S f = 12592 kHz V SR = 2220 5/6 0,35 QPSK (0:0:0)
trying 'S f = 12596 kHz V SR = 3700 5/6 0,35 QPSK (0:0:0)'
(time: 03:24.003) skipped: (srate 3700000 unsupported by driver)
initial_tune:2813: Setting frontend failed S f = 12596 kHz V SR = 3700 5/6 0,35 QPSK (0:0:0)
trying 'S f = 12601 kHz H SR = 4400 3/4 0,35 QPSK (0:0:0)'
(time: 03:25.993) skipped: (srate 4400000 unsupported by driver)thanks in advance!
[View Less]