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 and client hangs after starting a recording

Started by hondansx, February 14, 2013, 18:50:57

Previous topic - Next topic

hondansx

Hi Marten,

sorry for that, but another error.
If I start a recording, then the client will hang and shows me only a black screen. Have to kill it manually.
Seems it could be any kind of loop.


Black_Screen1.log:19:33:01.881635 [notice] 3221 Recording - findnext:comparing Frame 12 with current Frame 4789
Black_Screen1.log:19:33:01.881725 [notice] 3221 Recording - findnext:comparing Frame 4788 with current Frame 4789
Black_Screen1.log:19:33:02.087770 [notice] 3221 Recording - findnext:comparing Frame 12 with current Frame 4789
Black_Screen1.log:19:33:02.088191 [notice] 3221 Recording - findnext:comparing Frame 4788 with current Frame 4789
Black_Screen1.log:19:33:02.302089 [notice] 3221 Recording - findnext:comparing Frame 12 with current Frame 4789
Black_Screen1.log:19:33:02.302181 [notice] 3221 Recording - findnext:comparing Frame 4788 with current Frame 4789
Black_Screen1.log:19:33:02.510078 [notice] 3221 Recording - findnext:comparing Frame 12 with current Frame 4789
Black_Screen1.log:19:33:02.510171 [notice] 3221 Recording - findnext:comparing Frame 4788 with current Frame 4789
Black_Screen1.log:19:33:02.717423 [notice] 3221 Recording - findnext:comparing Frame 12 with current Frame 4789
Black_Screen1.log:19:33:02.717551 [notice] 3221 Recording - findnext:comparing Frame 4788 with current Frame 4789
Black_Screen1.log:19:33:02.923066 [notice] 3221 Recording - findnext:comparing Frame 12 with current Frame 4789
Black_Screen1.log:19:33:02.923162 [notice] 3221 Recording - findnext:comparing Frame 4788 with current Frame 4789


The full log is attached.

Walter

GA-EP43 | headless | 1xCineS2 Dual | 1xSkystar 2.6D | VDR 1.7.37 
Frontend: 1xRasperry | 1xION3

MartenR

19:32:56.519984 [debug]  3221 VVideoRec - JP 0:00:00 / 0:04:33
This is obviously a patched vomp with jumpplay patch.
I suspect, that it is not adapted to the latest changes in vomp, since the loop occurs right after the jump.
Please test it with a plain vanilla vomp, if the problem also occurs there I will look into it.
If not ask the author of the patch for trouble shooting.

Marten