Maschine 3.0 General Discussion

1121314151618»

Comments

  • MorrisEd
    MorrisEd Member Posts: 149 Advisor

    Doubtful anyone on this forum made an “impulse purchase” considering it’s made up mainly of the same users that provided the feedback for the release. Being disappointed at spending $70 wasn’t the point anyways, rather that there are companies that charge for stuff like this and those that don’t. Akai used to be the former, and NI the latter. They seem to have switched places. That’s the point. To each their own to anyone who prefers paying for small upgrades on dated hardware while the competition is providing large upgrades to modernized hardware for free.

  • 6xes
    6xes Member Posts: 729 Pro
    edited 4:53AM

    find the best tools to do the necessary jobs… and have them all work together as one cohesive tool!!

    people need to explore the options(tools) out there…. plenty of options!

    like you & no doubt many others… we dont just use a single tool to whack together for what we want to build!

  • Beatsandmore
    Beatsandmore Member Posts: 112 Helper

    No efx which is key if not there just sound pack I can convert into the competition..

  • Bodhi Beats
    Bodhi Beats Member Posts: 17 Member

    Forgive me if this has been asked, but: is there a plan to support the "basic" Kontrol mk3 integration when Maschine is run as a plugin?

  • itsWHOM
    itsWHOM Member Posts: 4 Newcomer

    I know many are underwhelmed by this update, but as a NI user for over a decade, having both mk2 and mk3 versions of Maschine and the Kontrol keyboards, I was willing to pay $29 just for the cohesion. With the UI and navigation design language NI has been trying to streamline over the past year, Maschine's software stuck out like a sore thumb. Been using it today and yesterday and the much-needed expansion of filetype compatibility makes the sampler feel powerful all over again, I was able to import audio from an mp4 youtube video just by changing the extension to .m4a and it seamlessly imported into the sampler without a third-party conversion software. Stems separation is nice, hopefully more powerful audio routing options are coming in plug-in mode. Look forward to what's to come.

    I use Maschine as a sound module in Logic Pro and the only features I am really looking for that I don't already have is automatic multi-output routing to DAW mixer. I have a template that I made where I individually routed each Maschine pad, and if I want to add a new instance of Maschine I either have to take the time to route each pad again, or open up the template. It is a bit tedious.

    The other improvement I am curious about is the plug-in latency during tracking for the AU version of the plugin. I am aware that you can toggle SHIFT + CHANNEL twice, or press the Maschine icon in the plug-in to re-sync the audio, but this needs to happen EVERY time the Maschine track has been deselected. Not a huge deal, but still a minor pain-point nonetheless. I fear this may be a limitation with the AU architechture/Logic Pro exclusivity as this has been the case for several years, but I have hope there may be some solution.

  • 6xes
    6xes Member Posts: 729 Pro
    edited 6:42AM

    i did a test, with one of the default maschine projects…

    i dropped the maschine3.vst3 onto a blank project in inside Reaper… and the Reaper DAW goes through a process of creating 16 additional tracks and does the channel routings automatically… i then load the maschine project

    after which point i only need to set the EXT 1/2/3/4 etc for each group to record the audio onto each track

  • JEightyFive
    JEightyFive Member Posts: 2 Newcomer

    I still haven't been able to use it yet. It downloads fine, but then freezes during the initial plug-in scan. It always freezes when it scans Addicted Drums. I don't know why that specific vst freezes the program. Has anyone else had this issue? And if so, what did you do to fix it?

  • 6xes
    6xes Member Posts: 729 Pro

    does the "esc" key work?

    try pressing the esc key as it begins the scan… not sure if that still bypasses the plugin scan like it did in maschine2.x

  • ozon
    ozon Member Posts: 1,694 Expert
    edited 9:42AM

    @Lionzinio thank you for listing the locations! 👍

    Scene Tempo : via the Shift + Scene buttons

    Which I already mentioned to be available, but it might be hard to find for some.

    Bounce : Only available in Ideas mode, via the Shift + Pad Mode buttons

    I couldn’t find that, so I checked the manual and didn’t find it there either. That will be handy on the M+, as the previously available drag and drop isn’t possible.

    Stem Separation : via the Sampler edit tools like Truncate and Normalise 

    Indeed and it makes sense to find it there. I didn’t actually look for that because I have no use for it. However, I don’t expect this to become available on the M+ as, it needs a lot of CPU power.

  • MaikR
    MaikR Member Posts: 303 Pro
    edited 9:40AM

    Exactly why I’m still requesting for the version 2 update (2.18.4) to Maschine+ and not simply version 3.

    We don’t know how version 3 will perform on M+ hardware and/or what features wil become available in standalone:

    Extracted from what became a never-ending story:

  • ozon
    ozon Member Posts: 1,694 Expert

    @Milkman wrote

    Then back at the end of 2023 something changed, to do with Bitwig + maschine2 routing, and all the years of templates and projects I had suddenly stopped working, causing me to make a support request with Bitwig. Cubase routing, somehow, was not affected.

    This is probably related using Maschine VST3 instead ofVST2? A lot of developers had a hard time getting MIDI to work in VST3 plugins and some even claimed it was impossible, although others were doing it (for a long time). If the routing works in Cubase (which is the VST reference implementation) but not in Bitwig, the Problem is most probably with Bitwig and not with Maschine.

    When you try to use your DAW to route midi in/out of maschine (really just out), it introduces problems and works differently DAW by DAW.

    Why do you need to route MIDI out Maschine if you - as mentioned in a previous post- don’t use its sequence? Or is this something Bitwig does automatically (wrongly) and Cubase doesn’t?

Back To Top