Author Topic: 32-bit / 64-bit in Windows 7  (Read 1162 times)

0 Members and 1 Guest are viewing this topic.

Offline chrisNova777

  • Administrator
  • Posts: 8296
  • Gender: Male
  • "Vintage MIDI Sequencing + Audio Production"
    • www.oldschooldaw.com | vintage audio production software + hardware info
32-bit / 64-bit in Windows 7
« on: March 04, 2017, 12:49:55 PM »
http://www.soundonsound.com/sound-advice/pc-notes-13


If you're having trouble mixing 64‑bit and 32‑bit audio host applications, plug‑ins and instruments, the third‑party jBridge utility may solve your problems. It's shown in action here running the 32‑bit Wusikstation inside 64‑bit Cubase 5.

Quote
As I mentioned in last month's PC Notes, Windows 7 is now available, and while a new operating system is highly unlikely to make audio software run more efficiently, many musicians with ambitious sampling requirements (such as those running giant orchestral libraries) are considering buying a Windows 7 64‑bit version so that they can utilise more than 4GB of RAM.

Musicians also seem to be beseeching developers to release native 64‑bit versions of all their favourite VST instruments and plug‑ins, but I doubt that this will happen widely just yet. Few developers can justify spending all the time needed to perfect a new 64-bit release that would sound identical to the 32‑bit version, unless users are prepared to pay for it. It seems far more likely that 64‑bit versions will appear, along with new features, as chargeable upgrades.




Quote
Building Bridges

For many musicians, the lack of 64‑bit plug‑in versions may not be a problem, since most 64‑bit sequencers provide 'bit bridge' wrappers, so that you can carry on using your existing 32‑bit plug‑ins inside your new 64‑bit environment. There may be little practical advantage to having a 64‑bit version of your plug‑ins and instruments. After all, the latest BitBridge XR incarnation in Cakewalk's Sonar X64 allows 32‑bit plug‑ins to collectively access up to 128GB of RAM (the maximum supported by Vista Ultimate X64 or Windows 7).

On the other hand, Steinberg's VST Bridge for Cubase/Nuendo plug‑ins can only share a maximum of 4GB RAM (which is still significantly more than the standard 2GB of 32‑bit applications), but sadly it's not proving very compatible with third‑party products. Steinberg insist that VST Bridge is a 'transitional aid', and that it's up to all other developers to release native 64‑bit versions of all their products, but for the reasons given above I don't think this will ever happen across the board, and there are plenty of 32‑bit products (including some marketed by Steinberg) whose development has already ceased.

However, for those who do have compatibility problems with their 32‑bit plug‑ins inside 64‑bit sequencers, there's also a third‑party product that seems to be gaining a lot of fans. The demo version of jBridge (http://jstuff.wordpress.com/jbridge) can be downloaded and run for 20 minutes before it times out, and once you're happy that it runs your 32‑bit stuff, it's only 15 Euros to purchase a license. You can also use jBridge in conjunction with the dxshell wrapper available from Polac (http://xlutop.com/buzz/zip/dxshell_v1.0.2b.zip), to enable older DX plug‑ins, instruments and MIDI‑based MFX plug‑ins to be run in 64‑bit sequencer hosts, and even to run 64‑bit plug‑ins in 32‑bit hosts.