MIDI Merge (Inputs 1 and 2) to MIDI OUT A

Hello,

Is it possible to use the MPC (OS JJ 2XL ) as a MIDI merger of MIDI in 1 & 2 in realtime to MIDI out A ?

Thx

Yes

tarbaby wrote:Yes

Can you explain how to merge the two (cc change and all other messages to the same out)?
Thanks TYPO

In A/B are always merged... As long as in mode/9 f1, active receive track is set to "all" & soft thru is set to "as track".then go to a midi track in the sequencer main page, set midi to out A.

tarbaby wrote:In A/B are always merged... As long as in mode/9 f1, active receive track is set to "all" & soft thru is set to "as track".then go to a midi track in the sequencer main page, set midi to out A.

When you send different messages on various tracks to external devices (daw hardware )Please explain
further.Soft thru is not going to trigger my efx,apeggiator,program change,and various midi messages sent out to a single MIDI OUT(no merge of A B possible that way)
Help me to understand. TYPO

TYPO wrote:

tarbaby wrote:In A/B are always merged... As long as in mode/9 f1, active receive track is set to "all" & soft thru is set to "as track".then go to a midi track in the sequencer main page, set midi to out A.

When you send different messages on various tracks to external devices (daw hardware )Please explain
further.Soft thru is not going to trigger my efx,apeggiator,program change,and various midi messages sent out to a channel merged in to one MIDI OUT.

Ok I guess I'm not understanding you.I have 2 keyboards both are connected to the midi In's on the Mpc. Both will send midi notes, cc's etc at the same time to the active track.If that track is a midi track it will send it to the midi out of that track.I can record input a & b on to that track. And then do the same on other tracks. Is that what your asking?

O.K. this is where we have a miss understanding.I am not talking about recording into the mpc on A+B.
I am talking about both recording and sending out midi(ALL MIDI DATA)to external devices.All cc and on every track A+B
And I must say JJ made this much easier.Peace TYPO

I know, this is what I've been screaming about. The Mpc channelized all midi input. I want to control the midi volume & pan settings on my modules & vsti's. So when I load a project,all of the midi & pan settings were just like I saved them.the only way to do that now is to record it with the q links, for each track. But that would be automation of every parameter. I like how when you change a sequence the Mpc sends out program change & bank change messages for all tracks that use them.

If he used that same principle for the track mixer, that a track can send volume & pan info for a track assigned to a midi output, per sequence,you can then use a midi fader controller for internal program & external midi tracks.Or just use the track mixer that's already in place...but I guess I'm the only one.

Here is my take on the JJOS 2XL.I feel that he has given you the midi monitor so you have to adjust.

I am not happy with the state of the mixer (dare I say)the akai was better.Less is more sometimes.

If (and I think it was you)somebody could get the midi mixer into place it would be a great improvement.

PEACE TYPO

.....I agree with you 100% Typo. But when it's so many voices screaming @ 1 time. It's hard to get heard.No matter how logical it is to have a MIDI production center, to send MIDI info such as this.

IMHO opinion i totally disagree bout the mixer.... its ok, not for midi guys but for volumne. MPC1000 will as stated by tarbay, record multiple midi channles to active track. All midi ccs are recorded onto active track from whatever channle used when set up as tarbaby suggest. Also use edit to copy and merge midi cc data but this is not real time of course.
What is wrong with using midi cc for volume to your synth like i do. So when i load project all volumnes and panning info for external synths are set as you want them. Easy Do thios instead of winning about how jj os aint good enough.

bliprock wrote:IMHO opinion i totally disagree bout the mixer.... its ok, not for midi guys but for volumne. MPC1000 will as stated by tarbay, record multiple midi channles to active track. All midi ccs are recorded onto active track from whatever channle used when set up as tarbaby suggest. Also use edit to copy and merge midi cc data but this is not real time of course.
What is wrong with using midi cc for volume to your synth like i do. So when i load project all volumnes and panning info for external synths are set as you want them. Easy Do thios instead of winning about how jj os aint good enough.

Who is winning about JJOS not being good enough?I do not care.I only feel you should research midi
merge and come back with a logical solution.Lets see TYPO

TYPO wrote:

bliprock wrote:IMHO opinion i totally disagree bout the mixer.... its ok, not for midi guys but for volumne. MPC1000 will as stated by tarbay, record multiple midi channles to active track. All midi ccs are recorded onto active track from whatever channle used when set up as tarbaby suggest. Also use edit to copy and merge midi cc data but this is not real time of course.
What is wrong with using midi cc for volume to your synth like i do. So when i load project all volumnes and panning info for external synths are set as you want them. Easy Do thios instead of winning about how jj os aint good enough.

Who is winning about JJOS not being good enough?I do not care.I only feel you should research midi
merge and come back with a logical solution.Lets see TYPO

I did give answer so just in case i wasnt clear here is a bit more detail......just select a midi channel thats 1 -16 A, set midi through to active track. all midi from any midi channel - A1-16 or B1-16 will be then sent through to this track and can be recorded or passed through to another device.(IT MERGES). I use this everyday, as I have many midi channles running to external synths and using above method i can control any cc on any synth with other synths by just selecting the active track that corresponds to device you want to control. You should also concern yourself with the midi cc mapping so all the same cc's correspond to the same funtions on all your midi devices. IE if you send cc76 to other device it might not be same parrameter. Do you get what im saying?
So RTFM and make sure you are sending correct cc, as not all devices are mapped to same midi cc's. So it might be merging but midi cc might be wrong for your device so then no effect.