Hi,
with the latest version of the vompclient (version 76aef7237b9a2f465e4d3d7ef4250eb7a087866c), the vompclient and than also the RPI crash short time after starting TV replay. If I select a SD-TV channel, the system crash after a view second and the vomp client shows the message "Connection lost". On HD channels only the keyboard connection lost after a view seconds. In both cases the keyboard LED flashes up before the system crash and I see some short video interrupts.
With a older Version of the vompclient I have not had this problems (no crashes). Yesterday I have also added my mpeg2 license key.
Do you have any ideas?
Claus
I've just tested my installation and I have no problem viewing live SD TV or recordings (I don't have an HD card). I'm running the latest vompclient on an up-to-date Raspbian distribution (with MPEG2 enabled), and vdr 1.7.29 on the server.
Hi davep,
is it possible for you, to test this image http://www.minidvblinux.de/download.php?file=3.0.1-rpi//MLD-3.0.1-rpi_vomp-client-2012.09.10_48.tgz again your vdr server?
Claus
@claus
A log file would help. (vompclient -d >debug.log).
One idea I looked into your distribution and did not find libcec .
May be I did not look close enough, did you include it?
I added libcec support on the weekend, maybe your old version did use a version before this change.
(Initialising of some libs is now handled by libcec (otherwise they are initiallized twice causing crashes), if it is not there or if it does not has raspberry pi support crashes are very likely.)
Also, please always test with the latest firmware (I am working on raspbian, I am always adapting to their current firmware)
Btw. somechange I made are causing a higher cpu load on the new commits, I have to think about a way to reduce this. Maybe this interferes with your local vdr server.
Marten
Quote from: clausmuus on September 11, 2012, 12:20:54
Hi davep,
is it possible for you, to test this image http://www.minidvblinux.de/download.php?file=3.0.1-rpi//MLD-3.0.1-rpi_vomp-client-2012.09.10_48.tgz again your vdr server?
Claus
Sorry I don't have any spare SD cards at the moment to test your image.
Hi Marten,
the libcec should be located at /usr/lib/arm-linux-gnueabihf/. I remember that the vompclient don't start without this lib (as I don't add it first).
I also use the latest server and latest client version from git (get last night at midnight). The firmware is from 2012.09.09
I will prepare the log file today evening.
Do you know the reason for the keyboard LED flashing?
Claus
Quotethe libcec should be located at /usr/lib/arm-linux-gnueabihf/. I remember that the vompclient don't start without this lib (as I don't add it first).
Did you make sure that raspberry pi support is compiled in? (Output from configure)
Quote
Do you know the reason for the keyboard LED flashing?
No ideas... sorry...
Marten
Quote from: MartenR on September 11, 2012, 14:04:13
Quotethe libcec should be located at /usr/lib/arm-linux-gnueabihf/. I remember that the vompclient don't start without this lib (as I don't add it first).
Did you make sure that raspberry pi support is compiled in? (Output from configure)
Do you mean raspberry pi support for the cec lib? I use the deb packages prepared by you.
Claus
QuoteDo you mean raspberry pi support for the cec lib? I use the deb packages prepared by you.
Ok, then it is included.
But it might be better to build it from scratch, since you are using a different distribution.
Marten
Hi,
yes, I plan to build it myself. But since I use raspian as development environment, your packages should work for me for now.
Claus
Hi,
ok, now I have compile the libcec my self. But it don't help.
You can find the debug log at http://www.minidvblinux.de/download/vompclient.log
Maybe the crash is not a vompclient crash, but a usb crash. This will also result in a not working keyboard and network. Maybe the reason is that vompclient makes more network traffic than the older version?
Claus
PS.:
I have found a solution for the problem. If I deactivate the SD TV deinterlacing, there are no more crashes. Also no crashes on HD TV. Why this?
QuotePS.:
I have found a solution for the problem. If I deactivate the SD TV deinterlacing, there are no more crashes. Also no crashes on HD TV. Why this?
Well there should be no deinterlacing activate, when using HDTV. Please look in the log if it says also for HDTV that deinterlacing is activated.
Please try too things, add in videoomx.cc, method AllocateCodecsOMX after "doeint=false" the line
dodeint=false;also change the line
Log::getInstance()->log("Video", Log::NOTICE, "Deinterlacing activated %d",deinterlace);to
Log::getInstance()->log("Video", Log::NOTICE, "Deinterlacing activated %d %d",deinterlace,demux->getHorizontalSize());Then try if the problem persists and post a new log for SD and HDTV.
When the ports of the deinterlacer were configured wrong, I had also a full crash of the system.
We just have to find out what is wrong in your system, probably a timing issue when configuring them.
Marten
Ok I looked closer to the logs:
Quote20:14:35.352084 [debug] 1956 PlayerLiveTV - afeed video startup
is repeated multiple times.
This seems to be an issue with the playerlive.
Please uncomment the log commands in threadMethod() and post a log file.
There is sth not working.
Marten
Hi,
ok, I will send you the new logs today evening.
Maybe it helps you to know, that I don't use a full HD screen, but a 1280x1024 TFT via DVI.
Claus
QuoteMaybe it helps you to know, that I don't use a full HD screen, but a 1280x1024 TFT via DVI.
There were also reports from other users in this case, that there are problems.
But anyway does recording playback work? If yes, I do not believe in an influence of the tft.
Marten
I will also test the recording playback today evening (with and without deinterlacing).
Claus
Hi,
here I have the new lo files for you. I have used the newest vompclient Version for this and extend the log messages as you wish.
SD TV: http://www.minidvblinux.de/download/vompclient.log.sdtv
HD TV: http://www.minidvblinux.de/download/vompclient.log.hdtv
The HD TV log don't contain the crash it self. the last 10 seconds was not stored. But it contains the first error, that deactivate the keyboard.
Claus
PS.: recordings are working without deinterlacing, with deinterlacing it crashes too.
Hi,
here I have the logfile with enabled logging in threadMethod() in videoomx.cc
http://www.minidvblinux.de/download/vompclient.log.sdtv2
Claus
Ok I have checked the logs and the only thing I see is:
Quote22:39:09.712685 [notice] 2063 Core - Signal 23 received
22:39:09.712841 [debug] 2063 Core - SIGURG caught
22:39:09.712921 [notice] 2063 Remote - na_signal
So something with your network connection is wrong. I do not think that it is really the deinterlacers fault,
but the deinterlacer might increase the needed CPU load or the drawn current by your power supply.
Anyway, so I suspect two possible reasons:
1) Your power supply is faulty, (I use a 2.1 A power supply, since I had problems with smaller ower supplies) and this is causing network problems.
2) Maybe your TCP window size is not optimal, so please go to options advanced and play a bit around with the TCP window size. If it helps report working and non working sizes (will help choosing default options).
Marten
P.S: Are pictures displayed? If yes, how do they look like?
You said, that you are using raspbain for compiling, does it work on this OS?
Quote from: clausmuus on September 12, 2012, 09:40:10
Maybe it helps you to know, that I don't use a full HD screen, but a 1280x1024 TFT via DVI.
Hi Claus,
does your Monitor Support HDCP? Mine does not. You can change some settings in the config.txt concerning HDMI/DVI. Unfortunately i had no time yesterday to dig deeper into this.
Till
Hi Marten,
that's maybe a good idea, that the power supply is not big enough. I use a 500mA power supply, what is maybe to less. I will test today evening a bigger one.
Claus
1000mA is recommended, i currently use a 800mA (since i still haven't found the one i bought with the pi).
Hi Marten,
you are right! It was the power supply. Now I use a 1000mA one, and have no more crashes :)
Thank you!
Claus
Ok, now I have learned, always ask people with odd behaviour in vomp on raspberry pi for their power supply.
Marten