Maschine 3.0 General Discussion
Comments
-
try moving addicted drums from the plug-in folder
0 -
Let me clarify when I said that no one cares. What I meant was sounds are cool and all, but just look at the feature sets of your competition. That’s my reasoning because NI a company, who wants to be last? Seems like no motivation is there. Don’t get it twisted @Matthew_NI, I love my Maschine, I also love the sounds. We just need more from you guys, and agin not trying to rub you the wrong way, but let this be a wake up call for y’all. Again just my .2cts.
4 -
if you have maschine 2 installed , I believe ( from testing the beta) when you install maschine 3 it automatically points to the path where your m2 library’s are installed .no need to copy anything, if it doesn’t automatically point to your older libraries, goto the m3 settings/ libraries and add the path to it and rescan .
no need to delete anything, as the maschine 2 library is completely different to the m3 maschine central library or expansion, whatever they’re calling it.0 -
any chances to see capture in Maschine? It is very useful feature for groovebox (see Ableton Move)
1 -
Does anybody get contfronted with partial VST user interfaces? Scaler 2 in my config:
Windows 11 (up to date), i9 13900K, 4070Ti 12 Gb, 6 4 Gb RAM
appears with only a view on 3/5 of the user interface. Same happend with other VST (Strumm Session by AAS) after a restart of the interface after a bored out shutdown of my monitor (Philips 4K Brilliance 328P).
I'm running a 4K resolution.
Update: A restart of the software solves the Strum Session problem but not the Scaler 2 Audio problem.
Greets to you all.
0 -
Does this help? https://support.native-instruments.com/hc/en-us/articles/22776526691101-Using-Maschine-3-in-HiDPI-mode-in-a-DAW-Windows
0 -
Stem separation, midi editing tools and a bad gui for a major update. What a joke.
7 -
Out— from maschine plugin's perspective. I wrote it this way to make a point, because this is where most of the issues remain. Regardless, no other device or software in my vast library has this trouble, pre or post VST3, and the "solution" to my particular issue is to just use the maschine sequencer that Im not interested in. I tried to get NI support for this, but support didnt seem interested in helping a Bitwig user at that time, so I moved on.
Whatever the issue truly is/was, I worked around it long ago and stopped worrying about it. After spending a few weeks upset that my projects and templates were broken, I learned my lesson and found other drum machines, I found better mk3 controller scripts and learned to just use the mk3 in MIDI mode, and I dont need to worry about maschine plugin integration inside Bitwig anymore. Too much trouble. Let me know when it stops being this much trouble.
0 -
Maschine 3 software functions without hardware but also works with the following Maschine pad controllers:
Maschine Jam
Maschine Mikro MK3
Maschine MK3
Maschine Studio
Maschine+ in controller mode
Maschine+ in standalone mode compatibility will be added ASAP. Currently projects created on Maschine+ in Maschine 2 format will open in Maschine 3, but not vice versa.
- Kontrol M-seriesKontrol A-seriesKontrol S-Series MK2Kontrol S-Series MK3
I expected that. So, no update to Maschine 3 on my side. S-88 MK1 is not that old (about 6 years since end of sale) and not unexpensive (over 1000 EUR) to loose NI support so fast.
8 -
People have vintage synths but sadly vintage hardware controllers in a lot of cases will not be a thing. Crazy we allow a max 5 year life cycle on certain products which could be longer.
6 -
Controllers have always been a bit risky thing IMO. Unless its a generic MIDI controller, chances are that sooner or later its proprietary support will end (ofter super abruptly) and it will then become a doorstop, unless you also "time capsule" the computing environment it was used with. This is why I've never consider buying expensive non-generic controllers, unless they also have some sort of standalone functionality which will remain usable even after the product support reaches EOL..
This is why I went with Maschine+ to begin with, instead of a MK3. MK3 will, in time, become another kind of doorstop, but at least Maschine+ will keep on trucking even after its support reaches EOL (well, as long as NI authorization servers are running anyway..)
We can only hope that in the near future, MIDI 2.0 kicks off properly, and we enter a world where even the proprietary looking/feeling controllers just utilize standard MIDI 2.0 conventions
6 -
Planned obsolescence. The motor of the modern economy.
6 -
Just think about kontrol mk3 wasted a full year to fix the software.. in 4 years it will be obsolete..
4 -
Still no onboard Play assist arpeggiator (only onboard Play assist chord so far). So maybe almost 1,5 years before the MK3 has the feature people expected on launch day.
4 -
That did the trick. Thank you!! You made my weekend.
1
Categories
- All Categories
- 19 Welcome
- 1.3K Hangout
- 59 NI News
- 694 Tech Talks
- 3.6K Native Access
- 15K Komplete
- 1.8K Komplete General
- 3.9K Komplete Kontrol
- 5.2K Kontakt
- 1.5K Reaktor
- 351 Battery 4
- 778 Guitar Rig & FX
- 400 Massive X & Synths
- 1.1K Other Software & Hardware
- 5.2K 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