the current 32bit version 7.6 orion doesn't support addressing more than 2gb. in practice on an 64bit os you get around 1.3gb before it fails to service any more instance creation of generators/fx..etc.
however you can get close to 3gb virtual mem for a 32bit user mode app on an 64bit os, if the /LARGEADDRESSAWARE flag was used while linking ( ref msdn )
if this cannot be fixed now for some strange reason, can this be expected to be fixed for the next release of orion? its hardly a matter of adding an extra linker flag and hitting build.
large memory supportModerators: Christophe, Mark
9 posts
• Page 1 of 1
large memory supportSounds like you stumbled across something important. Good job suneel!
large memory supportVery interesting.
Actually, because of this issue, I have lost one of my song I cannot open anymore on my new computer. Windows 7 64bits, 4 gigas. (this song had kontakt 4 and omnisphere I guess...) So I REALLY REALLY hope for a new release with a fix very soon. I use dozens of instruments and effects at the same time, but I still feel very limited with Orion. Personally, I consider it's a MAJOR ISSUE with Orion. I use Orion 7.62 - 32bits.
large memory supportI still rekkon its the vsts in use.
I use 7.62 and my track count is usually pretty high - 24 or more plus effects. Last one was 36ch audio plus fx and current project is 22ch audio with about 10 midi ch still in use plus fx on all midi ch and some audio ch = buss & master fx - machine usually peaks around 17-22% by OP rekkoning. ---=u f o=--- /Radiation Mutant / Snee-Nee-Iq
large memory supporthmmm... When I open that many channels, Orion crashes.
So what could it be? A broken vst? I've tried to rename the folder vstplugins and open the song again, but it still crashes anyway, as if the file was corrupted. I have a song ("golden boy", you can find it on myspace), I have tried recently to re-open it, and use Amplitube 3 instead of Amplitube Metal (favorite amp now, by the way). Orion crashes as soon as I try to open Amplitube 3. I don't even have time to see its interface. But it works very great in other songs, with less channels. Also, in a few songs with already a lot of channels, I have just tried to open new vsts to confirm what I think, and in the end, I have the message "out of memory". Sometimes, I use Directwave, Omnisphere, and Kontakt. And that means a LOT of channels. Anyway, I'm stuck. And I have to limit the number of instruments I use. Last edited by RebeccaPowers on Fri Mar 05, 2010 9:13 am, edited 1 time in total.
large memory supportyep its obviously the vst's. orions native synths and fx dont eat up too much ram. the cpu use only hits max 40-50%, but i am talking about ram. you hit more than 1.3gb virtual memory(add colum in task manager), then the rest is unpredictable.
large memory supportin my case i dont have crashes while opening sfs. its only while working on one you cannot add more instruments. thats probably what i would have done too to find the problem vst. is this when you load and sfs or work on an existing one? you could check on the task manager to see how much memory orion is taking. But you need to look at virtual memory column called VM Size. You need to add it to see it, by default it is not shown in the task manager. limiting the number of instruments is easy once you have a concrete structure for the song. i just render to wav and re import the channel as an audio track. But the problem is in the idea phase where i def tend to experiment before giving the track a feel. it is not uncommon to have 2 leads and 4 support synths. now for each of those synths you are going to add fx etc. then you are going to import drums for konkat, samples from omnisphere....so obviously you are going to run out of ram soon. If orion 32bit was compiled with the /LARGEADDRESSAWARE flag you can go up to a little over 3.5gb in a 64bit os, which is around +2gb over the current 1.3gb limit.
large memory supportWell I hope they'll do the /LARGEADDRESSAWARE thing you're talking about.
Concerning my crashes, I have two different problems. One sfs file which crashes Orion, but strangely it used to work on my previous computer, windows xp 32bits, only 2 gigas of ram, outdated. I have no idea why. Tried to change vsts, render output, etc. Nothing works. It's like the file is broken. The other crash is when I try to open too many vst (instruments or effects), and sometimes I get the message "out of memory". (so yes, to answer your question, it happens when I'm working on a song with already lots of instruments) Thanks for the tip about render the song to wave, I actually thought about that this morning. Very good idea. Not perfect but I guess it could help. I have checked on the task manager, sometimes Orion takes 750 megas of memory, but I have 4gigas! So I don't understand how it can run out of memory. And even on songs with lots of instruments, Orion uses only 25% of the CPU power. Big change from my previous computer, which had only one processor, a pentium IV 3,2ghz. It was impossible to create anything. But anyway I WANT /LARGEADDRESSAWARE Last edited by RebeccaPowers on Fri Mar 05, 2010 1:46 pm, edited 1 time in total.
large memory supportYou'll only run out of memory is you are using very large samples/sample sets. Omnisphere and Kontakt could definitely be the culprits in your case. But I'm pretty sure Kontakt can drag sample data from your HDD on the fly, so it may be something else. I'd only expect to run out of RAM if I was using a lot of Audio Tracks.
Dell G7 (Hexa-Core i7)|Cubase Pro 10||Analog Keys|Ultranova|MicroMonsta|Uno|Skulpt|Craft Synth 2.0|
novakill.com
9 posts
• Page 1 of 1
Who is onlineUsers browsing this forum: No registered users and 108 guests |
© 2017 Synapse Audio Software. All Rights Reserved. |