Vienna Symphonic Library Forum
Forum Statistics

181,989 users have contributed to 42,199 threads and 254,645 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Annoying sample behaviour.

  • Annoying sample behaviour.

    D
    D

    I find when I open a big orchestral project, once everything has loaded and I press play, that a lot of samples don't play first time and I will have to play through a few times before everything sounds properly. Also if I have left the project for anything more than about 15 minutes or more the same problem occurs. It's like trying to start a car on a cold morning.

    I recently worked up a 14 minute project and found that when I tried to record it some samples later in the piece didn't play but if I stopped and played that section a couple of times they would sound but if I went back and recorded again there was a risk they wouldnt sound again.

    Is this recognised behaviour and if so is there anything I can do about it? Is there some setting somewhere that addresses this issue?
  • D
    D
    last edited
    last edited

    @DaveTubaKing said:

    I find when I open a big orchestral project, once everything has loaded and I press play, that a lot of samples don't play first time and I will have to play through a few times before everything sounds properly. Also if I have left the project for anything more than about 15 minutes or more the same problem occurs. It's like trying to start a car on a cold morning.

    I recently worked up a 14 minute project and found that when I tried to record it some samples later in the piece didn't play but if I stopped and played that section a couple of times they would sound but if I went back and recorded again there was a risk they wouldnt sound again.

    Is this recognised behaviour and if so is there anything I can do about it? Is there some setting somewhere that addresses this issue?

    This sort of things can occur:

    1. If the samples aren't fully loaded
    2. If your drives are set to sleep after a certain period of time
    3. If you are using Virtual memory

    Of these I think that 3 is the most likely. Check your Virtual memory usage. If memory gets a bit tight, then your computer will start to use virtual memory, which is not what you want.

    DG
  • D
    D
    last edited
    last edited

    @DG said:

    This sort of things can occur:

    1. If the samples aren't fully loaded
    2. If your drives are set to sleep after a certain period of time
    3. If you are using Virtual memory

    Of these I think that 3 is the most likely. Check your Virtual memory usage. If memory gets a bit tight, then your computer will start to use virtual memory, which is not what you want.

    Thanks DG. Having just gone back to  a project after leaving it idle for an hour the same stuttering, missing samples occured. After a few seconds I stopped it and played again and all was well.

    I'm currently using 19.21 GBs of my 24.75 GBs of RAM (78%). CPU is not getting above 60% and core temp not above 60C.

    As I've still got 22% of my RAM left I don't think it's a virtual memory problem. It just seems that if left unplayed some samples seem to go to sleep and need a couple of attempts to wake up again and it shouldn't be like that. Are there virtual memory settings in either the VSL software or Windows I should be adjusting?
  • D
    D

    How are you checking memory usage? Resource Monitor is probably the most useful Windows tool.

    DG
  • D
    D

    I've always had this on display.

    I've opened windows resource monitor and it shows this

    When it says used physical memory 100% does it mean RAM which the first monitor says is only 80%.

    Opps. No I've realised it says 79% very close to the intel monitor.