Problems with amplitube 2 (ASIO related)

[hubird]

no way

The only 'disadventage' of Scope is, it's a platform on it's own, usually you always have two platforms going, unless you use SFP as a life instrument source.
In a studio setting you must use ASIO and Midi connections between both platforms to get the thing rolling.
It makes it a professional platform, you can design any studio you like, save them as projects, and use them on command.
Who cannot cable

Just to tell you the truth, it's the other way around:
On pc (not on mac, I should get back a part of the money) you have Scope mode in 'XTC'.
It allows you to open almost every effect or mixer as VST in Sonar.
But...don't try yet, you need to understand very well how to set up a project and connect the ins and outs, at least.
XTC is a abandonnated path since years (by Creamware), you need to know how to make a XTC project before you enter Sonar's XTC settings, and it needs some tweaks on extension renaming of files, and more if you're unluckie.

[Geoffrey Taucer]

Ok, so that brings me back to my original question: how do I get something like amplitube to work? Routing the mixer's outs to the ASIO dest module didn't help; the app still doesn't seem to recognize the modules.

EDIT: ok, it looks like I lied about it working with colossus as well. I had it working yesterday....

[hubird]

then it's quite simple.
If you have loaded a ASIO out module, and Amplitube-standalone doesn't recornize the ASIO port, then something is wrong with Amplitube!
I'm on mac, but I can't remember this can be solved by pc-typical 'tweaks' in the basic OS settings.
But I think it should work bytheway, you must have something wrong.
Hopefully someone knows more
Gary has right, the use of A. as standalone is absolutely unusual, specially for a starter.
You have to learn Sonar, concentrate on the connections (ASIO busses and Midi ports), start getting confident with playing VST synths in Sonar and SFP synths in Scope.
If you get that done, you're almost there.

Btw, Amplitube doesn't generate sound, it needs to be fed.
So it would be perfect if 1. you're able to record a midi track that is triggering eighter a VST Sonar synth or a SFP synth, 2. play that recorded midi channel and record via ASIO the incoming audio on a track in Sonar.
Then you have something to apply the Amplitube on
I don't know if Sonar submits playing 'life' through Amplitude, if that's your concern, I guess so.
It's better to find the right Scope plugin to do the same, and monitor directly from SFP. Less latency at least.

[Geoffrey Taucer]

Ok, thanks.

EDIT: I get the same popup when I start sonar: it says I don't have asio source or dest modules.

I'm not sure why this is happenning, as I had sonar working (sort of) yesterday....

[hubird]

you did care to have the ASIO loaded SFP project open before opening A.?

[garyb]

once you get the idea of what is going on, this will all become unbelievably simple. until then let's see if we can get you on the right track.

please look in the device manager(start/control panel/system/hardware/device manager) and tell me if there are any exclamation points or question marks and if so where exactly...

scope is virtual reality. everything that works in the real world works exactly the same way in scope(for the most part). the routing window is the room your studio is in. an application like sonar is a multitrack recorder(audio and midi in this case), basically a tapedeck, or sonmething like a vs880. it has jacks(the tape deck does) to connect wires to it to be able to get sound in and out. it connects to mixers and then power amps and speakers to hear it.

in the scope routing window, there are modules. the scope(or pulsar or luna depending on what card(s) you have) analog source is the jacks on the cable whip on the outside of the computer, represented inside the computer. the jacks for sonar are called asio source(coming from sonar) and asio dest(going to sonar). sonar isn't alone in being able to use the asio modules. amplitude and other apps can as well, but only one app can use them at a time. there are other modules as well. the wave and 24bit wave modules can be used by any windows program(as it's input and output jacks) everything can be connected or disconnected in realtime, just like in the real world(that includes going between the real and virtual worlds in realtime as many times as you like depending on how much i/o you have). have fun.

a couple of things about using asio:
you must have the proper asio modules with the desired number of channels in your project before opening your asio app(sonar). when sonar(or any asio application) opens, it looks in your project to determine what kind of i/o jacks it will have available(this info applies to the sequencer midi source and dest modules as well, the midi jacks for your windows programs. if you have several apps needing midi jacks you should have several modules...). once sonar is open you cannot change the number of i/o channels, nor can you delete asio modules, you must close sonar first. closing scope first or removing the asio or seq midi modules while sonar is open will make sonar crash and make the asio driver unavailable to any other app without rebooting the computer. you can connect or disconnect the modules as you please, changing the wire does not affect the jack on your tapedeck, no? personally i use asio2 24bit source and asio2 dest modules in my work.

it is important that scope remain open when using any other apps. you can hide the routing window by clicking on the logo in the tray near the clock on the taskbar and choosing "hide". to show it again choose "show" or just minimize to the taskbar when you don't want to see it.

you want to monitor everything though the scope mixer. the cpu is not a realtime processor(scope's dsps are), so everything it does has lag time, known as latency. all asio apps have twice the ulli latency figure. if ulli is set to 4ms, total latency is 8ms. the shorter the latency, the more cpu resources used. the only way to experience true zero latency when overdubbing, for example, is by monitoring the scope mixer, don't monitor through sonar. this is a weakness in amplitube. i would suggest that dynatube might be nice for you. it doesn't have amplitubes impressive effects, but the amps sound reall and have tone. there are plenty of effects in scope as well as the stomp boxes you probably have plenty of. never the less, i'm not saying that amplitube is bad, far from it. it should work very well indeed.

see if this info helps you. if not, the please write step by step exactly how you are going about doing this and maybe we can find out where you went wrong....

[valis]

gary you should get paid for that level of diligence

[garyb]

i don't mind helping, i hate typing...

paid sounds good.

[hubird]

thought I covered it already, check it out

[garyb]

ok, pay you too...

[hubird]

ping

[voidar]

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.

There's some obvious faults to your project there.
Try this:

1. Luna Source -> ASIO Dest

2. ASIO Source -> mixer -> Luna Dest

3. Use Luna source/dest of choice. (I don't know what preamp you use.) BTW, how are you pluging your gutiar into your computer?

4. Run Amplitube live, or Sonar.

If this doesn't work, try different ASIO drivers - the ones with the 1 or 2 prefix. In fact, _do that now_. Those old ASIO drivers you use are provided for legacy support.

[Geoffrey Taucer]

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.

There's some obvious faults to your project there.
Try this:

1. Luna Source -> ASIO Dest

2. ASIO Source -> mixer -> Luna Dest

Luna analog source and dest or sp-dif source and dest? After hooking it up the way I think you're describing, I still have the same problem (screenshot attatched -- got analog input currently routed to ASIO dest)

3. Use Luna source/dest of choice. (I don't know what preamp you use.) BTW, how are you pluging your gutiar into your computer?

Guitar -> mixer -> soundcard input

If this doesn't work, try different ASIO drivers - the ones with the 1 or 2 prefix. In fact, _do that now_. Those old ASIO drivers you use are provided for legacy support.

How do I switch to different ASIO drivers?

[voidar]

You should hook up whatever hardware inputs you are using to the desired software destination. In your case Luna Analog Source.

Anyway, the connection is correct as displayed on the picture.

You change ASIO driver by loading a new one. See under "Software IOs".

You need a source and a dest of the same ASIO type. Try ASIO1 or ASIO2-FLT 64 source and 64 dest.

[Geoffrey Taucer]

I think I'm getting the hang of the routing. THis is pretty cool!

Still haven't been able to get any ASIO apps to work yet, though.

EDIT: here's my current setup. Still no functional ASIO

[voidar]

Yup, pretty cool .

Uhm, try the "64" drivers instead.

You mean that when Scope Fusion Platform is running and you load up Amplitube live, you can't select the "ASIO SCOPE"-driver from the prefs?

Maybe you should run the installation again. Perhaps the driver isn't loaded in your system.

[bassdude]

I think I'm getting the hang of the routing. THis is pretty cool!

Still haven't been able to get any ASIO apps to work yet, though.

EDIT: here's my current setup. Still no functional ASIO

By this you mean that you are still getting the no asio modules loaded error in amplitude? I think just to get this sorted out just create a project with nothing but ASIO Source and ASIO Dest modules (no connections to anything) to start with until we get that error sorted out.

Regards to your last screenshot. Send your mixer output to Luna Analog Dest if you are monitoring via the analog outputs of the luna card.

And yes, the routing is very cool. It is one of the most powerful features of Scope.

[Geoffrey Taucer]

Nothing I do seems to work; I'm starting to think this might not have anything to do with the routing, though I have no idea what else could be causing it; the problem occurs with any ASIO app I try to run.

Here's the exact error message:

"Scope Fusion Platfrom is not running or ASIO Source and ASIO Dest modules are not included in your current project."

As you can see, neither is true.

[voidar]

Surely this is strange.

In regard to that error the ASIO SCOPE driver seems to be installed.

Did you try reinstalling the software?

[Geoffrey Taucer]

You mean reinstalling the scope software or the other apps?