Maschine 3 - Requests & tips for improvements

Sunborn
Sunborn NKS User Library Mod Posts: 3,296 mod
edited November 2024 in Maschine
image.png

This discussion was created by comment split from: About your ideas for Maschine 3, where at least half of the comments was irrelevant (something that i find extremely annoying in conversations).

This thread is exclusively about Maschine 3 software.
NOT about Maschine + or any other hardware or software, neither about complains or problems.

So please keep it clean and focused on the specific subject. Or, simply go to the thread mentioned before. Thank you.

Tagged:

Comments

  • Maxray
    Maxray Member Posts: 124 Advisor

    Agreed… and those are some great ideas, btw!

    I had a few myself that I've posted on different threads before. One of them being, to make Controller Editor the main MIDI Setup software for all of the NI Hardware. Additionally, to refashion it to be more like a Reaktor interface or GUI, where we can make connections and even share connections between devices. It would make life easier when we're using our NI Hardware, like Komplete Kontrol and Maschine, in other Programs. It would also allow us to save our various setups as Template files, such as production, live performance and external controller templates.

  • DiosGnosis
    DiosGnosis Member Posts: 197 Advisor

    Polish. I've encountered some graphical inconsistencies in the GUI, CPU spikes not seen in MSW2, latency under same circumstances as in M2SW, but M2SW has no latency, and some overall rough edges when it comes to VST3 compatibility/stability. Almost all of these issues are from Plugin Alliance/Izotope plugins, partners of NI.

    In my humblest of opinions, before moving forward, fix the foundation. If I'm running the show at NI (ha!), I'd focus efforts on ensuring M3SW is a solid foundation to build from. Structural integrity is so crucial. Ask the Three Little Pigs.

  • Nikal Might
    Nikal Might Member Posts: 30 Member

    Move the plugin menu to the browser, so we can use the search function without having to create a preset for every single plugin. If I want to add a plugin via the software, I have to click the plus button, scroll through hundreds of vendors and then select a plugin. If the vendor is near the end eg Waves, it's really slow and painful. If I want to avoid it in the future, I have to save the default preset and use it to search. The nested menu system feels quite archaic compared to the browser which is right there.

    It would also be nice to have a search function or some kind of shortcut accessible from the hardware to cut down on scrolling. You get the same problem as with the software menu.

  • Blotj
    Blotj Member Posts: 2 Member

    I agree with a lot of update suggestions here, especially stability and full screen. I suspect that we could all add and add countless of these, but in spirit of DiosGnosis's comments on Polish I think I agree with that. UX/UI issues would be where I'd hit first, just to remove overall friction here.

    1 - Add editable Keyboard shortcuts, particularly zoom schemas for the various views.

    Like so many other applications, not just sound, but node graphs, video editors etc, being able to zoom in an out easily with various alt/shift/ctrl + scroll options would make editing generally more fluid and fun.

    2 - Allow vertical scaling of audio tracks, preview waves in samples toggle.

    Sometimes you need to line audio up, but not being able to visually scale in timelines makes this painful. Clips might benefit from this, optionally, too, even a vague preview as one can't easily time one clip relative to another that way.

    3 - Extend note split to clips.

    Unless I'm missing a glaring feature, it's hard to split a clip in arranger, especially long ones.

    4 - Improved lock state management, and automation curves.

    Transitioning lock states is a lovely thing. I'd love to be able to colour and name these clearly — again if this is possible, I missed it. But it feels like the arranger view could do with it's own track to fire these. Or clips could be book-ended with them. I'd love curves in general automation, too, and could see that extending to these. I like the idea of dialing in the overall sound with the current systems as is, and then having control to deploy them in this way.

    5 - Allow sound pallet scaling.

    Similar to the intent that Sunborn was saying. Playbox, for example, loads with a preset then stays that way, even if you pick something else — allowing horizontal scaling of ui here would allow us to decide what we see of a file name. The default truncation is commonly not helpful especially when working with loopcloud, for example. At the least, a tool tip that shows the full name would be helpful on mouse over.

    6 - Tuneable color pallete.

    Plenty of visually impared folks struggling with existing scheme. I like it, personally, but allowing tuneable parameters here is a good idea.

    7 - Piano Roll - Collapse key or highlight it in piano roll.

    For the less musically literate among us, and for the dyslexics who struggle to interpret the keys sideways, some help here would be good. There's also a lot of detail in this view so it would be helpful to pick out the notes we care about.

  • Kymeia
    Kymeia NKS User Library Mod Posts: 5,213 mod
    https://community.native-instruments.com/discussion/comment/195154#Comment_195154

    Thing is the browser and plugin menu serve very different functions. The plugin menu just gives you access to plugins, which won't have params mapped to Maschine (or Kontrol) knobs etc. The browser menu gives you access to everything that is mapped to the NKS standard, not just plugins but also preset banks and sample libraries.

  • Kymeia
    Kymeia NKS User Library Mod Posts: 5,213 mod
    edited December 2024
    https://community.native-instruments.com/discussion/comment/192400#Comment_192400

    All great ideas - preview generation would really speed things up and so would getting the preset name from the plugin (where possible)

    Full screen mode is there and works well for me (on Mac) but for some reason it's not working on Windows, I guess due to a bug, I don't see why it would have been deliberately removed, especially just on one platform unless it wasn't working well on Windows.

  • PK The DJ
    PK The DJ Member Posts: 2,230 Expert

    I think NI just accidentally overlooked it on the Windows build.

  • Rilkecat
    Rilkecat Member Posts: 58 Helper

    I find @Sunborn ideas great. The less mouse required the best. I suggest so:

    1- Text Entry Dialog, just like in Maschine+. For all save as screens (either presets or projects)

    2- Fix some old workflow bugs:

    a. Audio Mute gets ON after using Lock. (btw why not include Audio mute on/off for Groups too?)

    b . Volume/Swing/tempo button gets deactivated after entering+leaving Mixer (unlike with Browser/Arranger/Sampling).

    c. SAMPLER: Sample loop on 1-shot does not work, even when LOOP is ON.

    d. Cannot UNPIN Pad mode, Keyboard, Chords, Step.

    Cheers to team!

  • 6xes
    6xes Member Posts: 809 Pro

    the splitting of the 3 sections to allow for independant placement & snap-on(makes for additional vertical sizing options)

    ie.

    Scene/Pattern area

    in/out/plugins

    midi/sampler section

    recall/disabling of the independant sections as & when needed

  • Wilmar Boer
    Wilmar Boer Member Posts: 93 Advisor

    I have four main wishes for the upcoming future of Maschine 3(+). But I don't know if this is the place to post them.

    1)
    As far as battling CPU intensive tasks in the M+ is concerned it would be awesome if there could be more than 2 aux sends. Ideally a + sign next to aux 1 just like the plus sign in the plugin section. So you can add as much aux sends as you need (or max it to 8 or something). I basically setup 4 aux sends in a DAW Template with a short room reverb, a long (hall) reverb, a delay and a chorus. Now I often use the same delay or reverb plugin in multiple places because the 2 aux sends are taken. It would be great for using external (pedal) FX too, which in turn would also save CPU. But then the max inputs of the M+ is a restriction, see point 4.

    2)
    Better use of the right screen in plugin windows instead of display the plugin name in giant characters would be great. EQ curves, Gain reduction with compression, Envelope curves in polysynth, etc… The same goes for the new Kontrol keyboards. It looks beautiful, but why showing a big plugin or instrument name and only rotary controls with numbers beneath it. Use that screen estate for feedback about what is going on please. In the Maschine software the native Maschine plugins already have a GUI that would fit a small screen.

    3)
    Some love and attention to the sound and project browser. On M+ you always need to scroll a giant list of patches even after a narrow down in instruments and chategories. That makes that patches starting further in the alphabet gets used less. Some kind of randomize function or sort A>Z / Z<A would be nice along with the ability to make your own folders when it comes to sounds and project files.

    4)
    Don't restrict inputs to 4 stereo pairs. My M+ is the centerpiece in a dawless setup. My Zoom L20r can handle 20 inputs and deliver them class compliant to the M+. And my outboard gear is always connected. But M+ can only take 8 of them (4x stereo). On MPC's and Akai Force the whole connected audio interface is available.

  • Maciej Repetowski
    Maciej Repetowski Member Posts: 681 Guru
    edited February 3
    1. Bank select AND program change for external instruments
    2. Color palette is a bit too dark, should be adjustable, dark is fine for me but we should be able to change the Gamma.
    3. User definable keyboard shortcuts for all UI buttons, transport, etc.
    4. Midi learn for all UI buttons, transport, etc.
    5. Ability to completely hide UI elements, in example: when using as drum machine in sequencer, clips/patterns panel is not needed.
    6. Global setting for treating MIDI In as a drumkit, to use with keyboard controllers, without the need to always set it up in a Group.
    7. Global setting for remapping drum triggering notes in drumkit mode to different notes and octaves, i.e. C1, C2, etc.
    8. Internal Vocoder, Vocal FX and Pitch Transformer Effects
    9. Internal RTA Analyzer
    10. HiDPI interface

    That’s my „humble” list.

Back To Top

Categories