@Pereira You are lucly i like you because if you were someone else I would ... NOW you are saying that other McDSP plugins are seen. Do they work? Do they work without Soundtoys? If they freeze, have you tried the fix I explained. Those are questions that need to be answered in order for whoever is on the other side of the ocean try to find a solution.
REVO does not do a complete job. How many times do i need to repeat that? Every time I run into someone with Omnisphere problems what is the first thing I do? I clean up the whole registry. Then I run ULTRASEARCH. Ableton, the same. Studio one, the same. AsI said, it is the best thing short of a fresh install. You are getting rid of all the shit that will cause conflicts.
Since the problem you have SEEM to be with just that one plugin you need to do with THAT plugin the same thing I told you to do with Studio One. REMOVE IT! Then use the search term Futzbox in Regscanner. Then do the same thing with ULTRASEARCH. When you are done delete the 64 plugin folder from Studio One. Restart Studio One. Reinstall Futzbox WITH the installer I will be sending you. Restart STUDIO ONE and go to VIEW>PLUG--IN MANAGER>UPDATE-PLUG-INS.

 

Man you're VERY lucky too LOL (maybe also old like me and with poor eyesight...) if you were someone else I would.....kindly reply as well
If you read my previous and private messages I already told somewhere.....
THEY WORK! and without the Soundtoy (the magic......) trick; I always use McDSP 6050 Ultimate Channel Strip v6.2.0.10.
It is inside
C:\program files\vstplugins\mcdsp
folder, like futzbox after its installation, but S1 shows only 6050 and not fritzbox when opened effect browser.....
And also....I TOTALLY agree with you about REVO, I think I'll use next time IOBIT and I'll TOTALLY follow your advices

Futzbox in Regscanner: already done, no traces left.......I'lll do the same with Ultrasearch

? I'll wait it, many thank, I just supposed this was the main issue


Finally: thanks a lot, you are the perfect helper

 

BTW: I have some "logistic" problems, cause I'm writing from a PC far from my DAW, and I'm working on this one (the DAW) on a project, so I can't make tests and modification in real time on it....

 

And as follows the end of the story.......hoping this will be useful for somebody (I don't believe so, but, who knows, just to avoid any loss of time also to stupid people like me......)

All done...with updated apps...and precision...and finally reinstalled S1 4.6 "regular" from R2R
And result is:

Exactly the same as before
Only the vst3/64 appears inside S1 effects browser in MCdsp folder (as before), as usual you can load it only if you load a Soundtoy plug before it, and.....
---------------> it doesn't work
as before it doesn't change nothing varying its presets, better, it brings the system being erratic and freezing

So, thank you so much, now it's time to do something more useful......

 

MAC please! One last question. Are you installing both the 64bit vst3 and vst2 ?

 

Last edited: Jun 22, 2020

man, if you're rolling around laughing, you've hit the target, big joke indeed............
Anyway, them both, but in one of the infinite attempts, maybe one time only the vst2
and remember, don't blame win10, this only a crack release that doesn't work inside it: why all the other work? Take a look during installation: if you change the default installation directories, the regular "\" becomes "/"

 

If it was only in one of your system i will blame the crack, however, how come that it does work for everyone else BUT it does not work for you in 2 different system? I just had it installed it in 2 different Windows 10 with studio One, and guess what? It does work. One is a 1909 and the other a 2004. I don't believe in coincidences, therefore, there must be something with the way you set up your systems that it does not work. Grab anyone's W10 install it, and it will work. Only general issue is that you need Soundtoys or the 6550 to open any McDsp in Studio One when on W10.

 

Who ???????????????????.....except you, of course....and vst2 or vst 3?

 

BOTH! Bro, I am not a magician, I am using the same thing as you are. After thinking about it for the last 10 minutes, here is something you should try. We have been dealing with just Studio One, and the fucking Futzbox which you reinstalled. Maybe, the problem is being caused by another of the McDSP plugins, after all they d share components and registry. Therefore, remove every McDSP plugin. Each single one. Do the same thing with regscanner using McDSP. Then do same using Ultrasearch. When you have removed them completely Get rid of that 64 bit folder @ThugLife told you about. Restart your OS. Open Studio One and do a new scan of all your plugins. Close Studio One. Reinstall Futzbox ONLY. Install both the vst2 and vst3. When done. Zip either the vst2 or vst3 and delete the respective dll. When finished, open studio one and rescan. If it does not work, close Studio One and zip that dll. Get rid of that 64 bit folder again. Open Studio One and rescan. Close Studio One. Unzip the dll that you first zipped. Open Studio One and rescan. If it still does not, buy a MAC.

 

Risus abundat in ore stultorum ?

I already told (and this worth lalso for the great Futurwine!)
!!!! That I also see the VST3 !!!!!!
and it works BADDDDDDDDDDDDDDDDDDD

Maybe if there was a bigger font.....

 

So now, the one who is trying to help you is a fool? Message received.

 

My only daw is Ableton but @The Pirate asked me to install studio one and try the mcdsp vst3 to show you it works.

He send me the links and i just followed his instructions very easy and it worked

First We Tested the vst3 , I zipped the eliminated the vst2 dll and tested it on ableton and studio one.. It worked right away, then i did the same to test the vst2, zippped and eliminated the vst3 file.

At first the vst2 did not work he told me to run studio one with windows 8 compatibility and it worked right away, then i deactivated the win 8 compatibility and it kept working .

I used to see this pluggins on pensados place but i never knew it was available .

 

You were going to the wrong place. Pensado's ain't got jack shit. You need to go to the sister's place.

 

This is a Win10 and McDsp problem. The last release of McDSP plug-ins were not compatible with win 10 because McDSP didn't make them compatible in the first place. They just work in Reaper and Pro Tools . McDSP fixed this in their latest version. Unfortunately it's not cracked yet or even if it is, still not released by the groups
I am having the same problem in Win10 S1 5.4 and it only works if I put a Soundtoys plugin ( AudioUtopia Release ) before it . But this doesn't work if you have a project where you have used the plugin without putting a Soundtoys before it , it just crashes S1 and doesn't load , Tried the compatibility mode , doesn't work .
on Win10 Pro. x64

 

Had The same Issue In Live 11 after using a Symlink for the bundle, when Futzbox alone had been working fine, and this solved it! You just made my day.

 

win 10 x mcdsp is not compatible? source?

im having the following crack releated issues with mcdsp ML4000. when engaging M(aster) and L(ink) on all bands. close the plugin open it, adjust one band. the link is lost. doesnt happen with legit. same version. thats literally the only plugin i pray to be fixed so i can leave my ilok at home and not risk losing it when on the go.

 

Having a similar issue with McDSP x Studio One 6.2 x Win10. MC2000 / MC404 doesn't work for me.

So i just loaded S1 in compatibility mode for windows 8 and surprisingly MC404 did work, and i could use it as normal. However in Win8 mode the DAW's GUI is a little laggy. I'd love to be able to use MC404 in regular Win10 mode.
Given that McDSP worked in Win8 mode, what might be the steps for me to take to get it to work in normal Win10 mode? (McDSP usually crashes the DAW as soon as i load it)