Is it possible to use Amplitube in BIAB as a stand alone

PG Music Home

I'd like to run my guitar thru my interface and then thru amplitube into the audio record function of BIAB, is this possible, or to use it with another DAW?\

Rob

RB can do it, BiaB probably can too, depending on soundcard.

BUT, why not just 'listen' to the effect while using it (and recording), but actually record the guitar track dry? Then you can use the same effect during playback. This way you can tinker with the effects later to fine tune them.

In RB the option is in Audio Prefs window; 'Use Input Monitoring', and 'record IM' are both checkboxes.
'Using' it allows you to hear it but not record it. 'Record IM' option records it.

Let's see. To use AT3 you have to use an ASIO interface.The way Bob mentions is probably the easiest. I have Ampeg SVX for bass that now lives in AT3. I use the IKM Stealth Plug and play AT3 standalone. The output of the Stealth goes to a mixer. The Aux send goes to the in of the sound card.

Quote:

RB can do it, BiaB probably can too, depending on soundcard..

Not worked here for me. For my live show I tried to setup Amplitube (tried both as a VST and in standalone mode) with BIAB out through my VLT - no joy

/

When Amplitube (using ASIO4all) is used as standalone, BIAB throws an error "..wave device in use". And I have found no way to play audio into BIAB with the VST on the audio track in Real Time.

Perhaps someone has achieved this.

Hey, Rob:

In the support section of the PG Music website, on the Video page, there is a video titled: Using AmpliTube with Band-in-a-Box and RealBand.

Approximately 31-minutes-and-15-seconds into the video, the narrator shows how to record in RealBand through Amplitube. Although you did specify Band-in-a-Box in your original post, the info in the video may still be of some use to you. Hotcha!

Be well, be happy.

Sincerely, Bro. Dave
www.brodavelister.com

Unlike RB, BIAB does not have "Enable input monitoring"

I do it all the time as stated but it takes a separate interface for AT3 and the soundcard for BIAB into a mixer.

Quote:

I do it all the time as stated but it takes a separate interface for AT3 and the soundcard for BIAB into a mixer.

John, you are always a step ahead of me. OK, I tried to run the VST in RB for live monitoring which playing over my arrangemetns and it did work nice - form a guitar sound perspective, however, as you know, my show is in BIAB.

So you got me thinking, I actually have two soundcards on the laptop, the external VLT and the internal with its output from the headphone jack and my PA has a built in mixer. Since BIAB will not allow the VLT to run both itself and Amplitube (as etiher a VST with live monitoring or as a standalone sharing the single external VLT - it seems you are suggesting that I can cable-in both of the cards.

How does this sound:

First, I have to have BIAB output to the VLT since BIAB is also sending a midi channel to control harmonies - so therefore BIAB has to send to the VLT.

I have to have Guitar input from the VLT also since this is where I have the 1/4" jack.

So If I run Amplitube in Standalone mode with its input from the VLT, but with its output to the internal headphone jack so may be an option.

Well I tried this all last night and no go. But it was very complicated with multiple options for drivers. So should I keep on trying? Does it sound like I am on the right path.

If this would work I could literally eliminate the Guitar Amp from my giging. Not a big thing, but every less wiring and setup on stage save times and frustration.

Quote:

When Amplitube (using ASIO4all) is used as standalone, BIAB throws an error "..wave device in use". And I have found no way to play audio into BIAB with the VST on the audio track in Real Time.

Try UNchecking, "ASIO Always On"...

--Mac

Dan,
I didn't know the VLT could be used as a sound card.Are you sure? I'll answer your question based on it being a sound card. OK here goes.
1.Set BIAB to use MME drivers with it's output to the VLT
2. Plug the guitar into the input of the VLT
3. Plug the thru/guitar out from the VLT into the IN of the Internal card.
4. Set the internal card to use ASIO. Might have to be ASIO4ALL.
5. Open AT3 in standalone
6. Set input to AT3 from the Internal Card/ASIO4ALL
7. set output from AT3 to Internal/ASIO4ALL
8. plug the outs from the Internal card and the VLT into separate channels of the mixer.
My mention of Internal/ASIO4ALL is I'm not sure what will be listed in AT3 for available drivers.Also I doubt your internal card will have ASIO so you'll have to use ASIO for all..

Thanks Rob

I mostly wanted to practice with it to refine some preferred sounds, so i'll try the monitoring solution and see what happens.

I start a song playing in BIAB.

I open AT3 as an effect under Audio in the mixer.

If I change any parameters in AT 3 while the file is playing, it hangs up and I get a lot of digital noise.
I should have plenty of ram, so I'm thinking that I have to use ASIO vs MME. Can anyone confirm?

Rob

Quote:

Thanks Rob

I mostly wanted to practice with it to refine some preferred sounds, so i'll try the monitoring solution and see what happens.

I start a song playing in BIAB.

I open AT3 as an effect under Audio in the mixer.

If I change any parameters in AT 3 while the file is playing, it hangs up and I get a lot of digital noise.
I should have plenty of ram, so I'm thinking that I have to use ASIO vs MME. Can anyone confirm?

Rob

Rob, I really hope it did not appear I was hyjacking your thread. I do believe you and I are trying to do the exact same thing - although maybe for differenct purposes. However, I have spent several hours and have not been able to do this. RB - no problem, but not in BIAB

Toucher,
You will never get AT3 to work as a plugin realtime in RB using ASIO without issues and you have to use ASIO.

Quote:

Dan,
I didn't know the VLT could be used as a sound card.Are you sure? I'll answer your question based on it being a sound card. OK here goes.
1.Set BIAB to use MME drivers with it's output to the VLT
2. Plug the guitar into the input of the VLT
3. Plug the thru/guitar out from the VLT into the IN of the Internal card.
4. Set the internal card to use ASIO. Might have to be ASIO4ALL.
5. Open AT3 in standalone
6. Set input to AT3 from the Internal Card/ASIO4ALL
7. set output from AT3 to Internal/ASIO4ALL
8. plug the outs from the Internal card and the VLT into separate channels of the mixer.
My mention of Internal/ASIO4ALL is I'm not sure what will be listed in AT3 for available drivers.Also I doubt your internal card will have ASIO so you'll have to use ASIO for all..

John, I just saw this item. Missed it earlier. I have worked all day on this with some very promising results. First conclusion: I think it is time for me to move my live show on from BIAB to a more flexible application (I know I have said this before

, but this time I think I mean it). I have been gigging in BIAB for over 10 years and I finally think I need a change to move to a next level. More about the changes later

.

I was able to get the VLT to serve as an external sound card (this thing is so cool) in that I plugged the mic (via XLR) and guitar (via 1/4" plug) and my backing tracks (via USB) into it. I can then route the wet vocals to the PA, and the dry guitar to the computer for processing in AT3-VST and back out again to the VLT via USB and on to the PA. Only need one cable form VLT to PA. I still need to confirm that the midi from my backing tracks is controlling harmonies - but I am optimistic.

Thanks for your advice - it is always appreciated. I do believe a workaround with BIAB may be doable with the dual sound cards but for now I am trying something a little different. Time will tell how it works out.

Quote:

If I change any parameters in AT 3 while the file is playing, it hangs up and I get a lot of digital noise. I should have plenty of ram, so I'm thinking that I have to use ASIO vs MME. Can anyone confirm?

Rob

When I hear "I get a lot of digital noise", it makes me think about a mismatch in the transfer rate (44.1KHz vers 48.O KHz). And regarding ASIO vrs MME, I will always try both to see which works best...

Quote:

Quote:

If I change any parameters in AT 3 while the file is playing, it hangs up and I get a lot of digital noise. I should have plenty of ram, so I'm thinking that I have to use ASIO vs MME. Can anyone confirm?

Rob

When I hear "I get a lot of digital noise", it makes me think about a mismatch in the transfer rate (44.1KHz vers 48.O KHz). And regarding ASIO vrs MME, I will always try both to see which works best...

Nope. The old legacy asio code is causing the processor to really ramp and doing anything sends it over the edge.

I think the answer to this dilemma is, "it depends on several factors".

If you are trying to use an ASIO device that is LOCKED BITRATE in its own
Control Panel and that bitrate is something other than 44.1KHz, or not set to something that lets the host program select the bitrate, you could have problems.

If you are trying to use ASIO drivers and have not experimented with the all-important Buffer Settings in the sound device's Control Panel, this too can cause dropouts, strange sounds, etc.

If you are trying to use ASIO drivers along with another separate program at the same time and both programs are set to use ASIO and you do not UNcheck BiaB's "Asio Always On" setting, you can have problems as that setting really means that BiaB will not let go of the ASIO drivers to share with another program. This other program could be a VST or DX program, such as a Guitar Amplifier/Cabinet simulator, etc.

Use of ASIO drivers takes a bit more operator savvy and often experimentation with settings than the selection of the Windows Sound MME/WDM driers do, and that is often ignored or misunderstood.

Then, of course, there is there is the issue of "DRIVERS, DRIVERS, DRIVERS" -- Finding and installing the right drivers for your setup, often drivers included on the CD in the box with the device are outdated and not worth using before the item even ships, best to visit the website of the device manufacturer, support section, find and download the latest drivers for your device and install those, for ther are often changes made to the code that allow the thing to operate properly in the first place. And even then there are some drivers tht are created better than others, or at least updated in such fashion as to correct reported problems.

--Mac

I guess that's why I've stuck with MME for so long. But from the looks of things, I may have to start the learning process for asio. Thanks for the info, and "No Worries" Jazzman, you didn't hijack nuthin;

We're all after knowledge.

Thanks to all.

Rob

Quote:

The old legacy asio code is causing the processor to really ramp and doing anything sends it over the edge.

John, what old legacy asio code? Kent said in another thread that PG had problems with asio until 2009 but not any more. You are one of our resident experts, I'm wondering why you still feel there is this big problem with asio. This goes to what Mac said, there's a lot of moving parts to this starting with the latest versions of Biab/RB and a modern PC running Win 7. If you're running older stuff, all bets are off. I was one of the biggest beaters of that drum when I was using my old P4 2.8. Never could get the asio to really work. After tons of tweaking I could get the latency down to about 40ms, no lower. Now with the latest and greatest I'm running 10ms with no problems at all. The first thing I did with the new box was go to EMU's website and download their latest drivers. Works perfect.

This is yet another example of nobody but us geeks knows anything about this. If a user is not willing to hit the books and become a total computer nerd and understand and apply what Mac just said should give it up now and take up golf or something.

In my probably useless opinion, there is no longer a problem with asio but it requires knowledge such as ASIO4ALL is not asio. It's only to be used if someone's device doesn't have it's own native asio driver. If your soundcard comes with it's own asio driver then update it, learn how to set it up in your DAW and use it.

Bob

Bob,
BIAB/RB runs fine on any modest machine as long as WINMM is used.
As soon as ASIO is used, BIAB's CPU usage rises abnormally.
My new/old desktop that I got the MB from RHARV goes from 9% CPU with MME to 87% CPU with ASIO.

Now the whole point is; this behaviour is not normal!
There is absolutely no reason why using ASIO instead of WINMM should
need additional CPU power.
These are merely drivers we talk about!Ask Eddie.
Audio drivers and drivers in general, hardly use any CPU power.

Put differently; if you need a 6Core monster machine to run BIAB with
ASIO smoothly
while it runs fine on any machine with WINMM, then there is something
wrong with BIAB.And it runs fine in other programs.

With buffers at 10MS I can keep it just under 60% unless I move the mouse or do anything else.

What kind of drive you put in that system?
Know the seek time? (just curious)
buffer size on drive?
rpm?

I ran two 120G drives with 8 meg buffer at 7200 rpm on that board. The 'seek time' was 8 mS, and if I pushed 8mS in ASIO on that system I noticed the difference. Not sure if it would apply at all, but it was something I noticed. Seek time seemed to match the ASIO threshold.. M-Audio 1010lt ASIO driver (10 in/out).

It was something I noticed and I've never asked anyone else.

Bob,
The thing is. Same drives, same songs, same programs. Biab/RB brings the processor to it's knees with ASIO. Sonar stays the same.I don't want to keep beating PG on this but there is something they need to look at. IMHO