Vienna Symphonic Library Forum
Forum Statistics

199,046 users have contributed to 43,151 threads and 258,882 posts.

In the past 24 hours, we have 3 new thread(s), 10 new post(s) and 58 new user(s).

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries
  4. Floating Ram on Mac Pro

  • Floating Ram on Mac Pro

    K
    K

    Hello, I am a first time user. I just purchased the chamber string collection. It sounds great!!! At first I started out with one gig of ram. I already knew that I needed more so I did. I upgraded to 3 gigs. As soon as I opened my VI, my memory read 1664 mb free. After loading a simple matrice I noticed that either I was losing in math or my memory flew down tremendously. All the way to under 1000 mb. And floating down without even using anything else. One minute it is at 997 the next minute it is at 664 then 1024. What the @#$# is going on here. Do I need more ram to stablize. I only had one application open. Its a brand new mac pro so is there some kind of special configurations that I have to do? With that memory I can't even create the replication of a chamber orchestra because I would max out at 2 tracks. I'm using it in stand alone. Could that be it? Please help cause ram is expensive.

    By the way VSL is excellent. I cannot tell the difference between a real chamber section and the real thing. Great job
  • B
    B

     I have the same problem using a new Mac Pro 2Gb with the VSL VI Special Edition (Full). However I use a host. Logic 8 stops playback sometimes when I load more than 3 matixes. It says: system overload and refers to the audio driver. A mac has CoreAudio and I use a TASCAM FW-1082 (firewire) mixer for an audio interface so that should be powerful enough. VSL recommends 2Gb memory which I have... And the memory decreases too...

    Has anyone experience with Logic 8 and VI Special edition?  
  • S
    S

     My experience with Logic 8 corroborates yours. Although I have 7GB of RAM installed in my G5 I have gotten the "Audio/MIDI out of sync" error message when playing back a single instance of VI (281 MB of the Bösendorfer). I've found that I can usually avoid this by selecting an empty audio track during playback. However, it is important to note that this error message occurred only very rarely in Logic 7 - even when it was near the limit (almost 3GB) of samples loaded.

    In my experience Logic 8 is fairly buggy and has some design changes that, in my experience, impede rather than enhance workflow.

    An example of what I mean by buggy is that, while the Piano Roll window works OK if it is part of the new "consolidated window," it becomes quite problematic when run as a separate window. Data sometimes completely disappears from view (although it still plays back), the playhead frequently disappears when scrolling, sometimes the entire window goes blank - no data, no frame, just blazing white, the zoom controls frequently freeze. (none of these problems occur in Logic 7).

    As far as design problems are concerned:

    1.Information in the Inspector window which uses a small black font against a gray background is, at least for me, far less legiblle than the white against green of the Logic 7's channel strips. There is, as far as I can tell, no way to increase the size of the fonts or contrast. I find that because of lower contrast throughout, legibility is reduced in comparison to Logic 7.

    2. The Audio Configuration Window has been eliminated making the copying of a set of plugins and their settings from one file to another more difficult.

    3. The position slider on the Transport has been eliminated.

    In other words, to me, Logic 8 seems an unfinished product. It does not surprise me that it exhibits anomalous behavior in a variety of ways.  
  • B
    B

    Well, the strange thing is.... when I use only Logic or JamPack plugins.... everything works perfect and smooth 

    Hopely there'll be major Logic updates soon