I would recommend reposting this in the main thread for @markus' driver for this device (in general that is a good practice for all community-derived apps and drivers):
Others in that thread (including me) have observed the same issue, with a possible solution indicated.
