i hope they get it done (at least in beta state) till the official release of windows 7 ...
is it only EW play engine that causes what some of you describe or is it a more universal behaviour? the main difference in between kontakt/exs/halion/play and e.g. vienna instruments is how they stream from disk. they all don't load 1g into RAM for a piano patch (unless you turn off streaming which is a bad idea).
It's only the EW Play engine... but i also had "engine crashes" with Kontakt by adressing too much RAM...
the main issue remains as EWs fault, because the engine just works very unstable within 32bit.
the first 15 minutes work just great, but afterwards serveral issues are going to appear.
things like if you're loading up a complete different instrument, PLAY doesn't get it at all - and of course: no change to the sound,
or the sound gets shorter and shorter, till crackle...
or cubase just crashes..
and there are more of this kind ...
east west is the biggest reason for me to get into the 64bit dimension...
just waiting for windows7 to get myself a new machine with loads of ram.
so i have to stay informed which of my plugins won't work with the new system, and my Virus TI is the biggest point NOT to update
checking this forum every day (not just once) with hope...
I have no use for very good orchestral samples though.
Only one Quantum Leap Piano Patch can take more than 1GB - and it's not even an extraordinary instrument.
Even the very Basic NI Kontakt-Library can kill your Ram with no problem at all.
like all the others ...
got the symphonic orchestra and ql pianos myself...
actually, not just that it takes a huge amount of ram, the 32bit-PLAY-engine works very unstable for me.
they recommend to use the library within a 64bit-host, which is better anyway.
But as you may know, Windows 7 is just the "bigger brother" of Vista.
So, if you get it done within Vista, there's almost nothing to add to get it on Windows7 working...
btw. XP64 wouldn't be a good choice... since xp64 generally is supported by just a couple of developers...
Vista64 and 7 would achieve more benefit...
maybe because access owns macs it's more important...
1. support for MacOS 10.6 (Both 32 bit and 64 bit).
[size=10]2. -VC: Reaper (unsupported host) was crashing when VC was instantiated (fixed)
1. is it much work to port the mac-64bit version into windows-64bit? sadly, no windows version atm
2. ...you support an unsupported host?
I just recognized, I got it totally wrong!
Even Vista64 would need 64bit support... so there actually IS a system to get things done!
, i think they dont want to have to rewrite huge sections just because MS change something at the last minute...
do you mean "Microsoft"?
last minute decision?
where have you been?
vista64 was released january 2007. not to mention XP64.
as you can see, there was a lot of time to get prepared...
Yes, it is.
... you cannot even use (and install) the virus within a 64bit environment ... i know, it's a shame.