Spark iAP Interface on Windows 10 64
-
How do I get the drivers and how do I get the drivers installed for Spark iAP Interface on Windows 10 64?
-
@info-7 said in Spark iAP Interface on Windows 10 64:
How do I get the drivers and how do I get the drivers installed for Spark iAP Interface on Windows 10 64?
Yes: windows drivers and installation info for the Spark Amp? (very good question)
I just really hope by the time I get my Spark amp delivered (late May I've been told) that a few more issues will be ironed out - like what Android/Windows O/S and or firmware versions will work, and even which devices they know definitely work.
Not all of us want to go out and buy Apple devices to be able to use an amp that has been said works on Android... which version of Android? (I know I can use it without linking it to a device, but that was really a big part of the build up and hype getting us to buy this amp.)
This is the first post I've seen asking for Windows drivers....are there actually Windows drivers?
I'm thinking no - but it would be good to have a FAQ page just for what works
- operating systems (yes and no)
- firmware versions tested (yes and no)
- hardware tested (yes and no)
That way we can point these kinds of posts to the FAQ page - or other link, so the person knows. (Is this forum just for us users?)
-
There is an official driver
https://help.positivegrid.com/hc/en-us/articles/360039598451-Spark-Windows-ASIO-Driver-
-
Hi,
I also have Windows 10 64-bit running and connected my Spark by USB.
Now - in my device manager I find an Spark-Line-Input, a Speaker Output and a Spark Audio Controller.
Never the less there is still that iAP device, and although I have the ASIO driver installed, that iAP device is a mystery to me: It still doesn't run (see the yellow triangle!) and noone has answered me the question, what this thing really is, and what it is for. I've been asking on Facebook several times …
-
I had this problem. Anyway, I ran the firmware updater. Even though it reported that there was nothing to update, I found that the missing driver issue went away after I ejected the device and reconnected it. Here's hoping it stays that way.