Recent Posts

Pages: 1 2 [3] 4 5 ... 10
VOMP for Raspberry Pi / vomp 0.5 - my test results
« Last post by winschrott on January 12, 2019, 11:24:10 »
Hello Chris,
hello MartenR,

I use this wonderful client since many years together with yavdr. After a couple of years I changed my current installation with v0.4.1 to the current v0.5 from git and I´m very happy about the current improvements:

- very fast listing/starting playback of recordings (big subvolume mounted via smb) which took ~15sek in earlier versions
- no problems with HD+-channels in addition to current vdr 2.2.0
- new skin

But I found the following problems with the current git:

- TV is restarting after power-off when connected by CEC and switched to the HDMI of RasPi (Panasonic TV / RasPi 3 with current firmware, 'hdmi_ignore_cec_init=1' in config.txt set so TV does not turn on when raspi starts)
- litte colored strip of background can be seen if transmitted picture is not over the full screen and no overscan is configured (could be solved by completely black background when playing TV or playback of recordings)
- refresh of info-bar is not complete when display of time changes or a new channel is selected after the info-bar is called -> new time or channel number is display over the old one
- when complied with the current package-hints in one of the older threads, CEC will not run until I install the current cec again (simply by calling 'apt-get install cec-utils') which replaces the older, manually defined cec library

I tried to understand the sources, found the color-definitions to change the background to complete black. But I was not able to find the positions for info-bar and the restarts of my TV... If you would tell me where I should begin with my investigations or if you need some debug-info, plz tell me.

Last thing:
Actually I switched the gpu-mem to 256MB because sometimes I only got a black screen (which I can leave with back-key to the normal tv) when calling the EPG by the blue-key. This is gone since 256MB GPU and a fixed definition of HDMI-parameters to 1920x1080/50p (normal 24" display is connected with a HDMI/DVI-cable).

Over all I´m very happy with vompclient on raspi! Thanks for your work and tell me if I can help you with further development!

VOMP General / MVP / [solved] MVP Rev. H4 promlems with vomp 0.5.0
« Last post by kristinam on January 11, 2019, 22:19:36 »

First of all let me say thank you for many years of TV-streaming-fun in our house.
I run a headless easyVDR and have 6 MVPs for the familiy TVs.
I'm very happy that MVP ist still supported.

After updating easyVDR to 3.5 I have this problem:

4 MVPs are working fine, also the raspberry Pi 3B works fine with the image file from loggytronic.
But two MVPs can't connect to the GUI server (that's what the display shows).
Both MVPs are Rev H4 boxes.
I remember that there has to be a "dongle.bin.ver" file that belongs to the "dongle.bin". The files are where they belong, both in the vdr-plugin-vompserver directory.

It would be great if there is a solution an I can keep my two MVPs.



VOMP General / MVP / Re: Some statistics from the Android Remote App
« Last post by muellerph on August 16, 2018, 17:04:45 »
This is my app on Google Play. As app owner/developer you get such info from Google.

But I just saw that Google removed it on 1st August. I need to check why, but I assume as I didn't upload any new version since 2 years and min. Android version is not correct.
VOMP for Raspberry Pi / Re: vompclient 0.5 features
« Last post by Chris on May 09, 2018, 16:17:41 »
I've just tested compiling it against the latest libcec library package in Raspbian Stretch and it compiles OK. (I don't know if it actually works...) I think there has been a confusion in the repository with the package names and dependencies which appears to be resolved now if you start with installing libcec4-dev.
VOMP for Raspberry Pi / Re: vompclient 0.5 features
« Last post by Chris on May 09, 2018, 15:11:24 »
Just out of interest, assuming you use a web VDR manager, which one do you use?
VOMP for Raspberry Pi / Re: vompclient 0.5 features
« Last post by Chris on May 09, 2018, 15:07:04 »
Hi ralph, it's good to hear from someone still using vomp! Now if only the forum notify system had worked it wouldn't have taken me so long to read your message... Oops!

I have just tried to compile vompclient on a fresh Raspbian Stretch and yes, you're right it needs some attention. It is possible but really the downloads and documentation need updating to support it OOTB.

So, in answer to your questions:

1. How you describe is exactly how I use vomp - lircd with uinput events. Since I don't use that Pi's console for anything else, vomp is always hiding the login prompt with the strange characters so it's not really a problem. The strange characters are caused by the kernel's /dev/input system taking the characters that lircd-uevent gives it and handing it to the console as keyboard input. Since the remote buttons are never going to get past the login prompt it's an ignorable problem... Having said that I did once have a quick look into whether it is possible to have the kernel be selective about which input devices it uses for console keyboard input but I didn't find a way. Perhaps there is a way to "consume" the key press... Maybe a bit more digging around would find a way. I would rather not change to support lirc directly because the current system of using /dev/input enables lirc, USB IR receivers and real keyboards simultaneously.

2. As I said above, it is possible but with the following modifications to the instructions on the web site. The packages need to be altered like this:

Code: [Select]
sudo apt-get install libcec-dev libcec4=4.0.1+dfsg1-1+rpi1 libavresample-dev
This installs an old version of libcec. I still need to see if the later version works.

The git clone needs to be at HEAD, not "-b 0.5.0", as there are patches in there to enable compiling on stretch.

Also on my installation I need the following extra line in

Code: [Select]
@@ -86,6 +86,8 @@ int VideoOMX::init(UCHAR tformat)
   if (initted) return 0;
   initted = 1;

+ bcm_host_init();

I was communicating with Marten Richter about this but I haven't done the fix properly yet. I think he recommended a better place for that line.

After all this, it compiles and works.

3. When I made the last release I tried rolling forward my VDR version as far as possible. I got to 2.2.0 which worked. 2.3.1 broke all four of my VDR plugins and was therefore a step too far. I will have to work on this.

4. Erm, good questions. We should write something on the VDR Wiki.

5. If I remember correctly it was Marten Richter who created the Debian integration. I'm sorry, I hadn't considered those files at all when I made the last release - I've not been near them. This needs work.

6. Yes! What do you want to tackle first? ;)

7. Apparently not! I've always run vomp on single purpose Pis so it running as root hasn't been an issue. I had assumed that all the hardware access would require root permissions but it seems not. There is some code around VT switching that fails when not run as root but it doesn't seem to be making a difference. I will ask Marten what that does.

Having looked at all this in response to your message I think it's definitely time to re-base on Stretch and get a 0.5.1 released, and soon.
VOMP for Raspberry Pi / vompclient 0.5 features
« Last post by ralph on March 11, 2018, 19:59:35 »
Hi vomp developers,

I just noticed that there has been a new release of vomp for RPI. Thx a lot for that :D. I am with vomp since more than 10 years now and it is still the best vdr streaming solution out there.

I tried to find answers to various question about the release but it is rather silent around vomp nowadays. I checked vdr-wiki, vdr-portal and the git for information. It seems most people rely on Kodi, which in my opinion is not suitable for the performance of a RPI. I also checked the git logs and got some ideas, while I am unsure in some aspects. Perhaps the developers would like to give some information on the release:
  • Is lirc supported now? I was using the lircd creating uinput events, but this also caused the console to show a lot of strange characters. Direct usage of lirc would be the better solution imho. CEC is not working for me as my TV does not support the forwarding of remote control events.
  • Is it possible to compile on Raspbian Stretch? I saw some commits regarding stretch, but is it working ootb with updated CEC and FFMPEG versions?
  • Is the server plugin also working with vdr 2.3.x? Latest Ubuntu versions seem to ship now with 2.3.x. Any experiences?
  • Is it planned to provide some information at the vdrwiki, in the vdr portal or at least as a readme? The marketing of vomp is rather modest. Or are no new users wanted?
  • Is there a chance to get a Debian package being built? The debian tree is currently reflecting the version 0.4.2 as head. Perhaps this can be updated. Also, the system integration is based on init and not systemd. This is a little outdated for jessie and stretch. Are there somewhere updates around already?
  • Are contributions welcome? In which way? I did not see the possibility to add myself as a developer. At least at the packaging point or by writing a readme I should be able to contribute a little.
  • Is root really needed to run vompclient? I was running vompclient 0.4.1 always without root and never observed any trouble.

Thx for any further information provided.
VOMP for Raspberry Pi / Re: [solved] Option Advanced Menu not working properly
« Last post by MartenR on January 15, 2018, 07:16:08 »
Thanks for reporting this.
I have added your fix to the git.

VOMP for Raspberry Pi / Re: Option Advanced Menu not working properly
« Last post by kowovomp on January 14, 2018, 21:34:39 »
sourcefile VOPTS.CC needs to be corrected:

WRONG: option = new Option(19, "Advanced Menu", "General", "Menu type",Option::TYPE_TEXT, 2, 0, 0, options19);
CORRECT: option = new Option(19, "Advanced Menu", "Advanced", "Menu type",Option::TYPE_TEXT, 2, 0, 0, options19);
VOMP for Raspberry Pi / Re: Option Advanced Menu not working properly
« Last post by kowovomp on January 14, 2018, 19:07:57 »
I've found the error  ;D

The client tries to load the option from the ADVANCED section, but it's saved to GENERAL.
As a workaround i've moved the "Menu type = Classic" parameter in the conf-file to the correct section.

Pages: 1 2 [3] 4 5 ... 10