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
Yes, and i'm running Jammy with 56 installed. I wonder then why it's trying to use 51.. Is there a setting where you specify which libraries to use?
I got this now straighted out, and got xineliboutput-sxfe installed without any dependency issues. What i still get is the same error message
# vdr-sxfe
vdr-sxfe: error while loading shared libraries: libavutil.so.51: cannot open shared object file: No such file or directoryI have claimed once for an fake item, and required a refund. For AliExpress customer support it was enough to prove with video an photos, and when the seller did not respond within a certain time frame, they refunded the money, and probably withdrawed it from the seller...
Hi Emma53
If I got I right, you bought the SSD from AliExpress. Did you claim for a refund?
Hi,
Thanks guys for cleaning up, and making it an own topic. Should have done it from the beginning
Poking more around, i found out that i get a dependency error when installing xineliboutput-sxfe. I managed to install 2.2.0+git20211212-2.1 with Aptitude which i now realize is a completely wrong version which is from the Ubuntu universe repo
I am probably missing a repo with the libxine2, because i get this error when running apt install xineliboutput-sxfe
The following packages have unmet dependencies.
libxine2-xvdr : Depends: libxine2 (>= 1.2.11-3yavdr0~jammy) but 1.2.11-2 is to be installed
E: Unable to correct problems, you have held broken packages.
I guess i'm missing a repo?
René
Hi Guys,
Sorry for interrupting in English
I'm running Ubuntu Jammy and i upgraded vdr and a bunch of plugins with the seahawk1986 vdr-2.6.5 repos. I changed many years ago to Softhddevice, but got never working outputting the sound into two different sound devices at the same time (HDMI for TV + aux for my headphones). I get it working with either one, but not both audioroutes at the same time. Many years ago I had this combination working with xineliboutput over Pulseaudio, and now I would want to get this feature back by switching back to xineliboutput. vdr-sxfe seems to be missing in this repo, because i get the error "vdr-sxfe: error while loading shared libraries: libavutil.so.51: cannot open shared object file: No such file or directory". I wonder if it would be possible to get xineliboutput-sxfe also added to this repo?
Viele Grüße,
René
Yep, i found that, and got it compiled Would it be possible to add this patch to the master repo?
Thanks for the patch! I guess i missed it
Hi,
Thanks! Great to see that it's not a forgotten skin. I got though the following error when compiling it:
enigma.c: In constructor 'cSkinEnigmaDisplayMenu::cSkinEnigmaDisplayMenu()':
enigma.c:1383:49: error: 'min' was not declared in this scope
enigma.c:1383:49: note: suggested alternative:
/usr/include/c++/4.6/bits/stl_algobase.h:233:5: note: 'std::min'
enigma.c: In constructor 'cSkinEnigmaDisplayTracks::cSkinEnigmaDisplayTracks(const char*, int, const char* const*)':
enigma.c:3811:49: error: 'min' was not declared in this scope
enigma.c:3811:49: note: suggested alternative:
/usr/include/c++/4.6/bits/stl_algobase.h:233:5: note: 'std::min'
enigma.c: At global scope:
enigma.c:182:1: warning: 'clrTitleShadow' defined but not used [-Wunused-variable]
enigma.c:204:1: warning: 'clrMessageInfoFg' defined but not used [-Wunused-variable]
enigma.c:205:1: warning: 'clrMessageInfoBg' defined but not used [-Wunused-variable]
enigma.c:206:1: warning: 'clrMessageWarningFg' defined but not used [-Wunused-variable]
enigma.c:207:1: warning: 'clrMessageWarningBg' defined but not used [-Wunused-variable]
enigma.c:208:1: warning: 'clrMessageErrorFg' defined but not used [-Wunused-variable]
enigma.c:209:1: warning: 'clrMessageErrorBg' defined but not used [-Wunused-variable]
make: *** [enigma.o] Error 1