Maschine 3.0 General Discussion

1…1819212324…27

Comments

  • naturaldichotomy
    naturaldichotomy Member Posts: 18 Member
    https://community.native-instruments.com/discussion/comment/188955#Comment_188955

    word!!! 🤜🤛

  • ozon
    ozon Member Posts: 1,807 Expert
    https://community.native-instruments.com/discussion/comment/190038#Comment_190038

    It is possible … as long as the editor supports them, and drivers are available for current OS - which is not the case for MK1 on macOS. Given that Maschine kontrollers are kompletely dumb (and therefore are kompletely kontrolled by the software), it’s a decision not a necessity to abandon them.

    https://community.native-instruments.com/discussion/comment/189970#Comment_189970

    Matt somewhere mentioned that there are millions and millions of Maschine users. Many having more than one Maschine controller, most of them now obsolete. Imagine a pile of one million Maschine Mk1 rotting on the beautiful beaches of Ghana. Because that’s where they end up…

    https://en.m.wikipedia.org/wiki/Agbogbloshie

    https://de.m.wikipedia.org/wiki/Elektronikschrottverarbeitung_in_Agbogbloshie

  • tetsuneko
    tetsuneko Member Posts: 779 Expert

    ahh so the MKI/ MKII Maschine controllers are not class compliant MIDI devices? Well that just made things close to impossibiru.. Thank gods we at least have CC MIDI devices these days

  • ozon
    ozon Member Posts: 1,807 Expert
    https://community.native-instruments.com/discussion/comment/190148#Comment_190148

    Neither is the Mk3. AFAIK, all NI controllers need drivers.

  • tetsuneko
    tetsuneko Member Posts: 779 Expert

    Whatt! I didn't expect that. MK4 controller family better come with class compliant USB MIDI as a fallback option.. requiring proprietary drivers for MIDI controllers is so early 2000's, get on with the times FFS

  • Milkman
    Milkman Member Posts: 269 Advisor
    https://community.native-instruments.com/discussion/comment/189901#Comment_189901

    The inclination for people who represent brands to say "its only you having this issue" is extremely, extremely frustrating, and is why I left Steinberg years ago.

    No, it isnt just me experiencing issues between BWS and maschine. There are many others who complain about that integration on KVR and elsewhere, as well as on these forums. Dont "you are all alone" with me, thanks. You can see them lining up in suggestions forums, asking for better integration.

    Let me be more specific, if I can: my templates were all built in 2022-23 - templates with maschine2 as an instrument track, receiving MIDI from several MIDI tracks each on their own channel. I was able to read and write MIDI for each track without using the maschine sequencer. This worked for YEARS and for 100+ projects.

    Then, I cant put my finger exactly on when it happened — January-February 2024? One day I loaded a project with that identical template and I got errors from BWS about "feedback loops detected, audio engine stopped" on THE SAME TEMPLATE I had been using for 15-18 months or so.

    I started an email chain with BWS support — BWS accepted the issue, and they were able to reproduce it in their test environment. Next, they said they would put me in touch with the developer, but then I didnt hear back…. so I also sent support requests and forum post to NI - also didnt hear anything back or I got very generic, unsatisfying replies.

    So I worked around the problem and stopped worrying about it. I could have gone back and yelled at support some more, but you know Im getting exhausted with brands that make me do this and I just prefer easier relationships overall.

  • D-One
    D-One Moderator Posts: 3,559 mod
    edited November 11
    https://community.native-instruments.com/discussion/comment/190267#Comment_190267

    I didn't say it's "only" you in the sense your the only one in the world, I said its a problem for you as in it could also affect others, sure, but it's not widespread… Given my activity if problems are widespread I would know, I really mean no offense or to be confrontational. I was offering you help… If you do not want it, its fine. Carry on I guess.

  • fabsonsan
    fabsonsan Member Posts: 7 Member
    edited November 12

    Mk2/Mk3 are class compliant for macOS, not for windows
    MK1/MK2 driver should work on Windows 10/11, ( win7 and above)
    MK1 user on mac where fkt with the introcdution of macOs catalina, for some follow up os version, some user where able to use a workaround (check the reddit link, the post is 5years old).

    I remember, i was working for an engineer for embedded systems at that time, and he nuked his place with f bombs, after upgrading to catalina. i had to laugh so hard, i think that was the first time mac users experienced, what windows user experience with every windows update cycle for years

    Here are some starting points for workarounds.. but outdated, i doubt it's really helpful, sorry

    (https://www.reddit.com/r/NativeInstruments/comments/ei8mn1/comment/hygc6f8/?context=3)


    (https://support.native-instruments.com/hc/en-us/articles/360000334278-Operation-of-NI-Legacy-Hardware-Devices-on-macOS-10-12-10-14)

  • Ed M
    Ed M Member Posts: 151 Advisor
    edited November 12

    The stem separation works great, and is better than Serato sample in my opinion. Other than that the 3.0 update isn't a full version update in my opinion. Because of the low update price I don't feel robbed, but it's a close call.
    I hope, and assume more is coming in the future.
    I was hoping the 3.0 update would get me to use Maschine again. I am sad to say this is not the case.

  • Eric Rabb
    Eric Rabb Member Posts: 47 Helper
    https://community.native-instruments.com/discussion/comment/189734#Comment_189734

    Definitely a sole single coder here. I’m just gonna do whatever, bump it if they like it or not. This is what it is huh? I’m not a fan either. I hate to ask for a customizable GUI, but that’s what’s needed here. 🤦 again. That should’ve been super simple. Plug in delay compensation if implemented, would be a hit! Again my .2cts #MakeMaschineGreatAgain !!!!

  • ozon
    ozon Member Posts: 1,807 Expert

    @fabsonsan wrote

    Mk2/Mk3 are class compliant for macOS, not for windows

    According to several online sources (not NI, which claim they are class compliant), it seems that the Mk2 MIDI interface is class compliant, and the Mk3 audio interface (but not MIDI) is class compliant, while the controller pads/buttons/encoders don’t work at all without a driver and the proper software. This is a hot topic for musicians who want to make music on their mobile devices and were hoping to use Maschine hardware as MIDI controller.

  • nicholasbinder
    nicholasbinder Member Posts: 15 Member
    edited November 12
    https://community.native-instruments.com/discussion/comment/188832#Comment_188832

    What do you mean? Yes, of course the scale is set on-device, but you're communicating with the DAW via a controller script (depending on the DAW), aren't you? Or how else are you able to display track levels on the Mixer page?

    EDIT: Just to make this clear, I'm happy about the on-device scale integration. I just immediately assumed it would follow the scale set in the DAW, which would've made sense to me since there's DAW integration already. Also I don't want to hijack this thread, but if scale-following is impossible to do because of technical limitations, knowing this would be of interest to me.

Back To Top

Categories