Moderate Latency with MIDI Keyboard

[mswlogo]

Originally Posted by dj

Hi,

Go to Setup/Midi Device Configuration and double click on the device you want to send to. In the dialogue box that comes up, uncheck Echo Midi Input To Output. That should get rid of your feedback problems.

Midi channel numbers have nothing to do with Voice numbers. To change the voice you wish to hear (instrument sound), click on the Speaker icon to the left of the track (in Window view) and select a new sound from the box. It's a General Midi list by default.

To change sounds within a piece of music, use the Sound Changes tab in the Main Palette to set a new sound by clicking in the place you want it.

Good luck.

David

I did uncheck "Echo Midi Input To Output" and it did not fix it.

I change Instruments all the time with the Speaker Icon in Notation. But if I'm not recording what "Staff" (Speaker Icon) is there to change instrument (Voice) on for the KeyBoard?

Each Staff is assigned a MIDI Channel and a Voice.

The Keyboard is on Channel 1 and can select it's own Voice.

But something in Notation is overriding the Voice on KeyBoard Channel (Channel 1), which I setup such that no Staff is assigned to.

[Sherry C]

Hi,

I have the Kaysound keyboard, too - we're talking about just a MIDI controller, correct?

For my setup, I use
(1) ASIO4ALL as the ASIO driver (yes, you'll want this )
(2) SynthFont as my playback device (with the MIDI loop disabled, as you've already done).
(3) and turn the GS Wavetable OFF. It interferes with ASIO, and will cause latency issues even with other devices (pernicious little bugger).

In Composer,

1. click on Setup/MIDI Devices Configuration
2. click on "Ports/Select Ports.
3. In the right-hand panel, make sure that "Microsoft GS Wavetable" is UNchecked.
4. Ok/exit out the dialogs

That hopefully should do the trick.


ttfn,
Sherry

[mswlogo]

Originally Posted by Sherry C

Hi,

I have the Kaysound keyboard, too - we're talking about just a MIDI controller, correct?

For my setup, I use
(1) ASIO4ALL as the ASIO driver (yes, you'll want this )
(2) SynthFont as my playback device (with the MIDI loop disabled, as you've already done).
(3) and turn the GS Wavetable OFF. It interferes with ASIO, and will cause latency issues even with other devices (pernicious little bugger).

In Composer,

1. click on Setup/MIDI Devices Configuration
2. click on "Ports/Select Ports.
3. In the right-hand panel, make sure that "Microsoft GS Wavetable" is UNchecked.
4. Ok/exit out the dialogs

That hopefully should do the trick.


ttfn,
Sherry

Sherry you don't need ASIO4ALL if your sound card supports ASIO. ASIO4ALL is a bandaide for sound cards that don't have ASIO support.

I did everything you said and it mostly works.

Except I got MIDI Feedback, I switched to LoopBe30 and that fixed that.

My only issue (which is not huge) is something I think in Composer is overriding the Instrument (voice) I choose on the KeyBoard. If I Choose for example 16 for Organ (on the keyboard display), the Organ works fine. But as soon as I play music from Notation to play along with, it changes KeyBoard (sound it produces) back to Piano even though KeyBoard display will still show 16.

How do you control the KeyBoard's instrument (Voice) in Notation (when not recording). There is no staff associated with the KeyBoard.

EDIT: A little more info on Notation Changing KeyBoard Instrument.

In SynthFont you can see a temp Midi Channel with Oragan Selected. As soon as I hit Play on Notation it Changes to Piano.

While it's playing I can change KeyBoard again to Organ and it will stick. The second I touch the staff, to say jump to another part of the staff, it flips back to Piano.

Also I have to have LoopBack in LoopBe30 on to get any sound from Notation or KeyBoard. That does not make sense to me. Nothing should need to be looped.

[mswlogo]

I reinstalled LoopBe1 and magically got it working without the MIDI loopback error. I swear I set it up the same way.

It seems the KeyBoard wants to always mimic one of the Instruments (Voice) of the Staffs that's playing.

I had chose another Tune that was a Church Oragan and I didn't realize it until 1/2 hr later that the KeyBoard was now staying a church Oragan. Exactly the same one the Staff was playing.

I had earlier tried to set all Staffs (of tune with Paino) to some random instrument (no Pianos) but the KeyBoard still tayed Piano (01). But when I brought up a tune that had no Piano and only organ, I got Organ on the KeyBoard immediately.

This is an amazingly powerful way to learn.

My goal is just to learn basic accompaniment (typically reserved for left hand) but I'll use both hands.

My main instrument is fiddle. But this sure is fun. Perfect intonation, kind of depressing actually, compared to how much work it is to get a nice tone out of fiddle even after 4.5 years. Ugh.

[mswlogo]

LoopBe1 MIDI Feedback Errors are back.

The reason it worked is tune dependent.

I went back to the first tune I was playing with and MIDI Feedback errors immediately returned.

I tried deleting some of the Staffs that were already muted and it would go longer before getting feedback, but still eventually fail.

Then I pruned it down to 1 staff and it still got feedback after a while.

I attached the two tunes.

Angeline the Baker.Not will immediately get MIDI Feedback Error

Music for a Found Harmonium.Not will play fine.

[Sherry C]

Hi,

If you're using LoopBe30, try turning off the "detect MIDI feedback loop." There are some files that apparently trigger a bug (being fixed for the next release) in Composer by sending out multiple MIDI cc commands, which tricks LoopBe into thinking there is a feedback loop when really there isn't.

You mentioned earlier that you'd tried this and it worked. I'm pretty sure this is the issue, and the workaround for you.

ttfn,
Sherry

[mswlogo]

Originally Posted by Sherry C

Hi,

If you're using LoopBe30, try turning off the "detect MIDI feedback loop." There are some files that apparently trigger a bug (being fixed for the next release) in Composer by sending out multiple MIDI cc commands, which tricks LoopBe into thinking there is a feedback loop when really there isn't.

You mentioned earlier that you'd tried this and it worked. I'm pretty sure this is the issue, and the workaround for you.

ttfn,
Sherry

Yes, LoopBe30 worked but I was curious if I had something setup wrong and tried LoopBe1 again. I also thought it wouldn't hurt being free as well if it worked