From mrresp1@optonline.net Mon Apr 11 20:18:52 2005
Subject:Re: New B4 runtime problem

does it run in safe mode?

mark


>
> I also use B4, and I used to get the same message "b4.exe has
> encountered a problem and must close..." once in a while on startup.
> I formatted my pc and reinstalled Windows and now it seems to be ok...
> I only use three MIDI controllers through a Microlite MIDI/usb
> interface, and had this problem anyway, so maybe it's not related to
> your MIDI-OX or MIDI-YOKE...
>
> --- In CloneWheel@yahoogroups.com, "Kevin" wrote:
> >
> > I've been using B4 for about a year now with no problems. Yesterday I
> > had a problem which was significant enough to have to patch the audio
> > input to my Leslie around the B4 and use the organ sounds directly
> > from the Kurzweil.
> >
> > I am running B4 (standalone - not VST plug-in) on a 850 Mhz PIII with
> > 384 Mb RAM, MOTU Fastlane USB, SB Live 5.1 with KX Project driver w/
> > 5.33 ms latency, Win XP SP2. This is on a tower workstation with a
> > monitor, not a laptop.
> >
> > I am using 2 digital sampled keyboards with integrated MIDI
> > performance controllers (keyboards) as upper and lower manuals.
> > These are a Yamaha PSR GX76 for the upper into MOTU Port A, and
> > Kurzweil PC1X into port B via a MORLEY EP-1 (expression pedal which
> > merges the Kurzweil perf data with the expression data).
> >
> > Since the EP-1 sends MIDI expression and the B4 Swell is a different
> > controller number I use MIDI-YOKE to do data mapping transforms on
> > MOTU port B. Expression is mapped to B4 Swell (if this map is not in
> > place, then the expression drives the tube amp output). The Ch1 MIDI
> > out from the Kurzweil is mapped to Ch2. (it is not easy to change the
> > MIDI out chan on the Kurzweil and get it to persist across power
> > cycling - it's easier to map its default Ch1). The MIDI-OX output
> > then goes to MIDI-YOKE and MIDI-YOKE goes to one of the B4 inputs.
> > The other one is fed from the Yamaha directly. Keep in mind that
> > this has been in operation for about a year with no problems in live
> > performance every week which includes setup, startup and shutdown.
> >
> > My typical startup sequence is make all connections, boot the PC,
> > start MIDI-OX and verify through channel monitor display that timing
> > is being received from the Kurzweil (this is an indication that MIDI-
> > OX is receiving data), play the Kurzweil and press the expresssion
> > pedal to monitor MIDI data. Then start B4. Normally the
> > last "session" of B4 is loaded (same for MIDI-OX - last profile is
> > loaded). At this point I have the B4 running and providing hammond
> > sounds.
> >
> > I recently started using a 3rd midi input with very little activity
> > on it through the sound card's joystick port.
> >
> > Yesterday, I kept getting the dialog from B4 startup "b4.exe has
> > encountered a problem and must close...".
> >
> > I allowed it to close, and then had to kill and restart MIDI-OX. (I'm
> > sure the MIDI-YOKE driver was hosed at this point. No amount of
> > restarts or PC reboots solved the problem and I was relegated to
> > patching around the B4 and using the Kurzweil's sounds directly - not
> > as nice but I am thankful that I was not using simple "dumb"
> > controller keyboards with no sound samples inside. About half of my
> > performance is organ and the other half is various sampled sounds
> > including piano, and exotic instruments.
> >
> > Any ideas?
> >
> > I tried:
> >
> > bypassing MIDI-OX and routing the MIDI direct to the B4
> > increasing latency from 5.33 to 20 milliseconds.
> > removing the third MIDI input from B4's list of inputs
> > removing the third MIDI plug from the sound card's joystick port
> >
> > all to no avail.
>
> To unsubscribe, send email to: CloneWheel-unsubscribe@yahoogroups.com
> Yahoo! Groups Links
>
>
>