Maschine 3.0 General Discussion
Comments
-
Most of us routing maschine into DAWs arent using the maschine sequencer. That's what a DAW is for… we arent double routing anything. This is why Ive fallen back to using my mk3 as a MIDI-mode controller for Triaz and other things - its just too annoying to use in plugin mode.
The issue is the use of groups and sounds, routing those groups and sounds to corresponding input/output channels in your DAW. If you have a single instance and single group, its simple. Add another group/instance, and it breaks down, stops working in some DAWs, creates loops, etc.
This wasnt fixed because it isnt a priority for NI to help people NOT USE the sequencer in maschine. They want you to use the sequencer, so they are not focusing on making routing in/out of DAWs any easier.
2 -
Are you able to manually copy over everything to the new Maschine 3 library (i have everything on an external drive) and manually delete then Maschine 2 library??
0 -
Yes thank you for the video i use cubase a little different setup but yes that's how I use it and save a template in maschine software plugin.. thank you
1 -
What? I dont quite understand what you are saying. I was replying to the NI employee.
1 -
Could you please answer why this wasn't on the list...
0 -
A lot people say this, I don’t understand what is expected… there’s several ways to route things depending on many things, how can the software guess what you want to do? You might work in a simple way or not, route possibilities have to exist to acomodate several use cases, with choice comes configuration.
Do you want to play the Pad chromatically or do you want an each note to trigger each Pad? Where do you want the midi, in daw or in Maschine? Is mono out ok or you want stereo? How many midi channels to waste on Group X? Then there also the setup on the DAW itself, which MAS plug has no control over…. Choices, choices…
Mas already has Batch conversion on Groups to facilitate some configuration.
Routing is really easy once you understand how it works and why there are choices, and you can save a template to never do it again.
Maybe it can be improved but I never seen a tangible suggestion on how, people just say “make it better”. “How sway?”
I don’t mean to dismiss the request as it’s valid, im just curious.2 -
depending on the DAW you use, and/or external audio applications you use
i dont box myself in or limit myself with respect to what a DAW can do….
the routing within Maschine is more than sufficient for what i can achieve, even loading up a another maschine project to take the place of another is relatively easy with the Reaper DAW i utilise…
if of course the DAW you utilise doesnt save Maschine routings as a DAW preset… the problem is the DAW
knowing which DAW's save ALL the maschines values& routing within a project as you saved it , is indeed a good DAW to use!!
edit: for Reaper it's the FX templates that can be saved… which keeps all the values&routings intact (remove a maschineFX plugin and replace it with another saved maschineFX plugin)
0 -
Dude.
Years ago, when I was Jeremy S on the forum (before the reset), you and I spent years talking about maschine2 routing. I participated in 100s of threads about it, thanked you for the guide, sent dozens of others from KVR and elsewhere to your threads to benefit from your guides, etc. You remember that, right?
I became fairly expert with maschine2 routing inside Cubase 10, 11, 12, 13, and now finally 14, as well as Bitwig 4 through 5.2.5. I built my own templates, created my own guides, and helped others. Then back at the end of 2023 something changed, to do with Bitwig + maschine2 routing, and all the years of templates and projects I had suddenly stopped working, causing me to make a support request with Bitwig. Cubase routing, somehow, was not affected.
Long story - Bitwig support couldnt solve it and claimed something in maschine had changed, and maschine's routing (1 instance of maschine, multiple MIDI tracks connected back to it) was now causing feedback loops that were killing Bitwig's audio engine.
I brought this to this forum a few times, but didnt get any traction. Then, I mentioned this in one of the big "culture change" threads that happened here, and you seemed to think I was attacking you personally. That was really shocking because I was talking about overall customer service and overall maschine2 development, to do with routing. I dont know what happened there…
No, routing for maschine2/3 is only easy when you leave it alone and do it internally. When you try to use your DAW to route midi in/out of maschine (really just out), it introduces problems and works differently DAW by DAW. I know all of this like the back of my hand at this point.
2 -
I was making 😁 I'm on the same page as you..
1 -
Remove please
0 -
i dont know if you are familiar with the blue cat connector FXplugin… but it has some useful functions in that as long as a external application can utilise VST's… then you can use it as a routing tool.. to go from an external application to a DAW
the bluecat plugin used with VirtualDJfree… allows me to have 4 separate isolated track outputs to route out of VDJfree… with the vdj2.0 stem features still in tact! very useful plugin
1 -
The update is not as transformative as the free update to 2.0 that brought auto-sampling. I feel the point of this update is just to train customers to pay for updates on new software version numbers, which will almost certainly be combined with discontinuing support for older versions more quickly. I can’t really trust NI anymore unfortunately. If this update is worthy of 3.0, then what stops them from introducing Poly AT next week and calling it 4.0? Then then week after we get the automation updates and 5.0? They seem to be doing the same thing with Kontakt BTW. NI is a great example of why we should all be moving away from software entirely in favor of new hardware that can integrate well with major DAWs. This new batch of tech managers seems dedicated to destroying long standing unwritten customer/vendor norms.
2 -
a person who makes a impulse purchase without knowing what they are buying… have themselves to blame for the disappointment
i probably wouldve been kicking myself if there wasnt something i liked in the update…
that said, it would make little difference if i purchased it today… or 3 months from now waiting… becos eventually the added updates would bring added value…. but as i saw 1 thing of value when making the purchase(independant tempos)… i was happy to pay for it…
upon looking deeper into the changes i found there was the added bonus of increased input amounts… that for me made it worthwhile….
for people who dont see the added value of both aforementioned features, are likely project oriented people who dont route audio between applications!
1 -
They just need to make a sound module version of maschine with there expansions and expansions as a plugin..
1 -
??????????????
0
Categories
- All Categories
- 19 Welcome
- 1.3K Hangout
- 59 NI News
- 677 Tech Talks
- 3.6K Native Access
- 14.9K Komplete
- 1.8K Komplete General
- 3.9K Komplete Kontrol
- 5.1K Kontakt
- 1.5K Reaktor
- 347 Battery 4
- 773 Guitar Rig & FX
- 399 Massive X & Synths
- 1.1K Other Software & Hardware
- 5.1K Maschine
- 6.6K Traktor
- 6.6K 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