Problems with amplitube 2 (ASIO related)

Geoffrey Taucer · Post by **Geoffrey Taucer** » Sat Mar 17, 2007 11:26 am

I use a scope home card, and I'm having trouble running amplitube 2. When I try to open up the amplitube standalone app, I get a popup thing that says that ASIO source and ASIO dest modules are not included in my project, and when I open up the audio setup on amplitube, the output channel dropdown menus are completely blank.

How do I set up ASIO source and dest modules?

Post by **hubird** » Sat Mar 17, 2007 12:01 pm

geez...didn't you read anything of the manual

try the software in/out menu...

Geoffrey Taucer · Post by **Geoffrey Taucer** » Sat Mar 17, 2007 12:04 pm

Software meaning within amplitube or within scope?

Post by **hubird** » Sat Mar 17, 2007 12:13 pm

Scope, you see those main menus at the top of your Scope project window??

Geoffrey Taucer · Post by **Geoffrey Taucer** » Sat Mar 17, 2007 12:24 pm

Oh, that.

I've got the modules in the routing window; I guess what I need help with his how to set up the routing.

Post by **hubird** » Sat Mar 17, 2007 12:47 pm

ASIO modules are in/out 'plugs'.
They connect to native software that uses the ASIO protocol (Audio streaming In Out or something), like sequencers and a lot of stand alone soft(also VST) instruments.
Your audio is going through it...
Connect the monitor out or the Mix out of your Scope mixer to the ASIO Dest. module, your sequencer will 'see' that ASIO plug in it's appropriate window where you can affirmate it or make it active.
Then you can record the audio on a track if you want.
VSTi sounds can be send to your Scope mixer the other way around (Source module then).
One rule: first load your Scope project with the modules you think you'll need, only then open your sequencer!
You can't change ASIO settings while your sequencer is open already, at least the new settings won't be seen!
The same way you can't exit Scope before closing your sequencer without getting troubles (freezes or so).

Take some time for the manual, try everything out before actually wanting to be productive.
The platform is lik a real studio, you just chain machines by cables...it's not difficult, only 'much' in the beginning

.

voidar · Post by **voidar** » Sat Mar 17, 2007 12:49 pm

I suspect when you "figure it out" it will blow your mind

.

Geoffrey Taucer · Post by **Geoffrey Taucer** » Sat Mar 17, 2007 1:09 pm

Thanks a ton.

EDIT: still getting the same error, but what you've said has at least helped this to make a bit more sense... I'll experiment a bit.

voidar · Post by **voidar** » Sat Mar 17, 2007 1:16 pm

You need to load a set of ASIO source and dest in the project. Then you need to hook those up to a hardware input/output. This is all represented in SFP.exe as modules. As explained, you hook these up by clicking on ins and outs, like virtual hardware.

SFP.exe must be running when you load amplitube live.

Post by **hubird** » Sat Mar 17, 2007 1:23 pm

(@GT)
ok man

btw, Midi sequencer source/Dest modules connect the midi between your sequencer and Scope...and Pulsar Source/Dest (or something) represent your hardware Midi in/out of the card, you have to load them to get midi in and out your computer, see the Hardware In/out main menu.
You'll get it

Don't forget: the DSP's of your card must be loaded before the card can do anything...hard and soft in/outs must be 'driven'...some people expect the card to work already by booting the comp...it's not, that's because it's DSP, happening realtime, and that's why it's said to sound so good compared to native processing which is buffered and 'calculated'

(no 'exe' here tho, I'm on mac).

Post by **hubird** » Sat Mar 17, 2007 2:34 pm

...and tell us about your first big aha-Erlebnis...

Geoffrey Taucer · Post by **Geoffrey Taucer** » Sat Mar 17, 2007 2:51 pm

Hehe, it may be awhile before I develop a real mastery of all this; I basically just made the switch from a consumer/hobbyist system to a more-or-less professional one, so I'm dealing with a bunch of stuff that I do not yet have any real idea how to use.

Post by **hubird** » Sat Mar 17, 2007 2:58 pm

you use a native sequencer?

Geoffrey Taucer · Post by **Geoffrey Taucer** » Sat Mar 17, 2007 3:41 pm

I'm using Sonar.

Any chance you could give me a screenshot of what the routing should look like for the amplitube standalone to work? I've attatched a shot of how I have it set up now.

Post by **hubird** » Sat Mar 17, 2007 4:19 pm

I don't have Sonar or Ampltube, but you have to realize that the ASIO protocol permits only one 'client' at the time.

The source modules are a different story, I'm talking about ASIO only.
You could load Amplitube as VSTi in Sonar.
You just have to check your latency settings in Scope and Sonar.
As long as you stay under 25 ms for the whole setup you won't notice I guess.

you know you can add ASIO channels by doubleclicking the ASIO Source module?
For both in and out!
Use always the same (couple of) ASIO drivers, preferrable ASIO2 (allowing direct monitoring, but forget about that now).

You got the picture already I sea

You are listening to the mixer's out now, taking the view that you have connected the analog out of the card to your sound system (amp, mixer).
If you record the incoming audio from -say- a Scope synthesizer -played life by Midi- from the mixer's out via a ASIO channel to Sonar, you will also record the signals coming already from Sonar, f.e. your Amplitube playing life by recorded midi or as an audio file already.

Therefor, you can output every track inside the mixer, by muting the channel from the master outputs, and sending them to the Direct Out (check the manual), which you find back on the mixer module in the project window.

There are other possibilities, it depends what you need to include in the signal.
It's just to show you the picture, how to think.
You will never be out of cables in your studio

Why have you the mixer's out connected to SPDIF out?
A good use of that output is connecting it to a auxilliary (effect send) of the mixer through to an external reverb with digital ins like the Lexicons.

Midi perfectly done

Hope Sonar will do, there were some reports about ASIO troubles or something, not sure tho.

If you click on 'Int.' on the AUX page of the mixer, you can make connections from the pop-up menu, and the module image starts showing the activated aux(iliary) (effect send).

Post by **garyb** » Sat Mar 17, 2007 4:48 pm

sonar is great with scope.

hubird is right, asio is not multiclient. you can only use one asio app at a time. you must use the vst version with sonar. please read the manual, the project you posted is the "dummy" project that is just to let you have some quick fun. for best results you need to be able to edit it. asio ins and outs can be added by rght clicking on the module and choosing "surfaces" and then "asio settings".

Post by **hubird** » Sat Mar 17, 2007 4:50 pm

hubird wrote:Midi perfectly done

silly me

Thought, a tight look already...
long time go I saw that project

Geoffrey Taucer · Post by **Geoffrey Taucer** » Sat Mar 17, 2007 5:00 pm

Yeah, like I said, I'm just learning.

I haven't tried using Amplitube as a VST within sonar; so far, I've just been playing around with the standalone version.

When you say ASIO is not multiclient, what does that mean? Does that simply mean I can't run standalone amplitube and sonar at the same time? That's not what the problem is; when I'm trying amplitube, I'm not using it with sonar running as well, I'm doing it with amplitube being (I think) the only ASIO app running.

Now, with Colossus standalone (which takes midi input, as opposed to amplitube which is an effect for audio input), I'm not having any problems. As far as how scope handles the two, what's the difference? I mean, I know one is an instrument and the other is an effect, but do I need to configure the routing differently to use the two?

I have read some of the manual -- parts I'm finding to be understandable and I think will be pretty useful once I really get rolling, but other parts I'm finding to be a bit dense and hard to follow, or simply hard to navigate to find what I'm looking for (this thing with amplitube being one such case, since I'm not entirely sure what I should be looking for).

Post by **hubird** » Sat Mar 17, 2007 5:17 pm

right

You must chain the effects to your mixer somehow.
This is how it works:
Two types:
1. effect sends.
Use the channel's send (aux) knobs for sending the signal to a send effect.
Typical send effects; reverb, delay. you open sends on different channels in different send settings to one single effect.
Reverbs tend to use some DSP power, so sends are economical.
Set the 'dry' level (open the effect's module) always on zero then, to avoid the infamous phase delaying.
I explained you the project cabling alreadty, use the aux outs of the mixer.
2. insert effects. you load them in the inserts of each channel.
These effects are meant to transform the signal on it's own, like distortion, phase, bit crushers, filters, compressors, equalizers, etc.
Inserts are handy, you don't have to make any connections, they are channel bound tho.
You can however decide to direct out several channels and cable them back into a free mixer channel, to combine channels to inserts.
Volume settins or the source channels should fit with the insert settings tho.

Geoffrey Taucer · Post by **Geoffrey Taucer** » Sat Mar 17, 2007 5:27 pm

But that's just for scope's effects, right? Or is there some way I could load amplitube into scope's DSP and use it as a module?