OK.  Sorry for the misunderstanding  It sounded to some of us  like you wanted to use 32 bit and 64 bit version of the exact  same plugin. 

Why use a 3rd party chained when Sonar can already do that. Make fx chains that is.

mudgel
Why use a 3rd party chained when Sonar can already do that. Make fx chains that is.

They are not linear chain tools, rather network tools with their own controls of volume, panning, dry/wet etc ...
I've just seen Sonar's fx chains as an easy way to link several fx plugins into one, displaying and automating preferred controls.
But there might be something that I don't know or realize about them, so if there's a way to do this with fx chains please let me know how!
 
http://www.vstforx.de/index.php/product-details
http://www.ddmf.eu/product.php?id=3
 
You can probably achieve at least some of this with a clever setup and using f.e. sends and buses.
There's also sidechaining and some plugins with multiple parts have some routing internally that solves it in those particular cases.
But as I see it not even these combined give this flexibility and simplicity.
In this format it also goes into the creative area, not just problem solving.
 
By the way, if we could just "split" the signal in the beginning of an fx chain and it was summed in the end of it a lot of this could be achieved. Especially if we could use fx chains inside fx chains.

mudgel
Why use a 3rd party chained when Sonar can already do that. Make fx chains that is.

Well if you tell me how I can do parallel processings with the fx chain,I'll gladly use it..
 
An example:
I want to have 3 bands treatment on a Bass. The low with just a compressor, the middle with a distortion and a compressor, and the high with another distortion and maybe a flanger  and of course a third compressor. The 3 compressors are sidechained with my kick track. One last thing is I want to add an automated delay on just the right channel.
This kind of thing is simple to do with those "3rd party plugins".Can you do this with FxChains?
 
I sent cake walk a feature request to get a modular FxChain, but I don't think they'll do it.

Iv just looked at the website you linked to. Interesting for sure.

Also noticed that VstForx is only 32 bit at the moment with a request for 64 bit version being shown. That means it's currently being loaded by Bitbridge in Sonar x64. Is VstForx loading your 32 or 64 bit plugins?

vstforx is now x64.
 
But, x64 loads only x64 and x86 only x86...The reason of the post...

Yeh I just found the updated information on the blog regarding 64 bit. It sounds in the info that the 64 bit version should load both 32 and 64 bit but I guess your saying it doesn't.


JBridge allows you to process plugins so that they appear as 64 bit and renames them. Do that rather than set Sonar to use jBridge by default. I would put all the 32 bit plugs that you want to use in a single folder and then have jBridge process them and then put that folder into Sonars VST scanners path.

That's what I intend to do..
Hope I won't get weird jBridge things with my plugs.

If you have jBridge process the plugins, it will create copies of them, leaving your originals alone.

guigz2000
That's what I intend to do..
Hope I won't get weird jBridge things with my plugs.

A bit curious - how has jBridge worked out?
 
By the way - the reason for Cakewalk not finding the 32-bit is very probably that they have the same VSTID. So the right way to go about it (in the rare case when both versions are needed) would be to ask the plugin developer to use different id's. Failing this you could possibly use what's under "ID Hacking" at this link:
 
http://www.soundonsound.c...icles/pcnotes_1107.htm
 
It is risky so don't do it unless you both know what you're doing and feel that it's worth it.
Note that you might have to search the id reversed, instead of f e "Plug" you use "gulP" - it's mentioned but easy to miss.
 
Edit: It would of course be nice if it was possible to make Sonar accept 32/64-bit with the same id and might be worth a feature request. As far as I know there's no way to make that happen within Sonar right now, if someone knows differently please chime in. It is a fair rule I guess, id's should be unique. As this is also probably a rare case, question is if it's worth the Bakers effort though.