The future of Maschine
Comments
-
Ah and just another think (says Columbo), why can't I change routing via a user template without erasing the existing sound? Needs to be a +Sounds button next to the +Routing +Patterns buttons.
1 -
Argh only stereo outputs not mono I just discovered (again), guess that's another enhancement request :( Guess there are workarounds…
Sorry this is rapidly turning into my own personal b*tching thread!
1 -
@CakeAlexS said:
Another thing, user templates and routing, often some settings are not saved. Surely it can't be that hard to fix?
Can't say I have ever experienced this, I have projects nearly 10 years old that still load fine with all routings in place. I also havent seen anyone report this, maybe you've stumbled upon a bug?
Indeed. I suggested this before, I dont think it will ever happen tho; people have such a hard time understanding routing that there's no backup from other users to specific practical suggestions like this one… People can just say "we want better integration".
A workaround is to
- Save the Sound/Group (With whatever sounds or patterns you want to keep)
- Load a preset with +Routing, (loads the routings and resets the sound)
- Load the Sound/Group from step #1 with +Routings disabled.
Result: You changed the sound and kept the Routings. It works, but it's for sure convoluted.
It's fine… TBH I was surprised you seemed so happy about the state of things a few days ago and said to myself: "wait until he rediscovers all the issues" ahahaha
2 -
Yeah it's all went Pete Tong once I started sync'ing and routing with DAWs! I no doubt raised these issues years ago but I've forgotten.
Having said that I finally manageable workflow now with Studio One although stuff stated here on this thread is still a PITA and slows it all down.
Pretty much all of it is basic stuff that should have been sorted by now. Oh well!
2 -
I dont see why not, at least for the current gen controllers MK3 and M+, MIDI 2.0 is just software, not hardware, imagine having to buy a new computer to use MIDI 2.0…
Maschine uses proprietary communication that is translated to MIDI by it's drivers and background services anyway (a combination of OSC and some other stuff I think)… This is why MAS controllers are not MIDI class-compliant, which in this case can actually be an advantage.
Now the DIN Ports might be trickier and require firmware updates (?), assuming theres enought storage there for however big MIDI 2.0 ends up being, it should also be doable unless NI decides to use this as an excuse/advantage to sell new models.
2 -
"Can't say I have ever experienced this, I have projects nearly 10 years old that still load fine with all routings in place. I also havent seen anyone report this, maybe you've stumbled upon a bug?"
From 13:40. He's loaded up a template with routing, the only thing he should be changing is the MIDI channel but as you can see he's changing a lot more.
https://youtu.be/JXyPxR_11OE?si=cRr1cA4APzdZKSvz
0 -
Oh… My bad. I'm able to reproduce.
Loading a Group doesn't recall the Group's
Channel
orStart Note
for some reason, everything else seems to work. I'll report this2 -
Argh need a stop button with Standalone app.
0 -
See image above, top is standalone, bottom is plugin.
So with the plugin I can drag and drop MIDI/audio files into my DAW, but I guess I can't do that with standalone right? (I can certainly drag and drop stuff from my Studio One to Maschine 3.2 standalone app).0
Categories
- All Categories
- 18 Welcome
- 1.7K Hangout
- 67 NI News
- 895 Tech Talks
- 4.6K Native Access
- 17.8K Komplete
- 2.2K Komplete General
- 4.8K Komplete Kontrol
- 6.3K Kontakt
- 1.1K Reaktor
- 407 Battery 4
- 923 Guitar Rig & FX
- 467 Massive X & Synths
- 1.5K Other Software & Hardware
- 6.4K Maschine
- 8.2K Traktor
- 8.2K 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