KVR Audio

dwozzle · Post by **dwozzle** » Tue Dec 27, 2016 8:44 pm

@jdnz, thanks for checking, good to know it's working for someone, though I'm sure IK tested a bunch of different environments that all worked. It's not in their best interest not to test, or to release known-buggy stuff, it's just that there are a million variations of a million variables in play.

However, besides me, and @tappert above seeing something similar with his TC card, someone on the Helix group sees it too. Not positive what driver and interface they're using, might be Helix, which I haven't tried.

DeBro · Post by **DeBro** » Tue Dec 27, 2016 9:10 pm

I'm getting this same error opening Amplitude standalone on Windows 10 Home with the Focusrite 2i2. It doesn't even open to the regular amp interface. My workaround is to initialize the VST in Cantabile Lite and play on.

Zydraka · Post by **Zydraka** » Tue Dec 27, 2016 9:16 pm

Is it a 1st or 2nd gen 2i2? If it's the 2nd gen make sure to install the latest driver because one of the recent updates fixed issues where it wouldn't work with standalone applications like Amplitube.

DeBro · Post by **DeBro** » Tue Dec 27, 2016 9:31 pm

My 2i2 is first gen using the latest beta driver released on the 21st Dec 2016. All ASIO compatible applications including Sonar Artist are working superbly with this driver- no issues except with Amplitude.

dwozzle · Post by **dwozzle** » Tue Dec 27, 2016 10:37 pm

My 2i2 is also 1st gen, using Focusrite USB 2.0 Audio Driver 2.5.1. I'm not aware of a beta driver, that's what shows up on the downloads page when I select Scarlett 2i2 [1st Gen.], and it's what Programs and Features says I have installed.

DeBro · Post by **DeBro** » Wed Dec 28, 2016 1:29 am

Here's the link to the Focusrite USB2 Drivers 4.15.0
http://beta.focusrite.com/

dwozzle · Post by **dwozzle** » Wed Dec 28, 2016 2:03 pm

Hmmm, not sure I want to throw a beta driver into the mix, especially since it's not working for you.

IK Support is asking that I try ASIO4ALL as a test, more inclined to do that. I haven't had a chance yet though, have a new non-music laptop I've been setting up, big project (I'm a programmer).

No one has said anything about the wisdom and risks of installing ASIO4ALL. No comments, anyone?

dwozzle · Post by **dwozzle** » Wed Dec 28, 2016 10:31 pm

jdnz wrote:
dwozzle wrote: AmpliTube OTOH can only connect to Windows Audio, with the expected horrible latency.

I gather nobody else is seeing this?
I tested it here - standalone AT4 connects fine via asio to my KA6 on win7x64

Which exact Amplitube version are you using? It used to work for me too, has forever, but after the 4.1.0 update, it doesn't.

Also, installing ASIO4ALL did let AT see and use the 2i2. It's not a real solution, but I've passed that info along to Support as requested to help them troubleshoot, and it lets me use AT in the mean time.

jdnz · Post by **jdnz** » Wed Dec 28, 2016 11:29 pm

dwozzle wrote: Which exact Amplitube version are you using? It used to work for me too, has forever, but after the 4.1.0 update, it doesn't.

I'm using 4.1.0 as well (updated when it came out) - since 4.1.0 does work with asio4all for you (as well as the ka6 asio driver for me) it's got to be something weird with the focusrite asio driver.

Perfect excuse to buy a flash new interface

dwozzle · Post by **dwozzle** » Wed Dec 28, 2016 11:43 pm

The 2i2 is my living room casual listening and occasionally playing a bit of guitar interface. In the "studio" I have an 18i20, and also a Helix, which I haven't tried as an interface yet, but should do just fine assuming I don't need a lot of inputs, which I usually don't.

Also, several other people on various forums, including in this thread, have hit the same behavior with other interfaces and drivers.

Also also, the 2i2 has worked for me with Amplitube for a long time. It's only this latest update seems to have a problem with it, and some but not all other interfaces, or there are other variables involved.

Ron21377 · Post by **Ron21377** » Sun Feb 05, 2017 12:42 am

I have the same problem running Amplitube 4 with Cubase AL 9. When one or the other is running, the other can't initialize the audio drivers (Steinberg UR 44 audio drivers).

The only way I can get Amplitube 4 to work with my DAW is to use it as in insert effect. As a stand-alone app, it seems to interfere with other running programs (guitarpro 6 is another one).

Ugh

Ron

shidostrife · Post by **shidostrife** » Sun Feb 05, 2017 2:24 am

That happened to me the first time I install Amplitube CS. It worked fine after a few restarts (on different days), I didn't even remember what I did that made it work, it just worked. I use Scarlett 212 2nd gen.

Xlr7765 · Post by **Xlr7765** » Mon Mar 06, 2017 5:58 pm

Has anybody found a solution to this problem using focusrite ASIO drivers with AT4 4.1.0 stand-alone? I'm using Win 10 x64 but the AT3 stand-alone app works fine with same focusrite driver. So it looks like a bug in AT4.
I have a support request but I'm not holding my breath. How good is IK multimedia's support? Wish I'd never bought this now. The plugin doesn't play well with Ableton Live 9's midi CC interface which is another big annoyance.

dwozzle · Post by **dwozzle** » Mon Mar 06, 2017 6:43 pm

My support issue from Dec 24 2016 has fallen into a black hole. Support is no longer responding to me asking what's going on.

Which is apparently nothing, far as I can tell. Disappointing.

I've been concentrating on Helix for a while now, or I'd be really pissed.

dwozzle · Post by **dwozzle** » Tue Mar 07, 2017 1:26 am

Interestingly, I just got this reply to my ticket:

My name is Paul Hudson, I am the Support Manager with IK Multimedia.

Sorry to see of a lack of contact here. We certainly apologize for the delays
and oversight of your ticket.

The problem you are describing has been seen by a few other users and was
finally recreated here on one system. We recently changed the way AmpliTube
interfaces with audio drivers, for example we are now properly supporting WASAPI
and standard Windows drivers. This appears to be causing some headache for a few
users trying to use the latest version. You could resort back to AmpliTube 4.0.2
but it does not offer the ability to host the Fender Collection 2. This version
did not contain these changes and should work fine.

That said, the issue can also be as simple as the Audio Interface may be using a
different Sample Rate then your AmpliTube 4 project is set up to use. Make sure
to either create a new project in AmpliTube 4 to change your Sample Rate inside
your software or use the Control Panel -> Sound menu to change your Audio
Interface's Sample Rate.

That can often fix the troubles but if not, it seems you are being affected more
deeply. As mentioned, we did recreate this on one Windows system and a fix will
be applied in the next AmpliTube update which is set for this month. I will be
checking on this tomorrow for a more solid ETA if currently available.

If you have any questions, please feel free to reply here.

Thanks.

Paul Hudson
Service / Support Manager

So that's progress of a sort I guess, we'll have to see how it goes when the next update drops. I for one am not rolling back to an earlier release, not worth it to me.

Just to be clear, when Paul said to reply "here", he was talking to me about replying to my ticket, which isn't an option for anyone else with this problem.

I'd strongly suggest that anyone else experiencing this issue file a ticket ASAP, with as much detailed info as you can, to up the odds that their proposed fix actually applies to as many of us as possible.

Latest Amplitube "Could not initialize Audio Device"