Sundtek Support Forum

Was fuer Plugins werden denn eingesetzt?

/opt/bin/mediaclient --lc sollte auch anzeigen welche Applikationen worauf zugreifen, eventuell blockiert ein Programm den Treiber?

Hi,

Zitat von: Sundtek am April 08, 2010, 10:28:45 Vormittag

we will add it to the next driver release which we will provide around mid next week (14th April).

Great! My system is not exactly stable, which is possibly why I haven't yet seen the stick turn off after 15s ... quite possible that some of my software does not close right and keeps on claiming the device. So having a command to explicitly turn it off, will save hours of troubleshooting of what could be wrong with my system

you can check with

/opt/bin/mediaclient --lc

which client is accessing the device.
 
In order to force the disconnection you can run:

/opt/bin/mediaclient --dc [pid]

Ok, I assume (but am not sure) that crudely the process goes:
* stick receives a frame of a given resolution
* stick packs the frame, sends it via USB
* PC/driver receives USB packet, retrieves data, unpacks frame
* PC then decodes frame

Only in case of analog TV the stick can do this. For digital TV MPEG2/4 is directly broadcasted over the air or through the cable, the stick converts this signal into a USB conform signal and the driver translates this USB Signal into a system usable format. We do not have access to the stream on videoframe level for DVB.

some applications use to check the API version that's the problem, even though it's nonsense.

your Distribution is not correctly installed (or at least there's a bug with the dvb headers).

you can try to lower the API Version with following command:

/opt/bin/mediaclient --setver=5.0

and retry with w_scan, w_scan was packaged for the DVB API version 5.0, but our driver by default provides API support for the DVB API 5.1, it tries to detect lower versions which works with correct systems, for incorrect systems it can be set manually

what distribution do you use?

In case of tvheadend you can also ask in the tvheadend IRC channel on freenode.net where tvheadend developers and users give support to other tvheadend users we are watching it and try to help out too.

Fuer CI+ gibt es derzeit noch keine Loesung, bei den CI Modulen wird auf eine SmartDTV Loesung gesetzt.
Mehr Informationen bezueglich den CI Geraeten wird es in den naechsten Wochen geben.
Die CI Loesung wird selbstverstaendlich von allen unseren Sticks unterstuetzt werden. Die letzten Treiberupdates hatten die Entwicklung leider wieder etwas verzoegert.

Version: http://www.sundtek.de/media/sundtek_installer_100402.sh

Features:
* added configuration option for automatically starting an application after a device got attached 1)
* another rework of audio processing, this version now isolates audio to not be able to affect the driver when a problem occures. Older Pulseaudio versions are known to cause problems - when problems are detected the driver will automatically restart the audio output for analog TV and FM radio.
* the logfile now also contains the process id
* 4 DVB-C devices have been tested at the same time with this version
* also tested 1 analog TV and 1 DVB-C device at the same
* added workaround for kaffeine 1.0 pre3 bug (which comes with Ubuntu 10.04, kaffeine tries to read DVB data before setting up a transponder).

Bugfix:
* mplayer dvb://[channel] wasn't able to use the signal lock which was returned by the driver.

1)
The configurationfile /etc/sundtek.conf can contain 2 parameters, device_attach and device_detach.
Those parameters can be used to start or reinitialize applications after the driver initialized a device.

Example:
/etc/sundtek.conf
device_attach=/usr/bin/usb_deviceattach.sh DEVID
device_detach=/usr/bin/usb_devicedetach.sh DEVID

DEVID will automatically be replaced with the device ID which is also returned by /opt/bin/mediaclient -e

Die aktuelle Treiberversion stellt mittlerweile 2 Konfigurationsoptionen zum Initialisieren von VDR bereit

z.B.:
/etc/sundtek.conf
device_attach=/usr/bin/usb_attachscript.sh DEVID
device_detach=/usr/bin/usb_detachscript.sh DEVID

Als speziellen Parameter kann DEVID angegeben werden, dieser wird dann durch die deviceID welche wie bei /opt/bin/mediaclient -e angezeigt wird ersetzt werden.

Haben Sie diesen Treiber versucht:
http://www.sundtek.de/support/BDA_WHQL_Standard_Installshield.zip (24.12.09)

Wir hatten das Problem mit der Signatur mit dem alten Treiber.