Ymmv,
susiwong
These plugins won't stop working because you use Win 7 x64...dickiefunk wrote:I'm trying to put off going to Windows 7 64 bit as long as possible as I don't want to have to stop using these!!
Wow that's great news!!xx JPRacer xx wrote:These plugins won't stop working because you use Win 7 x64...dickiefunk wrote:I'm trying to put off going to Windows 7 64 bit as long as possible as I don't want to have to stop using these!!
Superb!! Happy Days!!!!susiwong wrote:Most software issues in x64 are caused by installers, registry entries, paths and so on, none of that applies to Bootsie's plugs, or to any other dll-only plugins fwiw.
The real problems are driver related, that's what you have to investigate before jumping ship.
I'm using Bootsie's plugins on XP64 without the slightest glitch ever.
Ymmv,
susiwong
Asus P5K-E Wifi AP, Q9450 @ 3.2, Thermalright XP120/Papst, 4GB OCZ, 7600GS, HDSPe Digiface, 2 UAD-1 PCI, UAD-2 Quad, Duende PCIe, Antec P-182, Seasonic S500, XP64, C5
Just noticed you're planning to use the 64bit version of Cubase - really ?dickiefunk wrote:Superb!! Happy Days!!!!susiwong wrote:Most software issues in x64 are caused by installers, registry entries, paths and so on, none of that applies to Bootsie's plugs, or to any other dll-only plugins fwiw.
The real problems are driver related, that's what you have to investigate before jumping ship.
I'm using Bootsie's plugins on XP64 without the slightest glitch ever.
Ymmv,
susiwong
Asus P5K-E Wifi AP, Q9450 @ 3.2, Thermalright XP120/Papst, 4GB OCZ, 7600GS, HDSPe Digiface, 2 UAD-1 PCI, UAD-2 Quad, Duende PCIe, Antec P-182, Seasonic S500, XP64, C5
Thanks for the info. I think I'm getting a little confused heresusiwong wrote:Just noticed you're planning to use the 64bit version of Cubase - really ?
The bitbridge in Cubase is rather flaky to put it politely.
If 4Gb project size is enough (it sure is for me, including Superior 2, Jamstix 2, Kontakt with Scarbee bass and a few other instruments, various VSTi and audio tracks in every project) you'll be much better off with the 32bit version of Cubase in a 64bit OS.
I was talking about compatibility in that scenario, not in C5/64![]()
That I don't know.
Cheers,
susiwong
In this context all we're talking about is project size regarding RAM, this is not about sound quality.dickiefunk wrote:Thanks for the info. I think I'm getting a little confused here![]()
What the difference between using Cubase 5 32bit and 64bit?
When using a 64 bit host you need 64 bit plugins. You can use 32 bit plugins but you'll need a bridge and the one in Cubase is not very good apparently (I don't really know, I don't use Cubase).dickiefunk wrote:Thanks for the info. I think I'm getting a little confused here![]()
What the difference between using Cubase 5 32bit and 64bit?
Correct except for the last paragraph, as you yourself noted.xx JPRacer xx wrote:When using a 64 bit host you need 64 bit plugins. You can use 32 bit plugins but you'll need a bridge and the one in Cubase is not very good apparently (I don't really know, I don't use Cubase).
But Windows 7 x64 don't have any problem with 32 bit apps. So you can install the 32 bit version of Cubase on Win 7 x64 and use all your 32 bit plugins with no bridge needed. The only advantage of using 64 bit Cubase is it can use more than 4 gig ram for itself.
But when using a 32 bit app in Win 7 x64 each app can have it's own 4 gig ram to itself. In Win XP 32 you can use ~3 gig ram total for all the applications running. Even if you use only 32 bit apps in Win 7 x64 each apps can use a full 4 gig ram for itself. That's great when multitasking with heavy programs.
ps: I think 32 bit version of Windows can use 4 gig for each process running but when doing this it's using virtual memory (slow) since it can't address more than 4 gig physical ram (but I can be wrong on this).
Not fixed yet in 1.5! Any ideas?bootsie wrote:The crashes in Reaper are fixed. I will check about the buffer clearing after rendering ...Dandruff wrote:What about this? Fixed in 1.5?Dandruff wrote:Bootsie,
the crashes in Reaper seems to be fixed indeed. Many thanks for this!
But this problem isn't:Dandruff wrote:epicVerb in Reaper:
render-burst.rpp (12.3kB)
-> load the project
-> file -> render -> render
=> once render is finished you hear this:
render-burst.wav (154.9 kB)
This shouldn't happen. There should be silence. When using Reaper's ReaVerb, there's no such sound after render is finished.
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement
© KVR Audio, Inc. 2000-2026