Messages

Come to think about it, I think I only saw that flickering with omxplayer. I assume the deinterlacer is different for omxplayer and vompclient?

I increased the memory available to the GPU to 128MB and playback works nicely now!

I do see a lot of warnings about incorrect frame size, on multiple channels. Playback is smooth and error free though.

root@raspberrypi:~/vompclient-raspi# ./vompclient -d -s 192.168.1.100 > /tmp/vompclient.log
[mp3 @ 0x1fb93c0] incorrect frame size
    Last message repeated 14119 times
[mp3 @ 0x4bbf4740] incorrect frame size
    Last message repeated 249 times
[mp3 @ 0x4b8f4740] incorrect frame size
    Last message repeated 375 times
[mp3 @ 0x4b7f4740] incorrect frame size
    Last message repeated 2259 times

I also see some flicker on the top line on some material (ads), am thinking this migth be an artifact from deinterlacing?

Here's a logfile from starting up and playing a recording, and a second log file from starting up and playing live television, with some channel swapping.

I run as

root@raspberrypi:~/vompclient-raspi# ./vompclient -s 192.168.1.100 -d  > /tmp/vompclient.log
[mp3 @ 0x1018d40] incorrect frame size
    Last message repeated 174 times

and get the incorrect frame size warning on both recordings and live tv. This VDR setup works very well when running locally on the pc with vdr-sxfe, so I'm pretty sure it's not a bad tv signal (dvb-t).

Ok, in any case, here's my hardware. I'm fairly new with the raspberry pi. Is there any other diagnostics that is of any help?

root@raspberrypi:~# cat /proc/cpuinfo
Processor   : ARMv6-compatible processor rev 7 (v6l)
BogoMIPS   : 697.95
Features   : swp half thumb fastmult vfp edsp java tls
CPU implementer   : 0x41
CPU architecture: 7
CPU variant   : 0x0
CPU part   : 0xb76
CPU revision   : 7

Hardware   : BCM2708
Revision   : 000f
Serial      : 00000000f312dcfe

Could it simply be this one?

15:15:31.760139 [EMERG]  17349 Core - Could not retrieve free virtual console, please change permissions

When the audio stops, I get these in the logs;

01:10:59.704494 [notice] 17259 Video - eventHandler 1e63288 1 80001000 0 0
01:10:59.709542 [ERR]    17259 TS Demuxer - TS Misaligned!B
01:10:59.712109 [ERR]    17259 TS Demuxer - TS Misaligned!B
01:10:59.723308 [notice] 17259 Video - eventHandler 1e63288 1 80001000 0 0
01:10:59.743302 [notice] 17259 Video - eventHandler 1e63288 1 80001000 0 0
01:10:59.763326 [notice] 17259 Video - eventHandler 1e63288 1 80001000 0 0
01:10:59.783300 [notice] 17259 Video - eventHandler 1e63288 1 80001000 0 0
01:10:59.803077 [ERR]    17259 TS Demuxer - TS Misaligned!B
01:10:59.803967 [notice] 17259 Video - eventHandler 1e63288 1 80001000 0 0

I have attached a complete log from startup until starting playback of live television (with no picture).

I think I might experience the same problem. Audio is ok for a while (about 30 secs - minute?), then it seems to go mute. My logs on the client side is mostly

01:07:53.247543 [notice] 17259 Video - eventHandler 1e7d190 1 80001000 0 0
01:07:53.267534 [notice] 17259 Video - eventHandler 1e7d190 1 80001000 0 0
01:07:53.281729 [debug]  17259 VDR - Sending KA packet
01:07:53.287642 [notice] 17259 Video - eventHandler 1e7d190 1 80001000 0 0
01:07:53.299481 [debug]  17259 VDR - Rxd correct KA reply
01:07:53.307612 [notice] 17259 Video - eventHandler 1e7d190 1 80001000 0 0
01:07:53.327582 [notice] 17259 Video - eventHandler 1e7d190 1 80001000 0 0

etc.

Ah right, didn't spot there was a more recent branch than master.

I'm just trying out vomp on rpi, and applied this patch to the vdr-plugin-vompserver on my stock yavdr 5.0 installation. Before the patch I got

Protocoll mismatch s: 0 c: 200

now I get

Protocoll mismatch s: 100 c: 200

Is there a new patch somewhere that i need to apply to the server plugin?