MixControl Pro (Group Buy Started)

VST, AU, AAX, CLAP, etc. Plugin Virtual Effects Discussion
Post Reply New Topic
RELATED
PRODUCTS

Post

DNR Collaborative wrote:If there are any other willing beta-testers, we're still looking for quite a few more, specifically on the Win x64, All VST3 and AU side.


Steven
Hi Steven, I've signed up, but didn't include any system information as I was a beta tester for the previous release, so to recap: I'll be testing all 32 / 64 / VST 2.4 and VST 3 versions in 3 different hosts :D

Cheers mate,
George
Eternitysound VST Banks

Post

DNR,

I hate to suggest it so far along the development, but I just noticed that there is a saturation feature. It would be nice to have it multi-banded, so u could add Low, Mid, High Saturation.

Sometimes it is nice to add a little sheen over some frequencies, not all.

Post

DNR Collaborative wrote:If there are any other willing beta-testers, we're still looking for quite a few more, specifically on the Win x64, All VST3 and AU side.


Steven

I sent an e-mail in order to sign up. Can test VST/VST3 on Win x64. Cubase 6 and Reaper.

Post

Having picked up MixControl the other day, I'd like to sign up for beta. I'm running Win7/64-bit w/4 GB RAM, and using Reaper 4/64-bit beta. (I also can test the 32-bit version in Sound Forge 9.)

I did already notice something in MixControl 1.07, at least in the aforementioned version of Reaper -- if you change the background, and then the UI gets taken off the screen (e.g., when Reaper focuses on Plug-In B and you didn't set Plug-In A [MixControl] to Always On Top), it reverts to the default background.
Tom Smith
http://tomsmith.bandcamp.com - http://www.filkertom.com - http://www.thefump.com
Win10/64 - I5 3570K - 16 GB RAM - BIAB 2016 - Reaper 5 - Sound Forge Pro 9

Post

filkertom wrote:Having picked up MixControl the other day, I'd like to sign up for beta. I'm running Win7/64-bit w/4 GB RAM, and using Reaper 4/64-bit beta. (I also can test the 32-bit version in Sound Forge 9.)

I did already notice something in MixControl 1.07, at least in the aforementioned version of Reaper -- if you change the background, and then the UI gets taken off the screen (e.g., when Reaper focuses on Plug-In B and you didn't set Plug-In A [MixControl] to Always On Top), it reverts to the default background.
That is due to the x64 version installing the resources in a wrong path.

I did post the workaround in the TeamDNR support forum, but it has been removed. In any case, you just have to move the folder in the right location.

TeamDNR was aware of this a while back, I'm sure the problem won't be there with the new version.

Post

Hi,

I hope you are aware of a problem running Mixcontrol AU in Logic Pro 9.1.4. It crashes AU validation, and causes the Auvaltool to quit unexpectedly. Hoping for a fix for this in MCPro, since Logic is my main DAW.
I would also like to sign up for beta testing on an iMac running 10.6.6, with Logic Pro and Ableton Suite 8.2.2, though uve specifically mentioned you're looking for Win7 x64 Beta Testers.

thanks,
Chetan

Post

Amon1973 wrote:That is due to the x64 version installing the resources in a wrong path.

I did post the workaround in the TeamDNR support forum, but it has been removed. In any case, you just have to move the folder in the right location.

TeamDNR was aware of this a while back, I'm sure the problem won't be there with the new version.
I'm not quite sure why the workaround would have been removed. Was this on the KVR forum or our new website forum?
CT wrote:I hope you are aware of a problem running Mixcontrol AU in Logic Pro 9.1.4. It crashes AU validation, and causes the Auvaltool to quit unexpectedly. Hoping for a fix for this in MCPro, since Logic is my main DAW.
I would also like to sign up for beta testing on an iMac running 10.6.6, with Logic Pro and Ableton Suite 8.2.2, though uve specifically mentioned you're looking for Win7 x64 Beta Testers.
There has only been one other instance that I can find in the records about the AU version failing, but it was due to a conflict on the end user's computer. If you're interested in beta-testing with us, please shoot us an e-mail @ support(at)teamdnr(dot)net and we will add you to the beta team.

And just to re-iterate: anyone sending in e-mails for beta-testing, you will receive an e-mail from our beta system in the next few days with information on downloading and testing the new beta of MixControl Pro. We have 2 new team members who will be working at logging and communicating errors and fixes between users, so the beta-testing should go very smoothly :)


Steven

Post

DNR Collaborative wrote: I'm not quite sure why the workaround would have been removed. Was this on the KVR forum or our new website forum?

Steven
It was on the KvR sub-forum, reason made a sticky of that thread as it was dealing with some authorisation issue with the x64 version. The workaround was the same, if I remember correctly: moving the MC folder into the correct Program Files folder (or either install the x86 version and authorise that one).

Post

Actually, I realized that I hadn't imported the license file. But when I tried to do so, it said, "Registration failed". So I don't know what to think. Any idea what I'm doing wrong?
Tom Smith
http://tomsmith.bandcamp.com - http://www.filkertom.com - http://www.thefump.com
Win10/64 - I5 3570K - 16 GB RAM - BIAB 2016 - Reaper 5 - Sound Forge Pro 9

Post

filkertom wrote:Actually, I realized that I hadn't imported the license file. But when I tried to do so, it said, "Registration failed". So I don't know what to think. Any idea what I'm doing wrong?
You're not doing anything wrong. Assuming you're talking about the x64 version, it fails because the data folder is not where it's supposed to be. Take a look at your HD's directory: you should have the usual Program Files and Program Files (x86) folders - now, you'll also find another folder named something like "Program Files (x86)x64" containing only a sub-folder named TeamDNR. Move this folder to your default Program Files folder and try authorising again.

Post

DNR Collaborative wrote:
Amon1973 wrote:That is due to the x64 version installing the resources in a wrong path.

I did post the workaround in the TeamDNR support forum, but it has been removed. In any case, you just have to move the folder in the right location.

TeamDNR was aware of this a while back, I'm sure the problem won't be there with the new version.
I'm not quite sure why the workaround would have been removed. Was this on the KVR forum or our new website forum?
I think it was this thread

Should be quite a simple fix I think only changing the install path string in the installer :)
Last edited by Nielzie on Wed Jul 06, 2011 2:57 pm, edited 1 time in total.

Post

Definitely that thread. I didn't find it under TeamDNR and supposed the sub-forum was deleted :oops:

Post

Amon1973 wrote:Definitely that thread. I didn't find it under TeamDNR and supposed the sub-forum was deleted :oops:
I remembered that thread because of the odd person mixup I had there :lol:

Post

Amon1973 wrote:
filkertom wrote:Actually, I realized that I hadn't imported the license file. But when I tried to do so, it said, "Registration failed". So I don't know what to think. Any idea what I'm doing wrong?
You're not doing anything wrong. Assuming you're talking about the x64 version, it fails because the data folder is not where it's supposed to be. Take a look at your HD's directory: you should have the usual Program Files and Program Files (x86) folders - now, you'll also find another folder named something like "Program Files (x86)x64" containing only a sub-folder named TeamDNR. Move this folder to your default Program Files folder and try authorising again.
I actually copied it there, figuring having it in both places would not hurt anything. Still didn't work. Do I have to move the license directly into that folder?
Tom Smith
http://tomsmith.bandcamp.com - http://www.filkertom.com - http://www.thefump.com
Win10/64 - I5 3570K - 16 GB RAM - BIAB 2016 - Reaper 5 - Sound Forge Pro 9

Post

filkertom wrote:I actually copied it there, figuring having it in both places would not hurt anything. Still didn't work. Do I have to move the license directly into that folder?
I think maybe it's 2 separate issues that are occuring. If you install the 32-bit version, the x64 will authorize properly.


Steven

Post Reply

Return to “Effects”