Remember to register Amplitube, even the free version. ASIO4All controls the speakers directly, bypassing the Windows Operating System (that's why ASIO is fast), so it doesn't matter for ASIO if the speakers are disabled on Windows, except that if they are enabled, sometimes ASIO4ALL cannot take control of the speakers. If you want ASIO4All to work propertly you most likely need to disable the speakers (right click the speaker tray icon, select Playback Devices, right click the speakers and select Disable you can always reenable the speakers again using the same process). The red X on the ASIO output usually happens because of this: most of the PCs will have Windows synth running and taking control of your speakers and headphone outputs. MIDI is used to control gear inside Amplitube, so most likely, if you are a beginner, you should forget about it all together. Remember, MIDI has nothing to do with Amplitube sound. Those Asio4all configuration pics look good. I'll try to find Beta 1 and try that instead, in case it's ASIO that's the problem. It gives me a sound initialization error.ĮTA: Got Beta 1 from the ASIO site, but it made no difference.

Once I've run Amplitube, and exited, I can't play the Rocksmith Demo any more. So it seems Amplitube is grabbing the audio device, but won't let ASIO use it. After starting Amplitube, and even if I exit Amplitube, it pops up a message saying the device is being used by another application. When I do this just after booting, they work fine. If I go into Control Panel -> Sound, select my speakers and click Configure, it lets me try to test my speakers. If I click Panel, and look at the ASIO panel, there's a red X next to my audio output. There's no sound coming from the speakers, though.įor output in the Audio MIDI Setup settings, the Left and Right channels both say Not Connected. Strumming the guitar makes the input and output level bars go up, so it seems to be processing the sound. When I look at the Audio MIDI Setup, I can select the Rocksmith cable for input now (not sure what changed).

Unfortunately, the problem seems to be Amplitube itself. Thanks for those pictures, that helps narrow down the problem.

Setting up amplitube 3