Maschine 2.15 is out!
Comments
-
*standing ovation, throwing my hat*
THANKS for the info Matt!
3 -
Not sure how you mean, KK gets updated every time Maschine does with the same (applicable) features/fixes.. it shares a lot of the same codebase it seems.
0 -
I have not dug into the new autosampler, I hope to next week as I have been anticipating/wishing for an autosampler for a long time. That said, the 5 layer, 7 octave, multisample sounds I made with MainStage took several minutes to load on M+...until I upgraded my SD card to a Kingston U3, not what took minutes now takes seconds. Once I am home from traveling next week with all my studio gear and the new autosampler I plan to start building a big library of sampled hardware, really looking forward to it.
4 -
As I said in my post you quoted:
Info on KK's progress tends to be meager. It really feels that KK is treated in a second hand manner with regards to info and such.
Case in point... I have to constantly come to Maschine category of this forum to glean a morsel of information about KK.
KK category of this NI Community gets less attention from NI mods/admins.
1 -
I see what you're saying, if you mean you don't care about Maschine but feel like you need to come here.
It is strange because KK is much more widely used and popular than Maschine.
1 -
fabio machado van zeller
What i would really like is that we would talk more about "Maschine 2.15", or the other subjects of other threads. Everybody can do, write (or read) whatever they want but i think it´s strange that people complain that "they don´t listen", yet in almost every post they are complaining about the same stuff over and over again. They don´t listen so why trying.😲
99.9% of the people that read this posts can´t really do anything about your frustrations, so please reconsider if you want to continue to nag us mere users.
Also, an exercise of self conTROLL: if you feel that this post is against you personally, it is not. Can you restrain yourself and not answer to this post that is really not asking you anything? 🍿
I've just looked back through the whole of this thread to see what might be upsetting you so, and I'm still puzzled.
The majority of the posts are actually about 2.15.
The fact that it was in theory released in an unfit state, which meant that many users couldn't use it, and updates on its progress were not what many would wish, is going to inevitably bring up considerations about NI's behaviour which while away the time they actually can't talk about 2.15. You may be new here, but many aren't
If people do complain about the same things over and again, then surely that is because they are not being listened to by that company. In some strange way you almost seem to find that acceptable if not commendable, or I've really misunderstood you. You find that a plus point??????
I cannot find an ignore button on this software, but it might be pertinent to ask for it to be implemented, so you don't have to view any posts which might upset you.
Meanwhile, please respect that others may not share your views, and it's a little ironic to post a post complaining about people complaining.
Until an ignore button is found or implemented, surely it's easy enough to skip reading a post if you find it inappropriate.
2 -
Good morning,
yesterday I wanted to use the 2.15 update first time with my Maschine Mikro MK1. And I had to downgrade to 2.14, because the controller doesn't respond anymore. Is this a known isse with 2.15 and Mikro Controller?
0 -
@tempsperdu wrote
Until an ignore button is found or implemented
There‘s an ignore list on your profile.
Enjoy!
3 -
Yupp. New update due any day now.
1 -
Thanx. What are the features that you think NI autosampler is missing? Im asking this because i think my use will be fairly simple :)
Interesting about the SD card. I\ll try to do a test sampled instrument myself and try it, once we get the *cough* update on the M+.
0 -
Go @Kaiwan_NI 💪 looking forward to the fix :)
2 -
LOL should be problem solved then innit 😄
0 -
Every time I log in I have 100 notifications about this thread, it's a bit annoying tbh as it dominates my notification list and makes me miss other stuff.. It also makes it very hard to keep up with whats going on with the update.
What do you guys think about the next update threads being aggressively moderated? Specifically deleting / editing posts with:
- Back seat / couch potato NI business analyst types of comments (NI should do this or what)
- Feature requests (cool update bro but what about X and Y and Z)
- My MPC/DAW/whatever-else-product does this or that better.
- Any discussion of other products, platforms, iPad this, android that, etc..
Basically, if it's not about the update, its features then posts are removed, this could be useful but also can be perceived as censorship.
6 -
I second heavier moderation for all future version update threads. I'd actually encourage dividing threads into two "tiers" from now on - threads where staying on topic would be more vigilantly enforced, and all the rest. Threads about version updates should certainly be more "no nonsense" than many others.
3 -
When you feel your voice is not being adequately heard by those that can possibly affect change.... you make noise where it WILL be heard... and it can sometimes be a bit annoying and messy.
If NI was more responsive in other areas of this community, it would be help decrease the amount of frustration being voiced here.
2
Categories
- All Categories
- 19 Welcome
- 1.3K Hangout
- 59 NI News
- 662 Tech Talks
- 3.4K Native Access
- 14.5K Komplete
- 1.7K Komplete General
- 3.8K Komplete Kontrol
- 5K Kontakt
- 1.5K Reaktor
- 345 Battery 4
- 759 Guitar Rig & FX
- 391 Massive X & Synths
- 1.1K Other Software & Hardware
- 4.8K Maschine
- 6.4K Traktor
- 6.4K 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