Thank you for the help guys!
I will try the /3GB in the boot.ini file and see how that works out (hopefully that wont kill the kernel).
Also, I Should have mentioned i was aware of the RAM limit in 32-bit systems to spare you guys some air
Anyways… how’s that 64-bit version of renosie coming along?
On windows, you’ll need 64bit versions of every single plug you are using then. So its good that Renoise is still 32bit on windows.
A 32bit host needs 32bit plugins, a 64bit hosts 64bit plugins. And there are just a handful of 64bit plugins out there?
Also 4GB is quite a lot. What we need instead is large sample streaming (not loading huge samples into memory) support…
I think a huge advantage of streaming is the fact it is the first step to HD recording in Renoise
For sample based instruments it would be nice when there is layers and stuff so yeah streaming is nice albeit as an option because if you are in 64 bit and you have enough RAM to not stream an instrument then why stream it ? RAM is much quciker anyways and 64 bit is the way of the future
yes, there are just a bunch of 64-bit plugins, but basically it’s because only RAM-hungry plugins are in need for a real 64-bit version, while the others can rely on a wrapper.
Garritan ARIA, and East-West PLAY are already available in 64-bit fashion. I hope Kontakt will be too; I actually didn’t understand yet if there is a real 64-bit version of it, but I don’t think there is any yet.
If Renoise64 will be released, I would consider switching to a 64-bit OS, although you would also need 64bit drivers for your soundcard, which is another non-obvious issue you may face with…
Actually there is a 64 bit ASIO driver wrapper too for any card
I have tried it with about ten cards so far and all worked perfectly
Now i just gotta try and get the dev to release it standalone instead of just as part of his DAW
The DAW is in early alpha and i hope i can get him to release the driver wrapper sooner than the DAW
s this a generic wrapper VST? Haven’t heard of this before. Could you post a link?
Well, the 32bit version works just fine in 64bit windows + you can use up to 4GB instead of 2GB memory, so thats already an improvement. There much much more to do to make Renoise as sample HD streamer. That has not necessarily something to do with the 64 port…
what follows is my experience, but I am trying to think as generally as possible.
I think that those who are considering the migration to a 64-bit environment are really not interested in a complete 64-bit porting of their whole VSTs set; having that bunch of RAM-hungry plugins ported to 64, using others through a bridge if needed to mix them up, would suffice.
A perfect 64-bit system would comprise:
64-bit version of Renoise
32-bit version of Renoise
64-bit version of Kontakt, PLAY, ARIA
32-bit version of other plugins, and 64-bit version where available
jBridge or similar
the idea is that, when you need more than 4GB of RAM, you are probably making sample-based music which will probably use samplers rather than synths. about CPU usage, I can make the example of my system: I have a 5-years old dual-core AMD CPU, but the CPU is enough to play an entire orchestra; what limits me is the HDD speed and the RAM.
for synth-based music, I would be happy with 32-bit Renoise loaded in 64-bit OS.
do you mean that I could load Kontakt64 in Renoise32 under Windows64 and be able to load more than 4GB of samples? well, this would enough for me then.
there are multiple easy ways to fix this, really: usually you use Kontakt with aliases, so if you save the entire Kontakt multi as a single NKI file, you only have to load the new 64-bit DLL once, reload the NKI file and set up the aliases. for othe plugins, saving the preset and loading it back can be made in minutes.
also, I would not mind if I could not upgrade past songs.
Problem is for me that i want to use as a little VST plugins as possible and use Renoise specifically for its sample playback abilities
So 64 bit Renoise is way more useful to me than being able to load 64 bit plugins into 32 bit Renoise