Maybe separate Consequence MIDI out with Max for Live?

[riley4reason]

Hi,
I'm using live 8.1.1 on Windows 7, I can get midi out working on other VSTs but all 3 Consequence MIDI channels come over the same routing. No option to choose Consequence MIDI out in other channels, Just one with all 3 channels coming over no matter the channel I choose per instrument in Consequence.

Any help is appreciated.

Thanks! Riley

[riley4reason]

I found this in the manual but there does not seem to be 3 different channels showing up from Consequence in Live 8.1 or Cubase 5.1. I thought this one of the things the 1.1 update was about.

From the manual.

"MIDI Channel: Above the Instrument loader you can find the MIDI channel setting. Select
the MIDI channel on which the instrument sends it's individual triggers and notes."

These midi outs don not show up, unless I missing a setting, or something.

If it's not possible, that would be good to know too.

Thanks! Riley

[Sugar Bytes]

You need the Consequence 1.1 update.
Then in each instrument section you can choose the output midi channel.
The problem is that most hosts (Cubase,Live,...) simply ignore the channel.
Sorry,
Robert

[UncleAge]

If it's not possible, that would be good to know too.

It's possible using a workaround. Keep in mind that by default Live ignores the separate midi channels (well, at least in this setting).

In WinXP SP2
The only reliable way I could find to get around it was using Bidule. Setting up the Bidule plugin was painless, though not intuitive really. You do your routing inside Bidule which will allow you to access each of the three midi channels from Consequence.

In OSX 10.6.3
And just for the record, this isn't a slam dunk in OSX either. Even though you can click the Consequence logo and choose to use the IAC driver for the midi routing, the mapping is sometimes lost after long periods of use. Basically leaving no midi routing from Consequence to any other track. I'm not sure if its a Consequence issue or a Live issue but it will happen from time to time. The fix is to restart the computer. Or... Once again use Bidule.

FWIW, the midi timing is much tighter when I use the Bidule plugin versus the IAC driver on the Mac. Sorry I can't help you with the Win7 side of things. I haven't made that upgrade yet. And as always, ymmv...

Also, I found that Reaper has no issue with the channels coming out of Consequence. You can access them directly with no workarounds. Who knows when Live will see this functionality.

I hope this helps you a bit.

[riley4reason]

Thank you UncleAge! I have used bidule in the past and I like it well enough for routing purposes.

Riley

[riley4reason]

I'm not a max for live programmer, so I have to ask if this is possible.

Do you think we could separate Consequence MIDI out with Max for Live?

Riley

edit:
I found this max4live object for midi in.

midiparse
Interpret raw MIDI data

Description
midiparse will separate raw MIDI bytes by message type
Arguments
None.
Messages
bang Clears the midiparse object's memory of any partial MIDI message received up to that point.
int MIDI-message-bytes [int] Numbers received in the inlet are treated as bytes of a MIDI message (usually from a seq or midiin object). The status byte determines the outlet which will be used to output the data bytes.
float MIDI-message-bytes [float] Converted to int.

Information for box attributes common to all objects
Output
int: Out 4th outlet: The number is a program change.

Out 5th outlet: The number is an aftertouch (channel pressure) value.

Out 6th outlet: The number is a pitch bend value.

Out rightmost outlet: The number is the MIDI channel number.
list: Out leftmost outlet: A note-on message. The first number is a pitch value and the second number is a velocity value.

Out 2nd outlet: A polyphonic key pressure message. The first number is an aftertouch (pressure) value and the second number is a pitch value (key number).

Out 3rd outlet: A control message. The first number is a control value and the second number is a controller number.

[UncleAge]

Yes and no. I'm just getting my feet wet with Max, so I can't say for sure, but the question was posed once upon a time and the answer was no. The reason is that even if the Max instrument could parse the midi info Live won't route it. It will still just give you a drop down on the receiving track allowing only consolidated midi info. Consequence providing that option at the plugin level is a rarity I believe. And kudos to Sugarbytes for trying to address this issue.

The yes part of the answer is a little more involved. If there was a way for a Max midi instrument to exist on several tracks at once and transfer midi data inside these instances then maybe the answer is yes (think utility midi plug). Keep in mind though that this would in effect still be a workaround.

On a side note... If more users found a necessity for internal midi routing, and made more noise for the feature, then maybe the Abes would address this issue. However, it seems most host developers concern themselves more with the audio side of development and less with the midi side of things. What I found odd is that Reaper had no issue recognizing the midi outs. The Abes have been at it for much longer so it leads me to believe that the desire to address the issue does not exist within the developers or users.

[riley4reason]

yeah, Reaper is interesting in it's abilities. Thanks! Riley

[ukslice]

You could always duplicate the track another two times and turn the information off for a different instrument on each track, then route the three tracks to three new midi tracks. This is just a theory and untested.

I tried something different last night where I just cut and pasted the output from one consequence demo to three midi tracks then it was quite obvious which parts were bass, chord and lead, especially if you put the bass and lead at opposite ends of the octave settings and chords in middle. Just a matter of deleting chords and lead from the bass track, bass and lead from the chord track and chords and bass from the lead track. Then either select all notes and move to a better octave or use Lives pitch midi plugin. That worked really well. So well in fact that I am considering purchasing. The sounds aren't good enough in my opinion hence the need to export results to midi.

No reason why you can't do this split in Reaper if that works (see above) and then export as a midi track into Ableton Live.

[Silvand]

You need the Consequence 1.1 update.
Then in each instrument section you can choose the output midi channel.
The problem is that most hosts (Cubase,Live,...) simply ignore the channel.
Sorry,
Robert

Actually cubase doesn't ignore the Channel,
You just need to activate the midi filter (Input transformer) that can be found on the top of each midi/instruments track inspector.

That's the reason why, it would very interesting, for cubase/Sonar/Reaper... users, to have a multi-channel output for Thesys.

Best,
Silvand

[UncleAge]

You need the Consequence 1.1 update.
Then in each instrument section you can choose the output midi channel.
The problem is that most hosts (Cubase,Live,...) simply ignore the channel.
Sorry,
Robert

Actually cubase doesn't ignore the Channel,
You just need to activate the midi filter (Input transformer) that can be found on the top of each midi/instruments track inspector.

That's the reason why, it would very interesting, for cubase/Sonar/Reaper... users, to have a multi-channel output for Thesys.

Best,
Silvand

I'm curious... There is only one note sequencer, so, what would go out on the other channels?

[Silvand]

You're right UncleAge, When I say multi-cnannel output I mean multi-pages, each with their own Note Sequencer and dedicated channel.

[sunhome]

Multipage Thesys would be sweet I like that idea!

Regards, James

[UncleAge]

You're right UncleAge, When I say multi-cnannel output I mean multi-pages, each with their own Note Sequencer and dedicated channel.

That would be something to see! Tabbed sequencers with something like ghosted notes in the background from the other sequencers? hmmm...