lapicidae / vdr-server

VDR Docker Image based on Arch Linux
GNU General Public License v3.0
7 stars 1 forks source link

Plugin Robotv #4

Closed nolimitek closed 8 months ago

nolimitek commented 2 years ago

Is it possible to add the Robotv Plugin? https://github.com/pipelka/vdr-plugin-robotv

Thx and best regards Chris

lapicidae commented 2 years ago

Theoretically, you can do this yourself by creating your own PKGBUILD.
Then proceed as described here.
You can find many suggestions in the VDR4Arch GitHub repository.
If you are successful then please share the PKGBUILD with us and possibly also with the plugin author.

Maybe I'll have a look at it myself, since roboTV seems to be an interesting plugin. However, I lack the time right now.

P.S.
Revising the pkgbuild tutorial is on my ToDo list

nolimitek commented 2 years ago

Thx for your reply. My Problem is i am a complete noob in arch. I already tried to build a pkgbuild but with no success. Can you explain me how top do that

Thx Chris

lapicidae commented 2 years ago

You could also ask the VDR4Arch team if they would include roboTV.

I am also not skilled in creating PKGBUILDs, however this tutorial seems to be a good introduction... and of course the Arch wiki. In the VDR4Arch git you can examine a lot of PKGBUILDs and get inspired.

lapicidae commented 2 years ago

I have created a working PKGBUILD. Please unpack into the directory "vdr/pkgbuild" and then start the container. (don't forget to publish port 34892)

I will also take care of a simple web server so that the channel logos (picons) can be used in RoboTV.

Download: vdr-robotv.tar.gz

nolimitek commented 2 years ago

WOW. Thats great . Will test it asap

thank you so much

regards Chris

lapicidae commented 2 years ago

Simple picons & epgimages server added -> c3ed371

new Image is on dockerhub

nolimitek commented 2 years ago

I have tested it. But there is a problem with the plugin. If you add a recording over the live plugin the robotv app disconnects every 4 seconds.

regards Chris

lapicidae commented 2 years ago

I get one short disconnection after each timer action.

I also saw your issue description in the roboTV git and will create some logs soon and add them there.

nolimitek commented 2 years ago

That would be nice because i find no logs

Thx

nolimitek commented 2 years ago

Hi,

The plugin robotv can not be build anymore copy to build dir...

build package...

==> Making package: vdr-robotv 0.15.0-1 (Mi 23 Feb 2022 16:36:06 CET)

==> Checking runtime dependencies...

==> Installing missing dependencies...

error: target not found: vdr-api=2.6.0

==> ERROR: 'pacman' failed to install missing dependencies.

==> Missing dependencies:

-> vdr-api=2.6.0

==> Checking buildtime dependencies...

==> ERROR: Could not resolve all dependencies.

Reassign permissions: /etc/PKGBUILD.d

Reassign permissions: /etc/vdr

Reassign permissions: /srv/vdr/video

Reassign permissions: /var/cache/vdr

Reassign permissions: /var/lib/vdr

Reassign permissions: /vdr/channellogos

Reassign permissions: /vdr/timeshift

Reassign permissions: /vdr/log

regards Chris

lapicidae commented 2 years ago

Try this: vdr-robotv.tar.gz

nolimitek commented 2 years ago

same failure

==> Making package: vdr-robotv 0.15.0-1 (Mi 23 Feb 2022 16:52:26 CET)

==> Checking runtime dependencies...

==> Installing missing dependencies...

error: target not found: vdr-api=2.6.0

==> ERROR: 'pacman' failed to install missing dependencies.

==> Missing dependencies:

-> vdr-api=2.6.0

==> Checking buildtime dependencies...

==> ERROR: Could not resolve all dependencies

lapicidae commented 2 years ago

Weird... change in PKGBUILD:

depends=('gcc-libs' "vdr-api>=${_vdrapi}")  
to  
depends=('gcc-libs')  

This should work, but I will have to check later if the pseudo package "vdr-api" is not installed by default.

nolimitek commented 2 years ago

now it works thx

nolimitek commented 2 years ago

I get one short disconnection after each timer action.

I also saw your issue description in the roboTV git and will create some logs soon and add them there.

Do you have already some logs about the failure . And do you use the robotv plugin by yourself ?

regards Chris

lapicidae commented 2 years ago

Do you have already some logs about the failure.

Unfortunately no, as I can no longer reproduce the error.

My docker settings to test robotv: enabled plugins -> ciplus ddci2 dvbapi epgborder epgsearch live robotv streamdev-server vnsiserver forwarded ports -> 2004/tcp 3000/tcp 34890/tcp 34892/tcp 6419/tcp 6419/udp 8008/tcp 8009/tcp 8099/tcp

Have you changed the log level in vdr/system/conf.d/00-vdr.conf to --log=3? This way, usable logs should be created, also as few plugins as possible should be active.

And do you use the robotv plugin by yourself ?

No, primary I use a Chromecast (with GoogleTV) with kodi and the vnsi-plugin.

nolimitek commented 1 year ago

Is Robotv now implemented in your docker image ??

lapicidae commented 8 months ago

Should have been done by the VDR4Arch team. See VDR4Arch/vdr4arch#247 (pull request "Add vdr-robotv")