Sundtek Support Forum

Are those tuners connected to an external USB Hub?

so, the /etc/sundtek.conf contains only line, which is loglevel=max
I restarted the container, I hope that this forces the sundtek driver to read the conf file and log the debug level of events in the mediasrv.log.

you said the mediasrv.log should be under /var/log/syslog, but it's in /var/log and it contains only this, events from 4 days ago.

2024-11-07 11:59:00 [195] Starting up Multimedia Framework (Aug 22 2024 14:52:09)
2024-11-07 11:59:00 [195] Detected DVB version.h
2024-11-07 11:59:00 [196] Starting service processor (PID 196)
2024-11-07 11:59:00 [195] API Version: 5.11
2024-11-07 11:59:00 [195] Running on Linux (4.9.277-82)
2024-11-07 11:59:00 [195] scanning devices
2024-11-07 11:59:00 [195] scanning for drivers
2024-11-07 11:59:00 [195] scanning for plugins
2024-11-07 11:59:00 [195] Starting up device manager
2024-11-07 11:59:00 [195] Setting permission of /dev/dvb to 777
2024-11-07 11:59:00 [195] This is to avoid problems if TV Applications are started as another user
2024-11-07 11:59:00 [195] as seen on eg. Synology NAS Systems where tvheadend is unable to read
2024-11-07 11:59:00 [195] /dev/dvb and because of that would not detect the TV tuner
2024-11-07 11:59:00 [195] scanning devices done
2024-11-07 11:59:00 [195] attached devices:
2024-11-07 11:59:00 [195] registering ID: 0
2024-11-07 11:59:00 [195] Memory mapped transfers are not available
2024-11-07 11:59:00 [195] Using dynamic configuration
2024-11-07 11:59:00 [195] DTV1 Transfer is set to: Bulk
2024-11-07 11:59:01 [196] Autostarting scripts in /etc/sundtek/
2024-11-07 11:59:02 [196] executed all available items
2024-11-07 11:59:02 [196] trying to load uinput module
2024-11-07 11:59:02 [196] loading uinput kernel extention failed, remote control will not work with lirc
2024-11-07 11:59:02 [195] No remote control support available
2024-11-07 11:59:02 [195] Initializing SYSV-IPC
2024-11-07 11:59:02 [195] Allocation using pg for type 65678
2024-11-07 11:59:02 [195] Allocated Shared memory buffer: 0x7f8f813000
2024-11-07 11:59:02 [195]
2024-11-07 11:59:02 [195] This device is using the new voltage control mechanism
2024-11-07 11:59:02 [195] Hardcoded limit 500mA
2024-11-07 11:59:02 [195] Vertical Polarisation is set to 13.00 Volt
2024-11-07 11:59:02 [195] Horizontal Polarisation is set to 19.80 Volt
2024-11-07 11:59:02 [195] Current limit is set to 1000 mA
2024-11-07 11:59:02 [195]
2024-11-07 11:59:02 [195] demodulator successfully attached (DVB_S/S2)!
2024-11-07 11:59:02 [195] Allocated Shared memory buffer: 0x7f8f7ad000
2024-11-07 11:59:02 [195] Allocated Shared memory buffer: 0x7f8f154000
2024-11-07 11:59:02 [195] Allocation using pg for type 16
2024-11-07 11:59:02 [195] Allocated Shared memory buffer: 0x7f8f06e000
2024-11-07 11:59:02 [195] Setting up default decoder settings
2024-11-07 11:59:02 [195] attaching video decoder
2024-11-07 11:59:03 [195] Configure urbs for bulk
2024-11-07 11:59:03 [195] Registering OSS emulation
2024-11-07 11:59:03 [195] registering: adapter0/0
2024-11-07 11:59:03 [195] registered virtual: /dev/dvb/adapter0/frontend0
2024-11-07 11:59:03 [195] registered virtual: /dev/dvb/adapter0/demux0
2024-11-07 11:59:03 [195] registered virtual: /dev/dvb/adapter0/dvr0
2024-11-07 11:59:03 [195] registered virtual: /dev/dsp0
2024-11-07 11:59:03 [195] registered virtual: /dev/video0
2024-11-07 11:59:03 [195] registered virtual: /dev/vbi0
2024-11-07 11:59:03 [195] Initializing Remote Control Support



on the other hand, this is what dmesg on the host (not inside container) says, and it's much more verbose this time.

[1553838.984414] docker0: port 5(veth530535f) entered disabled state
[1573794.834967] meson6-dwmac ff3f0000.ethernet eth0: Link is Down
[1573797.906832] meson6-dwmac ff3f0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[1590976.267703] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 2 ret -71
[1590976.267976] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.268160] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.268291] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 2 ret -71
[1590976.268776] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.268940] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.269019] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.269161] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.269290] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.269421] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.269495] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.270440] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.270553] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.270776] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.270919] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.271360] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.271493] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.271776] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.271891] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.272077] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.272153] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.272310] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.272395] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.272572] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.279730] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.279976] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.280108] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.280293] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.280374] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.280568] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.280672] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.280862] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.280946] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.281158] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.328307] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.328625] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.328763] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.328930] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.329014] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.329152] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.329279] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.329414] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.329488] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.330186] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.379983] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.380267] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.380396] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.380563] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.380698] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.380833] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.380960] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.381095] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.381172] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 187 len 1 ret -71
[1590976.381350] usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 187 len 1 ret -71
[1590976.391340] usb 1-2.4: USB disconnect, device number 12
[1590976.669541] usb 1-2.4: new high-speed USB device number 13 using xhci-hcd
[1590982.005279] usb 1-2.4: device descriptor read/64, error -71
[1590983.997597] usb 1-2-port4: Cannot enable. Maybe the USB cable is bad?
[1590984.101107] usb 1-2.4: new high-speed USB device number 14 using xhci-hcd
[1590984.901077] usb 1-2.4: device descriptor read/64, error -71
[1590985.865019] usb 1-2.4: device descriptor read/64, error -71
[1590985.973621] usb 1-2-port4: attempt power cycle
[1590987.261280] usb 1-2-port4: Cannot enable. Maybe the USB cable is bad?
[1590987.828853] usb 1-2.4: new high-speed USB device number 16 using xhci-hcd
[1590987.828903] usb 1-2.4: Device not responding to setup address.
[1590988.036993] usb 1-2.4: Device not responding to setup address.
[1590988.244808] usb 1-2.4: device not accepting address 16, error -71
[1590988.245781] usb 1-2.4: the parent's name is 1-2
[1590988.245851] usb 1-2-port4: Device no response
[1590988.251507] usb 1-2-port4: unable to enumerate USB device
[1590989.373206] usb 1-2-port4: Cannot enable. Maybe the USB cable is bad?
[1590989.476752] usb 1-2.4: new high-speed USB device number 18 using xhci-hcd
[1590991.708653] usb 1-2.4: device descriptor read/64, error -71
[1590994.544441] usb 1-2.4: device descriptor read/64, error -71
[1590994.652669] usb 1-2-port4: attempt power cycle
[1590995.304421] usb 1-2.4: new high-speed USB device number 19 using xhci-hcd
[1590999.458932] usb 1-2.4: device descriptor read/8, error -71
[1590999.585354] usb 1-2.4: device descriptor read/8, error -71
[1591000.028140] usb 1-2.4: new high-speed USB device number 20 using xhci-hcd
[1591005.163850] usb 1-2.4: device descriptor read/8, error -110
[1591005.345653] usb 1-2.4: device descriptor read/8, error -71
[1591005.451983] usb 1-2.4: the parent's name is 1-2
[1591005.452052] usb 1-2-port4: Device no response
[1591005.452103] usb 1-2-port4: unable to enumerate USB device
[1591005.703772] usb 1-2.4: new high-speed USB device number 21 using xhci-hcd
[1591010.899452] usb 1-2.4: device descriptor read/64, error -110
[1591010.899818] usb 1-2.4: Device no response
[1591017.967046] usb 1-2.4: device descriptor read/64, error -71
[1591018.178972] usb 1-2.4: new high-speed USB device number 22 using xhci-hcd
[1591023.442692] usb 1-2.4: device descriptor read/64, error -110
[1591023.443074] usb 1-2.4: Device no response
[1591039.057717] usb 1-2.4: device descriptor read/64, error -110
[1591039.058100] usb 1-2.4: Device no response
[1591039.169904] usb 1-2-port4: attempt power cycle
[1591039.821672] usb 1-2.4: new high-speed USB device number 23 using xhci-hcd
[1591045.097354] usb 1-2.4: device descriptor read/8, error -110
[1591050.473056] usb 1-2.4: device descriptor read/8, error -110
[1591050.684975] usb 1-2.4: new high-speed USB device number 24 using xhci-hcd
[1591055.848729] usb 1-2.4: device descriptor read/8, error -110
[1591061.224396] usb 1-2.4: device descriptor read/8, error -110
[1591061.332886] usb 1-2.4: the parent's name is 1-2
[1591061.332959] usb 1-2-port4: Device no response
[1591061.333009] usb 1-2-port4: unable to enumerate USB device

I have 2 tuners (skytv and dual, I was waiting for quad tuner which never was released), connected via USB hub, I'll remove the older skytv dongle and USB hub and will connect it directly to my home linux NAS which has sadly only one USB port (...) and will observe if that's not the USB hub causing this.

Hallo zusammen,

ich versuche mit dem MediaTV Pro III und ffmpeg/DirectShow Videokassetten unter Windows 11 zu digitalisieren.

ffmpeg -list_devices true -f dshow -i dummy
Zeigt alles an was ich brauche:
[dshow @ 000002a56de17380] "Sundtek Video Capture" (audio, video)
[dshow @ 000002a56de17380]   Alternative name "@device_pnp_\\?\usb#vid_2659&pid_1210&mi_01#6&7df4f7a&1&0001#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{9b365890-165f-11d0-a195-0020afd156e4}"
Und dazu ffplay -f dshow -list_options true -i video="Sundtek Video Capture"
zeigt

[dshow @ 000001da302d6580] DirectShow video device options (from video devices)
[dshow @ 000001da302d6580]  Pin "Capture" (alternative pin name "2")
[dshow @ 000001da302d6580]   pixel_format=uyvy422  min s=88x72 fps=25 max s=720x576 fps=25
[dshow @ 000001da302d6580]   pixel_format=uyvy422  min s=80x60 fps=29.97 max s=720x480 fps=29.97
[dshow @ 000001da302d6580]   pixel_format=uyvy422  min s=88x72 fps=25 max s=720x576 fps=25
[dshow @ 000001da302d6580]   pixel_format=gray  min s=88x72 fps=25 max s=720x576 fps=25
[dshow @ 000001da302d6580]   pixel_format=uyvy422  min s=80x60 fps=29.97 max s=360x240 fps=29.97
[dshow @ 000001da302d6580]   pixel_format=gray  min s=80x60 fps=29.97 max s=360x240 fps=29.97
[dshow @ 000001da302d6580]   pixel_format=uyvy422  min s=88x72 fps=25 max s=360x288 fps=25
[dshow @ 000001da302d6580]   pixel_format=gray  min s=88x72 fps=25 max s=360x288 fps=25
[dshow @ 000001da302d6580]  Pin "Audio Out" (alternative pin name "3")
[dshow @ 000001da302d6580] Crossbar Switching Information for Sundtek Video Capture:
[dshow @ 000001da302d6580]   Crossbar Output pin 0: "Video Decoder" related output pin: 1 current input pin: 1 compatible input pins: 0 1 2 5
[dshow @ 000001da302d6580]   Crossbar Output pin 1: "Audio Decoder" related output pin: 0 current input pin: 4 compatible input pins: 3 4
[dshow @ 000001da302d6580]   Crossbar Input pin 0 - "Video Tuner" related input pin: 3
[dshow @ 000001da302d6580]   Crossbar Input pin 1 - "Video Composite" related input pin: 4
[dshow @ 000001da302d6580]   Crossbar Input pin 2 - "S-Video" related input pin: 4
[dshow @ 000001da302d6580]   Crossbar Input pin 3 - "Audio Tuner" related input pin: 0
[dshow @ 000001da302d6580]   Crossbar Input pin 4 - "Audio Line" related input pin: 1
[dshow @ 000001da302d6580]   Crossbar Input pin 5 - "Video YRYBY" related input pin: 4
Bild bekomm ich damit auch wunderbar, allerdings habe ich auf der Tonspur nur elektronisches Geraschel und Gepiepse.
Habe mal eine Beispieldatei angehängt (ja, die hat kein Bildinhalt weil ich keine Quelle angeschlossen hatte, das ist so richtig).

Hat jemand eine Idee, ich komme da mit ffmpeg nicht weiter. Leider hat der Laptop mit dem ich aufnehme auch keinen Line-In sonst würde ich das einfach dort einstecken.

Verwende den Treiber 2016-07-13 für die MTV Pro 3.

/etc/sundtek.conf
loglevel=max

that will show what the driver is doing.

The log is stored in /var/log/mediasrv.log

also try ir_disabled=1 in /etc/sundtek.conf it's using interrupt transfers, which is a little bit different from the rest.

I suspect part of the problem are power outages. it happens at my place, there are split of the second outages. but I'll enable debug logging as you suggested. I think already second time, but I'm idiot, so I have to open 3 different threads for one issue.