The Trumpet Help...

edited June 2008 in General Questions
Hi guys.



I love The Trumpet SO much, but I'm really getting poor, poor performance.



On my slave I'm running a lot of VSL Brass and 4 instances of Altiverb. One of those instances is used for The Trumpet. With one Trumpet I can play around with no glitches, however if I add just another Trumpet averything goes to hell with CPU spikes jumping up and down - unplayable. This is at 512 DMA buffer.



To add insult to injury I sometimes get note cutoffs. For instance right now I just tried playing a line with the VSL Epic Horns. Then when I played a Trumpet phrase along side the Horns, The Trumpets notes were cut off prematurely. This is with a single trumpet and single VSL instrument playing simultaneously!



My Computer is a P4 3.0Ghz with loads of ram. Has anyone gotten significantly better performance on a similar speced system? Am I expeting too much, and my less than stellar computer simply can't run state of the art sampling?



As a side note I have also tried run The Trumpet on my main daw which is same specs as my slaves. I have tried run it in cubase with nothing else, not even Altiverb. Again it plays 'ok' with one instance, but when adding another Trumpet it simply can't cope!



:cry:



[edit]Ok. I just tried minimizing my Windows on the slave. This allowed me to play Epic Horns along side The Trumpet with no cut-offs.



But I still can't load and play two Trumpets.

Comments

  • edited 10:02AM
    Hi Christian,



    I replied you question already in the VI forum - this is actually the same reply just for our readers.



    Yes, The Trumpet - being a "very interactive" instrument - is relatively demanding. The low memory load doesn´t matter so much here though. It´s the number of internal voices, use of convolution, and extremely complex scripting what makes the CPU so busy. During the developement phase I was using the Intel D, dual core, 3 GHz (NOT the Core 2 duo) which seems to be similar to your machine - and experienced similar limitations: opening a second nki led to some dropouts. This made me buy a new PC using the Core 2 technology. I was told that the Core 2 processors and the recent motherboards are much faster - and so it is! It seems that, while using older PCs, bouncing or freezing is the right solution. However, I also got a feedback from somebody using a rather old Athlon-based computer (2 GHz). He managed to optimize the settings (in the Kontakt DFD area and the audio buffer size) in such a way that he could remarkably improve the performance. I will ask him for more details. Maybe you could also try using different buffers (multiples of 256), and different DFD and voice settings? Or, for example, if your P4 is a single CPU system, you will probably have to deactivate the double processor support in the player/sampler settings. Native Instruments support could be helpful.



    BTW, users of the most recent, carefully configured PCs reported that they could open even up to 11 trumpets on Quad Core Q6600 machines, or, for example, 5 - 6 on a "normal" core 2 duo 2,6 GHz.

    On the other hand, I think bouncing or freezing is not a bad option, anyway. After all, if you let your real trumpet player(s) go home, you also and up with some audio tracks. You cannot even make any corrections afterwards...

    If I find out some further information, I´ll let you know as soon as possible.

    BTW, I´m still waiting for the reply of that Athlon user - he is not available at the moment.



    Best,



    Peter
  • edited 10:02AM
    Hello,



    I use the sequencer energyXT which lets my assign VST plugins to seperate CPU cores (using a Core 2 Quad q6600 here). Perhaps something like this would be beneficial - I know some of the other modern sequencers are starting to support dedicated processor core VST instruments as well.

Leave a Comment

Rich Text Editor. To edit a paragraph's style, hit tab to get to the paragraph menu. From there you will be able to pick one style. Nothing defaults to paragraph. An inline formatting menu will show up when you select text. Hit tab to get into that menu. Some elements, such as rich link embeds, images, loading indicators, and error messages may get inserted into the editor. You may navigate to these using the arrow keys inside of the editor and delete them with the delete or backspace key.