...
OK, this has been a problem (even with the previous thread safe
patches I was using), but when I try to use streamdev in suspend
mode with Klaus' new threading patch, it appears that VDR is
creating TWO threads.
Dec 19 12:33:07 poseidon vdr[26763]: switching to channel 10300
Dec 19 12:33:07 poseidon vdr[30554]: transfer thread started
(pid=30554, tid=1900553)
Dec 19 12:33:07 poseidon vdr[30555]: transfer thread started
(pid=30555, tid=1916938)
Dec 19 12:33:07 poseidon vdr[30556]: receiver on device 1 thread
started (pid=30556, tid=1933323)
Dec 19 12:33:07 poseidon vdr[30557]: TS buffer on device 1 thread
started (pid=30557, tid=1949708)
Dec 19 12:33:10 poseidon vdr[26779]: ERROR: thread 1933323 won't end
(waited 3 seconds) - canceling it...
Dec 19 12:33:10 poseidon vdr[30555]: transfer thread ended
(pid=30555, tid=1916938)
Dec 19 12:33:10 poseidon vdr[26779]: buffer stats: 0 (0%) used
That's odd. Does streamdev mess around with "Transfer Mode"?
I probably am not the right person to answer that question, but I know
that if you manually tune vdr to a channel and then try to stream, it
works fine. But, if I am on a different channel and use the suspend
option to tell vdr to switch to the channel that I want it to stream,
then there seems to be some kind of race condition that is causing two
threads to be created. I wish I could offer you more details.