News:

Latest versions:
Server plugin: 0.5.1
MVP dongle: 0.5.2
Raspberry Pi client: 0.5.2
Windows client: 0.5.2-1

Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Kleo

#1
Hi all,

I'm trying to replace two old MVPs by RPis and I noticed that since updating to the newer vdr,
dongle and vomp-server versions the clients don't switch to the first TV channel on bootup anymore.

Should that feature still be working or did I miss its removal/change of usage?

Best, Alex
#2
Sorry for bringing up this old thread.

I'm trying to replace two old MVPs by vomp-clients on raspberries and I'm having issues
configuring the VDR prio correctly.

Since switching to the new vdr version and vomp-server (vdr 2.0.3 + vompserver 0.4.0)
- to get the RPi working - I have Live-TV issues in the vomp-client (on the RPi AND the old MVPs)
when a recording starts on the server.

The server has two separate Technisat DVB-S cards and should have an available tuner when a
single recording starts.

Nevertheless I get a 'channel unavailable' message on thr RPi/MediaMVPs when a recording starts.
I have to go to a different channel and back to my original channel to get Live-TV back.

That didn't happen on the former Ubuntu 9.04 server with older vdr and vomp-server versions.

For completeness I have to say that there are the streamdev-server and xineliboutput-plugins
installed on the server. They are not used when that happens, but loaded in vdr. I'm not sure
whether their updated versions include changes to the handling of devices. That's why I'm not
exactly sure if it's actually a vomp-server/client issue.

But I'm hoping one of you can shed some light on the Prio setting and what to expect from a dual
tuner server.

Best regards, Alex