Midi Flood LoopBe1

Gai-Luron

• Nov 22, 2014 - 20:27

Type

Functional

Severity

S4 - Minor

Status

closed

Project

MuseScore

Hello,

I try to use MuseScore via Jack -> loopbe1 -> kontakt 5

but sometime loopbe1 détect midi shorcut and disconnect midi. When i log midi traffic it's seem that musescore flood loopbe1. is it a bug or loopBe1 is to sensible for shorcut?

Window7
b79c7fc

See attached file.

Attachment	Size
MIDILog.txt	56.53 KB

Comments

igevorse

• Nov 26, 2014 - 16:26

This is not a flood.
This is the way of initializing an instrument. We send all information about midi instrument (pitch, volume, pan, etc), and stopping all sounds by sending a NOTE OFF message to each note.
It should not break anything.
Do you have any error or warning messages from JACK/loopbe1/kontakt?

Gai-Luron

• Nov 26, 2014 - 18:47

Hello,

No other errors, only this "loopbe1 shorcut" and not systematically. i deactivate "midi in" in MuseScore to test, same issue.

In log, if you look timeStamp of "note off", you can see the same timestamp for many event. Maybe "Loopbe1" detect this like a shorcut in midi cable. Too many data in short time.
If i have time, i make a log with finale->Loopbe1->Kontakt to look events sended. With finale all work fine.

What i don't understand also is CC: Pedal (Sustain) periodically present in log. No such event are present in MuseScore file. After this event all "note Off" are sended.
The "note Off" for all notes are sended 2 times for 2 channel before first note play.

Don't care about this, it's my personnal test. Shorcut is detected with of without this.
00294639 1 -- B0 00 00 1 --- CC: Bank MSB
00294639 1 -- B0 20 01 1 --- CC: Bank LSB

PS : MIDI CC 120 (All sound off) it's not an other option to close all note at same time?

Thank's

Robert

igevorse

• Nov 26, 2014 - 19:14

"What i don't understand also is CC: Pedal (Sustain) periodically present in log. No such event are present in MuseScore file."
We turn the pedal off with this message. If we send NOTE_OFF without it and pedal was pressed before, we still could hear a sound.

I read about detecting shortcuts in LoopBE1. Seems like this is really because of too many data in a short time.

By the way, this error could also appear if you're connecting something wrong and making a loop.

"PS : MIDI CC 120 (All sound off) it's not an other option to close all note at same time?"
I don't remember why we didn't use this message, perhaps there were other issues.
I'll take a look at that piece of code.

Regards,
igevorse

Gai-Luron

• Nov 26, 2014 - 19:34

Hello,

Thank for reply,

I try to no make mistake on connecting midi. I also dactivate "midi in" in MuseScore.

I use a midi sniffer to log traffic on midi port and no schorcuts appear in log.

MIDI CC 120 Mutes all sounding notes. It does so regardless of release time or sustain.

MIDI CC 123 Mutes all sounding notes. Release time will still be maintained, and notes held by sustain will not turn off until sustain pedal is depressed.

Regards,

Robert

Gai-Luron

• Nov 30, 2014 - 12:48

Hello,

I attach "MakeMusic Finale" output for same score. The "All Notes Off" are used at the end after "Pedal (Sustain)". If you take a look at timeStamp, Finale send CC slower than MuseScore.

Regards

Gai-Luron