MixControl Pro (Group Buy Started)

[sinkmusic]

[quote="DNR Collaborative"Can I ask what hardware interface you are using, and which driver model? Also, you are on Vista if I remember correctly?[/quote]
Hi
I have a M-audio Ozonic, and i am using m-audio Asio drivers, on an Asus laptop running Vista, indeed.
I had no problem with the first batch of betas, only the two last don't output any sound...

[bM3w]

On Windows the VST3 64bit files still get copied to the wrong folder! They should belong in here:

/Program Files/Common Files/VST3


right now they get copied to

/Program Files(x86)/Common Files/VST3

which is reserved for the 32bit files!

Nothing major, but kind of annoying if you want to keep your system clean

[DNR Collaborative]

On Windows the VST3 64bit files still get copied to the wrong folder!

This should have been addressed as well. My apologies, I will check into this immediately


Steven

[Amon1973]

I don't have the "no output issue" anymore - the plug-in is much more smooth when closing / opening.

The installer still wants to install the x64 version into Program Files (x86)/Steinberg/Vstplugins... not a big deal for those who have a different location, but still.

Also, when I open an instance and set my own parameters, switching to a factory preset makes the previous settings the "default" presets - so if I delete the instance and load another one, it automatically loads with the settings I made previously. Not a big deal either, as you can reset the parameters with a click.

I don't know if it was meant to be addressed, but the Stereo section processes the signal in a very extreme way - should be more subtle and gradual, in my opinion.

[DNR Collaborative]

I don't have the "no output issue" anymore - the plug-in is much more smooth when closing / opening.

Very good, thank you for letting us know!

The installer still wants to install the x64 version into Program Files (x86)/Steinberg/Vstplugins... not a big deal for those who have a different location, but still.

For some reason this one did slip through but I have been informed that the issue has been corrected for the release version.

I don't know if it was meant to be addressed, but the Stereo section processes the signal in a very extreme way - should be more subtle and gradual, in my opinion.

There should be more information in the manual about this particular process - from someone who knows more than I about this:

"The stereo enhancer should be used VERY judiciously (between 1-5%) for content that already has a wider stereo field, especially content located in the higher frequency range. If the content has more of a narrow stereo field, a higher percentage can be used. Overall, this particular module tries to compensate for the variety of pre-processed sounds that can be passed through it, and therefore needs to be able to handle enhancing or reversing the stereo spectrum of a wide array of content."

I've passed on the suggestion anyways and I will look into weather or not it can be scaled a bit more evenly somehow


Steven

[audiosabre]

I still get audible pops (denormals?) when initially turning on saturation, and subsequently switching sat modes 2 & 3 [FL Studio 10.0.8]. Happens with both MCP large & small (x32).

[Amon1973]

I don't know if it was meant to be addressed, but the Stereo section processes the signal in a very extreme way - should be more subtle and gradual, in my opinion.

There should be more information in the manual about this particular process - from someone who knows more than I about this:

"The stereo enhancer should be used VERY judiciously (between 1-5%) for content that already has a wider stereo field, especially content located in the higher frequency range. If the content has more of a narrow stereo field, a higher percentage can be used. Overall, this particular module tries to compensate for the variety of pre-processed sounds that can be passed through it, and therefore needs to be able to handle enhancing or reversing the stereo spectrum of a wide array of content."

I've passed on the suggestion anyways and I will look into weather or not it can be scaled a bit more evenly somehow


Steven

Thanks Steven. I just thought to mention because on some sources (mainly sub-mixes which are already well-separated) even 1% seemed too much. Still, it can be useful between 1%-5% for processing groups like guitars or over-heads. Also, I'm not the man who thinks that each and every piece of software must please my taste even in the tiniest detail. I just wanted to point out because that way it's not very precise and one will never need the processing provided by higher values.

That said, this thing rocks and I truly hope it gets the attention it deserves - and deserved since day one: I'm one of those who bought it full-price shortly after it got out and never regretted spending on that

(EDIT: Too tired and stressed... this was worded very badly... hopefully just a matter of aesthetics, but still understandable? )

[pwal]

I still get audible pops (denormals?) when initially turning on saturation, and subsequently switching sat modes 2 & 3 [FL Studio 10.0.8]. Happens with both MCP large & small (x32).

+1, in minihost

[pwal]

Also, when I open an instance and set my own parameters, switching to a factory preset makes the previous settings the "default" presets - so if I delete the instance and load another one, it automatically loads with the settings I made previously.

i had this, and resetting the eq gave an audible pop

[DNR Collaborative]

I still get audible pops (denormals?) when initially turning on saturation, and subsequently switching sat modes 2 & 3 [FL Studio 10.0.8]. Happens with both MCP large & small (x32).

Also, when I open an instance and set my own parameters, switching to a factory preset makes the previous settings the "default" presets - so if I delete the instance and load another one, it automatically loads with the settings I made previously.

i had this, and resetting the eq gave an audible pop

Great job, thanks very much guys! We are trying to get each issue resolved appropriately, so these reports are a very big help

(EDIT: Too tired and stressed... this was worded very badly... hopefully just a matter of aesthetics, but still understandable? )

No, no it's not worded badly at all. We're very happy for all the constant feedback and suggestions, and without everyone helping us out, we would be lost. This is all very new for us and we are glad for the constant support from you all. Once again, without this help, I think we would have been working until Christmas to get this done


Steven

[Amon1973]

Great to know

[sinkmusic]

Hi
Problem solved, thanks to some kind help and tips from Steven

Now i am enjoying this new beta, and i like that channel strip more and more !

A couple of sugestions, and a little bug report :

- I wish i could enable/create a new eQ dot while double-clicking on the eq curve (like quite a lot of eq plugin do), it woul dmake things a bit quicker and easier (at least for me) ;

- When switching the eq spectrum display from "normal" to "fast", the low range of the eq seems to somewhat vanish (or acts weirdly) :

normal


fast

[_dada_]

Would'nt it be possible to add an option for the tooltips, to show the parameter values ??
OR some kind of overlay, showing up, when turning the knobs ?

yes, this is something we are looking into very carefully, because the previous version had text input, which we would have liked to keep, but we missed it while going through the interface design process. I will keep you updated as to what plans we make to address this

Hmmm ... nothing in b4 ...
Looks like it's not gonna make it into the first release ...


Still a great CS !



Jan

[DNR Collaborative]

Problem solved, thanks to some kind help and tips from Steven

Not a problem at all, glad to be of help

- I wish i could enable/create a new eQ dot while double-clicking on the eq curve (like quite a lot of eq plugin do), it woul dmake things a bit quicker and easier (at least for me) ;

That has already been added to the feature request list for some updates, thanks for the suggestion!

- When switching the eq spectrum display from "normal" to "fast", the low range of the eq seems to somewhat vanish (or acts weirdly) :

Ah, I see what you mean. I will send a report in with these references and see if there is a solution.

Hmmm ... nothing in b4 ...
Looks like it's not gonna make it into the first release ...


Still a great CS !

Unfortunately there were a few things that needed to be put off until initial updates begin, due to the amount of requests and fixes that were necessary. Initially we will be releasing the VST/AU versions of the software, and then shortly after that we will release the Pro-Tools version, and then we can start looking into update scheduling and getting some of the additions feature requests integrated into the current release


Steven

[DNR Collaborative]

Just a note to all current users - MixControl Pro has unofficially been released (uploaded) and I wanted to take a moment and inform everyone about the update. We will be adding the final build to all 1 and 2 year subscription holders very shortly and informing all users about the new version no later than tomorrow morning.


Steven