Mailing List archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[vdr] Re: [PATCH] streamdev for vdr 1.3.14-17 patch 0.3



> Anssi Hannula wrote:

(a patch) 

I tried Anssi's latest patch, but unfortunately, streamdev still doesn't
work properly with osdpip-0.0.7. As I wrote earlier, my VDR has only one
PCI slot, hence only one FF card. osdpip requires a second receiver to be
able to display all channels (and not only those which happen to be on the
same transponder as the original channel). So streamdev should be the
solution. 

But osdpip does not display the PiP when streamdev is active. It does work
in the background, as can be demonstrated when pressing "0" -- it goes back
to the original channel immediately, just the PiP is not displayed. 

Here's the excerpt from the log (just the relevant parts, not the whole
Autopid blurb):


Dec  2 08:34:27 linvdr vdr[2064]: Streamdev: Connected to server 192.168.20.1:2004 using capabilities TS
...
Dec  2 08:35:04 linvdr vdr[2088]: osdpip: receiver thread started (pid=2088)
Dec  2 08:35:04 linvdr vdr[2089]: receiver on device 5 thread started (pid=2089, tid=294925)
Dec  2 08:35:04 linvdr vdr[2090]: Streamdev: UDP-TS Assembler thread started (pid=2090, tid=311310)
Dec  2 08:35:04 linvdr vdr[2091]: TS buffer on device 5 thread started (pid=2091, tid=327695)
Dec  2 08:35:04 linvdr vdr[2092]: osdpip: decoder thread started (pid = 2092)
Dec  2 08:35:18 linvdr vdr[2064]: switching to channel 2
Dec  2 08:35:18 linvdr vdr[2084]: TS buffer on device 1 thread ended (pid=2084, tid=245770)
Dec  2 08:35:18 linvdr vdr[2083]: buffer stats: 7708 (0%) used
Dec  2 08:35:18 linvdr vdr[2083]: receiver on device 1 thread ended (pid=2083, tid=229385)
Dec  2 08:35:18 linvdr vdr[2064]: buffer stats: 0 (0%) used
...
Dec  2 08:35:21 linvdr vdr[2064]: switching to channel 3
...
Dec  2 08:35:21 linvdr vdr[2094]: TS buffer on device 1 thread ended (pid=2094, tid=376842)
Dec  2 08:35:21 linvdr vdr[2093]: buffer stats: 3948 (0%) used
Dec  2 08:35:21 linvdr vdr[2093]: receiver on device 1 thread ended (pid=2093, tid=360457)
Dec  2 08:35:21 linvdr vdr[2064]: buffer stats: 0 (0%) used
...
Dec  2 08:35:21 linvdr vdr[2096]: receiver on device 1 thread started (pid=2096, tid=409609)
Dec  2 08:35:21 linvdr vdr[2097]: TS buffer on device 1 thread started (pid=2097, tid=425994)
Dec  2 08:35:26 linvdr vdr[2064]: switching to channel 1
Dec  2 08:35:26 linvdr vdr[2097]: TS buffer on device 1 thread ended (pid=2097, tid=425994)
Dec  2 08:35:26 linvdr vdr[2096]: buffer stats: 3760 (0%) used
Dec  2 08:35:26 linvdr vdr[2096]: receiver on device 1 thread ended (pid=2096, tid=409609)
Dec  2 08:35:26 linvdr vdr[2064]: buffer stats: 0 (0%) used
Dec  2 08:35:26 linvdr vdr[2099]: receiver on device 1 thread started (pid=2099, tid=458761)
Dec  2 08:35:26 linvdr vdr[2100]: TS buffer on device 1 thread started (pid=2100, tid=475146)
Dec  2 08:35:26 linvdr vdr[2092]: osdpip: decoder thread stopped
Dec  2 08:35:26 linvdr vdr[2088]: osdpip: receiver thread ended (pid=2088)
Dec  2 08:35:29 linvdr vdr[2064]: ERROR: thread 294925 won't end (waited 3 seconds) - cancelling it...
Dec  2 08:35:29 linvdr vdr[2064]: buffer stats: 0 (0%) used
Dec  2 08:35:29 linvdr vdr[2064]: buffer stats: 0 (0%) used


Any idea what happens here? 

-- 
Fifty flippant frogs
Walked by on flippered feet
And with their slime they made the time
Unnaturally fleet.




Home | Main Index | Thread Index