Vienna Symphonic Library Forum
Forum Statistics

194,450 users have contributed to 42,922 threads and 257,971 posts.

In the past 24 hours, we have 5 new thread(s), 14 new post(s) and 78 new user(s).

  1. Home
  2. Sample Libraries
  3. Synchron Series
  4. Synchron Pianos CPU problem

  • Synchron Pianos CPU problem

    S
    S

    Hi, I'm new to the forums.

    Anyway my problem is Synchron Piano is unplayable for me because of CPU peaks. I've tried all preload sizes from 1k to 16k, down to 4 voices per microphone and none of it really removes the problem. I'm using a 2017 iMac with 3,4GHz i5 and 24Gt RAM so it shouldn't be a problem, right? Also I'm having none of these issues with the Synchron Player and the orchestral instruments, they're running just fine. How can I fix this?

    Thank you in advance.
  • PaulP
    VSL Team
    PaulP

    Hi, 

    Which drive are you streaming your Synchron Pianos sample content from?

    Also, how is it formatted and how is it connected?

    Thanks for the additional information!

    Best,
    Paul

    Paul Kopf Product Manager VSL
  • S
    S

    My sample content is located in the built-in 1Tb fusion drive. Should I be using an external drive instead? I'm new to using sample libraries of this "caliber" so I didn't realize it's a factor.

    Thanks.
  • PaulP
    VSL Team
    PaulP

    Hi, 

    The access /streaming speed for the samples is quite a factor. Which preload times do you see in the Preferences => Database?

    Could be worth trying your external SSD drive, if it's connected with a fast protocol like Thunderbolt 3... You simply have to add the new location in the DATABASE setting if you move the sample content. 

    Best, 
    Paul

    Paul Kopf Product Manager VSL
  • S
    S

    Just like Paul said, your problem is Fusion hdd drive. You need SSD for proper sample streaming. Replace that fusion drive or use it only as a storage for some data.

  • S
    S

    Ok so it appears that there's a separate preload value right next to the directory path that isn't affected by the default preload value at all. I changed that one and now it works just fine. Kind of a silly mistake on my part!

    Thanks for the help.