The yaVDR-Team proudly presents the - as we believe - first OSD independent picture in picture (PiP) solution for the VDR. If you own more than one DVB card, you are now able to watch two arbitrary channels at the same time!

A short notice: As some smaller bugs crept in at the last minute we decided to provide you with an updated ISO image called yavdr-0.3.0a.iso.

What has been fixed ?

• The Nvidia display driver is now the right/expected version (260.12)
• The driver package v4l-dvb-dkms now comes with two re-enabled patches related to mantis cards
• OSD Menu translations should work now for other languages than German and English (also added an updated French translation)
• The Italian version of the web interface should work now (no blue HTML screen any more)

Please note: if you are not affected by these errors there is no reason for redownload/re-install the ISO. These corrections will of course also be made available as package updates.

You can find the yavdr-0.3.0a.iso on the download page.

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.

"How to do that?" - you might ask.

Right from the start "suspend to RAM" was one of yaVDRs most beloved features giving our users the possibility to start their VDR within a few seconds. While this worked great for a lot of hardware, there were still some configurations where it didn't. That's why we decided to improve the situation by choosing a different method for yaVDR 0.3: "Userspace Software Suspend".

Ever wanted to start your VDR with your remote control? With yaVDR-0.3 you can, if the receiver of your remote control has the ability to wake the computer from sleep.

In order to get HDMI sound with these cards a fairly new alsa driver package is required. We used to ship an alsa-dkms package. However, since a while ubuntu ships allready compiled drivers of this version for each kernel update. 

So how you get your sound working now for these cards in yavdr-0.3 ?

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.

Why do we use upstart for our jobs ?

With Karmic, Ubuntu started the transition to upstart. With Lucid most of the important jobs have been migrated. Since yavdr 0.2.0 we base our distro on Ubuntu Lucid Lynx. To benefit from this new technology we decided early to go this road. The downside is obviuosly that its not that well known and documented as System-V init scripts.

So what jobs do exist in yavdr and whats ther task ?

Lets first start how we get the display ...

Lifeguard performs various tests specified by the user when vdr wants to shutdown the machine. The shutdown is postponed if any of the tests indicates that there are other processes that should not be interrupted.