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

Recent posts

#71
VOMP for Raspberry Pi / Re: bug report scraper_support...
Last post by dingo35 - March 22, 2015, 10:54:24
Very strange, the change doesnt seem to change anything in the behaviour ?!?

/EDIT: restartAtFramePi only gets called when state is switched to S_JUMP_PI , which is not switched when resuming a record to play....
#72
VOMP for Raspberry Pi / Re: bug report scraper_support...
Last post by MartenR - March 22, 2015, 08:41:20
Regarding 2), it is supposed to go one GOP back,
, may be changing:
vdr->getNextIFrame(nextiframeNumber, 0, &filePos, &iframeNumber, &iframeLength);
to
vdr->getNextIFrame(max(nextiframeNumber-1,0), 0, &filePos, &iframeNumber, &iframeLength);

in " void Player::restartAtFramePI(ULONG newFrame)" helps. Tell me if it helps.

Regarding 1), this is the gradient in the background, in order to change this, the player would have to set the background to black.

Marten

#73
VOMP for Raspberry Pi / bug report scraper_support ver...
Last post by dingo35 - March 22, 2015, 07:44:23
Although just one day experience, I really like the scraper_support version; it seems more stable than the current vomp-client version (I think that's because of the segfault conditions Marten debugged); haven't had to reboot once yet...(knock on wood).

I just have two small bugs to report:
1) When displaying a 16:9 screen on 4:3 TV in letterbox mode, the lower black bar is not black but dark blue; the upper black bar is black, as expected.
2) When exiting a recording, and resuming it, the recording starts about 30 seconds later than where it was exited. This is not new behaviour, it also happened on the current (git master) vomp-client.
I guess this has something to do with either the vomp-server or the vomp-client starting at the first i-frame it encounters, but it means all p- and b-frames in between the exiting and the resuming are lost.

IMHO, the correct thing to do would be to jump back to the first I frame and start playing from there; this is the behaviour VDR itself does. It usally means the resume point is a little before the exiting point, but a little "replay" of a recording is less annoying than missing half a minute of the story  :(
I have no idea how complex that might be, a quick (but less elegant) fix would be just to rewind 30 seconds after resuming.

Marten, any ideas on this?
#74
VOMP for Raspberry Pi / Re: compiling git problem?
Last post by dingo35 - March 22, 2015, 07:34:59
Yep, downgrading did the trick!
#75
VOMP for Raspberry Pi / Re: compiling git problem?
Last post by MartenR - March 21, 2015, 11:23:57
Well, stackoverflow is right, but the raspbian packages did not set the right compile flags. I am checking, what current status is.

Downgrade to 1.8 is the simplest thing, unfortunetely, the api of libcec had a slightly change.
You can also patch the interface yourself, somewhere in this forum are instructions, but I think then you will miss the raspberry pi cec support, which is quite important for vomp, even if you do not use it. (initialization of communication with bcm_host is inside libcec).

Marten
#76
VOMP for Raspberry Pi / Re: compiling git problem?
Last post by dingo35 - March 21, 2015, 11:13:42
Hi Marten,

In my experience stuff is patched to RasPi before it is added to the Raspbian image/repository.
I also found this link http://stackoverflow.com/questions/15315372/sending-cec-commands-via-command-line-over-hdmi, stating:
Recent versions of libcec will recognize the Raspberry Pi hardware as a CEC adapter.

Stackoverflow is usually a reliable source, but I guess testing after compiling would be the ultimate proof. I have no HDMI CEC device, but I recall to have read somewhere you have :-)

Answering your question, I am still on wheezy:
root@raspvideo:/etc# cat /etc/apt/sources.list
deb http://mirrordirector.raspbian.org/raspbian/ wheezy main contrib non-free rpi
root@raspvideo:/etc# apt-cache search libcec
libcec-dev - USB CEC Adaptor communication Library (development files)
libcec1 - USB CEC Adaptor communication Library (shared library)
libcec2 - USB CEC Adaptor communication Library (shared library)
root@raspvideo:/etc# cat /etc/debian_version
7.8


The libcec-dev changelog reports libcec (2.1.3-1) unstable; urgency=low

Should I downgrade to 1.8 or is the fixing of the compile errors a minor operation?
#77
VOMP for Raspberry Pi / Re: compiling git problem?
Last post by MartenR - March 21, 2015, 10:44:04
The problem are the missing development files for 1.8.1-1 .
Since I have only patched with raspberry pi support. I do not know, if the raspbian folks managed to included support for the raspi in their libcec version.
Anyway, did you switch to jessie? Since I do not have the split into libcec1 and libcec2.

Marten
#78
VOMP for Raspberry Pi / Re: compiling git problem?
Last post by dingo35 - March 20, 2015, 10:38:45
After apt-update, apt-upgrade I downloaded current vompclient (not vompclient-marten), did a git checkout scraper_support, but I keep getting a compile error in remotelinux.cc:

remotelinux.cc: In member function 'int RemoteLinux::initCec()':
remotelinux.cc:134:34: error: invalid conversion from 'int (*)(void*, const cec_log_message&) {aka int (*)(void*, const CEC::cec_log_message&)}' to 'CEC::CBCecLogMessageType {aka int (*)(void*, CEC::cec_log_message)}' [-fpermissive]
remotelinux.cc:135:32: error: invalid conversion from 'int (*)(void*, const cec_keypress&) {aka int (*)(void*, const CEC::cec_keypress&)}' to 'CEC::CBCecKeyPressType {aka int (*)(void*, CEC::cec_keypress)}' [-fpermissive]
remotelinux.cc:136:31: error: invalid conversion from 'int (*)(void*, const cec_command&) {aka int (*)(void*, const CEC::cec_command&)}' to 'CEC::CBCecCommandType {aka int (*)(void*, CEC::cec_command)}' [-fpermissive]
remotelinux.cc:137:44: error: invalid conversion from 'int (*)(void*, const libcec_configuration&) {aka int (*)(void*, const CEC::libcec_configuration&)}' to 'CEC::CBCecConfigurationChangedType {aka int (*)(void*, CEC::libcec_configuration)}' [-fpermissive]
remotelinux.cc: In member function 'virtual UCHAR RemoteLinux::getButtonPress(int)':
remotelinux.cc:251:36: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
remotelinux.cc:279:37: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
<builtin>: recipe for target 'remotelinux.o' failed
make: *** [remotelinux.o] Error 1


These are my libcec versions:
root@raspvideo:/usr/local/src/vompclient# dpkg -l | grep libcec
ii  libcec-dev                         2.1.3-1                            armhf        USB CEC Adaptor communication Library (development files)
ii  libcec1:armhf                      1.8.1-1                            armhf        USB CEC Adaptor communication Library (shared library)
ii  libcec2:armhf                      2.1.3-1                            armhf        USB CEC Adaptor communication Library (shared library)


Is the libcec1 1.8.1-1 version the problem? apt-get install libcec1 states it is already on the newest version....

What to do?
#79
VOMP General / MVP / Re: Remote control doesn't con...
Last post by 4ndreas - February 23, 2015, 17:50:21
Hi Ondrej,
sorry, I can't help you with your problem but if you need a workaround you can use an android smartphone as remote control:
https://play.google.com/store/apps/details?id=org.vomp.remote&hl=de
It uses an ip connection and will work even if your MVP infrared is really broken. This does not solve your problem but you can at least watch TV.

4ndreas
#80
VOMP General / MVP / Remote control doesn't control...
Last post by ondrej1024 - February 16, 2015, 22:35:23
Hi all,

I have been using the vompserver plugin (0.4.0) and the MVP for many years without trouble. Now, suddenly, without changing anything, the MVP remote control doesn't control the MVP any more. I can see that the remote is sending something because the red led on the MVP is flashing while I press the remote buttons. However I am stuck with the home menu (Welcome) on the screen and cannot select any menu item.

I have tried changing the remotes batteries, powered off/on the MVP, checked the network connection to the VDR. Everything seems OK. The MVP is booting up fine when I apply the power and connect the network cable. But I am not able to control the damn MVP any more. Looks like the MVP software doesn't recognise the keys the remote is sending. This is so weird.

Has anyone an idea what I could do to find out what's going on?

Thanks, Ondrej