Because of many problems with three different TV cards I had prevoiusly - I bought one which claims full linux support - Qbox II by TBS. After a few hours I have card working, hovewer I have a problem too. When I'm recording it seems ok, but when I'm watching through streamdev + VLC, there are errors about buffer overflow. Often it causes viewing to stop after a minute or so. I suspect there is need to set some larger buffers but I don't know where.
Aug 21 23:09:45 wuwek vdr: [5018] Streamdev: Accepted new client (HTTP) 192.168.1.10:2734 Aug 21 23:09:45 wuwek vdr: [5018] CAM 1: assigned to device 1 Aug 21 23:09:47 wuwek vdr: [5009] max. latency time 3 seconds Aug 21 23:09:51 wuwek vdr: [5030] streamdev-writer thread started (pid=5009, tid=5030) Aug 21 23:09:51 wuwek vdr: [5031] streamdev-livestreaming thread started (pid=5009, tid=5031) Aug 21 23:09:51 wuwek vdr: [5018] DVBAPI: 0.0 set CAM decrypt (SID 4807, caLm 4, HasCaDescriptors 0) Aug 21 23:09:52 wuwek vdr: [5032] receiver on device 1 thread started (pid=5009, tid=5032) Aug 21 23:09:52 wuwek vdr: [5033] TS buffer on device 1 thread started (pid=5009, tid=5033) Aug 21 23:09:52 wuwek vdr: [5018] Streamdev: Accepted new client (HTTP) 192.168.1.10:2737 Aug 21 23:09:52 wuwek vdr: [5030] ERROR: streamdev-server: couldn't send 48504 bytes: Połączenie zerwane przez drugą stronę Aug 21 23:09:52 wuwek vdr: [5030] streamdev-writer thread ended (pid=5009, tid=5030) Aug 21 23:09:53 wuwek vdr: [5018] client (HTTP) 192.168.1.10:2734 has closed connection Aug 21 23:09:53 wuwek vdr: [5018] streamdev-server: closing HTTP connection to 192.168.1.10:2734 Aug 21 23:09:53 wuwek vdr: [5031] streamdev-livestreaming thread ended (pid=5009, tid=5031) Aug 21 23:09:54 wuwek vdr: [5018] DVBAPI: 0.0 set CAM decrypt (SID 4807, caLm 5, HasCaDescriptors 0) Aug 21 23:09:54 wuwek vdr: [5018] buffer stats: 48692 (1%) used Aug 21 23:09:54 wuwek vdr: [5034] streamdev-writer thread started (pid=5009, tid=5034) Aug 21 23:09:54 wuwek vdr: [5035] streamdev-livestreaming thread started (pid=5009, tid=5035) Aug 21 23:09:54 wuwek vdr: [5033] TS buffer on device 1 thread ended (pid=5009, tid=5033) Aug 21 23:09:54 wuwek vdr: [5032] buffer stats: 50384 (1%) used Aug 21 23:09:54 wuwek vdr: [5032] receiver on device 1 thread ended (pid=5009, tid=5032) Aug 21 23:09:54 wuwek vdr: [5018] DVBAPI: 0.0 set CAM decrypt (SID 4807, caLm 4, HasCaDescriptors 0) Aug 21 23:09:54 wuwek vdr: [5036] receiver on device 1 thread started (pid=5009, tid=5036) Aug 21 23:09:54 wuwek vdr: [5037] TS buffer on device 1 thread started (pid=5009, tid=5037) Aug 21 23:09:54 wuwek vdr: [5015] Adding pid 208 (type 0xc0) RegDesc not found -> assume AC-3 Aug 21 23:09:54 wuwek vdr: [5015] Adding pid 213 (type 0xc1) RegDesc not found -> assume AC-3 Aug 21 23:09:54 wuwek vdr: [5015] Adding pid 1200 (type 0xc6) RegDesc not found -> assume AC-3 Aug 21 23:09:54 wuwek vdr: [5015] Adding pid 666 (type 0xc0) RegDesc not found -> assume AC-3 Aug 21 23:09:54 wuwek vdr: [5015] Adding pid 667 (type 0xc1) RegDesc not found -> assume AC-3 Aug 21 23:09:56 wuwek vdr: [5015] ERROR: 1 ring buffer overflow (188 bytes dropped) Aug 21 23:10:02 wuwek vdr: [5015] ERROR: 8 ring buffer overflows (1504 bytes dropped) Aug 21 23:10:09 wuwek vdr: [5015] ERROR: 10 ring buffer overflows (1880 bytes dropped) Aug 21 23:10:15 wuwek vdr: [5015] ERROR: 7 ring buffer overflows (1316 bytes dropped)
Marx
Ps. I know why I get: ERROR: streamdev: protocol violation (VTP) from 127.0.0.1:37275 It's from vdradmin-am which seems incompatible with VDR 1.7.28