Posts by JV16Bar

I would like to go to the full linux + development tools + compile everything route, so I guess RPI4 is the way to go. I already have some RPI4's but i didn't use them as vdr client as back then there were no good output device such as rpihddevice for RPI3 (and I liked the fact that RPI3 doesn't need active cooling).
I will look at the RPI4 topic to find out which is the best *hddevice to use.

Thank you all for your support, i managed to achieve my primary goal to play internet radios as native VDR channels.
For anybody with an older Raspberry: for me the RADIO protocol using VLC is a perfect solution, on RPI3 it is working very well.

However now I'm thinking to try some video streams as well My RPI3 OS is very outdated, it is a Raspbian Buster and i don't want to upgrade it for various reasons. So I can't install a modern yt-dlp on it.
But i think i would try another alternative, I see on this forum that many of you are using media players as native VDR clients. Can somebody point me to a specific model which is available nowadays and can be used with vdr? I would use it only as streamdev-client, so i don't need to attach any physical DVB card to it.

I changed vdr to run with a normal user, so the vlc problem is solved now.
Looking at the code i think the radio protocol doesn't use vlc2iptc or any other script.
Perhaps the codec parameters are hard coded in streambasehandler.cpp ?
Anyway using the radio protocol now playback and zapping are fine.

OK, looks like my main problem was that i ran vdr as root, and vlc doesn't like that
Now radios plays well, zapping is quick (~ 1-2 sec).
What is the advantage of using EXT protocol instead of Radio?
This kind of entries seems to work fine:

Hank FM:220:S=1|P=0|F=RADIO|U=https%3A//dbc.streamguys1.com/wwhk-fm.aac|A=1|H=V:I:0:0:257=@4:0:0:3:1:2:3

Thank you for your detailed answer, it helped me a lot to clarify the usage of the plugin.

Sorry for coming to this thread, maybe it's not the right place.
I wanted to ask if anybody using vdr + rpihddevice + iptv plugin with an older RPI.
I have multiple RPI3s running VDR, and on one of them i compiled iptv plugin. Trying to listen some radios (to replace the mplayer plugin), and it works, but after i change the channel it takes about 10-15 seconds to play.
I didn't manage to play any TV stream, but i don't know either if the RPI3 is capable of such a transcoding. For me only the radios would be relevant, as i would like to replace the mplayer plugin, to have the webradios as native VDR channels.

Quote from apolon

you mine this in vdr setup.conf ?

streamdev-server.HTTPPriority = 0

Yes, or OSD:
Menu - Settings - Plugin - Streamdev-server

Try to raise the HTTP Server Priority from 0 to a higher value.

I use as VDR server a Raspberry PI CM4 with official Raspberry IO board. The DVB-S card is connected to the PCI-E port with a riser cable. This setup works fine for several moths.
This is the riser cable: https://www.berrybase.de/pci-express-x1…rungskabel-20cm

It could be something wrong with my Raspi 2 OS (altough i did not received any errors during update). I managed to compile vdr-2.3.4 on my raspi 3 without any errors.

pi@rpi3:/opt/vdr-2.3.4$ uname -a
Linux rpi3 4.4.12-v7+ #892 SMP Thu Jun 2 15:41:19 BST 2016 armv7l GNU/Linux
pi@rpi3:/opt/vdr-2.3.4$ ll ./vdr
-rwxr-xr-x 1 pi pi 5.5M ápr   28 11:07 ./vdr

Well, 2.3.3 I did not try, I used 2.3.1 on this raspi.
But I have another raspi (3 B) which runs 2.3.3 fine.

I will try 2.3.4 on raspi 3 tomorrow.

Thank you for the hint, I upgraded my kernel, and now I have:

pi@rpi2B / $ uname -a
Linux rpi2B 4.9.24-v7+ #993 SMP Wed Apr 26 18:01:23 BST 2017 armv7l GNU/Linux

But when I compiling vdr-2.3.4, I'm getting the same error.

What am I doing wrong?

dvbdevice.c: In member function ‘bool cDvbTuner::GetSignalStats(int&, double*, double*, double*, double*, double*) const’:
dvbdevice.c:585:19: error: ‘DTV_STAT_SIGNAL_STRENGTH’ was not declared in this scope
dvbdevice.c:586:19: error: ‘DTV_STAT_CNR’ was not declared in this scope

This is a Raspi 2 with raspbian without dvb device.

I know this is an old thread, but my problem is somehow related to what is discussed here.
I have: rpi3 with a 24" HDMI monitor. I'm using vdr-2.2.0 and rpihddevice latest. Recently I purchased a 7" touch tft display for the raspberry pi, and I set it up as the primary display for the raspberry. I'm starting rpihddevice with -d5, so I have the VDR live picture + OSD on the 24" monitor, and I'm using the 7" display for graphtft-ng plugin. So far so good. The problem comes when I switch off the HDMI output. Until now I used a preprogrammed "power off" button on my remote to call a script which takes care about switching off the display + RC etc. I turned off the HDMI display with:

/opt/vc/bin/tvservice -o

Without the 7" display this method worked perfectly, but now, when I switch off the HDMI, vdr-rpihddevice switches the live tv output to the primary (7" LCD) display, which is not what I would like to do. Is there a way to "force" rpihddevice to not use the primary display at all?
I tried both rpihddevice --display 5 and --display 6 with the same results. In config.txt i set up the lcd display as being the primary one.

Check, if you have latest firmware installed.

I wonder, what skins are you using with rpihddevice in general. I have 4 raspberries, and I haven't seen any advantage "stressing" them with complex skins, like skindesigner. Skindesigner needs more resourses than the whole vdr + streamdev-client + satip + rpihddevice.
3 on my raspberries (rpi 1 A, rpi 1B and rpi 3B) I'm using "simple" skins like skinsoppalusikka and/or skinenigmang, and only on my rpi 2B I'm using a very outdated skindesigner with the most simple skin (metrixhd), as I made some customizations to it, like displaying a temperature graph which is helpful for me. In other aspects I see no advantage using complex skins.

Hungarian AAC radio channels on 9° East 11957 Mhz V are working now, thanks.

Thanks for this info, I will try it. I invested too much time in this project (my main Raspberry Pi vdr client) to give up now

Yes, it outputs DD 5.1 too (but I don't need it, as my hifi system is 2.0). But it has a serious drawback: it doesn't bypass CEC commands, so I can not put my tv to standby anymore via HDMI CEC

I don't want to hijack your thread, just want to notice, maybe someone is interested: i bought this HDMI audio extractor from ebay. It does the following: it extracts audio signal from HDMI to an analog/SPDIF toslink (optical) output. It outputs audio on HDMI output and audio output simultaneously. It comes without a power adapter, but it has a micro usb power connector, so it can easily be powered from the Raspberry Pi itself. I don't think it's a high end audio device but it outputs much better audio than the RPI2's analog output.