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

Main Menu

Black screen on some channles

Started by clausmuus, October 18, 2012, 08:37:50

Previous topic - Next topic

clausmuus

Hi,

most time, but not every, if I select one of the dvb-t NDR channels, I get only a black screen. Some times I get this also on some other channels, but the most time only on the NDR channels. The audio is every time OK. If I switch mutiple times to the same channel, every 10. I get also the video.
I use a local running VDR.
Do you have any idea?

Claus
MLD - A Distribution also for the Raspberry PI

MartenR

No, direct ideas. The question is what is happening no video arriving, video not displayed, or video jammed in the pipeline.
You said, that you get audio. What is if you wait some time, does audio playback stop? Then probably the video scheduler is blocking video playback, which is a known issue for ard hd..., I have to figure out what is happening there.

Marten

clausmuus

I had only test this for at maximum some minutes, but in this time, the audio don't stop. I have the problem on sd-tv channels (over dvb-t). HD have I not tested until the last two weeks. The system load is very low if only the audio will play back.

Claus
MLD - A Distribution also for the Raspberry PI

MartenR

Then it is something different....
Please post a log file.
But probably more test are required, it might be that video comes to late for display....

Marten

iampivot

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.


iampivot

#5
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).

MartenR

80001000 means OMX_ErrorInsufficientResources, that means that some resource is not available. Probably the video codec, which crashes sometimes.
I do not know the details. I need a longer log file, since I can not determine which component 1e63288 is.
But also TS Misaligned, sounds like bad reception. It is know that the decoder crashes too easy if the video stream is corrupt. Mostly only a reboot will help.

Marten

iampivot

Could it simply be this one?

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


iampivot

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

MartenR

I need your error message from log like you provided it, together with the log part at playback start up. Only in this case I can identify the omx component, which is failing.
But I am already very sure, that the ts stream is broken. (TS misaligned) So a problem on the vdr or with your antenna.

Marten

iampivot

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).


MartenR

The video codec is reporting unavailable resources.
When this happens a reboot might help. (The codec on firmware side is not working!)

Also no mpeg2 license key might be an issue, vomp should check for this, but may be the undocument mechanismen was changed in newer fimwares.
So please test with omxplayer if mpeg2 playback works.
Also check if you have enough memory for the GPU 128 MB at least!

Marten

iampivot

#13
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?

MartenR

The mp3 frame size messages are only there, since I was too lazy to implement a mpeg audio frame size parser, since except for the annoying message it works anyway.

Flickering on the top line does not sound like an error. It is probably the overscan area, which is normally not seen on tv.
I think you can configure your raspi to enable overscan, than this elements will not be seen.

Marten