eratu


Oh, one other quick note:

I did change the AUD.INI file with the standard tweak for multi-core:

I set the ThreadSchedulingModel=2

Not sure if it did much, but I set it anyway. :)

At least in Vista, this thing worked awesomely. 
 
I don't look at Sonar's CPU meters though.  I always use the Task Manager.
 
 

eratu


Am I correct that Beatscape is 32-bit????????

Sadly, yes :-(

Jose: Thanks, man. Thought that was the case, and I agree. :(

UnderTow: Ultimate is 23% cooler than Pro.

SONARtist

eratu
Am I correct that Beatscape is 32-bit????????
jose7822
Sadly, yes :-(
 
Guys, I presume that from the sad smily that you use Beatscape quite a bit.  I'm using it a lot and was wondering whether it was EOL s/w (as it seems a lot of people didn't appreciate it enough - sure, it's a bit buggy, but there are workarounds).  Anyone know if Beatscape is going to be continued (is it 3rd Party ?) ?

BTW, great thread and thanks for the updates !

I don't use Beatscape a whole lot, but I do use it to trigger some drum samples.  The Matrix View can surely do this, but I find it too big for this :-P
 
But Beatscape is an original Cakewalk plugin (not 3rd party), so I'm sure they'll keep developing it.
 
 
Take care!
 
 

Okay, now I'm having problems with Dimension Pro x64. It says multisamples not found when loading a patch. Incredibly annoying. Will uninstall and then reinstall. This should not be this much of a hassle for Dimension Pro.

EDIT: Seriously, I'm annoyed. I've already tried installing twice. This is starting to !@#$ me off. All I'm doing is installing the Dim Pro x64 version, and I change the sample library location to another hard drive. One more attempt.

Hang in there, bud

You may not realize this, but I'm sure there are a lot of forum lurkers watching your every move - thinking (as am I) "there I am in the future"

We all wish you the best, and I thank you for this post as I will be there too, later

Thanks, Brammer! LOL! I appreciate that. I just went through a bunch of Dim Pro posts in this forum that appeared to have similar problems. I tried several things, including editing the registry, etc. No go. Dim Pro x64 installation appears to have some sort of snafu, at least with my system. Disappointing. Hard to imagine what that issue might be considering THERE'S NOTHING ELSE ON THIS COMPUTER except Sonar and Reaper right now. It's about as virgin of a Win 7 installation as you can get.

After taking a deep breath, I'm trying one more time, only this time I'm just installing the Dim Pro 32-bit version. Let's see if that works.

Update on Dim Pro:

Okay, I just finished installing the 32-bit version instead of the 64-bit version. Now, it works.

However, I'm quite disappointed that the 64-bit install did not work. This is supposed to be a 64-bit plugin, and I'd rather run that then the 32-bit version via BitBridge.

Additionally, when I click on the DXi version of Dim Pro in the plugin menu, it fails to load. Obviously, since it is the 32-bit version. Why would it even show up in that list? Not a huge deal, but it really shouldn't even show up. Only the VSTi version loads, and that via BitBridge.

Summary: Not impressed with this phase of the installation. But at least I have Dim Pro available again.

I may try to install the x64 version again, now that the 32-bit version is already installed. Perhaps that will do it?

Hey Eratu,

I have reason to believe that, now that you have the 32 bit version up and running, installing the 64 bit version should now work.  I just noticed that Dimension Pro installs almost everything under Program Files (x86) /Cakewalk /Dimension Pro.  The exception is the Dimension Pro 64 bit .dll which installs under Program File/Cakewalk Dimension Pro. 

Give it a shot :-)

Jose: Unfortunately, it didn't work. Dim Pro x64 once again could not find the multisamples. However, Dim Pro 32-bit still could. :( I think I'm giving up on Dim Pro x64 for now, and will just stick with Dim Pro 32.

Phoenix: I've checked the registry a dozen times, all appears correct there, no luck with Dim Pro x64. But 32 seems okay with BitBridge.

So, I've now uninstalled both the 32-bit and 64-bit versions of Dim Pro, and now, I will re-install just the VSTi version of Dim Pro 32-bit. I think I've paid my dues on it now, so if someone else wants to take a stab at Dim Pro x64, please have at it and PLEASE let me know if/how you got it working.

Update:

Up and running with Dimension Pro 32. Working and sounding fine with BitBridge. Not happy AT ALL with the waste of time on 64. Life goes on...

Now to move forward with other plugins and see what happens. Fingers crossed.

Jose: No idea if they have a download version. Sounds like a great idea if they do.

Just installed some FabFilter plugins. Quick and easy installation. They are 32-bit plugins so they require BitBridge.

However, I have run into what could be a show-stopper already. :(

These are critical plugins for me...

I cannot get FabFilter Timeless 2, Simplon and Volcano 2 to work well with BitBridge.

Basically what happens is that after I start loading up instances onto tracks, fairly soon I will get "The folowing plugin failed to load..." error message. Sometimes it takes 3-4 plugins, sometimes 7-9 or more... but eventually I will get that error. Try putting 2-3 or more per track, and put different FabFilter plugins on one track, that tends to get it to fail.

I think it happens when 2 or more of these plugins are loaded into one BitBridge instance, but I could be wrong.

Anyway, I would appreciate it if someone out there could install these plugins (demos are available) and see if you run into the same problem on x64 with BitBridge.

This is a fairly large problem for me since I use several instances of these plugins in many projects. :(

Looks like I have to break out the JBridge adapter already.

Stopping for the night. More tests tomorrow.

YOu probably have doen this already with respect to Dim Pro but just in case you haven't.

Did you edit the registry (ie make sure all references to Dim Pro were deleted) when you uninstalled before reinstalling?

brammer to eratu >> Hang in there, bud.  You may not realize this, but I'm sure there are a lot of forum lurkers watching your every move - thinking (as am I) "there I am in the future"

We all wish you the best, and I thank you for this post as I will be there too, later
Hang in there, bud

+100

Jose: Thanks, man, great idea, I just did that and see below for my latest report.

SONARtist, brammer: :) Still going... hope to get this thing resolved...

UPDATE:

Okay, I've now sent emails and/or posted to Cakewalk, FabFilter and JBridge... and also have run many more tests on FabFilter plugins.

To sum it up, this is what I wrote to Cakewalk:

--------------

I'm continuing to test Sonar 8.5.1 x64 in Win 7 x64 and besides the
Aliasfactor issue (which is a very low priority for me right now) I've
hit a pretty big snag with FabFilter plugins and BitBridge 2.0.

I'll be contacting FabFilter shortly, but I'm wondering if there's
something you can do or suggest. I've done a lot of testing, and it
appears FabFilter plugins and BitBridge 2.0 don't currently work well
together. That's a critical set of plugins for me.

Basically what happens is that when two or more plugins of different
types from FabFilter are loaded up on to one BitBridge 2.0 instance,
the second or third one is rejected with the following error: "The
following VST plugin failed to load..."

I've been able to force a conflict by forcing plugins to be loaded
onto one BitBridge server.

I've also been able to get many more plugins loaded by forcing just
one type of FabFilter plugin to load on one specific BitBridge server.

For example,

Try loading FabFilter Timeless 2, Simplon and Volcano 2 on one
BitBridge instance... it will fail.

However, if I manually designate BitBridge server 1 for just Simplon,
then I can load several Simplons without a problem. Then I designate
BitBridge server 2 for Volcano 2 and can load many instances of
Volcano 2 just fine, and so forth.

This is obviously tricky to keep track of (this workaround is needed
for all the FabFilter plugins I tested -- Twin 2, Volcano 2, Timeless
2, One, and Simplon).

If I designate 5 BitBridge servers -- one for each -- this seems to be
the kludgey workaround.

So, obviously, something strange is going on when two or more
different FabFilter plugins are loaded into one BitBridge instance.

The problem is not immediately noticeable when you are using the
round-robin auto-assignment of BitBridge since it automatically
spreads out the instances to different BitBridge servers, however,
even in that mode, after 5-6 different plugins, you'll hit the
conflict, so the only way to manage it is to force one plugin type per
BitBridge server.

I use these plugins quite often in many of my projects, so this is a
pressing issue to resolve for me. I've also been in touch with the
JBridge developer, and he's working on a possible solution as we
speak, from his end. And again, I'll be in touch with FabFilter
shortly. I hope there is something that can be done natively inside
BitBridge about this ASAP.

Best, James

----------

As stated, I was also in touch with the JBridge developer, and I've already contacted FabFilter.

FabFilter has not yet gotten back to me, nor has Cakewalk. However, amazingly, the JBridge developer, João, already got back to me! Wow! Within several hours he was able to come up with a possible tweak to JBridge that might do the job. He just sent me an internal build of JBridge "1.14c2" and my preliminary test is that it works far better than before. He said he didn't know if it would break anything with other plugins, and I have no way of knowing that at this time. I'll be in touch with him again so perhaps we have a solution!

Due to João's incredibly fast turnaround time, may I humbly suggest that we support this guy and send him the money he needs for continued development. With this type of resource available to our community, we need to respect his great work and support him.

So, summary of status:

1) FabFilter really needs to release an x64 version. But since they haven't, then ideally, their products will work perfectly with BitBridge out of the box. Right now, they don't. Hopefully between Cakewalk and FabFilter we'll get a solution.

2) In the meantime, João of JBridge fame is working on something. It's not fully tested, but it shows a lot of promise.

3) Also in the meantime, it's possible to force BitBridge 2.0 to spread out the plugins across different BitBridge instances as long as you keep one type of FabFilter plugin per BitBridge instance. A pain in the neck at the very least, but it does appear to work if you are careful.

4) More to come on this issue... will report back any progress between any of these parties.

5) FabFilter makes some amazing plugins, worth every penny. May I suggest those of you who like their plugins or own their plugins to contact FabFilter to bring further awareness of our x64 needs...