Vienna Symphonic Library Forum
Forum Statistics

195,405 users have contributed to 42,984 threads and 258,234 posts.

In the past 24 hours, we have 6 new thread(s), 20 new post(s) and 56 new user(s).

  • MIR, latency pops and clicks.

     I am attempting to do my first project in MIR and having finally programmed the first track am having a few problems mixing:

    1. So far I can't get a clean playback at any combination of buffer and MIR buffer multiplier.
    2. Even if it was clean, the latency compensation of Nuendo only goes up to 100ms, so everything is reaaaaaaally late.
    3. If I can't move faders more or less in real time, how am I supposed to mix?

    Any suggestions for workflow gratefully received, as currently I'm seriously considering abandoning MIR for the time being until computers are faster.

    DG


  • How many instruments are you looking at?

    Right now , I'm working with 512 samples latency and 1* internal buffer multiplier with 32 instruments on a machine considerably less powerful than yours (... with Nuendo 5.1 on the same computer). The CPU meter is constantly below 50%, most of the time around 20%. I get clicks when I move an instrument while it's playing, but that's part of the game.

    ... I don't really understand what you mean by "Nuendo's latency compensation". Are you using the hardware inserts of Nuendo?


    /Dietz - Vienna Symphonic Library
    1. I have 116 Instruments in the project, 100 VI Pro and 6 Kontakt.
    2. I have MIR inserted in the VSTi Rack as an External VSTi.

    DG


  • DG,  sometimes pops and clicks are coming from cpu spikes.

    Have a look in the task manager >ressources monitor. It's necessary that all cores in use. Sometime they aren't.  

    Did you notice this link: http://ultimatecomputers.net/forum/viewtopic.php?f=7&t=3644

    Has tweaked my system in this way. It has improved the performanced much more than I thougt at the first glance.

    (Was good before, but it's amazing now.)  Maybe it helps for you too.

    Kind regards

    Frank


  • Thanks for the suggestions, but all the correct tweaks have been done. I think that I just have to accept that MIR will not run my template on this computer. [:(]

    DG


  •  DG what amount of samples on average do you have loaded for each instrument - presumably the full monty. Thats a huge set up. I suppose it doesn't fit your work pattern to purge each instrument of unused samples. I was hoping if I upgraded my i7 puter with 24GB of ram that I could run a standard symphony orchestra with cherrypicking about 12-24 patches for each instrument. And out of interest what do you think it will take to run your set up - better CPUs and/or more ram?


  • last edited
    last edited

    @DaveTubaKing said:

     DG what amount of samples on average do you have loaded for each instrument - presumably the full monty. Thats a huge set up. I suppose it doesn't fit your work pattern to purge each instrument of unused samples. I was hoping if I upgraded my i7 puter with 24GB of ram that I could run a standard symphony orchestra with cherrypicking about 12-24 patches for each instrument. And out of interest what do you think it will take to run your set up - better CPUs and/or more ram?

     

    I am using about 24-25GB for samples, ad of course MIR takes 4-5 on top of that. However, I don't think that RAM is the issue as I have around 16GB to spare....! However, I think it is really a CPU/ASIO efficiency problem. He only way round this for me would be a faster PC, but there is no guarantee that the 12(12) core machines would work satisfactorily, so I think I'm going to have to wait for MIR Pro, in the hope that if I'm using audio inputs, and not VI Pro, this will take some of the load away from the CPU.

    DG


  • I don't know how much this will help you but what I did was when I had a weaker machine was work with instruments as groups.  I would complete sections, bounce them to audio tracks, then move on to the next groups of instruments.  I wasn't able to use all of my MIR instruments at the same time either (I could only get about 16 back then).  So I did the 4 strings, finished them and bounced them.  Then moved onto piano and percussion, bounced them. etc.  It got me through it.

    Sure would hate to see you lose all that time you spent setting that up because I know how long it took me to do a 1/3 of that.

    **edit, I also remember now that I had to go into my sequencer and tell the other instruments to not even play.  So when I was doing strings, I went into Logic and muted all non-string tracks so they didn't send any midi information to MIR at all.  This massively reduced CPU usage (obviously....)

    Maestro2be


  • last edited
    last edited

    @cgernaey said:

    I don't know how much this will help you but what I did was when I had a weaker machine was work with instruments as groups.  I would complete sections, bounce them to audio tracks, then move on to the next groups of instruments.  I wasn't able to use all of my MIR instruments at the same time either (I could only get about 16 back then).  So I did the 4 strings, finished them and bounced them.  Then moved onto piano and percussion, bounced them. etc.  It got me through it.

     

    I thought of that, but for me it is not possible to work that way. In order to mix properly I have to have control over individual instruments, the only way to do that would be to bounce each instrument separately. In fact there is already a compromise with that, as really I should be bouncing two tracks for each instrument; a 100% dry one and a 100% Wet one.  [:O]

    DG


  • Hi DG,

    Just out of curiosity, how many instruments do you have to disable to get a pop-free playback?


  • last edited
    last edited

    @kage49 said:

    Hi DG,

    Just out of curiosity, how many instruments do you have to disable to get a pop-free playback?

     

    I never bothered doing a scientific check, but if I did it by sections, I would probably be OK. Having said that, my MIDI programming is quite complicated at times, and this seems to add to the CPU load.

    DG