PT's dual low latency buffer, 110 instances of Kontakt 'n stuff.

[dtmprod]

Originally Posted by Sardi

IIRC correctly, there's 2 stages of buffer lengths dependent on what you set it too.

So for example, if you set it to 64 it has a playback buffer of 1024. If you set it to 512 it has a playback buffer of 2048.

I'm making those numbers up, but I recall reading something along those lines when 11 was launched.


Sent from my iPhone using Tapatalk

If that's true, wouldn't it show up in the delay compensation for individual tracks? Higher numbers for a higher buffer? Or would it only be noticeable in total system delay?

[clausiii]

Originally Posted by dtmprod

If that's true, wouldn't it show up in the delay compensation for individual tracks? Higher numbers for a higher buffer? Or would it only be noticeable in total system delay?

No, this has nothing to do with delay compensation.

[midnightrambler]

Originally Posted by Marsdy

The video is here: https://youtu.be/6JzwngQbgHE - The info is 2'19" in.

Dave

This AVID video must be BS? Or, I am doing something terribly wrong and/or misunderstanding that'a going on here....? -

I'm midway through a mix. As an experiment I've deliberately frozen all instruments and committed all Elastic, so only audio tracks are running. I've disabled Melodyne. There are no tracks in input monitor/record ready.


So, if I understand correctly, I should be able to set the H/W buffer to 32 samples and it not affect playback at all......? .... Have I missed something? - -

https://vid.me/OJnP

[TOM@METRO]

The way I understand this, the playback buffer on all audio tracks in playback is internally set at the maximum buffer for the sample rate you are using. Tracks in Record are set by the user in the Playback Engine drop-down menu. For Instrument Tracks, both Playback and Record are set by the user.

When a VI track is Committed, it is treated like an Audio Track.

I hope this helps.

[midnightrambler]

Originally Posted by TOM@METRO

The way I understand this, the playback buffer on all audio tracks in playback is internally set at the maximum buffer for the sample rate you are using. Tracks in Record are set by the user in the Playback Engine drop-down menu. For Instrument Tracks, both Playback and Record are set by the user.

When a VI track is Committed, it is treated like an Audio Track.

I hope this helps.

So why I can't I run my mix with a H/W buffer of 32 samples then, if this setting is not affecting playback?

[guitardom]

You are missing the other part of the equation. The buffer size also dictates how Pro Tools is prioritizing your CPU distribution. At a low buffer, the CPU is being prioritized for latency, as the buffer gets higher, its being prioritized for power.

[TOM@METRO]

Originally Posted by midnightrambler

So why I can't I run my mix with a H/W buffer of 32 samples then, if this setting is not affecting playback?

I wish I had a complete answer. My tests show what I have referenced above, but there may well be background activity about which we have little information. I fully agree that lower buffer settings do show an increased CPU load, and that does throw questions that have (so far) not been answered in detail.

Are there any Instrument Tracks in the session you posted?

And then, there's Steve's new post above mine.

[midnightrambler]

Originally Posted by TOM@METRO

Are there ant Instrument Tracks in the session you posted?

There were frozen instrument tracks, but I tried committing them to straight audio tracks and it still did the same thing.

[TOM@METRO]

Then perhaps there is much more going on here than the simple Avid explanation implies.

[midnightrambler]

Originally Posted by guitardom

You are missing the other part of the equation. The buffer size also dictates how Pro Tools is prioritizing your CPU distribution. At a low buffer, the CPU is being prioritized for latency, as the buffer gets higher, its being prioritized for power.

BUT the AVID vid claims that you can set a low buffer without affecting other playback tracks at all....? "This allows the user to get the lowest possible latency without having to constantly adjust the buffer or the session"