MIDI CC's with SFP (Minimax)

Ganool · Post by **Ganool** » Sat Mar 27, 2004 2:49 pm

Five inches from going completely mad.

Can any of you guys who own Minimax, help me with an easy test?

Load Minimax, play a tone on "A true Classic" and right-click on the waveform selector knob. Choose new midi controller 93. Add this.

Do you hear a change in sound?

Do the same for the two other waveform knobs with values 94 and 95 (don't think the value matter). Just by assigning MIDI CCs drastically changes the sound for me.

Is this... eh, normal?

Regards,

Carl.

at0m · Post by **at0m** » Sat Mar 27, 2004 3:56 pm

Osc3 does the same here, but don't let it drive you crazy.

Did you notice some mixers go mute if you assign a CC# to the main output level fader? The fader control goes to 0, yet the GUI remains in place. The same happens when loading a Remote Preset or a project which contains a CC# assigned master bus fader, and on other synths like Minimax and Inferno. It took me way too long for my liking to nail that bug down.

Now that I know, it's become less of a problem. I just recall a couple (often one doesnt do the trick) of presets from the devices or wiggle the knobs, to properly align GUI and underlining control.

Don't let that Osc3 type selector bug you

Ganool · Post by **Ganool** » Sat Mar 27, 2004 4:57 pm

Ok. Thanks for confirming this, but this really makes Minimax a bit useless for my purposes. I'll check out the demo of the CW Pro One and see if contains the same bug.

Cheers,

Carl.

Shayne White · Post by **Shayne White** » Sat Mar 27, 2004 8:16 pm

I haven't had that problem. Are you sure the position of the knob isn't simply being changed? I didn't have any change in sound quality -- the oscillators sounded the same for me when I applied automation.

Mr Arkadin · Post by **Mr Arkadin** » Sat Mar 27, 2004 8:46 pm

i've never had this problem either, although i'm on Mac. Why not save a MIDI CC template, load that first then load the presets?

<font size=-1>[ This Message was edited by: Mr Arkadin on 2004-03-27 20:47 ]</font>

Ganool · Post by **Ganool** » Sun Mar 28, 2004 3:46 am

No. I'm sure the knobs actually don't move. That's why I'm frustrated.

It's worst on oscillator 2 (with the A Classic-sound). Just by applying a midi CC to the 3 oscillators (manually) removes a great deal of the sound.

Are you SURE this doesn't happen with your Minimax? It's so wierd. I can't reproduce it with other synths (tried Pro One demo last night). I even generated a new Minimax to see if it was a bug in my version, but no...

Carl.

Liquid Len · Post by **Liquid Len** » Sun Mar 28, 2004 4:54 am

I have had this happen also - and even when I had the MIDI CC settings saved in a file, as soon as I recalled them, the instrument's sound changed.

Ganool · Post by **Ganool** » Sun Mar 28, 2004 5:25 am

Argh... for a moment there I hoped there was a problem on my system...

I guess I have to drop CW a mail and see if there are any solutions about this.

Carl.

at0m · Post by **at0m** » Sun Mar 28, 2004 9:09 am

Mr Arkadin wrote:
Why not save a MIDI CC template, load that first then load the presets?

I do that on my system, for example on Minimax. Some of the synth's parameters go haywire, I reset them by loading a couple of presets...

Ganool · Post by **Ganool** » Sun Mar 28, 2004 2:01 pm

That's another thing. I've just set up Minimax to be controlled by my Remote 25, and after assigning 90% of the controllers in Minimax, many of the patches sounds really weird. Even if I reload the .pre file or double click on a couple of patches.

First I thought it could be something with the Remote 25, but the weirdness is still there even if I assign the controllers manually.

_Could_ this be because of something else in my system? Sounds far-fetched, but computers are... well, computers.

Carl.

Liquid Len · Post by **Liquid Len** » Sun Mar 28, 2004 3:44 pm

What I wound up doing was assigning a few controllers at a time, checking that the presets sounded the same, saving the MIDI CCs under Midi Controller Presets, and assigning a few more etc. I think it was mainly the waveform type selectors that would not work.

<font size=-1>[ This Message was edited by: Liquid Len on 2004-03-28 20:43 ]</font>

Shayne White · Post by **Shayne White** » Sun Mar 28, 2004 10:29 pm

OK, I just did some of these tests, and I've made some observations. Here they are:

When I assign a MIDI CC to one of the waveform selector knobs (and they all behave the same way), the sound resets to triangle, but the GUI doesn't change. Wiggling the knob on my keyboard that's assigned to the parameter makes it behave properly. However, wiggling the knob on the computer screen produces this bug: the sawtooth oscillator isn't enabled, it's just ramp. On the third oscillator, since there isn't a ramp, it's "saw down" only. However, I can access those positions via the remote controller.

So there is definitely a bug, and I never noticed it because once I assign something to a controller, I always control it remotely from then on. See if it works the same way for you!

As for parameters changing when you assign CCs, that's the way all SCOPE devices hehave: the "remote" value is completely separate from the on-screen value. It's a bit annoying, isn't it?

Shayne

valis · Post by **valis** » Sun Mar 28, 2004 10:46 pm

this might be a silly question, but have you contacted creamware support with this info?

at0m · Post by **at0m** » Mon Mar 29, 2004 9:24 am

i have, they never replied.

i been hammering on this very subject short after 3.1c release, here on z, nobody bothered.

Ganool · Post by **Ganool** » Mon Mar 29, 2004 9:25 am

I also sent them a mail regarding this. Let you know if I get any reply.

Carl.

Ganool · Post by **Ganool** » Mon Mar 29, 2004 3:18 pm

You won't believe this.

I just bought Pro One from the Shop.
Guess what? The same problem.

I'd better log off now, before I begin to act really nasty.