Messages

Hi vomp developers,

I just noticed that there has been a new release of vomp for RPI. Thx a lot for that . 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.

Last week I posted this: http://forum.loggytronic.com/index.php?topic=757.0. Thx a lot for the fast feedback.

Now I tried to understand what went wrong and I found that one problem is the variable type (always 32 bit) while the ftell will only fail on 32-bit systems as the long argument is only 32bit wide there while on 64-bit systems the long argument is 64-bit wide. I had a look for similar issues and found another one in recplayer.c:

Code Select Expand



void RecPlayer::scan()
{
   .....

   segments[i] = new Segment();
   segments[i]->start = totalLength;
   fseek(file, 0, SEEK_END);
   totalLength += ftell(file);    // ftell will return a 32-bit (signed) value on 32-bit systems 
   totalFrames = indexFile->Last();

  .....


The ftell returns a long which is fine on 64-bit systems while the call will return a 32-bit trunated value on 32-bit systems. Since it returns a signed value the result may become even negative!

I suggest that you use ftello instead of ftell. And perhaps switch completely to fseeko even for the working call before ftell.

By the way: Why is the segments[0] array member never used? In C++ counting typically starts at 0.

Sorry for posting the issue again. I rebuilt the package and can confirm that the issue is fixed with the change.

Thx

Ralph

Hi,

I just updated to a Smart-TV. As this can play videos from VDR filesystem and the recordings in 2GB junks have been inconvenient, especially for HD recordings, I decided to set the maximum file size to 25 GByte. While watching one of the latest recordings the playback suddenly started from the beginning while it was impossible to jump to the end of the video at all. I assume that there is used a 32 bit never for file offset which is not sufficient for the complete recording. The size of the recording is about 6Gbyte. That fits well to the position where the restart happened.

I hope this problem can be reproduced. In the latest VDR versions the file size can be given in the settings. So it is likely that more users change this in future.

Ralph

Trying to add the Screenshots again. Sorry for the Brocken ZIP.

Hi everybody,

thanks a lot for the help.

Please find attached the screenshots of the config page in both screen orientations. It seems to be related to android 4.2.x. I have a mobile with android 4.1.2 that is fine while a tablett running 4.2.1 is already broken. The ascreenshot was taken with an android 4.4.4 device (nexus 5).

Ralph

Hi,

I use the pi vompclient with the VompRemote application on android. This works very well (except the configuration page that has a layout bug on newer android versions) and I do not need a remote or a keyboard. There is also a power button supported. When I hit the power button accidently twice for a wakeup (which happens from time to time with a touchscreen) the vompclient wakes up but does not do a connect to the server. The window "connecting to vdr" is not opened. The background image is loaded. Entering that state I did not find a way to recover from it. I need to login and use killall -9.

Pressing the power button on android after doing a wakeup via a connected keyboard leads to the same state.

Has anybody a workaround how this can be solved?