Bandstand problems

I finally got Bandstand to work after a fashion. I am disappointed in the product. Registration was complicated and buggy. Set up is too complicated. The product is way over priced for something that needs to be fixed yesterday. First, you are going to need 1024k of memory if you are serious about using the product. On stage you can't afford to have your computer freeze up or crash. The latency issue needs to be addressed. I downloaded "Asio4all" but haven't figured out how to use it with bandstand yet. If it works then NI needs to contract with the programmer to include it with the installation disks. The interface needs to be simplified. The eye candy is good, but something simpler would be better. First get the program working then go for looks.

The program needs to be tested with ALL of the major sequencers and programs: Band in the Box, PG Power Trax Pro, Cakewalk, Jammer, Cubase and all the rest.

For Power Trax and Band in the Box users unselect all of the output options, then tic the box to direct output through DixI and choose Bandstand. Now look for the Dixi icon in the toolbars of each program. Click on that to load bandstand as a plug in. When you load a MIDI file don't start to play it for a few seconds. Give bandstand a chance to load all of the sounds.

A few of the sampled sounds need to be replaced, especially that shrill alto sax.

You have the beginning of a good product. Now show the committment needed to make it a great product. Don't take too long. I'm 70 years old and have stopped buying green bananas.

Glenn H.

 

I got "Asio4All" to work and it does help with the latency problem. I want to use Bandstand with PG Music's Power Trax Pro but the main problem now is one of memory. This is the first program that I've had to totally freeze and lock up my computer. I'll going to install more memory to see if that helps. In my previous post I mentioned that the alto sax sounded shrill. Actually it wsa the soprano sax. The nylon acoustic guitar sounds okay on lower notes but the higher notes sound like steel.

Does anyone already use this at a church or on stage? Right now I wouldn't trust it. I might use it to make a wave file or an mp3.

I"m interested in tips to make it work better and hope the programmers don't take too long to fix the problems.

GlenH

 

Glenn, the only way I can get Bandstand to work trouble free with BIAB is to link the two via Midi Yoke. No glitching, no memory 'stickiness'. I think programs like this work fine at 'arms length' through a virtual cable. The problems start when one wraps itself inside another and two sets of program code start fighting each other.

I think the whole concept of 'plugins' is seriously flawed when it comes to prodcucts like this. I'm disappointed - and surprised - that NI (and other software synth vendors for that matter) didn't ensure trouble free running in the top ten or so likely music host products before launch.

I'm also having big problems with Hypersonic 2 and guess what they say? "It's not our product's fault - it's the host's."

 

I've given up. I find now that Bandstand loads in the wrong program patch too often. When I want violins I get piano. When I wanted choir ahs I got an oboe. With Roland I can change those on the fly. With Bandstand I had to restart everything. I can't live with that. I'm calling PG Music tomorrow to get my money back or swap for something that works better. I think Bandstand needs to look at how Roland Sound Canvas works and go from there. It's been a good learning experience but this old man just doesn't have the time to work with it any longer.

Fr. Glenn

 

For what it's worth, I purchased Bandstand, via PG Music, by the way about a week ago.

The only issue I had with BIAB was getting Bandstand "selected" as the synth in the first place. The fix for this was to use the 'Resiter new VSTi" selection in the BIAB synth dialog, then browse to the Bandstand .dll and select it.

Since then, it's worked great. And the sounds are MUCH better than most any competitor on the market I'm aware of for this type of product. You may be able to criticize a few here and there, but that will be true of any synth.

I find the guitars and drums a little "mellow" for heave rock stuff, but that is ok with me. And understandable. Bandstand was designed to be a general purpose sound module. Not to skew the sounds to please one group.

I do have 2Gig of ram, and an Athlon 64 processor.

To be fair to the critics, there are a few "wierd" things happening with patch selection in BIAB, but in general, it's working great. I haven't nailed down any issues that may be happening with the patches, but it is fairly minor.

I wish to HIGHLY recommend Bandstand. It is, in my opinion, by far the best way to use BIAB with a soft synth.

Eric

 

Eric
Where did you navigate to to find the dll? In my Bandstand folders I can only find one folder called Dxi and when I use 'Register a New DX Plugin' to click on the dll within that I get an XP popup 'Access Violation'.

John

 

I found it in the C:\Program Files\Cakewalk\VstPlugins directory.

I installed the Bandstand program on my C: drive, with the data files on an external K: drive.

The Bandstand DXi dll is in the C:\Program Files\Native Instruments\Bandstand\DXi directory.

I don't remember choosing anything but the defaultss on the Bandstand install, except for the K: drive for data.

Eric

 

A further note.

Before I did the browse to find the VST plugin file, the BandstandVST plugin already was shown in the BIAB synth selection list. However, when I selected it, nothing would happen. It wouldn't initiate a load of Bnadstand.

The browse trick overcame this, and once I had selected it that way, Bandstand loads as a VST plugin automatically when I start BIAB.

The file name for the Bandstand VSTiplugin is Bandstand VST.dll.

Eric

 

Sorry, no space .

BandstandVST.dll

Eric

 

Eric,

Thanks, I got it now.
BIAB runs ok like that, but on balance I think I'm going to still use Midi Yoke virtual cable; i.e. with BIAB and Bandstand both loaded but linked via Mid Yoke and Bandstand in standalone mode. With BStand operating as a VSTi plugin if I drag the BStand window at all the playback stutters badly and I also notice out of sync timing here and there compared to the Midi Yoke setup, where everything runs smooth as silk.

John

 

Thanks, John.

I may try MidiYoke.

I haven't noticed any timing problems with BIAB and Bandstand. Obviously you get a little glitch when you initiate a patch change during playback. On my system there may be a 3 to 8 second break in the playback at times during these patch changes. I sort of expect that.

BIAB itself has never been quite "right" . It seems to be a little quirky.

I'll check out MidiYoke.

Eric

 

Hi all,

if there are any remaining problems, please use the onlien support form.


Best,
Markus

 

Markus,
I've sent a support form asking why in Sonar you can only select GM patch numbers for Bandstand plugin - no names appear.

 

I must one of the lucky ones. I've had no real problems with Bandstand. My only issue is with the sounds. I use Bandstand with Sonar via midiyoke and ProTools as a plugin.

 

Hi all,

is that not something you have to set on the host side? I believe that e.g. ion Cubase I have to define a mapping file of some sort or use one already made for GM plug-ins.


Best,
Markus