search

GoXLR-on-Linux / goxlr-utility

An unofficial GoXLR App replacement for Linux, Windows and MacOS
MIT License
670 stars 37 forks source link

[BUG] Get Driver API library from registry #89

Closed FrostyCoolSlug closed 1 year ago

FrostyCoolSlug commented 1 year ago

Currently the path to the driver is hard coded in tusbaudio.rs which prevents the utility from launching on systems which don't use the standard path names.

Check how the official app locates the driver API file and attempt to replicate, otherwise search the registry for the install path.

lm41 commented 1 year ago

Windows uses always the english pathnames. Everything else is just the look. Screenshot (120) Screenshot (121)

Maybe the problem is that the driver is not installed in the default location?

devHazz commented 1 year ago

From what I've seen so far, the path is queried from an InprocServer32 on setup (I'd imagine) so it should be fine? I don't know much more about installs out of the default path unfortunately

FrostyCoolSlug commented 1 year ago

Good shout, the queried path is HKCR\WOW6432Node\CLSID{024D0372-641F-4B7B-8140-F4DFE458C982}\InprocServer32\ when the official app starts.

Had to change that slightly because we're a 64bit app, (remove the WOW6432Node component), but the util will now check there first as of 2a8d818c then fall back to the default path if it's missing.

FrostyCoolSlug commented 1 year ago

This has been released as part of 0.12.3 in commits 1add5d8, 2a8d818 and 6a8f116