MixControl Pro (Group Buy Started)

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

Post

mavdime wrote:My Logic woes are all fixed!

downloaded release 2 of the plugin, ensured all files from the previosu install were deleted (ie. in application support and plugin folders)

Installed release 2, then opened up Logic. In the Au manager I hit the button that says 'reset and rescan AU' and now all working perfectly

Many thanks to DNR for their snappy support!
Haha, I knew it! Thanks Manny :)

For everyone else - Manny has now confirmed what I have been deducing for the past few days here - we do not support an uninstaller. Please do not ask me why (I'll look into it), but it has something to do with the way we install support files and such. It appears to me that the issues that are being caused is because installing new updates requires the removal of prior version of the software. If you are having issues with the application, please remove the actual plug-in itself along with any supporting files such as license and "TeamDNR" folders and then run the application installer again. This should clear up any issues with installation conflicts. I will report these findings to the developer and look into providing just software patches instead of installing the entire application again.


Steven

Post

If anyone else with the AU validation issue could check on the re-installation process, please let us know if it works out for you. So far, we have had about 6 people send in reports who were able to re-install successfully, so it would be good to get more user input here if possible.

The uninstallation process and a list of every single folder which MixControl Pro is installed into on both PC and MAC platforms is now included in the manual, which has been updated earlier this morning:

MixControl Pro Manual v1.0.0.5


Steven

Post

For what it's worth, I've just been installing each new version over the old version, and I'm having no problems.
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:For what it's worth, I've just been installing each new version over the old version, and I'm having no problems.
Thanks Tom! It seems like it is a very random issue, but it appears to mainly happen on the AU platform of the plug-in. Also, has the sluggish UI issue been resolved with this last update for you? I know the other 2 who were having a slow UI occurrence have been pleased with the results, but I recall reading that you were having a similar problem previously as well?


Steven

Post

Actually, the GUI is quite quick now, so no problems there. I was (and still kinda am) having problems with the Small version of MCP swapping screens by scrolling down from the top, rather than either scrolling up or down relative to the previous screen or just swapping without the scrolling effect. When I click on 1, then 4, then 2, and it starts scrolling, I kinda expect it to scroll past 2 and 3, and then back up past 3. Just a psychological thing.
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

guvnor_p wrote:It looks great and I'm looking forward to using it. However I seem to have broken it on my first go!

The steps I took were as follows:

Added it to a track in Vegas 10 and it worked fine. I then duplicated the track and the new track output didn't work with some serious peaking clicks on the output. I've tried it without any of the modules turned on.

Now it shows that behaviour (no proper output, just loud clicks) in whatever application I use MixControl in, such as Adobe Audition, on different sound cards and even after a reboot, basically it no longer works at all.

I've sent this post to TeamDNR but just wondering if anyone else has seen this kind of behaviour.
I seem to be having a problem similar to this one - even with the r2 release from the site. The first time I ever used MixControl Pro it worked fine... and then it didn't. The old versions, pre-Pro work fine.

I'm using Energy XT 1.4 and Podium 3. Even after manually removing everything to do with TeamDNR and re-installing I have no output from the plug-in :(

All of the meters go up and down when I play a note on a synth - execpt the output one.

I'm on Windows 7 64bit with 4Gb of RAM. Really would love to get this working if possible.

Post

DNR Collaborative wrote:
Nig wrote:I just tried to install Mix Control (twice) but I opened up Logic and can't see it in my plug in list. It doesn't seem to be appearing in my plug in folder either.

Must I uninstall the old version first or am I doing something else wrong?
There seems to be a random issue with the AU version of MixControl Pro. We are planning on removing the licensing from the plug-in and replacing it with a standalone licensing application in the next week or so, but for the time being, you can try to remove the application and it's supporting files and then run the Release 2 installer again. Also, if you have any additional information about the issue, along with some contact information in order to help us diagnose further, I would very much appreciate that :)


Steven
Cool, will try this when I'm home and let you know the results, thanks...
Deep N' Dusty House Grooves !!!
Artist: http://soundcloud.com/nigel
Label: http://soundcloud.com/diplopiarecords

Post

filkertom wrote:Actually, the GUI is quite quick now, so no problems there. I was (and still kinda am) having problems with the Small version of MCP swapping screens by scrolling down from the top, rather than either scrolling up or down relative to the previous screen or just swapping without the scrolling effect. When I click on 1, then 4, then 2, and it starts scrolling, I kinda expect it to scroll past 2 and 3, and then back up past 3. Just a psychological thing.
Thanks Tom, we have this included already on the bug list, and we should hopefully have it cleared up for the next update :)
anzoid wrote:I seem to be having a problem similar to this one - even with the r2 release from the site. The first time I ever used MixControl Pro it worked fine... and then it didn't. The old versions, pre-Pro work fine.

I'm using Energy XT 1.4 and Podium 3. Even after manually removing everything to do with TeamDNR and re-installing I have no output from the plug-in :(

All of the meters go up and down when I play a note on a synth - execpt the output one.

I'm on Windows 7 64bit with 4Gb of RAM. Really would love to get this working if possible.
Can you send the details into our support e-mail so that they can look into it further and contact you if necessary?


Steven

Post

DNR Collaborative wrote:Can you send the details into our support e-mail so that they can look into it further and contact you if necessary?

Steven
Will do. Thank you!

Post

anzoid wrote:
DNR Collaborative wrote:Can you send the details into our support e-mail so that they can look into it further and contact you if necessary?

Steven
Will do. Thank you!
Of course, not a problem :)

For all new bugs, or anyone wishing to report a bug they have encountered, we have setup a new page on the MixControl page to allow us to help people easier:

http://www.teamdnr.net/mcp-bug-reports/

This will send a bug report to the support staff and categorize it for us automatically, so it should help us be a bit more efficient :)


Steven

Post

mavdime wrote:My Logic woes are all fixed!

downloaded release 2 of the plugin, ensured all files from the previosu install were deleted (ie. in application support and plugin folders)

Installed release 2, then opened up Logic. In the Au manager I hit the button that says 'reset and rescan AU' and now all working perfectly

Many thanks to DNR for their snappy support!

Cheers

Manny
Same here. Can confirm that everything is working OK with Logic 9.1.5 in both 32 and 64 bit modes. Excellent, so far.

Thanks TeamDNR

Post

PeeWeeGee wrote:Same here. Can confirm that everything is working OK with Logic 9.1.5 in both 32 and 64 bit modes. Excellent, so far.

Thanks TeamDNR
Very good, thank you for the update :)


Steven

Post

Version for 2-year subscribers is still 1.5r1

Would also be nice if the exact version number was displayed in the plugins "About" box :)

Post

No output from 1.5r2 on Sonar X1c no matter what I do. 1.5r1 runs just fine. I can see activity from all parts of the chain when I turn them on but there is no output from the plug and the FFT display confirms that it is not outputting audio.

I noticed that a had set a high pass filter on the Default preset so I removed this and resaved the preset. Then I reloaded the plug. Now it works as long as I move any of the low cut knobs before actually running audio through the plug. I saw this same behavior in the first beta. I can also confirm this behavior in Reaper 4.02 on my system. Strange is that I did a completely fresh OS install since the first beta.

Also seeing some pretty nasty CPU spikes. Methinks this is the same issue anzoid is experiencing.

Michael

Post

ChasingAndromeda wrote:No output from 1.5r2 on Sonar X1c no matter what I do. 1.5r1 runs just fine. I can see activity from all parts of the chain when I turn them on but there is no output from the plug and the FFT display confirms that it is not outputting audio.

I noticed that a had set a high pass filter on the Default preset so I removed this and resaved the preset. Then I reloaded the plug. Now it works as long as I move any of the low cut knobs before actually running audio through the plug. I saw this same behavior in the first beta. I can also confirm this behavior in Reaper 4.02 on my system. Strange is that I did a completely fresh OS install since the first beta.

Also seeing some pretty nasty CPU spikes. Methinks this is the same issue anzoid is experiencing.

Michael
Could you send in a bug report via our dedicated bug reporting page?

http://www.teamdnr.net/mcp-bug-reports/

This will help us to keep things organized in the support department and make sure things are reported properly to the developer :)


Steven

Post Reply

Return to “Effects”