Maschine 3 in regards to maschine + fw update

Nyla

Im not sure if I'll get an answer for this, but I was just curious if any of the external midi problems/unrelated bugs got fixed with the v3.0 update for maschine software and if so, what's the likelihood of these fixes being implemented in the firmware update for maschine standalone.

Currently these things are not possible or broken

1. maschine + does not record external cc from another device. It is possible to map external cc to macros in the desktop software, and even midi learn them, then import the project back into standalone. You can see the values change when you look at the macros, ie sustain pedal makes the CC value change, but when you record a pattern while the auto button is pressed, no CC data is recorded. You can go into the pattern afterwards and change the CC manually with the encoders on maschine but you have no visual indication as to how far you're changing it. The value on the external device will change, and these changes will play back when the pattern is played, but the value on the macro shows 0.0% no matter how far the CC changes.
2. There currently is no way to sequence program changes/bank changes in standalone. Currently you have to load the project on the computer, sequence these things there, then reload on standalone. You can do a similar thing with PC in macros as you can with CC values, but again, you can't do this in a more useful/useable way in step sequence mode for example. Plus, the encoders range is extremely coarse and it is nigh on impossible to record these changes accurately live via automation recording, even with the project tempo slowed.
3. There is currently only 1 bank of cc for everything. This is a problem for when you want to sequence CC and you have more than one external device, each of them having their own sustain pedal, and each of them using the same CC for the sustain pedal. Certain devices, like my korg synths (wavestate mkII AND multipoly) let you reassign CC's, but only some of them. Even if you could, you can't record external cc anyways.
4. There is currently no latency compensation on an individual "sound" basis. Unless I'm misunderstanding how things work, which is possible, there seems to only be one singular setting for latency compensation and it's global for all external midi.
5. Not midi related, but when auto backup is on in standalone, when recording audio in either sampler or audio plugins, the recorded audio sample will have skips and time jumps in it. I'm assuming this happens when maschine auto saves. I haven't seen this mentioned anywhere on the Internet, and might just be a me problem. SD card is a reputable SanDisk 64gb in good condition.
6. Kontakt instruments will not load from saved projects. You can load a kontakt instrument, modify settings, etc. But as soon as you save and either load a different project or restart maschine +, any sounds that have kontakt loaded won't play anything, sequenced or live. In order to get it working again, you need to reload the instrument which clears any settings changes you've made. I've also had instances of loading a second kontakt patch in the same group causing the first one to become inoperable, just like if I had saved and restarted.
7. There is no way to view automation lanes with their sequenced values in standalone.

I know the firmware update conversation has been beaten to death, and I don't want to start any more arguments. I'm merely curious as to if any of this has been fixed in maschine 3, and if it has, does that mean it will be fixed in the v3 firmware update for standalone? I don't mind spending money on an update, especially if it helps keep the developers moving.

Thanks!

ozon

I don’t expect any of the above being fixed.

1, 2, 3, 4 are status quo of Maschine (3.0.1)

5 seems to be an isolated issue with your device.

6 is related to Kontakt license issues AFAIR.

7 is status quo of Maschine (3.0.1), as the controller doesn’t display it either.

MaikR

https://community.native-instruments.com/discussion/comment/194572#Comment_194572

Maybe already in the final version 2 (kernel) update…?
This is expected to be released (in Beta) first.

ozon

I don’t expect any of the above being fixed.

1, 2, 3, 4 are status quo of Maschine (3.0.1)

5 seems to be an isolated issue with your device.

6 is related to Kontakt license issues AFAIR.

7 is status quo of Maschine (3.0.1), as the controller doesn’t display it either.

Nyla

https://community.native-instruments.com/discussion/comment/207272#Comment_207272

Okay, thank you. I think I'll be moving to MPC then.

PK The DJ

MPC has it's fair share of problems too.

No way to set a time signature other than 4/4 for instance. It was there but they removed it!

Also if you're used to playing any loaded sound in keyboard mode, that's not so easy with MPC.

Nyla

https://community.native-instruments.com/discussion/comment/207413#Comment_207413

Everything you buy will have problems and bugs. Both of my korg synths for instance don't have CC's assigned to the filter knobs. I'm sure MPC will add time signatures back. But basic functionality with external gear is a must, especially with my band going dawless. NI has had 4+ years to implement this. Again, this has been hashed to death in the forums so I'm not really interested in talking about it too much. Plus mpc's plugins have more real world instruments that are more useful to me (I'm a metal musician). I don't use massive or monark in my final songs. That's what my wavestate and multi/poly are for. I do enjoy maschines plugins for audio though, but thats not enough to keep me using it.

Nyla

https://community.native-instruments.com/discussion/comment/207272#Comment_207272

I can't seem to find the thread on the kontakt license issue and I know I've seen it before but didn't read it because I hadn't tried using kontakt before then. Do you have the link? I'll keep looking but so far nothing. If I find it I'll comment again.

Deleuze001

What if Maschine Plus going Open Source using and building community features. Like Synthstrom did released the source code of the Deluge firmwaremake custom firmware using reaktor builds. win win for all