I installed SONAR 8.5 and most of my plugins today on my new StudioCat I7 DAW and I was able to get most everything working with either BitBridge 2.0 or JBridge.  The only one I've had issues with so far is BFD 1.5 which I'll only need if I open up one of my Legacy projects.  Of course it works fine in SONAR x86, so I can always get to those old projects that way.  BFD 2.1 is working fine under JBridge. 

I was worried that Voxengo's Analog Flux Suite might not work because I read a post on here that there were issues with it, but it seems OK... at least the TapeBus plugin is working fine.

I'm really loving the low latency performance of this new setup under Windows 7 x64.  I'm able to keep the buffers at 48 or 64 for most anything I throw at it.

Hey Genghis,

If you get a crash with Rapture (most likely the case), please send Cakewalk the MiniDump file the crash creates.

This gets stored inside the Sonar folder.  You'll see a MiniDump folder with the crash file in there.

The more people let them know about this problem, the better and faster they'll work on it.


Thanks a lot! :-)

Genghis,

Thanks a million!  Like I said, the more people report this, the better.

It is actually a shame one cannot work with such a great synth.  I have several old projects that use it and now I can't work on them because of this (and also because I refuse to install Sonar x86 :-P).  But, in the mean time, I believe you can use Rapture in Sonar 32 bit and it should work fine.  I can't tell you for sure though because it's been a while since I use Rapture in my projects, due to this problem.  So I just avoid it for now.  I thought Cakewalk solved this with the new update (v1.2.1), but it is still there.  Anyways, thanks again for your time.  Hope Cakewalk can find a solution soon.


Take care!

 
Windows 7 Fault Tolerant Heap
 
This new Windows 7 "feature" which is on by default should be disabled.
 
The feature tries to be clever with applications that crash a few times by chaning the memory manager behind the scenes to make the application more fault tollerant. Nice idea you think, except that the application is likely to run 15% slower.
 
So if you get a few Sonar crashes then the system may decide to slow the application down significantly to try to stop the crashes.
 
Here's an explanation of what it does....
 
http://www.theregister.co.uk/2009/11/18/windows_7_heart/page2.html
 
 
And here's Microsoft's page on the matter (with instructions on how to diable it)
 
http://msdn.microsoft.com/en-us/library/dd744764(VS.85).aspx
 
 
To disable the "Fault Tollerant Heap" entirely on a system you need to do the following ....
 
Set the registry key value HKLM\Software\Microsoft\FTH\Enabled to 0
 
After changing this value, restart the system. FTH will no longer activate for new applications.
 

Summary: Frontier Tranzport causing BSOD only on shutdown

I did a clean install of Win7 x64 and everything else. (I get a free day, and what do I do? Reload and backup my computer...sigh) The reason I did this, however, is because of the BSOD on shutdown and I wanted to pinpoint the problem as my Presonus, Digidesign, and other peripheral drivers are still in beta stage. And it's just nice to know thee things, isn't it?
So, it turns out it's the x64 beta driver for the Frontier Tranzport. It works great up until I decide to shut down, so I just kill the process in the Task Manager before finishing. Hopefully it'll get fixed but at least now I have a simple workaround.

That is all.

Cheers.

If you have a Frontier Tranzport, they now have a Win 7 driver and it will not "blue screen" the system when you shut down.  The older Vista driver will install in compatibility mode and work but you must manually do some file renaming and remove the startup item in the msconfig or you will get a "blue screen' when shutting down. 

I had to change the T.I. 1394 drivers to the "legacy" (got that from the Focusrite web site) for my Focusrite Saffire Pro 40 interface unit, to fix a dropout problem.

Other than the fact that some of  Sonar 8.5 Producer's advertised list of plug-ins are not 64 bit compatible and I had problems finding Sonitus presents until I found out they are accessed differently than 32 bit,  I haven't had any DAW problems (or for that matter Win 7 problems as I did a new install on a new 1TB hard drive - I have Win 7 64 bit Professional).  I have Vista 32 bit on a separate hard drive and Sonar installed on it and plan on keeping it since not all the plug ins are available in 64 bit.

Buddy110


Very nice thread Jose! kudos for putting it all together. Any other info, such as device manager tweaks, etc?

 
Thanks Buddy!
 
Not really, that's pretty much it. :-)
 
 
 

Yes, you're right Buddy.  Thanks for pointing this out.

I need to make some other changes to the OP too.  There are a few things that aren't really necessary anymore.  But I'll get to those later.


Take care!

Jose,
 
If you are updating the original list there are some corrections to the incompatible plugins.
 
Yellow Tools Independence, including Independence Free is now available as native 64 bit. The free 64 bit version works very well in Sonar.
 
And of course Toontrack have released their 64 bit public betas.

Made a mistake, sorry :-P
 
 

I hate when that happens. I mean, I really hate when that happens.

You've my sympathy, J.

K dub, John,

Thanks for the sympathy and words of encouragement.  I really appreciate that :-)

I just can't believe that it (the forum software) would do that though.  It's never happened to me before and I should've picked up on it when I first made the mistake of quoting myself.  That's what post #49 was (the mistake of quoting myself instead of editing the OP), and it showed the same kind of erratic formatting that is displayed in the OP.  However, I didn't think it would also delete part of the thread, which is what really got me mad.  The crazy formatting I could have dealt with, but now everything that was written in the first half is gone forever. 

I wrote all of that from memory and kept on updating it as I went, and with you guys' help.  So I don't think I'll be able to write all that again.  To be honest, I don't feel like witting all that again.  I spent a lot of time getting it to where it was, but I don't feel like going through that anymore.  Hope you guys understand.  But I don't know, we'll see.  I may fix it one day, but I don't promise anything.  At least most of the important stuff is still there -_-.

Anyways, thanks for your support guys.  It was a great OP while it lasted, thanks to you all.


Take care!

jamescater


 
Windows 7 Fault Tolerant Heap
 
This new Windows 7 "feature" which is on by default should be disabled.
 
The feature tries to be clever with applications that crash a few times by chaning the memory manager behind the scenes to make the application more fault tollerant. Nice idea you think, except that the application is likely to run 15% slower.
 
So if you get a few Sonar crashes then the system may decide to slow the application down significantly to try to stop the crashes.
 
Here's an explanation of what it does....
 
http://www.theregister.co.uk/2009/11/18/windows_7_heart/page2.html
 
 
And here's Microsoft's page on the matter (with instructions on how to diable it)
 
http://msdn.microsoft.com/en-us/library/dd744764(VS.85).aspx
 
 
To disable the "Fault Tollerant Heap" entirely on a system you need to do the following ....
 
Set the registry key value HKLM\Software\Microsoft\FTH\Enabled to 0
 
After changing this value, restart the system. FTH will no longer activate for new applications.
 

By following

Viewing Fault Tolerant Heap activity
Fault Tolerant Heap logs information when the service starts, stops, or starts mitigating problems for a new application. To view this information, follow these steps:

1. Click on the start menu
2. Right-click Computer and choose Manage
3. Click Event Viewer > Applications and Services Logs > Microsoft > Windows > Fault-Tolerant-Heap
4. View FTH Events

I see an option to disable FTH. Is it really necessary  to set the registry key value HKLM\Software\Microsoft\FTH\Enabled to 0? I dont even know how to do that anyway.

xLeviathanx

VigilantSound


Has anyone been able to run the (Rundll32.exe fthsvc.dll,FthSysprepSpecialize) Command to clear the list of apps that FTH tracks??

I cannot get this to run at all, it claims Rundll32. is not a valid 32 bit command? I am running 64 bit btw...?

I am on W7 64-bit and ran the command. I didn't get an error but I didn't get any kind of confirmation or pop up message afterwards.

By the way, does anyone remember the first part of Jose's post about the Firewire tweak and setting it to Legacy? I have a MOTU 896 HD and wondered if I would gain anything from trying out that tip.

Thanks!

Could these be the missing instructions?

1- Click the Start Button, type devmgmt.msc in the “Start Search” box and press Enter.
2- Expand the "IEEE 1394 Bus Host Controllers" node in the device tree on the right hand pane
3- Right click the host controller node select "Update driver software ..."
4- Select "Browse my computer for driver software"
5- Select "let me pick from a list of device driver on my computer ..." and Check the box before “Show compatible hardware”.
6. Choose the second option---1394 OHCI Compliant Host Controller (Legacy), and click next to update the driver.

Hi Folks,

Is there any workaround for the old Cakewalk FX suite?
I just installed Windows7 64bit. Everything works just fine, including older VST plugins. But I am using the older Cakewalk effects in existing projects... I still have the old Vista harddisk in my computer, and the boot manager is working fine. Yet, I don't want to go back.

Thanks,

Wilko