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]
Hi list,
since some time (1-2 years) I noticed that the DVB-T channels do not
show EPG anymore. I'm not sure what is the root-cause: either it
was the migration of French DVB-T to HD (in 2016) or an update of VDR.
Anyway, this morning I took the time to figure out what is wrong and
here is what I found.
In short, the channel-ID generated from the one received in the EIT
does not correspond to a known channel-ID from the channel list, and
VDR drops the whole section:
In cEIT::cEIT (from eit.…
[View More]c) we see
tChannelID channelID(Source, getOriginalNetworkId(), getTransportStreamId(), getServiceId());
cChannel *Channel = Channels->GetByChannelID(channelID, true);
and channel is NULL in my case.
I added some debug prints to GetByChannelID() in the search loop:
printf("sid: %d == %d, %s, %s %d\n",
Channel->Sid(),
sid,
(const char *)ChannelID.ToString(),
(const char *)Channel->GetChannelID().ToString(),
Channel->GetChannelID() == ChannelID);
And here is an example of what I get:
sid: 517 == 517, T-8442-2-517, T-0-506-517 0
The internal channel ID of vdr reads T-0-506-517. 517 is the SID, 506
is the radio-channel frequency in MHz. This is the right internal
channel for this EIT-section.
The EIT-channel-ID is telling me that 8442 is the original network ID
and 2 might be the radio-channel ID.
I tweaked the operator==() of ChannelID to make it work, but not in a
contributable manner.
How should this be fixed correctly?
Is this a regression introduced somewhere?
Can it be solved by configuration?
Thanks for any help.
best regards,
--
Patrick.
[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]
Hello,
I've a vdrserver running with vdr 2.3.8 and satip plugin 2.3.1-GIT-e008ee0.
It works great with a minisatip server 0.7.15.
But it keeps the connection to the minisatip server open all the time,
so the dvb adapter and lnb consumes power every time.
I added the parameter "--detach" to the satip plugin.
And now the connection to the minisatip will be closed when the satip
plugin goes in idle mode as expected.
But now, if a recording should started, nothing happens.
The satip plugin doesn'…
[View More]t open a connection to my minisatipserver and I miss
the recordings.
My config looks like this:
--snip--
[vdr]
--config=/etc/vdr
--epgfile=/tmp/epg.data
--grab=/dev/shm
--log=2.1
--mute
--no-kbd
--user=root
--video=/remote/vdr
-D-
[satip]
--devices=1
--detach
--snip--
and the setup.conf part of satip:
--snip--
satip.CICAM = 0 0
satip.DisabledFilters =
satip.DisabledSources =
satip.EnableCIExtension = 0
satip.EnableEITScan = 1
satip.OperatingMode = 3
satip.TransportMode = 0
--snip--
Can anybody see where I do the mistake ?
--
Regards
Dieter
--
I do not get viruses because I do not use MS software.
If you use Outlook then please do not put my email address in your
address-book so that WHEN you get a virus it won't use my address in the
>From field.
[View Less]
Thanks Klaus & all contributors to VDR!
On Sun, Apr 15, 2018 at 3:44 AM, Karim AFIFI <karim.afifi(a)laposte.net> wrote:
> Hi Klaus,
>
> Many thanks for this new release, and all the job around it !
>
> Regards.
> Karim
>
> -----Message d'origine-----
> De : vdr [mailto:vdr-bounces@linuxtv.org] De la part de Klaus Schmidinger
> Envoyé : dimanche 15 avril 2018 11:37
> À : VDR mailing list
> Objet : [vdr] [ANNOUNCE] VDR version 2.4.0 released
>
…
[View More]> VDR version 2.4.0 is now available at
>
> ftp://ftp.tvdr.de/vdr/vdr-2.4.0.tar.bz2
>
> A 'diff' against the previous version is available at
>
> ftp://ftp.tvdr.de/vdr/Developer/vdr-2.3.9-2.4.0.diff
>
> MD5 checksums:
>
> 12c6a3abeadfa915fcfe736bb047a3ab vdr-2.4.0.tar.bz2
> 6d98c2d619e82f3d4503146602fccde7 vdr-2.3.9-2.4.0.diff
>
> A summary of all the major changes since the last stable version 2.2.0 can be found at
>
> http://www.tvdr.de/changelog.htm
>
> When updating from an earlier version of VDR please make sure you read the INSTALL
> and MANUAL files that come with the VDR source _before_ doing so!
> Please make sure you have backup copies of all your configuration files,
> and verify carefully that your timers will be set to the correct channels
> after switching to this new version.
>
> Thanks to the many people who have contributed in the making, testing and
> debugging of this new version of VDR, and also to all users who just
> enjoy VDR!
>
> Please also visit the VDR homepage at
>
> http://www.tvdr.de
>
> and VDR's facebook page at
>
> https://www.facebook.com/VideoDiskRecorder
>
> Have fun!
>
> Klaus
>
> _______________________________________________
> vdr mailing list
> vdr(a)linuxtv.org
> https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
>
>
> _______________________________________________
> vdr mailing list
> vdr(a)linuxtv.org
> https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[View Less]
VDR version 2.4.0 is now available at
ftp://ftp.tvdr.de/vdr/vdr-2.4.0.tar.bz2
A 'diff' against the previous version is available at
ftp://ftp.tvdr.de/vdr/Developer/vdr-2.3.9-2.4.0.diff
MD5 checksums:
12c6a3abeadfa915fcfe736bb047a3ab vdr-2.4.0.tar.bz2
6d98c2d619e82f3d4503146602fccde7 vdr-2.3.9-2.4.0.diff
A summary of all the major changes since the last stable version 2.2.0 can be found at
http://www.tvdr.de/changelog.htm
When updating from an earlier version of …
[View More]VDR please make sure you read the INSTALL
and MANUAL files that come with the VDR source _before_ doing so!
Please make sure you have backup copies of all your configuration files,
and verify carefully that your timers will be set to the correct channels
after switching to this new version.
Thanks to the many people who have contributed in the making, testing and
debugging of this new version of VDR, and also to all users who just
enjoy VDR!
Please also visit the VDR homepage at
http://www.tvdr.de
and VDR's facebook page at
https://www.facebook.com/VideoDiskRecorder
Have fun!
Klaus
[View Less]
Apologies in advance for a somewhat long-winded post.
I am using an Asrock Celeron based N3150M board with a TT S2 6400 card
and a Digital Devices Cine S2 V7A card and 64bit kernels. The frontends
on the TT card are unused in favour of the DD card - the TT card is just
used for output. vdr is 2.3.9.
For a while now I have been assisting Daniel Scheller with testing his
mainline kernel DD drivers prior to release:
https://github.com/herrnst/dddvb-linux-kernel
Up until a few days ago, …
[View More]all was well, using his dd 0.9.32 drivers in
conjunction with kernel 4.15.0-rc6+.
The system was then updated to his dd 0.9.33 drivers and kernel 4.16+
and intermittent video/audio freezes of two to three seconds appeared.
After some driver bisecting it turns out that this is being caused by
the new kernel, not the dd drivers, (the problem occurs with the old
drivers in the new kernel.).
I am unsure quite where to start, to work out which kernel update has
caused this, but was hoping that the following log errors might point
somewhere useful:
Apr 11 09:46:18 vdr vdr[718]: [874] ERROR: driver buffer overflow on
device 1
Apr 11 09:57:20 vdr vdr[718]: [892] ERROR: 1 TS packet(s) not accepted
in Transfer Mode
Apr 11 10:11:29 vdr vdr[718]: [914] ERROR: 6 TS packet(s) not accepted
in Transfer Mode
Apr 11 10:21:13 vdr vdr[721]: [816] ERROR: driver buffer overflow on
device 1
Apr 11 10:21:21 vdr vdr[721]: [816] ERROR: driver buffer overflow on
device 1
Apr 11 10:39:33 vdr vdr[721]: [873] ERROR: 11 TS packet(s) not accepted
in Transfer Mode
Apr 12 14:37:32 vdr vdr[922]: [957] ERROR: TS packet not accepted in
Transfer Mode
Apr 12 14:37:32 vdr vdr[922]: [957] ERROR: TS packet not accepted in
Transfer Mode
Apr 12 14:37:32 vdr vdr[922]: [957] ERROR: TS packet not accepted in
Transfer Mode
Apr 12 14:37:33 vdr vdr[922]: [957] ERROR: TS packet not accepted in
Transfer Mode
Apr 12 14:37:33 vdr vdr[922]: [957] ERROR: TS packet not accepted in
Transfer Mode
Apr 12 14:37:34 vdr vdr[922]: [957] ERROR: TS packet not accepted in
Transfer Mode
Apr 12 14:37:34 vdr vdr[922]: [957] ERROR: TS packet not accepted in
Transfer Mode
Apr 12 14:37:34 vdr vdr[922]: [957] ERROR: TS packet not accepted in
Transfer Mode
The effect coinciding with these, is a frozen picture and mute audio for
up to several seconds.
Any help much appreciated.
Kind regards,
Richard Scobie
[View Less]
Hello everybody,
I am looking for the DVB API documentation. I know there is
https://www.linuxtv.org/wiki/
and
https://www.linuxtv.org/downloads/v4l-dvb-apis-new/uapi/dvb/dvbapi.html
but the wiki states, the current API is v5. And there don't seem to exist any
information about API v5.
Any hints?
PS: Is this the rigt list for such questions? A list for DVB specific topics
(not vdr specific) don't seem to exist?
--
Josef Wolf
jw(a)raven.inka.de
VDR version 2.3.9 is about to be released as stable 2.4.0 on April 15!
The archive can be found here:
ftp://ftp.tvdr.de/vdr/Developer/vdr-2.3.9.tar.bz2
(this is still the same as in my announcement dated March 18).
I have posted a few last minute fixes at
https://www.vdr-portal.de/forum/index.php?thread/131711-vdr-2-3-9-fixes
(don't worry about the German descriptions, just download the "vdr-2.3.9-*.diff"
files attached to each posting and apply them in order.
The following …
[View More]language files still have the given number of untranslated texts:
po/ar.po: 76
po/ca_ES.po: 76
po/cs_CZ.po: 22
po/da_DK.po: 208
po/el_GR.po: 271
po/es_ES.po: 22
po/et_EE.po: 7
po/fr_FR.po: 22
po/hr_HR.po: 208
po/hu_HU.po: 22
po/lt_LT.po: 22
po/nl_NL.po: 22
po/nn_NO.po: 336
po/pt_PT.po: 104
po/ro_RO.po: 22
po/ru_RU.po: 10
po/sk_SK.po: 22
po/sl_SI.po: 77
po/sr_RS.po: 76
po/sv_SE.po: 22
po/tr_TR.po: 208
po/zh_CN.po: 76
If nobody takes care of these, they will remain untranslated in version 2.4.0.
Klaus
[View Less]
*ISMAR 2018 - CALL FOR TUTORIALS*
The ISMAR 2018 organizing committee invites proposals for tutorials
associated with the ISMAR 2018 conference. The tutorials will be held on
16th and 20th October 2018, in Munich, Germany. The purpose of the
tutorials is to expand the knowledge in the fields of Augmented, Mixed, and
Virtual Reality and foster the next generation of researchers, developers,
and artists.
*Important Dates*
- *Tutorials Proposal Deadline: May 2nd, 2018 (all deadlines: 23:59 …
[View More]AoE)*
- Tutorials Acceptance Notification: May 10th, 2018
- Tutorials Dates: Oct 16th and 20th, 2018
*Format*
Experts, pioneers, and experienced developers and artists are needed to
propose and present tutorials that may target a specific application area,
a specific research area, or a topic of general interest for Augmented,
Mixed, and Virtual Reality.
Topics can range from introductory for AR/MR/VR novices to highly technical
for researchers. Tutorials can be half or full day tutorials, depending on
the scope of topics covered and the presenters available.
*Submission Guidelines*
To submit a proposal for a tutorial, please send an email to
wt_chairs(a)ismar2018.org with the subject "ISMAR 2018 Tutorial Proposal" and
a PDF document containing:
1. Title
2. Topics:
- Provide a brief summary of the proposed tutorial.
3. Preferable date for the tutorial: 16 / 20 / no preference
4. Motivation:
- Explain why ISMAR attendees would be interested in attending this
tutorial.
- Explain how an increased knowledge of this subject will advance
Augmented, Mixed, or Virtual Reality.
5. Presenters:
- Provide a really brief bio of the presenters', list of several
relevant publications on the proposed topic tutorial, and contact
information (e-mail, phone, affiliation)
- If you have taught this or a similar tutorial before, where and
when was it taught.
6. Target Audience:
- Describe what population this tutorial is targeted towards (e.g.,
students, industry professionals, everyone).
- Expected number of attendees.
7. Outline of Tutorial:
- Include the order of topics and approximate time for each topic.
For example:
1. Topic A: 1.5 hours
1.1. Subtopic A1
1.2. ...
2. Topic B: 1.5 hours
2.1. Subtopic B1 ...
After sending your proposal to the aforementioned email address, you should
receive an acknowledgment of receipt. Tutorial proposal will be reviewed by
the committee, and notifications of acceptance will be sent out after the
review period.
*Contact*
ISMAR 2018 Workshop and Tutorial Chairs: wt_chairs(a)ismar2018.org
- Gerd Bruder, University of Central Florida, USA
- Maki Sugimoto, Keio University, Japan
[View Less]