Vienna Symphonic Library Forum
Forum Statistics

181,953 users have contributed to 42,195 threads and 254,637 posts.

In the past 24 hours, we have 4 new thread(s), 13 new post(s) and 51 new user(s).

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries
  4. Notes not triggering

  • Notes not triggering

    J
    J

    I'm using VSL in Logic 8. My Mac is an 8 Core 3.2GHz.

    I'm having trouble suddenly. Notes are not triggering. Some do, some don't ; it's random. I've tried and checked all the settings and prefs in Logic but still the problem persists. It can be any patch. Sometimes I get what sounds like a spew of MIDI notes after a gap of silence. 

    'Chase' is set to chase notes. Buffer is set to 256. Sample rate is just 44.1 and it's at 16bit.

    Also I'm getting the disk overload warning way too often with hardly any VIs running.

    Can anyone please help?
  • A
    A

    I have this same problem using VSL on my Macbook Pro 2.4 ghz, 4 gb ram, OS X 10.5.8, with Logic 9, Mainstage 2 and Cubase SX4. The library is on a FW400 hardisk, but I hardly think this a streaming problem. It happens even with just a single harp or celesta patch. This has been happening with each release of VSL, right till the latest. VSL works perfectly on my studio PC DAW.

    Unfortunate, because I use my mbp for live work and can't use vsl reliably. I have no such problems with my PLAY, Spectrasonics and NI instruments.

    Any advice would be welcome.

    Thanks!
  • M
    M

    Do you still encounter these problems when switching to "built in Audio"?

    /regards,

    Maya
  • J
    J

    Yes. It's not my soundcard that is doing this. I've tried various different buffer settings etc in Logic's audio prefs.
  • W
    W

    I had a similar problem recently with all my Woodwind patches. Turns out I had copied a huge file (a system backup, 300+GB) to the harddrive, leaving only 50GB free (it's a 750GB HD). I noticed that when I played the same notes for a while, performance would improve. So I ran DriveGenius's defragment routine on the drive - problem gone. So against what some say, that defragmenting is fairy tale stuff that should not be needed with OSX, it solved my problem :-)

    also worth trying: repair or replace the drive's directory with DiskWarrior.