SPARK ASIO HORRIBLE
The ASIO drivers are terrible. Its impossible to reduce the latency beyond 128.If you do reduce it you will get no output sound. Its pointless having latency as low as 16 if one cant use it.
Even on an i7 3.6 quad core,24 Gb ram and an SSD drive there are still pops and clicks.
Its pointless recording when the guitar sounds are completely out of phase and sounds like a chorus pedal that's constantly on,and yes we want to monitor sounds through the Spark amp to have our sounds in real time.Its pointless having to turn down the music volume level.
Positive grid should address these issues and provide robust ASIO drivers for recording.
@tennisadam1 I sometimes wonder if it isnt the interface its self. I can get real low latency with the driver but get random pops and clicks. Different from cpu overload and too low latency clicks. I used asio4all also and have the same results.
@nwfungi Its definitely the Spark. I come top wonder why they even bother with developing an ASIO driver.
nux7osx last edited by
@tennisadam1 I thought I heard a long time ago, roughly when the amp was out that you could use a open source ASIO driver?
I'm going to see if there's a way, as honestly I think this has some bad potential issues. I am having random disconnects with the amp. I do plan to try out a USB 3.0 cable to see if that helps. It shouldn't, but considering my PC is pretty highly spec'd and all, worth a shot to try the cheap weak link being the generic cable.
I have a premium USB cable attached and still doesn't make any difference.
nux7osx last edited by
@tennisadam1 Have you tried ASIO4All driver? I saw a post in a old thread here that says using that driver helped. There was some lag but not much supposedly:
Look at about the 6th reply and a few replies... might try that in a while.
@nux7osx Can get real low latency with asio4all and better routing and options with it, but the sparks usb port still want to be a bit wonky at times.
@nwfungi This defeats the purpose of using the positive grid ASIO drivers. I don't see ASIO4ALL as the solution. We bought the spark 40 and we deserve robust drivers from a reputable company called positive grid.
Were we conned into thinking that we could record with this?
@tennisadam1 Are you looking for solutions or just here to complain?
@nwfungi It is important for Positive grid to know about their poor ASIO drivers.
We are here to give feedback for Positive Grid to solve the ASIO issue,the same way you are here to notify them about your wonky Spark USB port.
These are ways for them to find solutions since they developed the ASIO driver.
Many will be in agreement regarding the wonky ASIO drivers as they themselves are experiencing the same issues.
How else do you expect positive grid to fix these issues?
Do you expect us not to speak up?
dhbailey last edited by
@tennisadam1 True enough, but PG has been notified by many people on this forum for YEARS that their asio drivers are horrible and people have problems recording with the asio driver they provide. There is no way that PG could NOT know about how bad their asio driver is. Yet they do nothing. Proving they just don't care. since asio4all works much better, there is no reason not to use it. Your comments indicate that you think PG actually monitors the messages on this forum -- that is highly in doubt since there are rarely responses by PG representatives. If PG were actually working to improve the asio driver and if they were actually monitoring the posts on this forum then a representative would have responded by now with a comment like "We realize the problems with our asio driver and are working to improve it and expect to have a new version released soon." But in the more than a year that I've been on this forum, there has NEVER been such a statement. So we have a choice -- either use asio4all and get some decent recording over USB accomplished or keep beating our heads against the wall and keep trying to use the less capable and downright horrible PG asio driver.
Although PG wont read this.......................
I have noticed that the ASIO driver is concentrated on 1 CPU core that totally overloads and spikes at 128 ms buffer setting. Instead of the Driver being evenly spread out on the number of cpu cores PG ASIO has it set to one cpu core.
THIS SHOULD BE ADRESSED