More information on future updates M+

1192022242529

Comments

  • Rico010
    Rico010 Member Posts: 137 Advisor

    I work for a big outsourcing (software engineering) company, and we do engineer some of big name DAWs out there. No conflict at all. NDAs exist for this, and teams are split by secured locations as well.

  • LostInFoundation
    LostInFoundation Member Posts: 4,466 Expert

    can you imagine the backlash if people are required to wait/buy a new M+ HW model to be able to use this new architecture/gen for MAS v3? People would rage… badly

    Are you sure about this? Because it sounds a lot like what just happened in the Komplete world…and not only we didn’t have a backlash…for every user complaining, you can even find another one justifying them and saying that it is normal, that in technology we are even lucky to have a product for 8 years, because after it’s too old and it’s correct to put a perfectly working device EOL,…

    The ones raising their voices are simply relegated in a “niche/powerusers/complainers” category and ‘till the others still buy/preorder/switch…”who cares, move on”.

    And…no… NI is not scared of outsourcing…they are ALREADY doing that

  • olafmol
    olafmol Member Posts: 213 Pro

    Oh ******! Introducing an new generation of hardware, with a different architecture, while not upgrading your current core range of software that deeply integrates with your hardware. What can go wrong? ;)

    As said above, the only viable way to get out of that mess would be to have a "legacy translation layer" inside your software. But this does cost engineering capabilities, and maintenance, and it's not cheap at all.

    Fingers crossed…. but this sounds like an accident waiting to happen tbh.

  • MaikR
    MaikR Member Posts: 327 Pro

    Could (not) do versus Should (not) do. Little bits of history repeating or innovation in times of sustainability goals…?

    Of course we could take some ‘old’ (IT) practices for granted, but NI should also look at decent future support models.

    Ableton Push 2 is even older then M+, and it still did get some really nice feature updates after the release of Push 3.

    Elektron is also well-known for supporting there (older) hardware, even after the release of newer models.

    Not meant to start an in-depth feature discussion or platform comparison, just two examples of these kind of customer-friendly and sustainable business models.

  • MaikR
    MaikR Member Posts: 327 Pro
    edited October 14

    Just to ’bump’ this one over the weekend and into the new week… @Simon_NI

  • tetsuneko
    tetsuneko Member Posts: 794 Expert

    I doubt M+ is going anywhere. I'd say support for Maschine 3 for M+ is not a matter of "if", but a matter of "when"

  • AdelV
    AdelV Member Posts: 339 Guru

    They are waiting because Maschine 3 has higher priority than M+ firmware update in my opinion. And Maschine 3 update SW is planned for November. M+ Should be around the same date but it can be even next year. There is a lot of TO DO in terms of compatibility od both standalone and SW.

    🙈🙉🙊

  • D-One
    D-One Moderator Posts: 3,575 mod
    edited October 14

    Wasn't this pretty much confirmed by stating that Machine SW V3 is the current priority? At least that's how I interpreted it.

    Pretty sure of that too, the question is will it have all the bells and whistles of v3? Will it be a situation not as bad but similar to that of the KK MK2 VS MK3? Both for standalone and controller mode? 🤷‍♂️ Not doing 100% of whatever the new gen is doesn't necessarily mean "it's not supported" or going to die off.

    Possible? Very likely… worth the time and R&D from their POV with so much to do: Very unlikely.

    IDK, maybe its a perspective thing, personally I have never seen so much backlash in a KKS launch before and I was here for all but I must admit there might be some confirmation bias in my POV but i seriously doubt KKS3 has been selling like KKS Mk1/mk2 did. The M+ also doesn't have as wide range of users as KKS so I think people would complain a lot more.

  • LostInFoundation
    LostInFoundation Member Posts: 4,466 Expert

    Frankly…I HOPE people (eventually) will.

    What I see between NI customers is a little bit of disillusion….which leads to acceptance of everything.

    When I think about a backlash, I think about something that forces the company to step back (see Waves case). Not users complaining and the company continuing on its way (probably because they sell anyway)

  • D-One
    D-One Moderator Posts: 3,575 mod

    Backlash is just people complaining, it literally means "negative reaction"; if the company listens or not is another story.

  • darkwaves
    darkwaves Member Posts: 433 Guru
    edited October 15

    I assume maschine 3 will be released for desktop first. That's coming in November-ish. I'm not worried about that. I'm building a new computer soon and am not sure I'll even install maschine. "Maschine" is M+ for me now. I'm selfish and don't like being put on the back burner, but I understand their priorities.

    I assume maschine3 will make it's way to m+ sooner or later; but I'm expecting laaaaaaater.

    I'm hoping the firmware doesn't need to wait for maschine3 to make it's way to M+. I'm sure whoever "owns" maschine+ as a product on NIs side would probably like to ship as many changes in a single update as possible. Please get the firmware update out and then go back to whatever other updates are planned.

    They first hinted at this firmware back in march. I get it; priorities change. Not complaining (much). I'd just really hate to see this get pushed back further while waiting to get Maschine 3 working on M+ unless absolutely neccessary:

    lol. I didn't even realize the post I went search for was from page 1 of this very thread. Go figure

  • MaikR
    MaikR Member Posts: 327 Pro

    Some new bits…

    Maschine Plus related:

    What about Maschine+?

    Maschine+ is not affected by any of these changes.

    How long will you continue to support the current Maschine MK3 and Maschine Mikro MK3?
    Maschine MK3 and Mikro MK3 are the current generation of our products and we have no plans to end support for them anytime soon.

    The affected products are only the MK1 and MK2 generations of Maschine, which were released between 12 and 15 years ago. For an electronic device with desktop computer integration, this is quite a substantial age. And as mentioned, the main reason for us to retire them is to allow our software products and technologies advance to a degree that we could not do whilst still supporting those devices.

  • MaikR
    MaikR Member Posts: 327 Pro

    This metaphor… LOL 😅

    And yes, that’s why I like to concentrate the bits and pieces into one single M+ topic.

    Then again, awaiting some answers to my previous questions on the new architecture and how this will or will not affect the architecture (and future) of Maschine Plus.

    So hopefully @Matthew_NI @Kaiwan_NI or @Simon_NI can answer these, too.

Back To Top