I was planning for a oneliner in cron
I'm not familiar with mapfile, so i try to stick to grep. When i noticed that vdr hanged, i forgot svdrpsend.. If it ever happens again, i'll check what svdrpsend is returning..
I was planning for a oneliner in cron
I'm not familiar with mapfile, so i try to stick to grep. When i noticed that vdr hanged, i forgot svdrpsend.. If it ever happens again, i'll check what svdrpsend is returning..
Hi,
Is someone monitoring if VDR is responding, and restarting vdr if it detects a failure? While being away from home a couple of weeks, vdr froze, and i missed a buch of recordings. The process seemed to be running, so i was thinking of using simply svdrpsend (/usr/bin/svdrpsend ping |grep 'is alive' |wc -l) + a to check that vdr replies, and restart if it it does not return "is alive". Is there any other ways to determine if vdr "works"?
ps. sorry for posting my previous questions to the german forums (i understand and read well german, but writing sucks). I just noticed that we have also an "international" part of the forum
BINGO!
Now i got it working! My asound.conf was wrong. I found the working /etc/asound.conf configuration here: https://bbs.archlinux.org/viewtopic.php?pid=1191152#p1191152
So this is what is needed for vdr to get softhddevice working with two cards. First identify you cards. Here is how it looks for me
# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: SB [HDA ATI SB], device 0: ALC887-VD Analog [ALC887-VD Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 0: SB [HDA ATI SB], device 1: ALC887-VD Digital [ALC887-VD Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0
Display More
My internal card is card 0 and my Geforce hdmi card is card 1. You can use many notation ways: hw:0,0 and hw:1,3 OR hw:CARD=SB,DEV=0 and hw:CARD=NVidia,DEV=3 OR probably any prefix visible by aplay -L
Next my vdr softhddevice config file looks like this.
and /etc/asound.conf looks like this:
pcm.multiout {
type route;
slave.pcm {
type multi;
slaves.a.pcm "hw:CARD=SB,DEV=0"
slaves.b.pcm "hw:CARD=NVidia,DEV=3"
slaves.a.channels 2;
slaves.b.channels 2;
bindings.0.slave a;
bindings.0.channel 0;
bindings.1.slave a;
bindings.1.channel 1;
bindings.2.slave b;
bindings.2.channel 0;
bindings.3.slave b;
bindings.3.channel 1;
}
ttable.0.0 1;
ttable.1.1 1;
ttable.0.2 1;
ttable.1.3 1;
}
pcm.!default {
type plug
slave.pcm "multiout"
}
ctl.!default {
type hw
card SB
}
Display More
You can reload alsa with alsa force-reload or reboot your vdr
That's it
![]()
Ok. Unfortunately no combination seems to work. I would assume that multiout is the device to use, but that brings silence. All other combinations i have tested play the sound either via HDMI or the audio out port ![]()
Ahaa, i was not aware of being able to use multiple times the same switch! I will test when i get back home!
I got now some progress..
# /etc/asound.conf
# reload with: alsa force-reload
# test output: aplay /usr/share/sounds/alsa/Front_Center.wav
pcm.multiout {
type multi
slaves.a.pcm "hw:0,0" # Replace with your first card's ID
slaves.b.pcm "hw:1,3" # Replace with your second card's ID
slaves.a.channels 2 # Example: 2 channels for the first card
slaves.b.channels 2 # Example: 2 channels for the second card
bindings.0.slave a
bindings.0.channel 0
bindings.1.slave a
bindings.1.channel 1
bindings.2.slave b
bindings.2.channel 0
bindings.3.slave b
bindings.3.channel 1
}
pcm.!default {
type plug
slave.pcm "multiout"
}
Display More
This plays the sound in through both devices. What i have not yet figuredout is how to force softhddevice to play to this new device..
to be continued...
Hi,
Thanks for the hint! I will have a look, and hopefully i will manage to get this to work
First I have thogh to figure out how to get the plugin to output any sound to alsa, because what I have tried til now seem to return just silence ![]()
Hi,
I wonder if it is possible to have softhddevice to output the sound to multiple outputs? I have my tv connected to a Gforce GT1030, and my headphones to the motherboards analog audio output. Both audioroutes work, but indifidually..
I had such a setup with xineliboutput, but i lost my setting, and i can't get to work anymore ![]()
Hi,
I tried to search for this, but I probably searched with wrong keywords.
I can't seem to find a way to specify the date format used in Live. The current format (eg: sat, May 10) is probably based on the UI-language I use in VDR (Finnish), but i would prefer to have the date as dd.mm.yyyy. Without a year, the recording list does not show enough data.. Also the current format wastes too much space..
Would it be possible to have some day a setting where the date format could be set?
Hi seahawk1986,
I tested upgrading my Jammy VDR from 2.7.4 to 2.7.5, but it fails due to a couple of plugins are missing. It looks like Launchpad missed a couple of plugins
libxineliboutput-sxfe
vdr-plugin-mplayer
vdr-plugin-skinenigmang
vdr-plugin-streamdev-client
vdr-plugin-streamdev-server
vdr-plugin-xineliboutput
Could you please check if these could be added to the 2.7.5 repo?
Buy an GT1030, the other is out of support also...
Regards Stefan
Uhh.. You're right... Nvidia did not like the *nix world. The Asus GT1030 seems to be just 20€ more, so not a bad price either ![]()
One of the annoying effects caused by Launchpad hickups when uploading packages - I uploaded a version for jammy, the package has already been built and is waiting to be published.
I forgot to thank you! All worked perfectly after the package got released ![]()
Hi,
There are many GT1030 passive cards available.
The GT220 is way old. I use GT630/730, they run in focal, if in newer systems also I don't know.
Regards, Stefan
Wow, i would get a new Asus GT730 https://www.asus.com/motherboards-c…730-4h-sl-2gd5/ for around 80€. My motherboard seems also to have a free slot for the card! I have to do some more research ![]()
https://launchpad.net/~seahawk1986-h…buntu/vdr-2.7.4 has the permashift patch and plugin (and packages for jammy).
I can find the permashift plugin for focal https://launchpad.net/~seahawk1986-h…es_filter=focal and noble https://launchpad.net/~seahawk1986-h…es_filter=noble but can't find it for yammy ![]()
Under Ubuntu 24.04 you can probably only use the noveau driver, nvidia-340 from https://launchpad.net/~kelebek333/+a…es_filter=noble didn't work with the default x-server when I tried it shortly after the release.
I'll have to test a blank installation with noble and check if i get it to work. I'm a "if it works, dont touch it" guy, so it's always a bit scary to upgrade with ancient hardware ![]()
I have to start to prepare myself for getting new hardware. I got this box second hand for 13 years ago, and i have already replaced the motherboard + processor about 6-7 years ago. The GT220 still works, and i't just fantastic because it does not have any fan. I wonder if there even exists passive graphic cards anymore that can handle HD. The original AMD CPU was also with a really low TDP-value, so i managed with a big heatsink + a big slowly rotating fan..
Hi,
I'm using seahawk1986's repo for buntu jammy. Permashift was part of that repo til 2.6.9, but it seem to have been dropped off since then.
I'm running a pretty ancient box with a nvidia GT220 passive card that uses the version 340.108 of the Nvidia driver. Everytime there is a ubuntu version upgrade, i'm nervous upgrading
I actually just checked, and seems that buntu noble has this driver available too
Maybe time to upgrade...
Hi all,
I have been spoiled by great repos for ubuntu for many years now, and i have not needed to compile any plugins. Now i realized that the permashift-plugin available is for vdr 2.6.9, and i wonder if there is a reason why this is not packaged anymore in the ubuntu-repositories for more recent vdr-versions..?
Hurray! There it is
Thanks seahawk1986 !
seahawk1986 Will there be a release for ubuntu Jammy too? ![]()
Crap.. i figured it out.. i had in /etc/ld.so.conf.d/libc.conf with a timestamp from 2011 a the /usr/local/lib containing old xine-stuff.... Uncommenting that line, and vdr-sxfe seems to start again ![]()