Ok, before I go too far down the rabbit-hole...
My normal setup for this sort of software involves using ASIO4ALL to output through the onboard audio support. Upon starting BiaB, I tried to use that driver, only to find that the ASIO outputs are disabled, presumably because BiaB (via the MS Wavetable GS synth) is already using the audio device.
No problem, I would certainly prefer to use a DXi/VSTi substitute, starting with either the VSC3 or the Cakewalk TTS1 (similar Roland-based GM2 synth). I got that to work, but apparently BiaB still has the MS synth active, because the ASIO outputs are aren't available. (It's playing the TTS1, but apparently through the MME driver.)
What's worse (or, more to the point, completely unacceptable), this condition persists after BiaB exits: my other DAWs/VST hosts can't use the ASIO interface until I reboot.
I need to get BiaB to:
1. completely ignore the MS Wavetable synth,
2. send its MIDI output to the DXI/VST I specify,
3. send the DXI/VST output through the (low-latency) ASIO4ALL driver, and
4. leave everything in a usable state when it exits.
Suggestions?
Ooookay...three crashes and two reboots later...it's working. And I have absolutely no idea how or why.
It seems to be very persistent about using the MS Synth: even after it was working, I went through several cycles where it complained on startup that the Wavetable synth was in use, did I want to use the alternative MIDI out (LoopBE in this case), even though I had actually already selected LoopBE as the primary output...twice. Had to select 'none' and shut down, then reselect LoopBE and shut down again, before it would believe that's what I wanted.
Very odd, but I guess I'm ok for the time being. The main this is, now I can shut down BiaB and use something else without rebooting, otherwise it was refund time.
In the preferences do you have the use DXI box checked?
Lee,
As far as I understand ASIO, it is a one-application-at-a-time system. Have you tried running BIAB using MME just see if it works ok? Also, are you using different ASIO drivers in your other applications or are you going ASIO4ALL for all?
Noel
Try unchecking "Route MIDI Thru to..." in the MIDI selection window. Otherwise, it will route your MIDI input to whatever is highlighted in the Output window when Use DXi is checked. And you must have the Microsoft Synth highlighted at the moment...
--Mac
Preset MIDI channels can be modified via OPT >> Preferences >> Channels.
I use
Chainer mainly when I need to set a standalone virtual rack of plugins vst/dirx in my laptop, something very useful to me in case of live shows or gigs. Chainer is a "...standalone application has 10 slots for loading VSTi and VST plugins for quickly testing and creating unique sounds which can be saved as presets and also recorded as audio files..." Also I used Chainer sometimes with Band in a Box with great results. However now I use Real Band when need more control and multi-track plataform while preserve BIAB main and interactive features like chord reading, Real Tracks/Drums and song construction. In Real Band is possible to manage VST/dirx plugins assigned to different tracks/buses and groups, also there is low latency real time monitoring (depending of your system) of plugins, great when you are processing voices with reverb or delay or a guitar with an amp/efx simulator. I confess I stay in the middle of my "honey moon" with RealBand, until now has been a promising partner not being jealousy of my long courtship with Cubase, Nuendo, ProTools and others members of my digital harem
.
Lee,
In BIAB, my understanding is that you can load up to 4 DXi/VST synths but can only have one active at any one time. I'm not sure of this, but I believe that RealBand offers greater versatility in this regard.
Noel
BIAB can only address ONE MIDI output device at a time.
I see you are already using Loopback. This one has been on the Wishlist for eaons but we still have only one. There are other proggies out there that can serve as multiple VST hosts.
That said, I tried all that and now find it much more convenient to simply use a good MIDI output device that is GM compat when working inside BIAB, saving the mixed MIDI output stuff for the export to sequencer phase. Much neater and much faster in the long run.
--Mac
If it was dead easy, it would't be worth doing.
Take your time. MIDI is complicated, but not all that complicated, you just have something new to investigate, study and learn. The web is full of good info, websearch up some basic MIDI tutorials, terminologies and the like. Study the manuals that come with your MIDI hardware and software, if you come across a term you don't know or understand, don't just gloss over it, use websearch to see if you can find out what exactly is meant.
BIAB takes time and there is a learning curve to it also. Same goes with Reaper or any other multitracking software.
For now, I recommend you use the VSC DXi that comes bundled with BIAB while inside BIAB. There are a lot more patches available than just the GM bank. Upper Banks are available as well as GS or GM2 also, selectable in the VSC DXi Control Panel. The BIAB FAQ and Help files can show you how to find and install the proper Patchmap for the VSC DXi so that you can select instrument patches by group from the upper banks. For example, see all the available Electric Piano patches in one group and audition them as the song plays back.
Plenty of very good production numbers have been done using "just" the VSC DXi from start to finish.
--Mac
Omni = ability to receive and address all 16 MIDI channels simultaneously by the same device.
Local = Same as what some keyboards and softwares call "Echo" in the MIDI settings. Setting to "Local" means that incoming MIDI data will not be presented at the MIDI Output port of the device.
Thru should be rather self explanatory, typically means that MIDI data coming into the Input will be routed through to whatever is selected for the Output.
--Mac
