Re: [vdr] Media (.mkv) player on Raspberry Pi2 VDR client

[Gerald Dachs]

Am 2016-02-09 10:19, schrieb Nicolas Huillard:

Hi all,

My new Raspberry Pi2 install lacks a media player, which begins to be a
bit annoying. The current setup :
* NFS server
* DigitalDevices Octopus Net DVB network server
* VDR + rpihddevice + satip on the Pi2 : live TV, timers, recordings,
etc.


IMHO OpenELEC covers all your needs and is still lightweight.

Gerald

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Media (.mkv) player on Raspberry Pi2 VDR client

[Gerald Dachs]

Am 2016-02-09 10:43, schrieb Nicolas Huillard:

Le mardi 09 février 2016 à 10:33 +0100, Gerald Dachs a écrit :

Am 2016-02-09 10:19, schrieb Nicolas Huillard:
> Hi all,
>
> My new Raspberry Pi2 install lacks a media player, which begins to be a
> bit annoying. The current setup :
> * NFS server
> * DigitalDevices Octopus Net DVB network server
> * VDR + rpihddevice + satip on the Pi2 : live TV, timers, recordings,
> etc.

IMHO OpenELEC covers all your needs and is still lightweight.


As I understand OpenELEC, it is a lightweight Kodi (XBMC) distro, which
by definition gets VDR out of the way.


No, that is not true. I even helped to better integrate VDR into 
OpenELEC.


Gerald

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Media (.mkv) player on Raspberry Pi2 VDR client

[Nicolas Huillard]

Le mardi 09 février 2016 à 11:35 +0100, Gerald Dachs a écrit :
> Am 2016-02-09 10:43, schrieb Nicolas Huillard:
> > Le mardi 09 février 2016 à 10:33 +0100, Gerald Dachs a écrit :
> >> Am 2016-02-09 10:19, schrieb Nicolas Huillard:
> >> > Hi all,
> >> >
> >> > My new Raspberry Pi2 install lacks a media player, which begins to be a
> >> > bit annoying. The current setup :
> >> > * NFS server
> >> > * DigitalDevices Octopus Net DVB network server
> >> > * VDR + rpihddevice + satip on the Pi2 : live TV, timers, recordings,
> >> > etc.
> >> 
> >> IMHO OpenELEC covers all your needs and is still lightweight.
> > 
> > As I understand OpenELEC, it is a lightweight Kodi (XBMC) distro, which
> > by definition gets VDR out of the way.
> 
> No, that is not true. I even helped to better integrate VDR into 
> OpenELEC.

I meant that Kodi becomes the main interface, with a VNSI/PVR client
add-on, while the VDR instance will remain (in my case) on the headless
server, with a limited or non-existing UI.

Will the current stable Kodi 15.2 include your work ? Any specific
advice on how to have this kind of setup running ?

Many thanks !

-- 
NH


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Media (.mkv) player on Raspberry Pi2 VDR client

[thomas]

Hi Nicolas

Quoting Nicolas Huillard :


The mplayer plugin seem very old and may not work neatly with the
rpihddevice output.


As I understand the mplayer plugin, it just launches an external  
player - this won't work on the Raspberry Pi. But technically  
speaking, it shouldn't be that hard to write a plugin which browses  
through mkv files, reads them and passes the packets to VDR's output  
device by implementing a dedicated player class. But that's probably  
not the way you asked. ;-)



Maybe simply moving the MKV files inside the recordings tree, and
creating a vdr index for each work in some way.


Personally I convert mkv files to VDR recordings. Since you don't need  
to reencode anything this is quite fast and easy and you'll get all  
the comfort you're used from VDR. This even works for BD rips on the  
Raspberry, including subtitles and DTS sound tracks.


Regards,
Thomas



___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Media (.mkv) player on Raspberry Pi2 VDR client

[Füley István]

2016.02.09. 11:19 keltezéssel, Nicolas Huillard írta:


The mplayer plugin seem very old and may not work neatly with the
rpihddevice output.


I use mplayer plugin on my old RPI, and it's working fine, even with HD 
.mkv-s. It's patched for using omxplayer instead of mplayer.
See details here (neither do I speak German, but it's pretty easy to 
understand with Google translate).


http://www.vdr-portal.de/board18-vdr-hardware/board98-arm-co/121850-rpihddevice-mplayer-plugin-patch-f%C3%BCr-omxplayer/

regards,

István



___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Media (.mkv) player on Raspberry Pi2 VDR client

[Nicolas Huillard]

Le mardi 09 février 2016 à 10:33 +0100, Gerald Dachs a écrit :
> Am 2016-02-09 10:19, schrieb Nicolas Huillard:
> > Hi all,
> > 
> > My new Raspberry Pi2 install lacks a media player, which begins to be a
> > bit annoying. The current setup :
> > * NFS server
> > * DigitalDevices Octopus Net DVB network server
> > * VDR + rpihddevice + satip on the Pi2 : live TV, timers, recordings,
> > etc.
> 
> IMHO OpenELEC covers all your needs and is still lightweight.

As I understand OpenELEC, it is a lightweight Kodi (XBMC) distro, which
by definition gets VDR out of the way.
I'd like to keep VDR and avoid other things for various reasons (I'll
try OpenELEC on some spare SD card though).

-- 
NH


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] Media (.mkv) player on Raspberry Pi2 VDR client

[Nicolas Huillard]

Hi all,

My new Raspberry Pi2 install lacks a media player, which begins to be a
bit annoying. The current setup :
* NFS server
* DigitalDevices Octopus Net DVB network server
* VDR + rpihddevice + satip on the Pi2 : live TV, timers, recordings,
etc.
* an old VDR instance on the NFS server plays MKV media (using
xinelibouput), but lacks satip (no timers, no live TV anymore)

I will upgrade the old VDR to act as a headless epg/timer/recording
server. I will thus be unable to play the MKV media on it (headless).

What's the recommended light way to play MKV videos on the Pi2 from
within VDR ?
Adding XBMC on the Pi2 seems a bit too heavy.
The mplayer plugin seem very old and may not work neatly with the
rpihddevice output.
Maybe simply moving the MKV files inside the recordings tree, and
creating a vdr index for each work in some way.

(I use the MLD distribution (http://www.minidvblinux.de/) on the Pi2,
but the forums are all in german, which is a real problem for me...)

TIA,

-- 
NH


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Media (.mkv) player on Raspberry Pi2 VDR client

[Nicolas Huillard]

Le mardi 09 février 2016 à 11:24 +0100, tho...@reufer.ch a écrit :
> Quoting Nicolas Huillard :
> 
> > The mplayer plugin seem very old and may not work neatly with the
> > rpihddevice output.
> 
> As I understand the mplayer plugin, it just launches an external  
> player - this won't work on the Raspberry Pi. But technically  
> speaking, it shouldn't be that hard to write a plugin which browses  
> through mkv files, reads them and passes the packets to VDR's output  
> device by implementing a dedicated player class. But that's probably  
> not the way you asked. ;-)

I wonder why this kind of plugin does not exists since all these
years... The need and skills seem to be here. Unfortunately, I won't be
able to do this.
I'll check mplayer + omxplayer though.

> > Maybe simply moving the MKV files inside the recordings tree, and
> > creating a vdr index for each work in some way.
> 
> Personally I convert mkv files to VDR recordings. Since you don't need  
> to reencode anything this is quite fast and easy and you'll get all  
> the comfort you're used from VDR. This even works for BD rips on the  
> Raspberry, including subtitles and DTS sound tracks.

Can you please elaborate a bit on how you convert mkv to VDR ts ? I see
a 2011 thread on a related topic, but tools may have evolved since
then ;-)

Thanks for your answer !

-- 
NH


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] NOT SOLVED!!! buffer overruns and sync probs after change of receivers

[Thomas Netousek]

Harald,

if
- the problem surfaces only with a new DVBs hardware card (and not with 
the old one) and
-  it only appears when you have traffic both on the DVB card and on the 
network interface and

-  the problem only goes away when you cold boot

then this makes me think that you have a problem with the PCIe bus.

I trust you have updated the mainboard BIOS to the latest level, right ?

Can you please elaborate on the hardware
* mainboard make and model
* schematic of the mainboard and how network card, disk controller and 
DVB card are attached


Please run an iperf test (bi-directional) to measure the network 
performance when newly booted and when "the problem" has surfaced.


And I would guess that you can trigger the problem more easily if you 
run iperf, create disk activity (run a random access read-only disk test 
?) and run the remote video client at the same time.


Btw, there are LEDs on the Digital Devices card, do they change between 
the "good" and the "bad" state ?


Thomas

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Media (.mkv) player on Raspberry Pi2 VDR client

[Gerald Dachs]

Am 2016-02-09 12:01, schrieb Nicolas Huillard:

Le mardi 09 février 2016 à 11:35 +0100, Gerald Dachs a écrit :

Am 2016-02-09 10:43, schrieb Nicolas Huillard:
> Le mardi 09 février 2016 à 10:33 +0100, Gerald Dachs a écrit :
>> Am 2016-02-09 10:19, schrieb Nicolas Huillard:
>> > Hi all,
>> >
>> > My new Raspberry Pi2 install lacks a media player, which begins to be a
>> > bit annoying. The current setup :
>> > * NFS server
>> > * DigitalDevices Octopus Net DVB network server
>> > * VDR + rpihddevice + satip on the Pi2 : live TV, timers, recordings,
>> > etc.
>>
>> IMHO OpenELEC covers all your needs and is still lightweight.
>
> As I understand OpenELEC, it is a lightweight Kodi (XBMC) distro, which
> by definition gets VDR out of the way.

No, that is not true. I even helped to better integrate VDR into
OpenELEC.


I meant that Kodi becomes the main interface, with a VNSI/PVR client
add-on, while the VDR instance will remain (in my case) on the headless
server, with a limited or non-existing UI.


No, OpenELEC supports and provides a local VDR.



Will the current stable Kodi 15.2 include your work ?


yes


Any specific advice on how to have this kind of setup running ?


not really. My work just allows a channel scan from the vdr-addon 
settings instead of using the vnsi client interface to the VDR.


Gerald


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Media (.mkv) player on Raspberry Pi2 VDR client

[thomas]

Quoting Nicolas Huillard :


Can you please elaborate a bit on how you convert mkv to VDR ts ? I see
a 2011 thread on a related topic, but tools may have evolved since
then ;-)


There is no "VDR ts", it's just ts, so you can use every tool which is  
capable of handling ts streams.


When I'm converting BDs with makemkv on my Mac, I use tsMuxeR, since  
there's a nice Mac GUI available - this way, I don't even have to  
bother the keyboard for typing cli commands.


On Linux, using ffmpeg is also straight forward. Here's an example  
from my bash's history:
ffmpeg -i /var/data/media/movies/Breaking\  
Bad/Breaking_Bad_Season_1_Disc_1_t00.mkv -f mpegts -map 0:0 -map 0:1  
-map 0:3 -map 0:5 -map 0:6 -map 0:11 -map 0:12 -vcodec copy -c:a:0 ac3  
-c:a:1 copy -scodec copy -bsf h264_mp4toannexb 1.ts


You see, there's a mapping to get rid of unwanted subtitle tracks and  
the first audio track ist converted to AC-3 since it was stored as  
DTS-HD on the disc. But basically the command sould look like:


ffmpeg -i  -f mpegts -vcodec copy -acodec copy -scodec copy  
-bsf h264_mp4toannexb 1.ts


That's it. Put the file into a VDR recording folder, write a minimal  
info file (AFAIK only title, lifetime and priority is mandatory) and  
you'll see the new recording once you triggered VDR to update its  
recordings.


Regards,
Thomas



___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] NOT SOLVED!!! buffer overruns and sync probs after change of receivers

[Harald Milz]

Hi folks,

I hate to follow up on myself, but as it appears I cheered too soon. It now
also happens reproducibly when recording, and independent of vnsiserver or
anything else. 

The machine has been up for 4 days, and when starting a new recording, this is
what happens after some seconds:

Feb  9 11:41:37 seneca vdr: [624] i/o throttle activated, count = 1 (tid=624)
Feb  9 11:41:46 seneca vdr: [624] buffer usage: 70% (tid=623)
Feb  9 11:41:46 seneca vdr: [624] buffer usage: 60% (tid=623)
Feb  9 11:41:46 seneca vdr: [624] buffer usage: 70% (tid=623)
Feb  9 11:41:46 seneca vdr: [624] buffer usage: 60% (tid=623)
Feb  9 11:41:46 seneca vdr: [624] buffer usage: 70% (tid=623)
Feb  9 11:41:46 seneca vdr: [624] buffer usage: 60% (tid=623)
Feb  9 11:41:46 seneca vdr: [624] buffer usage: 70% (tid=623)
Feb  9 11:41:46 seneca vdr: [624] buffer usage: 60% (tid=623)
Feb  9 11:41:46 seneca vdr: [624] buffer usage: 70% (tid=623)
Feb  9 11:41:46 seneca vdr: [624] buffer usage: 60% (tid=623)
Feb  9 11:41:46 seneca vdr: [624] buffer usage: 70% (tid=623)
Feb  9 11:41:46 seneca vdr: [624] buffer usage: 60% (tid=623)
Feb  9 11:41:46 seneca vdr: [624] buffer usage: 70% (tid=623)
Feb  9 11:41:51 seneca vdr: [624] buffer usage: 80% (tid=623)
Feb  9 11:41:55 seneca vdr: [624] buffer usage: 90% (tid=623)
Feb  9 11:41:59 seneca vdr: [624] buffer usage: 100% (tid=623)
Feb  9 11:41:59 seneca vdr: [624] ERROR: 1 ring buffer overflow (1 bytes 
dropped)
Feb  9 11:42:05 seneca vdr: [624] ERROR: 31446 ring buffer overflows (5911848 
bytes dropped)
Feb  9 11:42:11 seneca vdr: [624] ERROR: 32635 ring buffer overflows (6135380 
bytes dropped)

(needless to say the recording is entirely crippled.) 

VDR is 2.2.0, plain but with PLAYERBUFSIZE and RECORDERBUFSIZE enlarged to 50
megs each. As I suspected earlier, enlarging the buffers only cures the
symptom. It's only a matter of time. As if memory regions and pointers weren't
cleanly free()'d but reused next time instead of malloc()ing new ones.
Looking at the cRingBufferLinear class this seems to be the case. But how can
this persist across VDR restarts? I'm puzzled. 

Restarting VDR, reloading the DVB drivers (dddvb-0.9.22 from Digital Devices)
does not remedy the overruns. Only restarting the machine does.

If anyone had an idea where to look, that would be great. e.g. were there any
significant changes in the TS buffer code between 2.2.0 and devel-latest? I'm
a bit reluctant to try 2.3.x because some plugins may not work with it. 

TIA!



On Mon, Feb 08, 2016 at 08:17:08AM +0100, Harald Milz wrote:
> Richard, 
> 
> On Sun, Feb 07, 2016 at 12:34:17PM +, Richard F wrote:
> > One of the things that the vnsi developer said to do set this in the VDR
> > config
> > 
> > vnsiserver.AvoidEPGScan = 1
> > (http://forum.kodi.tv/showthread.php?tid=203396)
> 
> Now that you mention it - I also see interruptions sometimes when Kodi appears
> to update its timers. That is, when it scans through the timer list,
> displaying the respective message windows bottom left. Sometimes, live
> streaming just crashes, and needs to be restarted manually. 
> 
> I'll give AvoidEPGScan = 1 a try - thank you! 
> 
> > I don't know where PLAYERBUFSIZE is - Kodi config file - which one?
> 
> No, that's in vdr:
> 
> dvbplayer.c:#define PLAYERBUFSIZE  MEGABYTE(1)
> 
> and 
> 
> recorder.c:#define RECORDERBUFSIZE  (MEGABYTE(10) / TS_SIZE * TS_SIZE) //
> multiple of TS_SIZE
> 
> Please not that it really cures only the symptom. If there is a problem with
> filling any emptying the buffer, leading to an overrun, then it will
> eventually happen, no matter what the size is. So far, I haven't seen this
> yet with 50 megs each. 
> 
> -- 
> A gift of a flower will soon be made to you.

-- 
Never be led astray onto the path of virtue.

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Media (.mkv) player on Raspberry Pi2 VDR client

[VDR User]

You don't need to bother with Kodi (unless you actually want to use
it). VDR + the mplayer plugin work perfectly fine. There's no point in
unnecessarily complicating a persons setup if that's not what they
want.

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Media (.mkv) player on Raspberry Pi2 VDR client

[Gerald Dachs]

Am 09.02.2016 um 17:07 schrieb VDR User:
> You don't need to bother with Kodi (unless you actually want to use
> it). VDR + the mplayer plugin work perfectly fine. There's no point in
> unnecessarily complicating a persons setup if that's not what they
> want.
I know nothing in OpenELEC that is complicating a persons setup, what do
you have in mind?
At least his current setup is complicated enough so that he has no idea
what to do next.

Gerald

!DSPAM:56ba1e4b68607589549215!


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Media (.mkv) player on Raspberry Pi2 VDR client

[VDR User]

>> You don't need to bother with Kodi (unless you actually want to use
>> it). VDR + the mplayer plugin work perfectly fine. There's no point in
>> unnecessarily complicating a persons setup if that's not what they
>> want.
> I know nothing in OpenELEC that is complicating a persons setup, what do
> you have in mind?
> At least his current setup is complicated enough so that he has no idea
> what to do next.

He has no idea what to do next because he lacks information, not
because his setup is complicated. And, any time you bundle additional
software along with all of the dependencies that come with it, it's
just more to maintain and more that can break. What sense does that
make when all he wants to do is play mkvs? Kodi is completely
unnecessary, surely you agree.

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr