Pure Delay
- KVRAF
- 9096 posts since 5 Feb, 2004
I just want to be sure i am doing this right
My host Studio One reports an overall plug-in delay of 6.3 ms. I made a MUX with Pure Delay at the end of the chain, with that same value. I then rendered the same bit of midi to audio before and after adding Pure Delay and looked at the wav starts and it looks like it compensates correctly. My question i guess is: does this value ever change, provided i don't change anything in my audio interface settings? Do I need to put Pure Delay into all of my MUX? Thanks!
If you have requests for Korg VST features or changes, they are listening at https://support.korguser.net/hc/en-us/requests/new
- KVRAF
- Topic Starter
- 9096 posts since 5 Feb, 2004
Hmm, it seems I had it backwards. I was looking at the wrong clips, the one WITHOUT Pure Delay is on time, the one with it is behind. Does this mean my host is properly compensating automatically for MUX tracks? The higher value i put into Pure Delay the more delay I was seeing.
If you have requests for Korg VST features or changes, they are listening at https://support.korguser.net/hc/en-us/requests/new
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
When a plugin reports delay to a host that performs compensation, the host will delay all other audio being rendered in parallel to align with that delay - that's "plugin delay compensation" (PDC). It's intended to eliminate unwanted delays caused by buffering for signal processing purposes (that can result in phasing effects).
MuX does not report delay to the host. Any delay you put inside a MuX will be considered "real" delay rather than processing delay and hence rendered "as is". That includes plugins that would otherwise report PDC to the host (as MuX doesn't use it) or the "pure delay" plugin itself.
MuX does not report delay to the host. Any delay you put inside a MuX will be considered "real" delay rather than processing delay and hence rendered "as is". That includes plugins that would otherwise report PDC to the host (as MuX doesn't use it) or the "pure delay" plugin itself.
- KVRAF
- Topic Starter
- 9096 posts since 5 Feb, 2004
OK, I'm just a little confused what my host is doing then. I closed, then opened my host, now it doesn't report any delay, and the MUX tracks are rendering a little late. Is there any issue with me manually nudging the tracks then? Anyhow I don't know if this REALLY makes any difference at all for me, I have never noticed an issue, maybe I'm being a bit too mental here 
If you have requests for Korg VST features or changes, they are listening at https://support.korguser.net/hc/en-us/requests/new
- KVRAF
- 2874 posts since 22 Oct, 2002 from "somewhere between digital and analog"
I've never noticed a delay with any plugin for 10 years... Ha! Maybe I'm not using enough plugins?
-
- Banned
- 897 posts since 8 Jan, 2005 from Detroit
the issue is that when a track is delayed by a few samples then theoretically the transients can become 'blurred' and not sound as sharp as they could if there were no delay. phase issues between tracks with stacked transients can lessen the potential impact of the resulting track. you could argue that people are never quite 'on top of' each other when playing real instruments, and that phase differences happen in nature all the time haha but in todays world of computer generated robot music, you need everything to hit exactly on or the perception is that its inferior, nevermind that youll simply squash those peaks anyway with compression and limiting. i suppose there can be a good argument for and against delay compensation. if you have layered many explosions for a movie soundtrack you dont want them blurred since the whole idea is to make an impact and you need all your high frequencies intact, however i doubt the average consumer would even know or care.
