x64 - What's IL's schedule?

[ThomasN]

Sorry, if this has been discussed/asked before.
As I'm thinking of switching to Win7 x64, I did some research on compatibility issues. I read on the Cubase forum, that IL VSTis (at least the none Maxx Claster ones) aren't even recognized by Cubase 5 x64. I'm aware of the fact, the Steinberg's bitbridge is quite lousy, but yesterday I also tried jBridge and although the plug-in (DirectWave) loaded fine, the GUI didn't show in the jBridge wrapper.
I own 4 of IL VSTis and my projects rely heavily on Directwave and Sytrus, so the question is, when can x64 versions be expected?

Thanks in advance for your answer.

[UltraJv]

http://en.wikipedia.org/wiki/Hell_Freezes_Over

[GeorgeZ]

You mean, what's Delphi's schedule?

[tony tony chopper]

Plugins by Maxx: possibly, as they're written in C++.
Mine: chances are very low.

[ThomasN]

You mean, what's Delphi's schedule?

Thanks for that interesting hint! Didn't know that it isn't possible to code x64 plug-ins in Delphi. In which language is Directwave written?

So, would it be a bit exaggerated to say, when I want to go with today's up-to-date technology, it's better to not count on IL? I mean it's at least an important point when buying new plug-ins.

[UltraJv]

You mean, what's Delphi's schedule?

Thanks for that interesting hint! Didn't know that it isn't possible to code x64 plug-ins in Delphi. In which language is Directwave written?

So, would it be a bit exaggerated to say, when I want to go with today's up-to-date technology, it's better to not count on IL? I mean it's at least an important point when buying new plug-ins.

Up to date (cutting edge) means trouble, reliable means tried and tested. Windows 7 64 bit runs 32 bit software and plugs very well. If you dont do youre homework and you jump into 64 bit DAW territory without seeing that its early days still in DAW land, you will get burnt. Some plugs will NEVER go 64 bit. Flaming the devs dosnt help.

[ThomasN]

Windows 7 64 bit runs 32 bit software and plugs very well.

I know, but what if my current projects hit the 2GB mark regularly, because I use a lot of samples and RAM demanding plug-ins? A 32 bit host on a 64bit OS wouldn't help me here in any way.

If you dont do youre homework and you jump into 64 bit DAW territory without seeing that its early days still in DAW land, you will get burnt.

First, I haven't done the jump yet, therefore my initial question.
Second, who hasn't done his homework? My workstation is now almost 2 years old, and the CPU supports 64bit and my mainboard up to 8GB RAM, but for what if software devs are so phlegmatic in doing the jump to 64bit? And this ISN'T directed to IL solely. Actually I coudn't believe it, when I saw that microshit made a 32bit version of Win7 and that's where the problem lies in the first place. But that's just my opinion.

Flaming the devs dosnt help.

I didn't flame anyone, I posed a justified question!

[UltraJv]

Windows 7 64 bit runs 32 bit software and plugs very well.

I know, but what if my current projects hit the 2GB mark regularly, because I use a lot of samples and RAM demanding plug-ins? A 32 bit host on a 64bit OS wouldn't help me here in any way.

If you dont do youre homework and you jump into 64 bit DAW territory without seeing that its early days still in DAW land, you will get burnt.

First, I haven't done the jump yet, therefore my initial question.
Second, who hasn't done his homework? My workstation is now almost 2 years old, and the CPU supports 64bit and my mainboard up to 8GB RAM, but for what if software devs are so phlegmatic in doing the jump to 64bit? And this ISN'T directed to IL solely. Actually I coudn't believe it, when I saw that microshit made a 32bit version of Win7 and that's where the problem lies in the first place. But that's just my opinion.

Flaming the devs dosnt help.

I didn't flame anyone, I posed a justified question!

There is a similar thread on the subject, Ive posted this from it :

aircargo wrote:
But obviously memory is a big problem for many with 32bit DAWs. It's
not so much a question of whether you can write a faster plug as it
is you writing a compatible plug with our 64bit DAW because we
switched up so we'd stop running out of memory.

Zaphod wrote :
well, here the discussion is subtle. For a standard lightweighting
plugin there is no apparent reason for upgrading. The issue is for
plugins with high memory requirements (samplers/romplers), their
developers are pushing in the x64 direction (we suggested to all our
customers to upgrade in some way). For the exception of reaper, a 64
bit daw can't load a 32 bit plugin, unless you are bridging the
process in some way (local udp/tcp, or interprocess communication).
So here the devil. The x64 conversion is not simple at all, it
requires a lot of testing, a in some case a lot of headaches.
Sometimes there is even a bigger issue: a x64 compiler was not
released (for example bcb). It's true that c++ should be compiled
everywhere, but SOMETIMES developers rely on local libraries (in the
same example, vcl)

So its not devs or Microsofts fault. Some apps/plugs wont be able to
be ported to 64 bit. People who want to experiment are using jbridge to act as a 32 to 64 bit go between. You can play with 64 bit stuff now but its still experimental. Mac hasnt even started 64 bit DAW support.


Heres the related thread :

http://www.kvraudio.com/forum/viewtopic ... sc&start=0