KVR Audio

dwozzle · Post by **dwozzle** » Sun Dec 25, 2016 4:07 am

I haven't used Amplitube for months, only a few times since I got a Helix. Today when I launched it after installing the newest version of Amplitube 4.1.0 to try out Fender Collection 2, basic audio isn't working.

First off, all my settings in the Audio MIDI Setup dialog are gone. Second, when I choose ASIO from the Technology dropdown, I get an alert, "Could not initialize Audio Device. Change audio driver or check your advanced Audio Settings in Control Panel, make sure input/output same rate match same value for selected device."

I'm using the same Focusrite 2i2 I've always used with Amplitube in the living room, and which I still use for headphones there, and which is working fined for playing audio, videos, etc.. Native Instruments FM8 standalone also sees the 2i2 via ASIO, and works fine with it.

In other words, Windows and another VST can use it, but Amplitube can't. Seems to be an Amplitube problem. This is Win 7 Pro 64 bit. I've filed a support ticket.

Anyone else seen this, or have any ideas?

Teksonik · Post by **Teksonik** » Sun Dec 25, 2016 5:17 am

Are you sure there is not another app that has control of the ASIO Driver ? Anything else open, another standalone, DAW etc ?

dwozzle · Post by **dwozzle** » Sun Dec 25, 2016 6:01 am

Thanks for jumping in.

I tried disabling Exclusive access for both input and output, no change.

Also, as I said, FM8 can see and use it, as can Windows itself, at the same time that Amplitube can't. It's weird.

spacekid · Post by **spacekid** » Sun Dec 25, 2016 11:22 am

Just to be sure: You have done a system restart? It will clear up any conflicts you may not be seeing. I've been doing fresh installs lately on a new machine, and am getting these conflicts when testing my plugins for the first time while doing other installs. They usually clear up on their own, or I restart to do it..then the normal registry cleanup and they are fine. The only thing that will do that, as mentioned, is that another program is currently using your audio resource in question - so the restart is the best first fix if you can't find what app is doing it. After further reading: Are your native Instruments releasing the driver correctly then?

dwozzle · Post by **dwozzle** » Sun Dec 25, 2016 3:14 pm

Haven't restarted since the Amplitube 4.1.0 install, I can try that, thanks for the suggestion.

Re FM8, problem happened before opening FM8 at all, just tried it to test whether other things could use the 2i2. At that point, both Windows and FM8 could see and use it, but not AT.

spacekid · Post by **spacekid** » Sun Dec 25, 2016 4:55 pm

^It will also happen if you accidentally over-click and open 2 instances of a standalone. If you wait around long enough, the working copy will open. This happens to me a little bit.

dwozzle · Post by **dwozzle** » Sun Dec 25, 2016 8:23 pm

Good thought, but no. I was careful launching it, and I checked Task Mgr, only one Amplitube instance. Also, FM8 and Windows can use it.

dwozzle · Post by **dwozzle** » Sun Dec 25, 2016 10:34 pm

UPDATE:
- Restarted my laptop, no change
- Tried some more VSTIs, all of them could see and use the 2i2
- SEM V, FM8, and impOSCar2 could use it at the same time

Really does seem to be a problem with Amplitube.

dwozzle · Post by **dwozzle** » Sun Dec 25, 2016 11:36 pm

Tried every other amp sim I have, they all work fine with ASIO and the 2i2.

That's S-Gear 2 (which is still awesome BTW), Studio Devil BVC, GTR 3.5, Guitar Rig 5, and ReValver Mk IIIdotV Standalone, no problem with any of them.

AmpliTube OTOH can only connect to Windows Audio, with the expected horrible latency.

I gather nobody else is seeing this?

spacekid · Post by **spacekid** » Sun Dec 25, 2016 11:55 pm

^I'd uninstall/reinstall at this point. You may want to use reg edit to delete any Amplitube keys just to be sure(though I can only think of a cache key that saves the last used audio, that would affect anything). Really puzzling though, good luck.

dwozzle · Post by **dwozzle** » Mon Dec 26, 2016 2:05 am

Think I'm going to wait for Support to get back to me after the holiday. At minimum, if that fixes it, they should know that some people end up in this state, not cool.

I'll play with the (by now semi-)new Helix models in the mean time (:-)

tappert · Post by **tappert** » Tue Dec 27, 2016 5:07 pm

Same problem with a TC soundcard

dwozzle · Post by **dwozzle** » Tue Dec 27, 2016 5:41 pm

Support said this:

Go to C > Users > Name > Appdata > Roaming > IK Multimedia > AmpliTube 4 > Delete the AmpliTube settings files here. Now retry it.

You must have show hidden files/folders option on in Windows to see the Appdata and beyond option.

Did that, no change. Same alert appears when I select ASIO from the Technology dropdown, so I can't select the 2i2.

dwozzle · Post by **dwozzle** » Tue Dec 27, 2016 7:33 pm

Next they suggested this:

Load Amplitube
Go to File > New session choose 44.1
Now retry choosing the ASIO again.

No change doing that, same alert appears, dropdown goes back to Windows audio. Also, if I choose File > New again after that, the Sample Rate dropdown in the Project Properties dialog is empty except for a greyed-out item saying '(no choices)'.

Next they said to download and install ASIO4ALL v2, open its control panel, and select the interfaces I want to use. This is not a fix they say, it's informational, "If asio4all works, then its something specific with the focus driver and we can look into this further."

I've never used ASIO4ALL. Any reason I'd regret installing it?

jdnz · Post by **jdnz** » Tue Dec 27, 2016 8:15 pm

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

Latest Amplitube "Could not initialize Audio Device"