Skip to content

MPK MiniMKII: Update to new Modality #287

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wants to merge 3 commits into from
Closed

MPK MiniMKII: Update to new Modality #287

wants to merge 3 commits into from

Conversation

@gilfuser
Copy link

In the device the same midi channel / numbers are used by more than one element. This would make the description of all four "Programs" messy and the use confuse. So I left to the user to edit the programs settings in the MPK MiniMKII editor to avoid the problem. Just choosing different midi channels for the different element types should do it.

Changed midiMsgType: \noteOnOff to the new way of having the same functionality using groupType: \noteOnOffBut

@gilfuser
Update to new Modality
096a3c9 
In the device the same midi channel / numbers are used by more than one element. This would make the description of all four "Programs" messy and the use confuse. So I left to the user to edit the programs settings in the MPK MiniMKII editor to avoid the problem. Just choosing different midi channels for the different element types should do it.

 Changed midiMsgType: \noteOnOff to the new way of having the same functionality using groupType: \noteOnOffBut
@LFSaw
Copy link
Member

LFSaw commented Apr 23, 2017

Thanks Gil!
I see a lot of other changes in the file though, mainly in the help section. Could you please elaborate what it is or remove them (for the sake of clarity)?

cheers

@LFSaw LFSaw changed the title Update to new Modality MPK MiniMKII: Update to new Modality Apr 23, 2017
@LFSaw
Copy link
Member

LFSaw commented May 20, 2017

@gilfuser ?

@gilfuser
Copy link
Author

Hallo lieber Till.
Sorry about the late response. I wasn't notified about your message (or maybe I just didn't see it. I'll check it).

That's the first time I do a pull request, so sorry about the lack of elaboration on what and why this description is better than the current one.

The main change I did was restricting the mapping only for the first page - or program, as called in the device.

The problem with the standard midi setup in the MPKmini is that only the midi channels 1 and 10 (0 and 9 in SC) are used. This leads to elements sharing both midi numbers and channels. This is really confusing, because when one moves one element is like moving the desired one and some rather random other to.
This already happens with one page, but with all of them, it becomes really messy.
The midi note pads overlap some piano keys from the central octave and the relative lower and higher ones.
In the first Program (or page) the bend joystick coincide with the first two knobs. Apparently there's nothing to do about that.
If you think I shouldn't worry about that and just map everything as it is, please tell me.
For my own use I made a midi setting, using the mpk midi editor, without any overlapping and a more rational use of midi numbers and channels. And also a corresponding MKtl description. If you think it worth, I could gladly share both files.

Here are some images attached, from the editor, that illustrates the case. I marked some of the overlaps, but with some extra patience more can be found.

cheers

mpk-mini-prog4
mpk-mini-prog3
mpk-mini-prog2
mpk-mini-prog1

@gilfuser
Copy link
Author

The images are in the reverse order somehow. So the first one is from the fourth program.

@LFSaw
Copy link
Member

LFSaw commented May 23, 2017

Thanks @gilfuser. I cannot test the behaviour (no MPK here :) ).
Is it possible to save the custom mapping as a sysex file? then we could add this and the factory default to the specialMessages in the description. Just like done in korg-nanokontrol2.desc.scd (scroll waaaay down...).

This would mean that people could use your updated description with a custom mapping, and go back to factory default.

@LFSaw
Copy link
Member

LFSaw commented May 23, 2017 •
edited
Loading

(and don't worry about being late or unfamiliar with the process, so am I :) I'm happy to have you taking part! )

@LFSaw LFSaw self-requested a review May 23, 2017 08:21
@LFSaw LFSaw added this to the Release 0.2.5 milestone May 23, 2017
LFSaw
LFSaw reviewed May 23, 2017
View reviewed changes
Modality/MKtlDescriptions/akai-mpkmini2.desc.scd Outdated
shared: (\midiMsgType: \noteOnOff, \midiChan: 9, \spec: \midiCC, \elementType: \pad),
elements: ((36..38)++(40)++(42..53)++(55)++(57)++(59..75)++(82)).collect { |i|
(key: (i).asSymbol, \midiNum: i)
key: \pnB,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why are the pads not named pad anymore?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just reviewed this and made some changes

@gilfuser
making a group for all pads
08c3eb8 
Changing again to name properly pads as 'pad'.
I was trying to make the path to the elements shorter, so to access and element, i.e a pad in the hardware Bank A from the midi cc message type, one could just write elAt(\pcA, x).
The two problems with that are: there's no "pcA" anywhere else in the Modality descs, and also would not be easy to treat all the pads, or all the pads from the bank A as a group, so it is less modal.
I'm then reintroducing a longer path, but I think is for the better. I accept suggestions about naming the pads. I'm calling them \note for the midi-note-type ones and \ccm for the cc-midi-type.
@gilfuser
Copy link
Author

Hi Till.

About what you asked two days a go.
There no documentation about sysex messages and the MPKminiII in their's website or manual. All the information points to the editor app.
I was trying to "extract" the sysex messages from the MPK mini Editor, but I couldn't.
Maybe there's a way, but I couldn't find it. The app uses a file with the extension .mk2. I tried to see what is inside it as text, but had no luck.
I also tried to monitor the midi activity while transmitting the setups. But the editor and a midi monitor can not be connected to the midi port at same time. Again, maybe there's a way.

cheers

@LFSaw
Copy link
Member

LFSaw commented May 27, 2017 •
edited
Loading

I installed the MPKmini editor and was able to spoof on its output with this software:

https://www.snoize.com/MIDIMonitor/

(if it says that it cannot find its driver, close all MIDI programs and disable the IAC bus in AudioMidiSetup )

@LFSaw
Copy link
Member

LFSaw commented May 27, 2017

screen shot 2017-05-27 at 15 56 58

screen shot 2017-05-27 at 15 57 24

screen shot 2017-05-27 at 15 57 48

@gilfuser
Copy link
Author

Hi Till.
I couldn't find a way to do it in Windows. I'll borrow a Mac to do it.

@gilfuser
Copy link
Author

MIDI-OX is the app that I suppose it should serve for that in W. But it doesn't appear in "Output".

@LFSaw
Copy link
Member

LFSaw commented Jun 5, 2017

any update on this?

@adcxyz
Copy link
Contributor

adcxyz commented Jul 8, 2017

@gilfuser - can you also store this setup as a file for the MPK editor?
If so, you could also commit that as well, and instruct people how to load it.
This is how the beatstep relative desc does it.
The sysex specialMessage would be nice to have, but if it's too time-consuming,
we can also drop it and use the file/editor.

@gilfuser
Copy link
Author

gilfuser commented Jul 8, 2017 via email

This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@LFSaw LFSaw LFSaw left review comments

Assignees

No one assigned

Labels

desc files

Projects

None yet

Milestone

Release 0.2.5

Development

Successfully merging this pull request may close these issues.

3 participants

@gilfuser @LFSaw @adcxyz