Two days ago, Klaus Schmidinger has announced the release of VDR developer version 1.7.21. As always, we are excited about the new version and want to thank Klaus for his steady work on VDR core.
The yaVDR team has already started to use the new developer version to create updated experimental VDR packages in our PPA unstable-vdr. Packages for Ubuntu Lucid (yaVDR 0.3) and Ubuntu Natty (yaVDR 0.4) are now available, but most of them are untested. It is possible that we will update our PPA testing-vdr with the predecessor version: Our VDR 1.7.20 packages that are only a couple of days old now need a new home.
A week ago, Klaus Schmidinger has announced the release of VDR developer version 1.7.20. As always, we are excited about the new version and want to thank Klaus for his steady work on VDR core.
VDR 1.7.20 will replace the VDR 1.7.18 packages in yaVDR in the near future.
Klaus Schmidinger has announced the release of VDR developer version 1.7.19 yesterday. As always, we are excited about the new version and want to thank Klaus for his steady work on VDR core.
Klaus Schmidinger has announced the release of VDR developer version 1.7.18. As always, we are excited about the new version and want to thank Klaus for his steady work on VDR core.
Klaus Schmidinger has announced the release of VDR developer version 1.7.17, introducing a TrueColor OSD to VDR. As always, we are excited about the new version and want to thank Klaus for his steady work on VDR core.
As we are using menuorg as default and changes to menuorg do not require a vdr restart, plus we needed to rework that section anyway, we felt that the use of menuorg to define the Commands menu would be preferable. If you used drive your own commands there, you need to change them to a menuorg custom template.
Inspired by a Howto of VDR Portal user "grmpl" has posted in yavdr subforum at http://www.vdr-portal.de/board/thread.php?threadid=99789 (Wow, what a post for someone who has just registered!), I thought it makes sense to write something on how to use inputlircd and the reason why we support it as an additional option.
Lircd is great on providing support for usual remote controls. In case of the device is an input device inputlircd is by far the better option. It takes the input events and translates them to lircd events. This makes it very easy, since no key needs to be defined explicitly, those if started with the right options (http://www.digipedia.pl/man/doc/view/inputlircd.8/) the keys will be directly available at the lircd socket.
A few days ago, Klaus Schmidinger has announced the release of VDR developer version 1.7.16 which is a welcome opportunity for us to revive our blog and update it with the good news. Please find a detailed list of changes below. We want to thank Klaus for his steady work on VDR core.
Last week, I tried to give you an overview about the different VDR developer versions. As of today, this overview is already outdated and has to be updated: Two hours ago, Klaus Schmidinger has announced the release of VDR developer version 1.7.15. We are excited about the new version and want to thank Klaus for his steady work on VDR core.
If you imagine the yaVDR distro being a human body, its heart would most likely be the VDR (core) software package. The VDR core is mainly maintained and extended by its inventor, Klaus Schmidinger. yaVDR 0.2 will use the currently latest VDR developer version 1.7.14 as its "heart". Although many users of VDR are very happy with 1.7.14, the current stable version of VDR is still version 1.6 which was released back in March 2008. Version 1.6 doesn't contain support for HDTV and DVB-S2 cards, that's why it doesn't make sense for us to use it within yaVDR.
