1
VOMP for Raspberry Pi / Re: Latest version of vomp fails to compile
« on: August 01, 2019, 07:05:25 »
May be just follow the suggestion of the compiler. Seems to be a change in libAv.
Marten
Marten
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
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.
2
VOMP for Raspberry Pi / Re: [solved] Option Advanced Menu not working properly
« on: January 15, 2018, 07:16:08 »
Thanks for reporting this.
I have added your fix to the git.
Marten
I have added your fix to the git.
Marten
3
VOMP for Raspberry Pi / Re: Vompclient for RPI 2 with raspbian jessie
« on: March 23, 2016, 09:18:08 »
Not with the scraper_support branch.... (here mediamvp is not ready).
It is also very likely, that we drop support for the mediamvp, see poll under annoucements.
Marten
It is also very likely, that we drop support for the mediamvp, see poll under annoucements.
Marten
4
VOMP for Raspberry Pi / Re: Vompclient for RPI 2 with raspbian jessie
« on: March 20, 2016, 13:36:19 »
We do not have debian control files for the server.
Do in another directory:
apt-get source vdr-plugin-vompserver
then copy the files from the git over to the new directory.
Then do the dpkg-buildpackage, but it will fail and tell you that there are changes in the directory, but it will also tell you how easily you can build a patch, do this and the dpkg-buildpackage again.
Marten
Do in another directory:
apt-get source vdr-plugin-vompserver
then copy the files from the git over to the new directory.
Then do the dpkg-buildpackage, but it will fail and tell you that there are changes in the directory, but it will also tell you how easily you can build a patch, do this and the dpkg-buildpackage again.
Marten
5
VOMP for Raspberry Pi / Re: Vompclient for RPI 2 with raspbian jessie
« on: March 19, 2016, 17:09:47 »
Does not look too bad..., I just forgot something.
Three points:
1) Are you on jessie for raspbian, I am just wondering since the vchost_config error, I think should be gone long ago...
2) I just forgot, you have to create a source tar in order, that debian is happy. You can do this with create_source_tar script in the debian directory, but you may have to adjust the version number in the script. This is the cause for the error you get in the end.
3) Your questions: "One last question: why do I compile vompclient 0.4.2-1 and not 0.4.1?
Does vompclient 0.4.2 fit to vompserver 0.4.1?
"
Well the scraper branch will eventually be 0.4.2 at some time. And only in this branch fixes for compiling in jessie are included.
And yes you need also the scraper branch on the server. But I think the additional work will pay off, since the scraper support branch gives you a nicer UI and if you have epgd and the scraper plugins installed you even get moviepictures.....
Marten
Three points:
1) Are you on jessie for raspbian, I am just wondering since the vchost_config error, I think should be gone long ago...
2) I just forgot, you have to create a source tar in order, that debian is happy. You can do this with create_source_tar script in the debian directory, but you may have to adjust the version number in the script. This is the cause for the error you get in the end.
3) Your questions: "One last question: why do I compile vompclient 0.4.2-1 and not 0.4.1?
Does vompclient 0.4.2 fit to vompserver 0.4.1?
"
Well the scraper branch will eventually be 0.4.2 at some time. And only in this branch fixes for compiling in jessie are included.
And yes you need also the scraper branch on the server. But I think the additional work will pay off, since the scraper support branch gives you a nicer UI and if you have epgd and the scraper plugins installed you even get moviepictures.....
Marten
6
VOMP for Raspberry Pi / Re: Vompclient for RPI 2 with raspbian jessie
« on: March 19, 2016, 07:51:53 »
Can you just try to get the current source from the scraper branch on jessie OS, and try to use dpkg-buildpackage and report the errors which occur...
Marten
Marten
7
VOMP for Raspberry Pi / Re: Vompclient for RPI 2 with raspbian jessie
« on: October 24, 2015, 08:26:30 »
You have to get the source from git and run dpkg-buildpackage inside the directory, of course with all build dependencies installed. Search on the web how to build a debian package.
Marten
Marten
8
VOMP for Raspberry Pi / Re: Vompclient for RPI 2 with raspbian jessie
« on: October 23, 2015, 07:15:50 »
Please tell me, what the problem is?
I do not have a RPI 2, but users of vomp reported to me, that the current development branch scraper_support just works on raspberry 2.
Of course you must have the corresponding server version.
Marten
I do not have a RPI 2, but users of vomp reported to me, that the current development branch scraper_support just works on raspberry 2.
Of course you must have the corresponding server version.
Marten
9
VOMP General / MVP / Re: Further issue with file size > 4GByte on 32bit
« on: April 21, 2015, 07:15:15 »
The ftell is already an ftello in the scraper_support branch in git.
Please use for further testing the development branch scraper_support, both on client and server side.
It will soon lead to an release.
The segments corresponds to the files of the recording, their number starts at 1.
That is the reason.
Marten
Please use for further testing the development branch scraper_support, both on client and server side.
It will soon lead to an release.
The segments corresponds to the files of the recording, their number starts at 1.
That is the reason.
Marten
10
VOMP for Raspberry Pi / Re: Playback starts from the beginning when files are >4Gbyte
« on: April 13, 2015, 06:54:06 »11
VOMP for Raspberry Pi / Re: bug report scraper_support version
« on: April 04, 2015, 14:37:26 »
2) is also now changed in git. It goes back to last iframe.
The problem is you never know how long you have to go back, since the resume point is determined on the server side.
That means as resuming point always the last frame, that was streamed to the raspberry pi is taken.
Since we have some buffering, that is always inaccurate.
Marten
The problem is you never know how long you have to go back, since the resume point is determined on the server side.
That means as resuming point always the last frame, that was streamed to the raspberry pi is taken.
Since we have some buffering, that is always inaccurate.
Marten
12
VOMP for Raspberry Pi / Re: bug report scraper_support version
« on: April 04, 2015, 13:32:22 »
1) is now changed in git.
Marten
Marten
13
VOMP for Raspberry Pi / Re: bug report scraper_support version
« on: March 23, 2015, 07:07:07 »
Ok, then it was the wrong one.
setstartframe should then be changed, with a similar logic.
Marten
setstartframe should then be changed, with a similar logic.
Marten
14
VOMP for Raspberry Pi / Re: bug report scraper_support version
« on: March 22, 2015, 08:41:20 »
Regarding 2), it is supposed to go one GOP back,
, may be changing:
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
, may be changing:
Code: [Select]
vdr->getNextIFrame(nextiframeNumber, 0, &filePos, &iframeNumber, &iframeLength);toCode: [Select]
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
15
VOMP for Raspberry Pi / Re: compiling git problem?
« on: 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
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