PT Logic

Logic Pro MIDI filtering using Osmose Expressive E

P

peterlemer

Logician
Logic version
11.1
Mac OS
Sonoma
It implemets MPE big time, and it outputs several problem Control messages on chs 1 and 16
At least one of these has borked the kbd ( it detects a loop when recieving CTR 117 on ch 16) amd I'm sure there are more to come as I dive deeper.

Id' like to be able to filter chs 1 and 16 either on any track I record Osmose on, and/or filter out chs 1 and 16 on the MIDI return.

Any idea for an external MIDI router that could do this?

pete

tags: Osmose, MPE
 
Sort by date Sort by votes
Peter Ostry said:
Software?
Bome MIDI Translator Pro

Hardware?
BomeBox (runs MIDI Translator Pro Files)

Bome has excellent online support in the forum.
Click to expand...
Fascinating thanks
This has also been suggested: https://www.cme-pro.com/product/usb-host-midi-interface/
what I've done meanwhile is to use Logic's own Environment/transformeor to successfully filter CTR 117 on any channel.
Is there a way I could do similar to a track's output?

That way, I could use Logic entirely in-house.

pete
 
Upvote 0
Depends on your setup.
Can you describe your MIDI signal flow, the virtual instrument(s) you use and at which point(s) you want to filter out disturbing messages?

I don't have an Osmose but a Roli and may be able to test some methods.
 
Upvote 0
Peter Ostry said:
Depends on your setup.
Can you describe your MIDI signal flow, the virtual instrument(s) you use and at which point(s) you want to filter out disturbing messages?

I don't have an Osmose but a Roli and may be able to test some methods.
Click to expand...
My setup:
Kawai digital piano talks to Logic on iMac, via Saffire Liquid. 5-PIN cable. It also connects via Audio to Liquid.
Osmose connects via USB to my iMac and also Audio via Liquid.
Liquid is connected via FW to my speakers.

Shedloads of plugins on my iMac.

Is that descriptive enugh?

pete
 
Upvote 0
Not sure I'm much help here. It seems to be about specific Osmose techniques.
I found an Osmose online manual page that talks about things you described.
It seems to me that the Eagan Matrix has nothing to do with MPE. MPE control data that is only used for MIDI transmission could interfere with this. At least that's how I understand the whole description in the manual.

1. (Quote from the manual)
"If you wish to record a performance on Osmose as MIDI and playback an authentic (or edited) recreation of this into the device later, then use the USB MIDI Haken port (Port 2). The Haken port will always send and receive data meant for the EaganMatrix. Using the Play port instead risks that your original performance isn’t reproduced correctly."

2. You should not record Osmose's MIDI channels 15 and 16 in your DAW.
As the manual says that channels 15 and 16 can interfere with the playback, block both channels in the Logic Environment. The manual also says that the EaganMatrix only reacts to channels 2-14 during playback. I don't really understand this (where are the program changes, for example), but it doesn't say that you should also block channel 1. You can use the freeware MIDI Monitor to see what comes in on channel 1 from Osmose.

3. 'haken local control' should be turned off for playback through a DAW.
According to the manual, CC 117 is a ‘DSP ping’ sent by the Osmose when ‘haken local control’ is switched on. If, on the other hand, CC 117 is received during playback, the Osmose tries to switch off local control. Perhaps this is not working properly and a MIDI loop is detected or this is simply system-related. You could ask the Expressivé support about this. However, it does not seem necessary to block CC 117 separately, because according to the manual this event is sent on channel 16, which is blocked anyway at the recording stage. Possibly check whether this is correct.

My tips for recording:
Use the USB Haken port (port 2) for MIDI recording, block channels 15 and 16 in the Logic environment. Switch off ‘haken local control’ on the keyboard (this may not even be necessary because of the channel blocking). The blocking happens on the environment layer ‘Click & Ports’ with a transformer between the 'Haken Port' in the Physical Input and the Sequencer Input. Of course you have to check this after you open a project, because Logic tends to lose cables between individual input ports and objects.

My tips for playback:
Use MIDI Monitor to check that channels 15 and 16 and CC 117 are NOT going to the Osmose during playback of any track. If this does happen, remove the corresponding events from the event list. Or block them with a MIDI FX plugin or convert CC 117 to something that doesn't hurt. Recommended Logic MIDI plugins are ‘Modifier’ and ‘Scripter’. Since they sit in the channelstrip, they work for playback, not for recording.
 
Upvote 0
Peter Ostry said:
Not sure I'm much help here. It seems to be about specific Osmose techniques.
I found an Osmose online manual page that talks about things you described.
It seems to me that the Eagan Matrix has nothing to do with MPE. MPE control data that is only used for MIDI transmission could interfere with this. At least that's how I understand the whole description in the manual.

1. (Quote from the manual)
"If you wish to record a performance on Osmose as MIDI and playback an authentic (or edited) recreation of this into the device later, then use the USB MIDI Haken port (Port 2). The Haken port will always send and receive data meant for the EaganMatrix. Using the Play port instead risks that your original performance isn’t reproduced correctly."

2. You should not record Osmose's MIDI channels 15 and 16 in your DAW.
As the manual says that channels 15 and 16 can interfere with the playback, block both channels in the Logic Environment. The manual also says that the EaganMatrix only reacts to channels 2-14 during playback. I don't really understand this (where are the program changes, for example), but it doesn't say that you should also block channel 1. You can use the freeware MIDI Monitor to see what comes in on channel 1 from Osmose.

3. 'haken local control' should be turned off for playback through a DAW.
According to the manual, CC 117 is a ‘DSP ping’ sent by the Osmose when ‘haken local control’ is switched on. If, on the other hand, CC 117 is received during playback, the Osmose tries to switch off local control. Perhaps this is not working properly and a MIDI loop is detected or this is simply system-related. You could ask the Expressivé support about this. However, it does not seem necessary to block CC 117 separately, because according to the manual this event is sent on channel 16, which is blocked anyway at the recording stage. Possibly check whether this is correct.

My tips for recording:
Use the USB Haken port (port 2) for MIDI recording, block channels 15 and 16 in the Logic environment. Switch off ‘haken local control’ on the keyboard (this may not even be necessary because of the channel blocking). The blocking happens on the environment layer ‘Click & Ports’ with a transformer between the 'Haken Port' in the Physical Input and the Sequencer Input. Of course you have to check this after you open a project, because Logic tends to lose cables between individual input ports and objects.

My tips for playback:
Use MIDI Monitor to check that channels 15 and 16 and CC 117 are NOT going to the Osmose during playback of any track. If this does happen, remove the corresponding events from the event list. Or block them with a MIDI FX plugin or convert CC 117 to something that doesn't hurt. Recommended Logic MIDI plugins are ‘Modifier’ and ‘Scripter’. Since they sit in the channelstrip, they work for playback, not for recording.
Click to expand...
wow, that's a handful 🙂 And I do believe I understood every word ! Thanks for your time and care, Peter, this will come in extremely useful as a couple of things you've said are new to me and easy to employ

pete
 
Upvote 0
Back
Top