Maschine 3.0
Comments
-
Exactly my point.
0 -
That isnt what Im asking for, no. I dont think the OP, either. Im asking for the ability to simplify the over-complex routing for people who dont use the software sequencer. The MK3 hardware makes a great drum/sketch/music pad and controller, and this is where I find most of the value in what I paid for this product. I can play "sound packs" with/without maschine or the mk3.
@D-One Ive once again tried every routing option offered by maschine inside Bitwig for just 1 single instance of maschine with 1 single group with a drumkit. Blank project, no template. Unless I create a second track with its input set for the output of the first track, I get no midi. If I record that midi into the second track then drag/drop the midi to the first track, it plays back fine.
Im going to chalk this up to some sort of miscommunication I guess. If I thought it was related to Bitwig's routing, I would make a ticket with them but this is too murky to really tell.
0 -
lol. So I finally figured out how to route multiple maschine groups into multiple bitwig tracks, for midi and audio, for reading and writing. <sigh>
This is why I asked over and over on these forums- there was something wrong with the existing instructions on how to route this in Bitwig. In cubase, the original routing instructions work just fine for anything I need to do, but there is onnnnne little difference in Bitwig.
Step 1, add instrument track. Add maschine2 VST to that track leaving it on midi 1, and REMOVE THE INPUT SETTINGS FOR THAT TRACK. If that track is set for "maschine mk3 ctrl midi", the rest of your routing wont work. This was the thing tripping me up, and the big difference between Cubase and Bitwig in terms of maschine.
Step 2, add a few instrument tracks for a few maschine groups. I added A1, B1, C1 to 3 instrument tracks using midi 2, 3, 4. Each of these instrument tracks must have its input set to maschine2 (device).
Step 3, create groups in maschine, route them normally(the same way D-One showed in his original guide for Cubase).
It was the first "dummy" instrument track that I was missing, and this solved the issue. Every guide and Q/A I viewed missed this step, and said "its EASSSSY!!! Just add this, add this, and away we go", when in fact there was one key detail missing.
2 -
I always thought that Battery4 was the "expansion player". NI could perhaps start here and expand the concept. Battery4 can read all expansions and that's exactly what I use it for when I want to access my Maschine expansions in Live, for example.
3 -
Yes, but no audio previews of kits (i don’t want to use KK) and no access to Maschine factory library. They also said that they won’t develop Battery any further, just maintain compatibility.
i can use (and i am) Maschine as it is in DAW, but I’d prefer streamlined version for this. But that’s just my subjective opinion.
0 -
good to know, because then a player version of maschine would be a great idea.
2 -
Ahh so you want a Maschine Expansion player
I for one use Maschine in my DAW with the sequencer, if Maschine didn't have its sequencing abilities in the VST version, I wouldnt use it. My workflow is creating track ideas in Maschine desktop or Maschine+ standalone mode, which I then open in the DAW plugin for final arranging & mixing, reloading the same Maschine project. If the VST player only played the sounds but didnt have the patterns/scenes/clips/locks data to go with the sounds, it would be worthless for me
In any case, anything like that should be optional, not the only way how it works
1 -
Maschine's sequencer might be frustrating to you, but I personally like it very much and its a key thing of Maschine for me. For example, I much prefer Maschine's sequencer implementation to Akai MPC's current incarnations
3 -
I was just about to say, if you can reduce the mk3 hardware and maschine software down to "sound pack player" (the naming choice isnt wasted on me lol), then you may as well reduce every drum machine except drum synths down to "sound pack player", including the original Akai devices from the 1990s.
The maschine sequencer isnt just frustrating to me, and the same frustration can be seen across many NI customers both on this forum and on KVR. Face it - that sequencer is far inferior to most DAW sequencers at a visibility, navigation, feature level, and trying to duress people into feeling bad about not using it is silly. I have a REAL sequencer, I dont need to step down to maschine. Sorry!
1 -
Ok 🙄 I am still allowed to like Maschine's workflow and its sequencer
1 -
this is a great idea!!!!!! i agree with your post
a slimmed down version for use in a daw would make maschine a tool i cannot live without but at the mo its just bloat and i can do everything i need to more conveniently with other apps
3 -
I didnt say you werent allowed to enjoy it, lol, I was highlighting a well known maschine integration frustration that many people complain about in the context of this relevant thread. You dont need to feel personally attacked unless you wrote the sequencer code? haha
For me, personally, Ive finally figured out how to get maschine fully routed inside bitwig5 in plugin mode - to force it into the no-sequencer format and workflow I want + all the groups, but this took lol 6 months, numerous posts and comments, numerous videos, etc. My template is now built and all my work is saved, but it certainly would have been nice to not have to go through all that.
Edit: It would be nice to have a version of maschine that you could toggle, like switch it into no sequencer mode where its basically a music pad and controller and the maschine interface focuses more on NI library content - instruments, drumkits, samples. All the real estate used by the sequencer and scenes and all that could be saved, focused more on finding sounds.
1 -
Why not ask for Battery 5 with proper NKS support then ?
I guess... I can't say for sure but there was one step that (as a non-Bitwig user) seemed random that enabled the empty instrument tracks to receive MIDI from another Plugin, I don't quite remember wich nor do I know if this method of dummy instruments tracks is the right way of doing it.... But it works, as it does in any DAW. The only reason I don't do guides for all DAW's is because I am not about to buy them just for that.
Glad you figured it out tho 👍
Anyway, I think it's really dangerous to be asking for things because of assumptions that "things don't work" when they do, this kind of scares me In those suggestion threads.
2 -
As a customer, I dont see "danger" in being frustrated with available documentation nor reaching out on the forum to say so. Quite the opposite. If that one specific tweak (for Bitwig, no maschine sequencer) was more widely understood, it would not have seemed that things didnt work.
If only Bitwig got the integration attention that Ableton gets, lol. In a fantasy scenario, I want to see Bitwig absorb Ableton, integrate all their best ideas, leave all the rest (the UI lmao), and hire all their people. I did say "fantasy". 😃
0 -
Read it again, i don't see any danger "in being frustrated with available documentation", that's normal.
I see danger in asking for Maschine to be an Expansion box because routing doesn't work, when in fact, it does work fine; especially now that NI is asking for feedback.
3
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