Massive X - the thread

[anxiousmofo]

Forget about the EDM crowd

I'm trying!

[Functional]

So we're no longer in the "reasonable" thread? The title has changed. Does this mean we can finally start talking unreasonably?

[acYm]

so, about the sucky browser. basically they just didn't bother to put a proper integrated browser in there and you're actually meant to load the thing in maschine/kk, right?
just trying to understand what's going on, since the first massive (well, the kore system anyway) literally invented modern browsing and all.

[highkoo]

just trying to understand what's going on

As it turns out, we dont actually need to know what is going on anymore.
Happy tweaking!

[EvilDragon]

I'm betting that the browser case was a matter of prioritization to meet the deadline, and because KK/MAS is there, those can be used in a jiffy. But I don't doubt for a second that the browser will see a bunch of improvements down the road.

[dellboy]

Forget about the EDM crowd, this thing can do mainstream stuff.

To quote a confused spaniard:

¿que?

Keep out of the hot sun and stay off the sangria.

[highkoo]

But,
With all the VSTs NI has done over all the years, how many times have they done preset-browser-code? How proficient might they be at that relatively simple and repeatable thing?
i.e. How much work is a preset broswer, at this point, at NI?

Sure, not a priority, but wouldnt it also be pretty far down the list of intensive time consuming coding jobs? Might it actually almost be a modular bit of code for them, at this point?
They were so strapped for time, after a six month delay, that they just skipped it?

Maybe, but then, why did they waste time designing those nice big static evenelope pictures, and making acres of real estate for them..?

Sorry for my yapping.

[pdxindy]

Yeah, that seems to be the biggest gripe - lack of automatable parameters.

I can understand this (and I agree about MIDI learn not being there, but one thing is kinda tied to another), but macros can be so much more powerful, and I really don't recall any instrument where I had to automate more than 16 parameters of a single patch in a project, ever. Do you know of anyone (apart from, maybe, BT)?

You've mentioned that a number of times now about not automating more than 16 parameters of a single patch.

But that is only part of the story. Automation is also used for midi controllers. So for example in Bitwig, I set up remote control pages to be able to edit banks of parameters of my various synths. That then works for every instance of the synth. Not possible in MX. Also, the MX macros cannot adjust things like filter type, number of unison voices etc.

[fisherKing]

But,
With all the VSTs NI has done over all the years, how many times have they done preset-browser-code? How proficient might they be at that relatively simple and repeatable thing?
i.e. How much work is a preset broswer, at this point, at NI?

Sure, not a priority, but wouldnt it also be pretty far down the list of intensive time consuming coding jobs? Might it actually almost be a modular bit of code for them, at this point?
They were so strapped for time, after a six month delay, that they just skipped it?

Maybe, but then, why did they waste time designing those nice big static evenelope pictures, and making acres of real estate for them..?

Sorry for my yapping.

that one is a puzzler (the static envelope images); very 1999...at least, you can make them larger by increasing the plugin window size

[pdxindy]

so, about the sucky browser. basically they just didn't bother to put a proper integrated browser in there and you're actually meant to load the thing in maschine/kk, right?
just trying to understand what's going on, since the first massive (well, the kore system anyway) literally invented modern browsing and all.

The browser (can't even call it that really) is terrible. If I make 500 presets, there is no way to organize them. It is just 500 untagged files in a single directory. Other than not saving presets at all, it could not be worse.

[highkoo]

you can make them larger by increasing the plugin window size

Makes the music come to life!

Ya, I imagine it not recalling preset names is a pain in the ass for patch makers also...

[Sparky77]

so, about the sucky browser. basically they just didn't bother to put a proper integrated browser in there and you're actually meant to load the thing in maschine/kk, right?
just trying to understand what's going on, since the first massive (well, the kore system anyway) literally invented modern browsing and all.

The browser (can't even call it that really) is terrible. If I make 500 presets, there is no way to organize them. It is just 500 untagged files in a single directory. Other than not saving presets at all, it could not be worse.

They will have to update it.

[Sparky77]

I'm betting that the browser case was a matter of prioritization to meet the deadline, and because KK/MAS is there, those can be used in a jiffy. But I don't doubt for a second that the browser will see a bunch of improvements down the road.

Yes, plus lots of other improvements.
But, despite all the complaints, its one cool synth.

[McLilith]

"UI that looks good" is exactly what's entirely subjective.

You should quote my complete sentence. Now you're taking it out of context.

That should be moved to:
viewtopic.php?f=70&t=304605&start=2805

Someone should cherry pick some of the best quotes from that thread, have some people with interesting voices read them into a microphone, and make a sample pack out of them!

[loungepanda]

The browser (can't even call it that really) is terrible. If I make 500 presets, there is no way to organize them. It is just 500 untagged files in a single directory. Other than not saving presets at all, it could not be worse.

And somewhat bugged. Can't type out space in my presets as it starts the Bitwig playhead instead. Probably has to do with focus issues which might also explain the stuck notes.