Will the next Maschine Plus Update be a paid update?
If it is, will it be paid for separately from the Maschine 3.0 update, or be included with the Maschine 3.0 update?
Comments
-
I do not know, but my guess is. If there will be update of Maschine Plus to Maschine 3, which I doubt a bit, it will be for free.
My guess is Maschine Plus MK2 will come instead. If NI wants to go on with standalone HW. Stronger HW than M+ mk1 is IMHO needed for more advanced plugins and so…..
But that is just my guess. I know nothing about NI plans and HW/SW prepared.
0 -
The Developer Team has already anounced, that they are working on M3 for Maschine+ and it will be published soon. Can't say anything about the price or if it is free.
1 -
Mathieu say it would be free
1 -
I think the Maschine 3 update for M+ OS will be free. However, you will also need a Maschine 3.0 license if you ever want to open your M+ 3 standalone projects on the desktop.
2 -
How is it that Akai are working with less, but provide more in terms of the number of plugins that run on the hardware? We don't necessarily need every Komplete Synth/Sample Library inside of Maschine+, I think we just need an array of built-in instruments with "Maschinified" interfaces, like they did w/ Polysynth & Bass Synth. How cool would it be to have mutable instruments oscillators or something in standalone?
3 -
thank you. I was just wondering if I’ll have to pay twice. :-p
0 -
How is it that Akai are working with less, but provide more in terms of the number of plugins that run on the hardware?
Because M+ has SW ported from computers. One reasonably expects that plugin sounds the same on computer and on M+. So, M+ must be able to handle plugins that have been designed for PC HW, which are generally stronger.
I do not know how Akai compares hardwarevise to M+, but if its HW is weaker than one of M+, plugins may be 'optimised' (simplified, stripped down) so that they may run well on its weak HW.
M+ has been, IMHO, rather weak (CPU, RAM) even in time of release (2020), not speaking about now…. HW refresh would suit it, IMHO.
Good to hear that M+ gets support and Maschine 3 will be ported to it and for free.
1 -
Yes Akai do generally make their plugins work on the desktop version and standalone - but they charge for them, and IMO quite high prices for what they are/do.
The MPC scenario is very similar to Maschine. Projects made on hardware can be transferred to software and vice versa.
Much like the curent NI situation though, with Maschine 3 being desktop only, Akai's is the reverse. Their MPC 3 is standalone only - and there's no ETA for the desktop version.
1 -
Anybody know what the Arturia Astrolab is running, in order to play presets from their various plugins? Cause that's another way to approach things…
0 -
Google is telling me the underlying system is Linux (as is usually the case with similar standalone units).
0 -
I guess what I meant was that they should look into creating truncated versions of their other kontakt , ensembles that are essentially preset players (But also, not auto-sampled/multi-sampled). So like, instead of having full access to all the A/B, FX, and Sequencer sections of some of the Play Series, you'd just get a handful of parameters that would be useful for live performance. (Maybe the user could even define what macros show up, like they do with Massive?)
0 -
I think here are two differences to blame for the difference in perception/perspective:
Firstly, i think NI kinda shot themselves in their proverbial feet by loading M+ with Monark, Prism, Raum etc. These are certainly a big draw to the M+, but they're CPU-heavy enough to immediately show the limits of the system. The same can be said of the Maschine kits from the expansions, which come so loaded with effects on both sounds and groups, that even from a fresh boot and loading one kit, I get terrible crackling/stutters.
Secondly, MPC has a long history of being used in a sampler-centric capacity, focusing on the chopping and resampling of audio material. This is generally on the opposit en of the CPU-usage spectrum. Even melodic sounds would likely be cut from single samples from audio loops.
Philosophically, MPC seems to be more of a ground-upwards approach, and with a workflow that works just as well now as it did on hardware way more underpowered than what we're using today.
As a quasi-DAW, M+ is pretty underpowered. But from a (re)sampling/groovebox perspective (even more so with in coming bounce-in-place), theres no reason why great music can't be made without going anywhere the near the limits of the CPU.
When I bought the M+ a few months ago i knew full well about the CPU issues. I was fully prepare for it and actually welcomed the idea of a sampling and resampling workflow, along with having to commit to ideas to keep moving long. Even so, I still couldn't help but be really disappointed the CPU stuttering with jut one kit loaded. Now I know that kits are just ways to give an idea of the available sounds in an expansion. I will just have to build my own kits.
Just my 2c
3 -
many kits have sounds loaded with several effect chains and if you want to combine kits you’ll max out the M+. But for me personally I browse kits and mark my favorite sounds, find them in the browser and load them separately, or just erase/clear unnecessary pads/sounds, and move the sounds to the same group. But tbh I find myself searching more in the one-shots rather than kits lately when it comes to drums at least. I use monark for basses and of course resample and inactivate monark, and so on. Fm8 and prism and massive all have really cool sounds and stuff, but I mostly resample just to save cpu. Mute the pad where the heavy synths are loaded and you’ll save without having to clear the pads. The drum/bass/poly don’t eat much cpu, so they’re no problem. I build my track within M+ as far as I can go, but when it’s time to finish a track I transfer the project to my laptop, turn off all fx, reset the volumes and pans and all so I have a good way export and finish my track in logic. All my synths are still loaded but muted in the project so I can continue changing chords or whatever when I continue in logic. So the limitations of the cpu are real, but I don’t need that kind of power in the M+. I have it when I need it in my M1 when it’s time to finish the job.
1 -
There are also some issues with my M+ - while playing single synth sound using fast and short notes. But when playing patterns/songs M+ can handle quite high count of groups playing simultaneously. I have a project with around 20 groups overall with about 12 playing at the same time, with lots of samples, synths and FX, and bit of automation. And M+ handles it perfectly, with max CPU load around 72%. Honestly speaking i didnt expect this, so it looks like its powerful enough :-) But there are some bugs of course, and i suppose one-kit-stumbling is one of them. And it needs to be reported, investigated and resolved. Otherwise the whole point of 'M+ is an instrument' vision is useless because sometimes its just impossible to play it. Please also take a look at these two threads, maybe such issues are looking familiar to you too:
0 -
Yeah! Pretty much SW and Plugins built from the ground up to be efficient in Standalone that also work on regular computers as a secondary priority
VS
SW designed for desktop computers that was ported over to a also work Standalone.
0
Categories
- All Categories
- 19 Welcome
- 1.5K Hangout
- 62 NI News
- 785 Tech Talks
- 4.1K Native Access
- 16.5K Komplete
- 2K Komplete General
- 4.3K Komplete Kontrol
- 5.7K Kontakt
- 1.6K Reaktor
- 378 Battery 4
- 845 Guitar Rig & FX
- 429 Massive X & Synths
- 1.3K Other Software & Hardware
- 5.8K Maschine
- 7.3K Traktor
- 7.3K Traktor Software & Hardware
- Check out everything you can do
- Create an account
- See member benefits
- Answer questions
- Ask the community
- See product news
- Connect with creators