NOTION Music Forum

Okay. So after a long conversation about this problem, what I am thinking is that you have two or more controllers on your Organ that are receiving CC 11 data.

CC11 Data is what Notion uses to send dynamic information. CC11 and Velocity are independent of each other. I think the reason that dynamics, which are sent via CC11, are giving you a problem because you might have two or morecontrollers on the organ receiving the CC11 data and they are cancelling each other out somehow. This could happen if your Volume Pedal and a Stop that changes the instrument's playback settings are both set to receive CC11 data.

Or, here is another possibility:

Another problem that could be happening is that you might be sending MIDI Data on multiple staves through the same MIDI channel. If you are doing that, then if the dynamics change on one staff going out Channel 1, and the dynamics change on another staff in a different way, and are also travelling out through Channel 1, then there is a conflict. Can you confirm that you are sending MIDI from multiple staves across Multiple Channels to your external Device (Organ).

Hope this helps...

-Admin

Dear Admin,

Thank you very much for your investigation. Your first assumption is correct. I am sorry to find an inconsistency between Notion and my organ for this reason: my organ uses CC11 for its expression pedals instead of CC7. This is a pity because this software is very well designed and fun to use. Is it possible to cancel my licence and get a refund in this special case?

For reference, this is the Viscount Prestige 80 Organ . . .



Prestige 80 Classic Organ (Viscount International)

There is detailed information on the MIDI Implementation, which includes examples, in the Advanced Manual, where the following link is the PDF version of the Advance Manual . . .

Advanced USA Manual (Viscount International) -- PDF (1.6MB, 80 pages)

[SOURCE: Download Area (Prestige Organs) ]

And this is the definition of the hithertofore mysterious "B0 0B 5A " MIDI instruction (from page 70 in the Advanced USA Manual):

xpression (CC 11)

Message which controls the sections expression.

Data format: BnH 0BH vvH

n=channel number :00H – 0EH (1 – 15)
vv=expression value :00H – 7FH (0 – 127)

[NOTE: For those folks who might not be so familiar with the more abstruse aspects of Computer Science, the "H" characters refer to "Hexadecimal" and "n" refers to a channel number, hence "B0" apparently maps to channel number 1 (where "1" is the decimal channel number, since counting starts with zero representing decimal 1), and the expression value is "5A", which is hexadecimal for the decimal value 90 . . . ]

And this might provide a bit of useful information, where among other things it appears that the organ sends MIDI CC messages both on MIDI Port A and MIDI Port B for the respective channels (from page 70 in the Advanced USA Manual):

3 MANUALS MODELS
Ch.1: Swell notes or controls (MIDI A)
Ch.2: Great notes or controls (MIDI A)
Ch.3: Choir notes or controls (MIDI A)
Ch.4: Pedal notes or controls (MIDI A)
Ch.5: Swell notes or controls (MIDI B)
Ch.6: Great notes or controls (MIDI B)
Ch.7: Choir notes or controls (MIDI B)
Ch.8: Pedal notes or controls (MIDI B)

2 MANUALS MODELS

Ch.1: Swell notes or controls (MIDI A)
Ch.2: Great notes or controls (MIDI A)
Ch.4: Pedal notes or controls (MIDI A)
Ch.5: Swell notes or controls (MIDI B)
Ch.6: Great notes or controls (MIDI B)
Ch.8: Pedal notes or controls (MIDI B)

- Control Change messages are sent always on both A and B channels.
- Ch.16 is a reserved channel (system)

Lots of FUN!

Hi Surfwhammy,
You've got it! My problem is there ... No solution.

I would think it could be easily solved with a custom rule set...

wcreed51 wrote:I would think it could be easily solved with a custom rule set...

If this is the case, no doubt that Admin will tell me the magic formula to write in my rules. It would be a relief!

lucha wrote:I am sorry to find an inconsistency between Notion and my organ for this reason: my organ uses CC11 for its expression pedals instead of CC7.

With the caveat that I am not an expert in MIDI and basically have only a minimal understanding of MIDI, I purchased the MIDI video tutorial from macProVideo and watched it, and as I recall there might be hardware devices that can be used to do MIDI instruction and command mapping, although this is mostly a guess . . .

MIDI Demystified (macProVideo)

Something like the Event Processor from MIDI Solutions might do the required MIDI translations . . .



MIDI Event Processor (MIDI Solutions)

And there are applications that run on the Mac and Windows for doing MIDI mapping, where these are two examples (Mac and Windows), and they might be able to transform a CC #!! command to a CC #7 command, coming and going . . .

MidiPipe for the Mac (MacUpdate)

MidiMapper for Windows (Sound Quest)

Lots of FUN!

And this would be a software version of the same:

http://www.bewaryprods.com/software/pro ... sMIDIfier/

lucha wrote:

wcreed51 wrote:I would think it could be easily solved with a custom rule set...

If this is the case, no doubt that Admin will tell me the magic formula to write in my rules. It would be a relief!

wcreed51 wrote:And this would be a software version of the same:

http://www.bewaryprods.com/software/pro ... sMIDIfier/

I like these ideas!

There should be a way to solve the problem, really . . .

Really!

Thank you guys, you're great! However, when writing a rule sufficient, it would be easier. See what Admin says.