Hi all,
I still have a problem with my new setup: * Raspberry Pi B (256MB system + 256MB video) * MLD 5.0.0 testing distribution (http://www.minidvblinux.de/) on a 4GB class 6 SD card, using VDR 2.2.0.203-207 * vdr-plugin-rpihddevice (from MLD 1:2015.08.24-37+2.2.0.203) * Octopus Net (firmware 1.0.55) : Linux VLC shows TV channels without problems * vdr-plugin-satip (from MLD 2015.09.19-20+2.2.0.203) * recordings on an NFS share (works for playing, didn't test recording) * the Raspberry is powered from one of the 5V output from the Octopus, which provides enough power for the CI interface, which seems
Playing live TV works great, until some point a few dozen minutes later, where some errors start to appear in /var/log/messages:
Oct 25 10:51:59 vdrpi user.err vdr: [17414] ERROR: 1 ring buffer overflow (940 bytes dropped) Oct 25 10:52:01 vdrpi user.info vdr: [17414] SATIP: Detected 1 RTP packet errors [device 0] Oct 25 10:52:05 vdrpi user.err vdr: [17414] ERROR: 496 ring buffer overflows (652736 bytes dropped) Oct 25 10:52:11 vdrpi user.err vdr: [17414] ERROR: 584 ring buffer overflows (768544 bytes dropped) Oct 25 10:52:17 vdrpi user.err vdr: [17414] ERROR: 584 ring buffer overflows (768544 bytes dropped) Oct 25 10:52:23 vdrpi user.err vdr: [17414] ERROR: 580 ring buffer overflows (763280 bytes dropped) Oct 25 10:52:28 vdrpi user.err vdr: [17413] rpihddevice: [libav] Header missing Oct 25 10:52:28 vdrpi user.err vdr: [17413] rpihddevice: failed to decode audio frame! Oct 25 10:52:31 vdrpi user.err vdr: [17426] ERROR: TS packet not accepted in Transfer Mode Oct 25 10:52:31 vdrpi user.debug vdr: [17413] rpihddevice: set HDMI audio output format to 2ch PCM, 48.0kHz Oct 25 10:52:38 vdrpi user.err vdr: [17426] ERROR: TS packet not accepted in Transfer Mode Oct 25 10:52:38 vdrpi user.debug vdr: [17413] rpihddevice: set HDMI audio output format to 2ch PCM, 48.0kHz
Some earlier errors were:
Oct 24 18:02:59 (none) user.err vdr: [11447] SATIP-ERROR: Connection timeout - retuning [device 1] Oct 24 18:03:00 (none) user.err vdr: [11442] ERROR: 584 ring buffer overflows (768544 bytes dropped) Oct 24 18:03:04 (none) user.err vdr: [11447] SATIP-ERROR: Connection timeout - retuning [device 1] Oct 24 18:03:06 (none) user.err vdr: [11442] ERROR: 584 ring buffer overflows (768544 bytes dropped)
Those errors lasted for hours, until I stopped VDR. It's usually not fixed until I power cycle the pi.
I don't know were to look from here. Options are: * the satip plugin may not be the latest one (but the version number is unclear and the MLD forum is all german-speaking, which is a problem for me) * the ethernet interface may miss packets even though it does not report any packet loss (I changed the cable -quality and length- without success) * the power provided to the rpi may be enough, but I don't know about temperatures (the video core reports 54°C, but the ethernet chip may be too hot) * maybe the Octopus does not provide a proper stream, or the problem comes from the VDR core or the rpihddevice output...
Since I'm new to rpihddevice, satip and MLD, and didn't stress previous Raspberry Pïs before, even though I use VDR since a dozen years at least, I'm really lost here.
Latest test: a few second after switching some channel, the image froze, sound looped, and the pi was not reachable anymore through SSH, even though the octopus still reported the live stream and the network LEDs on the pi was still blinking. Hardware problem, network driver problem ?
TIA,
On 10/25/15 11:44, Nicolas Huillard wrote:
Hi all,
I still have a problem with my new setup:
- Raspberry Pi B (256MB system + 256MB video)
- MLD 5.0.0 testing distribution (http://www.minidvblinux.de/) on a 4GB
class 6 SD card, using VDR 2.2.0.203-207
- vdr-plugin-rpihddevice (from MLD 1:2015.08.24-37+2.2.0.203)
- Octopus Net (firmware 1.0.55) : Linux VLC shows TV channels without
problems
- vdr-plugin-satip (from MLD 2015.09.19-20+2.2.0.203)
- recordings on an NFS share (works for playing, didn't test recording)
- the Raspberry is powered from one of the 5V output from the Octopus,
which provides enough power for the CI interface, which seems
Playing live TV works great, until some point a few dozen minutes later, where some errors start to appear in /var/log/messages:
...
I strongly suggest you use the newer Raspberry Pi 2 model. I have two of these in operation, and they work like a charm. Before that I also experimented with the model 1, but had similar problems as you described.
Klaus
Le dimanche 25 octobre 2015 à 12:04 +0100, Klaus Schmidinger a écrit :
On 10/25/15 11:44, Nicolas Huillard wrote:
Hi all,
I still have a problem with my new setup:
- Raspberry Pi B (256MB system + 256MB video)
- MLD 5.0.0 testing distribution (http://www.minidvblinux.de/) on a 4GB
class 6 SD card, using VDR 2.2.0.203-207
- vdr-plugin-rpihddevice (from MLD 1:2015.08.24-37+2.2.0.203)
- Octopus Net (firmware 1.0.55) : Linux VLC shows TV channels without
problems
- vdr-plugin-satip (from MLD 2015.09.19-20+2.2.0.203)
- recordings on an NFS share (works for playing, didn't test recording)
- the Raspberry is powered from one of the 5V output from the Octopus,
which provides enough power for the CI interface, which seems
Playing live TV works great, until some point a few dozen minutes later, where some errors start to appear in /var/log/messages:
...
I strongly suggest you use the newer Raspberry Pi 2 model. I have two of these in operation, and they work like a charm. Before that I also experimented with the model 1, but had similar problems as you described.
Well, thank you Klaus. That advice aligns with what I figured out this morning, reading, comparing and rebooting the Pi many times.
Le dimanche 25 octobre 2015 à 12:04 +0100, Klaus Schmidinger a écrit :
On 10/25/15 11:44, Nicolas Huillard wrote:
Hi all,
I still have a problem with my new setup:
- Raspberry Pi B (256MB system + 256MB video)
- MLD 5.0.0 testing distribution (http://www.minidvblinux.de/) on a 4GB
class 6 SD card, using VDR 2.2.0.203-207
- vdr-plugin-rpihddevice (from MLD 1:2015.08.24-37+2.2.0.203)
- Octopus Net (firmware 1.0.55) : Linux VLC shows TV channels without
problems
- vdr-plugin-satip (from MLD 2015.09.19-20+2.2.0.203)
- recordings on an NFS share (works for playing, didn't test recording)
- the Raspberry is powered from one of the 5V output from the Octopus,
which provides enough power for the CI interface, which seems
Playing live TV works great, until some point a few dozen minutes later, where some errors start to appear in /var/log/messages:
...
I strongly suggest you use the newer Raspberry Pi 2 model. I have two of these in operation, and they work like a charm. Before that I also experimented with the model 1, but had similar problems as you described.
I know have an RPi2 installed since a few days, which works great. It can almost record 3 channels and view a 4th one, everything from the network (SAT>IP to get DVB streams, NFS for remote storage). I may change my mind and get back to a single VDR instance, without client/server (the RPi 1 was not meant to record anything, relying on remote timers).
Thanks Klaus !
On Sun, Nov 15, 2015 at 07:09:41PM +0100, Nicolas Huillard wrote:
I know have an RPi2 installed since a few days, which works great.
Coincidentally, I acquired a Raspberry Pi 2 about 2 weeks ago. I installed Raspbian, compiled VDR 2.2.0 and the following plugins:
http://projects.vdr-developer.org/git/vdr-plugin-rpihddevice.git/ http://www.uli-eckhardt.de/vdr/cec.en.shtml http://www.saunalahti.fi/~rahrenbe/vdr/iptv/ http://www.saunalahti.fi/~rahrenbe/vdr/elvis/ (specific to my ISP)
The cecremote plugin allows the TV remote control to be used for controlling VDR. The TV-side implementation of HDMI-CEC is not perfect, but I think it is better than duplicating the RC hardware. The only cables attached to the Raspberry are HDMI, power, and Ethernet.
With the IPTV plugin, I can receive some MPEG2 and MPEG4 (HDTV) DVB streams that are multicast by my ISP. The HDTV streams sometimes suffer from dropped frames.
It can almost record 3 channels and view a 4th one, everything from the network (SAT>IP to get DVB streams, NFS for remote storage).
I guess those were not HDTV channels? When I tried pausing and then resuming live TV, storing the stream on the SD card, it stuttered a little. I did not try it with a USB hard disk.
I may change my mind and get back to a single VDR instance, without client/server (the RPi 1 was not meant to record anything, relying on remote timers).
In my household, the RPi will only be a part-time VDR client (mainly for playing back recordings), and part-time learning/tinkering platform for the kids. I plan to write a startup script that boots the RPi to VDR by default, but allows one to exit to the Raspbian desktop, probably by simply misusing the "Restart VDR" menu entry for that.
Thanks Klaus !
Yes, thanks to all contributors! VDR is a really great piece of software.
Marko
-
Klaus Schmidinger -
Marko Mäkelä -
Nicolas Huillard