Hi All,
When I play a recording and pause it, then i see the screen is standing still. Then I press escape to exit vdr-sxfe. Then I start vdr-sxfe again. Now i see the "no signal" screen. I expected to see the screen standing still at the position I paused it.
I use the following versions: $ pacman -Qm consolekit 0.4.6-4 cxxtools 2.1-1 oscam 1.10-5 sendemail 1.56-4 tntnet 2.1-2 ttf-vdrsymbols 20100612-1 vdr 1.7.31-1 vdr-addon-acpiwakeup 0.0.10-1 vdr-plugin-epgsearch-git 20120311-1 vdr-plugin-live-git 0.2.0.git-16 vdr-plugin-sc-hg 574-3 vdr-plugin-signal 0.0.1-4 vdr-plugin-xineliboutput-git 20120911-1 xine-lib-1.2 20120804-1
I see the following messages in the console:
$ vdr-sxfe tv vdr-sxfe 1.0.90-cvs (build with xine-lib 1.1.90, using xine-lib 1.1.90) VDR Server: tv WARNING: MRL does not start with 'xvdr:' (tv) <snip> [4470] [input_vdr] Connecting (data) to pipe:///var/lib/vdr/plugins/xineliboutput/fifo/pipes.476/pipe.0 [4470] [input_vdr] Pipe not found [4470] [input_vdr] Data stream connection failed (PIPE) [4470] [input_vdr] Connecting (data) to udp://tv ... [4470] [input_vdr] Server does not support UDP ? (UDP: UDP transport disabled in configuration.) [4470] [input_vdr] Data stream connection failed (UDP) [4470] [input_vdr] Connecting (data) to tcp://tv:37890 ... [4470] [input_vdr] Data stream connected (TCP) [4470] [input_vdr] WARNING: xine-engine setting "engine.buffers.audio_num_buffers":230 istoo low for HD-playback! Please use values between 500-1000! [4470] [input_vdr] using custom "no signal" image /usr/share/libxine-xvdr/nosignal.mpg
Press Esc to exit
vdpau_set_property: property=8, value=100 <snip> vo_vdpau: background_color = 0 [4482] [input_vdr] scr_tuning_set_paused: assertion failed: this->is_paused is true ! [4482] [demux_vdr] PMT changed, resetting demuxer [4482] [input_vdr] vdr_adjust_realtime_speed: assertion failed: this->is_paused is true ! <snip> [4482] [input_vdr] vdr_adjust_realtime_speed: assertion failed: this->is_paused is true !
Best regards, Cedric
On 09/12/2012 05:19, cedric.dewijs@telfort.nl wrote:
Hi All,
When I play a recording and pause it, then i see the screen is standing still. Then I press escape to exit vdr-sxfe. Then I start vdr-sxfe again. Now i see the "no signal" screen. I expected to see the screen standing still at the position I paused it.
I think it's the normal behavior. When xineliboutput is started, it doesn't have any data and if vdr doesn't send any because the stream is paused, xineliboutput has nothing else to display than the no signal screen.
Marc.
On 09/12/2012 05:19, cedric.dewijs@telfort.nl wrote:
Hi All,
When I play a recording and pause it, then i see the screen is standing
still.
Then I press escape to exit vdr-sxfe. Then I start vdr-sxfe again. Now
i
see the "no signal" screen. I expected to see the screen standing still
at
the position I paused it.
I think it's the normal behavior. When xineliboutput is started, it doesn't have any data and if vdr doesn't send any because the stream is
paused, xineliboutput has nothing else to display than the no signal screen.
Marc.
I agree this behavior is normal and technically correct. I think its a bit confusing, because when I see no signal, i think there's something wrong with the receiving hardware, like crashed DVB-t receivers, loose antenna and so on.
Xineliboutput is aware the stream is paused. Therefore I can think of 2 solutions: 1)Display a screen that says "Paused" instead of "No signal" 2)Unpause, and then re-pause the stream, just long enough to let VDR send an image.
Best regards, Cedric
Am 09.12.2012 10:14, schrieb cedric.dewijs@telfort.nl:
I agree this behavior is normal and technically correct. I think its a bit confusing, because when I see no signal, i think there's something wrong with the receiving hardware, like crashed DVB-t receivers, loose antenna and so on.
Xineliboutput is aware the stream is paused. Therefore I can think of 2 solutions: 1)Display a screen that says "Paused" instead of "No signal"
And how shall xineliboutput notice the difference?
2)Unpause, and then re-pause the stream, just long enough to let VDR send an image.
Xineliboutput didn't pause the stream, so it is not the job of xineliboutput to "unpause" the stream.
Gerald
!DSPAM:50c46e6f187481547110970!
Am 09.12.2012 10:14, schrieb cedric.dewijs@telfort.nl:
I agree this behavior is normal and technically correct. I think its a
bit
confusing, because when I see no signal, i think there's something wrong with the receiving hardware, like crashed DVB-t receivers, loose antenna and so on.
Xineliboutput is aware the stream is paused. Therefore I can think of
2
solutions:
1)Display a screen that says "Paused" instead of "No signal"
And how shall xineliboutput notice the difference?
2)Unpause, and then re-pause the stream, just long enough to let VDR send an image.
Xineliboutput didn't pause the stream, so it is not the job of xineliboutput to "unpause" the stream.
Gerald
My appologies, instead of xineliboutput I meant vdr-sxfe. i should have re-read my e-mail before I hit the send button. 1) vdr-sxfe does know the difference between paused and no signal, in the console I see a lot of messages like this: [4499] [input_vdr] vdr_adjust_realtime_speed: assertion failed: this->is_paused is true !
2) In my example the pause command is given by vdr-sxfe, but I agree it could have come from other sources (like the vdr-live plugin)
Best regards, Cedric
-
cedric.dewijs＠telfort.nl -
Gerald Dachs -
Marc