|
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
|
|
Thread Tools | Search this Thread | Display Modes |
|
#1
|
|||
|
|||
PT's dual low latency buffer, 110 instances of Kontakt 'n stuff.
It seems that some of us, including me don't fully understand or are even aware of how Pro Tools' dual low latency buffer introduced with PT11 works. I'm wondering if people are being fooled into using lower buffers than their system or PT session can cope with because of this?
In another thread, ( http://duc.avid.com/showthread.php?t=390774 ,) there is mention of an Avid video showing 99 instances of Mini Grand running. It definitely rings a bell with me. In the same thread there was talk of how Pro Tools dual low latency buffer works. I couldn't find any reference to the 99 Mini Grand instances but I did find an old video by Avid explaining exactly how the dual low latency buffer works. Since this is OT in the original thread I've started this one. The video is here: https://youtu.be/6JzwngQbgHE - The info is 2'19" in. I got it completely the wrong way round in the original thread linked to above. It seems that tracks in playback mode are in a permanent high buffer state which the user has no control over. Only Record enabled or input monitor enabled tracks use the buffer the user sets in Playback Engine. This obviously explains why I often get BIG jumps in CPU usage when I record enable a Kontakt instrument, especially ones with high polyphony counts and complex scripting. Getting back to the 99 instances of Mini Grand. I've just run a test and got 110 individual instances of Kontakt, (each using one instrument - the factory library Grand Piano.) With a buffer of 128 in PTHD 12.6.1 and OSX 10.12.3, CPU usage was reasonably stable hovering at the lower range of 48 to 60%. Each of the 110 instances maxed at 30 voices or 3300 voices of polyphony. It seemed stable too. (I got up to 130 instances but then started getting a few -9171 and -9173 errors.) The weird thing is, there wasn't much apparent difference in CPU usage when a track was recorded to and I went nuts bashing away on a MIDI keyboard. Maybe the instrument in question wasn't CPU demanding enough but I was running a heap of instances. (BTW, I tried the exact same thing in Logic. Again, 110 instances although Logic's CPU meter looked to be running higher, (more stable admittedly.) OSX's Activity Monitor also showed surprisingly similar results. Both Pro Tools and Logic used very similar amounts of RAM - around 11GB.) SO... In theory and according to Avid's video, playback is always at a high buffer setting internally preset by Pro Tools. It's only the record enabled/input monitor enabled tracks that are affected by the user buffer setting in Playback Engine. The thing is, to me it often doesn't feel like that is actually what is happening. I sometimes have to increase the buffer when VI and VE Pro polyphony and CPU usage gets above a certain level to stop pops and clicks. Why do I need to do that if PT is always running at a high buffer during playback? As an aside - I felt that with PT11, given the same buffer settings as pre-AAX versions of PT, latency was better at higher buffer settings. Personally, I find a buffer of 256 or even 512 is quite playable for most VI's (not Maschine!) I didn't in previous versions. Overall system delay is usually more of a concern for me. (I can't get system delay as low with HDX than TDM. I'd like to be proved wrong but it seems to me the cause is that I have to run a lot more plug-ins natively because there's no HDX version.) ...But I digress.
__________________
Dave Marsden UK |
#2
|
|||
|
|||
Re: PT's dual low latency buffer, 110 instances of Kontakt 'n stuff.
Quote:
exactly ... no tracks in record but a low BUffer results in Pops and Clicks .. Why ??? i thought it was only when you had tracks in record or input monitoring .. ???
__________________
Macmini M1 8/512 -OS 12.3.1 and PT2022.4 Logic Pro X 10.7.4 RME BabyFace Pro Macbook Pro july 2014 2.5ghz 16gb ram 512gb SSD - OS11.6.5 - PT 2021.3 Logic Pro X 10.7.4 RME BabyFace Pro |
#3
|
|||
|
|||
Re: PT's dual low latency buffer, 110 instances of Kontakt 'n stuff.
Dave:
Thanks for the follow through! You beat me to it. I'm going to run some tests this weekend. I suppose then that once other processes are brought in (plugins, elastic audio on audio tracks) that number comes down substantially. I'd like to then try to quantify those effects on native processing. Agreed that it doesn't feel like we have this power in practice. You rock!! Carl
__________________
PT 2021.10 HDX 16x24 -Mac Pro 12 Cores 48 GB RAM OS 10.13.6 - API 16 channel - AMS Neve 16 channel, AMS-Neve-SSL -Pres/Processing, Bock Audio, BLUE Bottle, Neumann, Josephson -Mics, Bogner, Kemper- Guitar, Chandler Zener-Curve Bender Outboard/Master. UAudio, Waves, Plugin Alliance etc. |
#4
|
|||
|
|||
Re: PT's dual low latency buffer, 110 instances of Kontakt 'n stuff.
Quote:
I'd be very interested to hear what you come with on your tests!
__________________
Dave Marsden UK |
#5
|
|||
|
|||
PT's dual low latency buffer, 110 instances of Kontakt 'n stuff.
Quote:
This my question as well. If no tracks are record enabled why would changing buffer size lower change the CPU usage? Other than the CPU usage is taking into account something other than the plugins. Sent from my iPhone using Tapatalk Pro |
#6
|
||||
|
||||
Re: PT's dual low latency buffer, 110 instances of Kontakt 'n stuff.
That's something that i want to know too!
__________________
My ears! My ears! clausiii ----------------- MacBook Pro i7 Quad 2.6GHz 16GB RAM ProTools 2020.11 Avid S1 Avid Dock Avid Control Digidesign Command|8 macOS Catalina MOTU 4pre MOTU Track16 Axiom Pro 25 LinnStrument 128 Roli Seaboard Block tons of stomp boxes tube amps guitars noise |
#7
|
|||
|
|||
Re: PT's dual low latency buffer, 110 instances of Kontakt 'n stuff.
Me too.
Jesper
__________________
Mac Pro 7,1 16-core, 96 GB, OS X.15.4, HDX 1, HD i/o 8x8x8 + HD i/o 16 digital + Metric Halo ULN 8 3D + RME Fireface 800 http://vicc.se/studio-alpha/ http://jesperelen.com |
#8
|
|||
|
|||
Re: PT's dual low latency buffer, 110 instances of Kontakt 'n stuff.
Is it not the case that this super-low buffer thing only applies when all MIDI is kept within PT...?
I don't think it works when the VI is held within VEPro. I'm out of the studio so can't easily check, but I think that's correct Sent from my iPhone using Tapatalk
__________________
Mac Pro 2019 3.5GHz 8 Core 48GB RAM OS 13.6.3 Protools Studio 2023.12 Antelope Orion 32, Vienna Ensemble Pro 5, UAD Quad PCIe |
#9
|
|||
|
|||
Re: PT's dual low latency buffer, 110 instances of Kontakt 'n stuff.
Quote:
I'm pretty sure VE Pro and the VI's it hosts are treated just like any other VI in Pro Tools. I'm sure I'm getting the same apparent latency when playing the same instruments in Pro Tools as when it's hosted in VE Pro. I need to do some testing myself though!!! As I said, it seems the super-low buffer is what you set in Pro Tools' Playback Engine. I've got it the wrong way round in the past. I always assumed that the Playback Engine buffer setting affected playback and that Pro Tools set a magical super-low buffer in the background. It's the other way round according to the Avid video! But given that the Playback Engine buffer actually does affect playback... weird!
__________________
Dave Marsden UK |
#10
|
|||
|
|||
Re: PT's dual low latency buffer, 110 instances of Kontakt 'n stuff.
Quote:
"When a MIDI or Instrument track that is routing MIDI data to an instrument plug-in is record-enabled, Pro Tools automatically suspends Delay Compensation through the main outputs of the audio track, Auxiliary Input, or Instrument track on which the instrument plug-in is inserted. This allows for latency-free monitoring of the instrument plug-in during recording. Delay Compensation for Instrument plug-ins works only when all MIDI and audio connections take place inside Pro Tools. WhilePro Tools does not suspend Delay Compensation when you are using ReWire to connect software synthesizers and samplers in other ReWire client applications (such as Reason), Pro Tools cannot account for any latency within the ReWire client itself." My experience of using VEPro (which I still love) in PT12 is that when using large track counts, trying to record a Superior Drummer track when there are loads of other tracks and plugins running is a non-starter due to latency. If the plugins are hosted in PT (rather than VEPro) then it's perfectly possible to record with Superior (with next to zero latency) late on in a session when many other plugins are instantiated and VI's are running, so long as the output of the Superior Instrument track is routed to the main monitor outputs, not a bus. It's kind of changed my workflow since PT12...
__________________
Mac Pro 2019 3.5GHz 8 Core 48GB RAM OS 13.6.3 Protools Studio 2023.12 Antelope Orion 32, Vienna Ensemble Pro 5, UAD Quad PCIe |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
How many instances of Kontakt can you run in the new pro tools HD 11? | Meccanizm | Pro Tools 11 | 5 | 04-10-2013 11:42 AM |
Anyone using Kontakt 3 or NI Stuff With PT8 And Getting By? | epu | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) | 16 | 12-17-2009 01:53 PM |
This buffer stuff is making me mad. | meltdown5 | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) | 9 | 07-25-2006 10:45 PM |
Buffer Issues and other stuff | sainsomnia | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 0 | 01-19-2006 12:44 PM |
New section for Dual monitor stuff | Ray Fabi | Pro Tools TDM Systems (Mac) | 1 | 04-18-2001 10:41 AM |