Vienna Symphonic Library Forum
Forum Statistics

194,301 users have contributed to 42,914 threads and 257,952 posts.

In the past 24 hours, we have 0 new thread(s), 17 new post(s) and 83 new user(s).

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries
  4. 2GB RAM machine problems

  • 2GB RAM machine problems

    J
    J
    I have a Macbook that I'm trying out in XP. It's got 2GB installed, and comes up as 1.96 in the Computer -> Properties. Reasonable enough. I'm loading instruments in Plogue Bidule and I don't seem to be getting anywhere near what I could get loaded in OS X. This seems strange to me. I'm noticing that Bidule quits at around 1,200,000 K in the Task Manager. Does that seem right to anybody? I was loading around 1.5GB in OS X... Is there something else I have to do to make this work as expected?

    Performance in XP definitely seems better, btw. This may partly be because I'm using a Profire Lightbridge -- hardware by a company who seems incapable of developing any capacity to write OS X drivers.

    ----------------

    On a side-note, I've discovered "Groups" in Bidule (I know, it shouldn't have taken this long!), and I'm really finding them handy. What I've started doing is grouping instruments into sub-mixes and saving those as Groups. Then, I can easily re-load that Group in any Bidule session. So I can have, for example, a Group for "2 Fl (dbl Picc)". The Group has 3 VIs, 2 Flutes and a Piccolo, has Stereo Squeezers attached to each, and a mixer merging these down to a stereo pair. When I load it up, it's all ready to go! Sweet. Of course, you could do all your spatialization in there too, if you wanted, and have it load with a single command -- and load into whatever ensemble/orchestra you're writing for! I like it...

    J.
  • T
    T
    last edited
    last edited

    @jbm said:

    I have a Macbook that I'm trying out in XP. It's got 2GB installed, and comes up as 1.96 in the Computer -> Properties. Reasonable enough. I'm loading instruments in Plogue Bidule and I don't seem to be getting anywhere near what I could get loaded in OS X. This seems strange to me. I'm noticing that Bidule quits at around 1,200,000 K in the Task Manager. Does that seem right to anybody? I was loading around 1.5GB in OS X... Is there something else I have to do to make this work as expected?

    Performance in XP definitely seems better, btw. This may partly be because I'm using a Profire Lightbridge -- hardware by a company who seems incapable of developing any capacity to write OS X drivers.

    ----------------

    On a side-note, I've discovered "Groups" in Bidule (I know, it shouldn't have taken this long!), and I'm really finding them handy. What I've started doing is grouping instruments into sub-mixes and saving those as Groups. Then, I can easily re-load that Group in any Bidule session. So I can have, for example, a Group for "2 Fl (dbl Picc)". The Group has 3 VIs, 2 Flutes and a Piccolo, has Stereo Squeezers attached to each, and a mixer merging these down to a stereo pair. When I load it up, it's all ready to go! Sweet. Of course, you could do all your spatialization in there too, if you wanted, and have it load with a single command -- and load into whatever ensemble/orchestra you're writing for! I like it...

    J.


    I have a MacBook Pro wiht 2 gigs as well that I pressed into use. I bought Bidule and haven't really used it on the PC/Mac side yet. I've been struggling with Bidule ASIO distortion issues on the PC's and haven't even gotten around to trying it on the Mac. My experience on the PC is that Bidule won't allow me to load as much as Forte or V-stack. This may be in issue with ASIO as it eats up a lot of DSP power. Twice as much as the other output drivers. Because of that I've been forced to work with V-stack for the time being.

    I didn't know about the groups. I'll have to check that out.

    I got as high as 1.79 with Rax on Mac, of course it wasn't usable. But it was working at just over 1.7. I wonder how V-stack would hold up on a mac running XP?
  • J
    J
    Well, I think... maybe... I sort of got this worked out. [;)] (how's that for confidence!)

    It seems as though it might be related to load/unloading lots of different samples. If I reboot, the overall capacity appears to be back to normal, at roughly 1.5GB. Kind of strange, but not too surprising. I'll keep my eye on it, to see if any other pattern arises, but that's the best I can figure so far.

    J.
  • cmC
    VSL Team
    cmC
    jbm, you should not forget that windows is splitting the available memory in a so-called kernel- and user-space (50% each = 2 x 1GB) and only the user space is available to load samples. regarding this OS X is more clever using available memory so the amount of loaded patches will be higher.

    regarding *having more space after reboot* you should consider memory fragmentation - not every host might handle this in the same way ...
    (memory fragmentation means basically the same as disk fragmentation - deleting something leaves a hole between used blocks which can only be used by new data which fits into this hole, otherwise the free space stays empty)
    christian
    and remember: only a CRAY can run an endless loop in just three seconds.
  • J
    J
    Sorry, Christian... I didn't see this until just now.

    Memory fragmentation is a good bet. I hadn't thought of that.

    cheers,

    J.