Chuck, in order to get more than 3GB you have to run multiple standalones.
DG
190,562 users have contributed to 42,746 threads and 257,186 posts.
In the past 24 hours, we have 2 new thread(s), 12 new post(s) and 34 new user(s).
By the way Christian, What do I have to do in order to get line-feeds between my paragraphs? It use to work when I was using Explorer but since I've switched to Safari, the problem has risen. I even tried multiple carriage returns in previous post with no luck. Is there something on my end I need to configure? Chuck
I'll get shouted at for this, but the simple answer is not to use Safari.
DG
Hmm. My undertstanding is that this is EXACTLY what VE is addressing. I don't have a large amount of ram to access(yet [;)]) so I cannot varify your problems. I read somewhere in the forum that Herb was running a 16 gig Mac using VE with tons of VI's loaded up. Just wondering b/c I plan on using VE much more when I get my "dream machine" built.
Actually, I mentioned somewhere else that I wished VSL would make VE something of a VSTi rack that would/could support 3rd party synths. Kind of like a software FX Teleport. I don't know what the legal ramifications are,but man THAT WOULD ROCK!!!![:P]
Anyhow,keep up all the cool stuff VSL !
luces
chuck, if this went down between my whining ... ;-)
depelopment is done and it is only a matter of time until we have the tools to give you the tools ... of course we all would love to have all in a single instance breaking the 4 GB on all platforms.
the safari issue is an issue with the used rich-text editor and as i assume the KJS engine (javascript interpreter) safari is using - the community software is not the only one having troubles with it (actually the german OSX developer blog is affected ... haha)
possibly the limitation of the KJS call stack to 100 entries is the reason but we have already set up a new test system to investigate with different editors and/or settings - there is a lot of AJAX involved so i ask you for patience ... the guys developing tinyMCE are also working on a possible solution.
the workaround (for paragraphs in a post and other formatting options) would indeed be to use firefox on the mac for the moment
christian