General MIDI editing workflows

Kai_NI · 2024-02-29T09:20:45+00:00

There was an error rendering this rich post.

Kai_NI

As a user,

I want to be able to mute, cut and merge MIDI events in the Pattern Editor / Piano Roll

in order to

apply common, state of the art workflows within Maschine.

This feature may include but is not limited to the interactions specifically mentioned above.

Find more posts tagged with

Implemented

Status: Implemented

Comments

LostInFoundation

@Kai_NI just a general comment concerning all the threads:

Good format, streamlined, concise, direct, without too many things that would distract.

Good job

theviirus

(Edit: oops misunderstood the format)

As a user: extend this to midi cc / automation too. Being able to copy automation (with or without notes) would be nice.

ozon

May this also include transformations?

In addition to transpose there should be a couple of mathematical/geometric functions available:

time stretch by factor (2x, 0.5x as presets)
pitch stretch by factor
reverse (classical use, think J. S. Bach)
inverse (classical use, think J. S. Bach)

theviirus

I think the thing that would make for the greatest workflow improvement for midi related editing and automation is the suggestion I made previously. Ill repost part of it here because it got 4 votes and I really think this would improve a workflow by eliminating a couple button presses for me. Its literally moving the midi macro view into an effect device.

https://community.native-instruments.com/discussion/comment/116554#Comment_116554

MIDI macro view, as a device in the plugin view of a "sound".

... Example. Sound 1: [SH01A (midi)] [overdrive] [EQ] [chorus] [ + ]

... Example. Sound 2: [reaktor midi processor (midi)] [SH01A (midi)] [fx1] [fx2] [ + ]

Per step editing/automation/"p-locking" is a lot easier when I don't have to tab between two different menus.

Kai_NI

Hey all,

I have created this thread here for the conversation around the what, how and why of the "Feature Ideas" section in general:

https://community.native-instruments.com/discussion/27613/feature-ideas-section-format-questions-and-clarifications/p1?new=1

It would be great if we can use the separate thread for the meta conversation and keep the conversation around particular features on the respective idea threads.

Many thanks in advance for your support!

b-righteous

I don't see simple mute/solo automation or retrospect/capture midi so listing here.

Pattern append/merge and split.

+1 for time stretch midi (double/half)

+1 for proper automation copy/paste and automation follows events.

Fix busted cop/paste behavior so it copies as expected without forward positioning and offset pitch.

ozon

@b-righteous wrote:

I don't see simple mute/solo automation or retrospect/capture midi so listing here.

FYI, there's a whole thread on Automation improvements, which is currently read only and will be worked on later:

https://community.native-instruments.com/discussion/19898/automation-modulation-improvements

Pattern append/merge and split.

Maybe this would be the fitting Story for such a request.

https://community.native-instruments.com/discussion/27165/crop-pattern-based-on-selection

Bit I have to admit that the seem to be on different levels of detail. General MIDI Editing Workflow is quite broad, and Crop Pattern based on Selection seems like a sub-feature of that.

b-righteous

https://community.native-instruments.com/discussion/comment/140936#Comment_140936

You are right about the mute/solo.

Pattern append is different from the crop pattern request. What I mean is the ability to glue two different patterns together. I did forget to mention after touch support.

eclipxe

Need the midi editor to be locked to a key/scale

theviirus

Maybe this is specifically Maschine Plus, as I don't use the software much...but my interest is in the M+ not the software.

As a user, I want to configure midi program change as part of the midi settings for each maschine sound channel.

In order to, ... recall programs and presets on external hardware by sending midi program changes immediately on project load. Midi program change should also be sent on "double tap stop". This would allow me to load a project and just press play. This would also greatly help anyone in a live performance situation because no one wants to do the "preset tap dance" just to start the next song with the right sounds/patches/samples/effects. It only gets worse and wastes more time when you need to do it on multiple hardware units.

Why I think this is relevant to the topic? This make it difficult to start or resume work on maschine plus. These features have been a part of almost every midi sequencer and daw I've used in my life but are missing from Maschine plus.

The "lock state" trick from Tetsuneko is how I finally got Maschine to do midi program change... but I should not have to do the lock state trick for project recall.

ozon

https://community.native-instruments.com/discussion/comment/147134#Comment_147134

And this, Ladies and Gentlemen, is how you write a proper User Story! 👏🏻

IMHO, regardless of category, this request could be directly submitted to the team and prioritized.

@Kai_NI what do you think, is there anything similar already in the backlog or should it be submitted as suggestion in the beta program?

D-One

https://community.native-instruments.com/discussion/comment/147134#Comment_147134

Excuse my potential ignorance, but why not just have those PChanges as modulation in your first (or even all) Patterns? As soon as you pressed play it would send them just as you're saying about that custom Stop feature.

Anyway, not sure that suggestion is quite on topic, theres tons of things lacking "that make it difficult to resume work" but sending the data on project load would be a great adition.

ozon

@D-One wrote

Excuse my potential ignorance, but why not just have those PChanges as modulation in your first (or even all) Patterns?

I‘m not sure how those PC events can be created and positioned on the M+.

And depending on the number of Groups which control external devices, you might need to create several „init“ Patterns.

theviirus

https://community.native-instruments.com/discussion/comment/147265#Comment_147265

1: Sending midi program change on every pattern cycle leads to drop outs occasionally when a preset that is still sounding is called up a second time...cutting off the previous note. Any edit youve made to a sound gets reset on pattern play or loop. This also does weird things to programs with their own clock (e.g. arps) and can lead to dropped notes, stuck notes, muted voices, timing issues.

2: Double tap stop is not a custom feature in my opinion. In almost every other midi or digital audio environment I've used since 2000, double tapping stop: returns song position to zero (and sends this for midi clock, midi time code, and even smpte i think), sends note off to all midi channels, (re)sends midi program change on all channels. For the octatrack and mpc, it also stops all audio sample playback and all audio processing (flushes all effect tails). For the OT it mutes all audio channels until the first audio "trig" occurs after pressing play. For Logic, Live, and other DAWs, it does almost all of these things on double tap stop too.

I don't expect full feature parity. But if we are talking "general midi" functionality, its not too leftfield to expect this relatively standard functionality. I'm also not trying to be too harsh about this, but this is a real headache right now.

D-One

Well, tbh a survey about what most important on and for the M+ crowd specifically would prob be more useful than all these general Maschine ones we have gotten the last few years, since the M+ is recent and doesn't have decades of standing feature requests. That's another topic tho...

https://community.native-instruments.com/discussion/comment/147296#Comment_147296

You can, with a Macro, but for that you gotta set it up on the computer first, then save a template I guess.... It's certainly not user-friendly tho, to say the least.

If the PR is tied to Pad Output then a Pad can only send 1 PR, sounds extremely limited to a single workflow to me... what if X user wants to change a synth patch midway through a Scene/Section? Having it tied to Patterns makes more sense (to me) and can already be done it would just require a way to set it up without a computer. It doesn't even need to be fancy, just a "rotate a knob to select the MIDI data type" kind of thing.

If I am not mistaken that's how the AKAI Force does it, tied to Clips which I think is the equivalent of Patterns in the Maschine world.

https://www.youtube.com/watch?v=37mfPILCVgw