Native Instruments Massive X Synth - Sequel to Massive (Out Now!)

[Vortifex]

Probably a dumb question, but... how do I pan the oscillators?

Have you tried saying bad things about them?

Seriously though, it's probably staring me in the face but I can't see how

[McLilith]

Is the use of "Bend" and "Over" as controls for the Gorilla oscillator intentional or a bad coincidence?

At least it’s flexible.

[zerocrossing]

Probably a dumb question, but... how do I pan the oscillators?

Have you tried saying bad things about them?

We’ve all missed the stand-up comedian boat.

[Functional]

Probably a dumb question, but... how do I pan the oscillators?

Have you tried saying bad things about them?

Seriously though, it's probably staring me in the face but I can't see how

Don't quote me on this but I don't think you can

[BDeep]

Probably a dumb question, but... how do I pan the oscillators?

Have you tried saying bad things about them?

Seriously though, it's probably staring me in the face but I can't see how

It's a mono signal path - no panning. So it's not you

[zerocrossing]

I’ve not installed it yet, and I’m already waiting for the next update!

[Vortifex]

Probably a dumb question, but... how do I pan the oscillators?

Have you tried saying bad things about them?

Seriously though, it's probably staring me in the face but I can't see how

Don't quite me on this but I don't think you can

WTF? That seems like a pretty big omission to me.

[jeffb01]

Probably a dumb question, but... how do I pan the oscillators?

Have you tried saying bad things about them?

Seriously though, it's probably staring me in the face but I can't see how

It's not the most intuitive synth - now I'm looking for it too. ha.

[McLilith]

Probably a dumb question, but... how do I pan the oscillators?

Have you tried saying bad things about them?

Seriously though, it's probably staring me in the face but I can't see how

Don't quite me on this but I don't think you can

In that case, run two instances of Massive X. Create a "left channel patch" for one, and a "right channel patch" for the other. Then, hard pan them to the appropriate Left and Right channels in your DAW?

[chk071]

Probably a dumb question, but... how do I pan the oscillators?

Have you tried saying bad things about them?

Seriously though, it's probably staring me in the face but I can't see how

Don't quite me on this but I don't think you can

WTF? That seems like a pretty big omission to me.

Dunno. What are you trying to do exactly? TBH, i never pan oscillators, unless i use unison.

[Functional]

Probably a dumb question, but... how do I pan the oscillators?

Have you tried saying bad things about them?

Seriously though, it's probably staring me in the face but I can't see how

Don't quite me on this but I don't think you can

WTF? That seems like a pretty big omission to me.

What did I just tell you? NOT TO QUOTE ME (with a typo)

But anyhoo, it's not really a big omission. Stereo signal means twice the processing power used just to allow panning like that. For this very reason, panning oscs isn't not really that common among many synths. Typically panning doesn't exist before the VCA.

[ghettosynth]

Probably a dumb question, but... how do I pan the oscillators?

Have you tried saying bad things about them?

Seriously though, it's probably staring me in the face but I can't see how

Don't quite me on this but I don't think you can

WTF? That seems like a pretty big omission to me.

Not at all. It's a mono path up to the effects stage where it becomes stereo. To do otherwise would either force the modular signal path to be stereo which would double the CPU for all of the other poly modules, or complicate the path by making the modular environment stereo and then having the modules either default to mono with one connection or be stereo otherwise.

[karrikuh]

None of the wavetables or noise tables are available in my demo, is this a bug or is that how the demo is?

no. You're having a problem with the additional stuff. Rescan Presets again - just do it. when that's done, close Massive X and reopen it.

Already did that twice and nothing happened, did it a third time and it worked. Ah well, temporary gremlin.

I'm having the very same issue, unfortunately rescan didn't help in my case. tried it at least a dozen times, including uninstalling/reinstalling MX. My setup: Massive X Demo, Win10, REAPER.

I verified that the content is located in
C:\Program Files\Common Files\Native Instruments\Massive X
(it contains Wavetables, Noistables etc. folders)

A registry entry ContentDir is present in
HKEY_LOCAL_MACHINE\SOFTWARE\Native Instruments\Massive X
and points to this directory.

Anybody else experiencing this?

Content directory doesn't contain factory presets. Have you installed the MX factory library? It's a separate download.

The issue is about wavetables/noisetables, not presets! The presets are there

[Functional]

Speaking of CPU consumption... is it just me or is Massive X surprisingly... light? It doesn't chug much at all. Maxing at 64 voices will still just barely consume much at all. I wonder is there like a "HQ mode" that I'm missing or something?

[MikeCallon]

What's happened to Komplete Kontrol mapping - am I missing something?

There are only 2 pages in KK for Macros 1 -16, nothing else is mapped at all and many of the presets have a naming mismatch between the Macro name in Massive X and what's displayed in Komplete Kontrol and on the S61 screens. Did NI drop the ball on this - anybody else seeing the same issue?