Maschine 3.0 General Discussion
Comments
-
once everything works in stand alone mode , it won’t be obsolete
0 -
The s series mk1 came out in 2014 , so that’s 10 years
-1 -
When i bought it on day one.. so i should have waited for mk4 then.. stop it please
0 -
there’s always a risk in buying things when they’re first released, that’s why I don’t own one yet , as at the time there was no maschine support, and no indication it was coming , my point was , when all the smart play features work on board from the keyboard , you won’t be tied to the computer and software / os updates etc , which tends to cause things to stop working or be discontinued
3 -
I think NI should do some adjustments to the color scheme of the GUI. My vision is not what it use to be, I work daily with a computer and use Maschine in my spare time. I find the new GUI very stressful for my eyes. I do not want to judge here the aesthetics of the new design but the black foreground with low contrast dark grey lines mixed with bright orange is not the best idea. I find much more comfortable to work with version 2.
6 -
Bro, there shouldn't have to have been an "indication", because the previous generation of controllers had Maschine integration. Taking it away is what is out of the ordinary.
3 -
Given the number of plugin and library issues/inconsistencies that I seem to have (separate discussion here
Maschine 3.0 software loading issues loading NI Kontakt Instruments — Community)
I would recommend a feature to streamline and give more control over both plugin and library enable/disable. Ability to filter the plugins bt VST2/VST3, by vendor. Also greater clarity over which libraries are being detected from from both Kontakt and Komplete Kontrol to allow users to debug and fix proble,s. They all seem different lists at the moment, and does not seem to have consistency of what will show and what will not. Greater UI control over these would allow users to troubleshoot easier.
0 -
@Matthew_NI as you can see, those complaining are not complaining about the aesthetics, but because of vision problems. These „super massive black hole“ UIs are looking cool and work for plugins or applications like NA which you only look at for a couple of minutes, but are less ideal for applications at which you look for hours and hours. An adjustment of the colour scheme or professionally designed themes for different lighting and eyesight conditions would be much welcome.
12 -
man it got angry quickly in here😅. pardon my ignorance, i am not involved with the community, so first of, hi everyone, hope y‘ all doing well!
but i thought, i‘ll chime in, bc maschine is the only product i use from ni that is actively developed, that i have an interest in. (wake me up, when ni picks up reaktor development again or native linux, at least ubuntu support😜)
i am hired to build a multimedia lab for an institution in the healthcare industry. i chose ableton live as the main audio tool, bc of m4l, the gateway drug to max/msp. btw max is a great sandbox to tinker/prototype/create custom sw, highly recommend it for everyone that is looking for diy solutions. anyway, i am experimenting with maschine as a platform for beginners in audio production, especially kids, clients with cognitive impairments and disabilities, bc of it‘s fast workflow (no big menu diving, visual feedback and limitations), solid native tool palette and great hardware quality.
my thoughts on the upgraded software:
- i like the flat ui design, only issue i have is with the standalone app on windows os. the contrast from the white menu bar and dropdown menus (top of the application window) to the black background, especially on big screens in environments where the screen is the brightest light source, it is harsh on the eyes, at least reintroduce fullscreen, like in maschine 2 software, that would be very much appreciated. (sorry if i missed the fullscreen feature)
- stem separation algorithm is nice to have, but i would prefer noise/tonal separation for one shot samples for sound design, than a basic implementation of isolating instruments with no way for spectral editing the results (artifacts and quality lost). it's cool, don’t get me wrong, for what it’s worth, it‘s good quality ( izotope👌). but also for remixing, i would only use native stems, but this is my way, others do things differently.
- workflow enhancements are solid i guess, nothing to complain about the introduced tools
my hope for maschine future is, that it keeps being accessible, affordable and fun to play with. i have my mk3 unit since 2019, using it almost daily, also for personal projects and garbage time, never had issues with the hw nor sw that i could recall that broke a project. but i do not use 3rd party vsts nor itself as a vst in daw. also most use case is as a midi controller, in fact it’s my main controller, i only switch to keys and mpe controller when this feature are needed, and of course push for ableton, when i have to.
cheers,
fabio
2 -
Sorry, given how active I am I don't remember that discussion… I dont have much of an ego online, if I mess up i am quick to apologize.
Maschine did not change anything in relation to routing afaik, but maybe Bitwig did? I dont use use it so IDK, my routed projects from 7 or 8 years still work today in Ableton and Cubase so…
It introduces problems for you, apparently… That doesn't mean its broken for everyone or the stuff your talking about would have gotten the traction it didn't get, when something is broken there tends to be 100 threads or comments about it..
Send me your project and i'll try to help and we make peace? how about that? If i find an issue I'll file an official bug report…
All of this is besides my point tho, my question was:
- How can the plugin guess how you want to route things?
- How can it be easier while still having choices?
- What is the actual tangible suggestion to an alternative to doing it manually? VS "make it better and easy" ??
Things like DrumKit Mode are "easy" but can only cover a super simple scenario.
3 -
Why do you need to route MIDI out Maschine if you - as mentioned in a previous post- don’t use its sequencer? Or is this something Bitwig does automatically (wrongly) and Cubase doesn’t?
To use the controller to send the right MIDI, on the right channel, with the right transposition, to the right DAW MIDI track, otherwise you cant use the Pads to Play/Rec directly to DAW. Theres options that also need to enabled/disabled to avoid MIDI feedback loop…
1 -
This, the negative aspects of the harsh black background colour, was repeatedly flagged during Beta. The very reasonable suggestion that there should be some mechanism to desaturate the overall background colour and give the user control over its tone.
I find it hard to believe that whoever chose the colour and decided that it wouldn't be changeable has done any research at all on the basic requirements for long term screen usage.
And not providing the mechanism to alter the tone of the background colour is very unhelpful.5 -
still should work .. mpc x came out in 2017 still works..
2 -
True .. impulse buyer sometimes and I'm always mad afterwards 😆
0 -
You know what else is from 2017 and still works? Maschine Mk3.
Not an excuse for anything but just saying…
6
Categories
- All Categories
- 19 Welcome
- 1.4K Hangout
- 60 NI News
- 724 Tech Talks
- 3.8K Native Access
- 15.6K Komplete
- 1.9K Komplete General
- 4.1K Komplete Kontrol
- 5.4K Kontakt
- 1.5K Reaktor
- 361 Battery 4
- 805 Guitar Rig & FX
- 410 Massive X & Synths
- 1.2K Other Software & Hardware
- 5.4K Maschine
- 6.9K Traktor
- 6.9K 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