Forums › Forums › dLive Forums › dLive General Discussions › Latency
- This topic has 14 replies, 8 voices, and was last updated 7 years, 9 months ago by SteffenR.
-
AuthorPosts
-
2015/06/16 at 8:01 pm #48740emptyoneParticipant
How will the latency be through the desk when you add for example FX and compressor to a channel?
2015/06/16 at 8:40 pm #48742Nicola A&HKeymasterChannel-based DEEP processing models (compressors, GEQ and more) won’t add any latency to the channel path. DEEP ’embedded plugins’ are available on all channels on the fly.
Inserting a RackFX from the FX rack (such as a pitch shifter or transient controller) will add latency dependent on the FX type.Inputs and groups are all delay compensated and phase coherent to the Mix Outputs.
2015/06/17 at 2:06 am #48747eotsskleetParticipantIs that already the same in iLive and GLD with the inputs being delay compensated and phase coherent to the Mix Outputs?
2015/06/17 at 10:17 am #48750SteffenRParticipantit depends…
2015/06/22 at 5:35 pm #48905papromikeParticipantThe latency is so low that it is a non-topic at this stage, The new FPGA processors are so fast that the system latency is under
.6ms
2015/06/22 at 10:32 pm #48907ddff_lvParticipant6 or 0.6 ?
ddff
2015/06/23 at 8:02 am #48912emptyoneParticipantThe latency is 0,58ms to be accurate. But 0,6ms is used be many including A&H
2015/06/23 at 2:40 pm #48918ddff_lvParticipantThat is impressive indeed.
ddff
2015/06/23 at 3:17 pm #48919ahjeffModeratorIs that already the same in iLive and GLD with the inputs being delay compensated and phase coherent to the Mix Outputs?
No, iLive and GLD have phase coherent busses, in that, for example, an input mixed to two groups will have the same phase in both. If you mix these two groups to a main, you should not have any comb filtering. However, if you mix an input to a main and to a group, then mix the group into the main as well, you could experience comb filtering.
In dLive, everything except the FX is delay compensated. You should not experience any comb filtering no matter what combination of mixes and inputs you have feeding another mix. The only exception is that if you have a signal mixed post delay, with the delay not set to zero, this manually added delay will not be compensated for.
[Edit] Please also refer to this knowledgebase article: https://support.allen-heath.com/Knowledgebase/Article/View/1202/0/what-are-phase-coherent-mixes
Hope this helps
– Jeff, A&H
2015/06/23 at 8:04 pm #48924SteffenRParticipantThe only exception is that if you have a signal mixed post delay, with the delay not set to zero, this manually added delay will not be compensated for.
I would expect exactly these… 😀
2017/02/21 at 7:52 pm #61505torParticipantcan anyone here tell me approximately what latency I should expect if had a bunch of input connected to DM48 routed via Tielines to MADI Slot card (to a digico SD8), and the MADI returns routed via tielines directly to the outputs of the DM48? Any documentation on these sort of things anywhere?
2017/02/22 at 9:56 pm #61533SteffenRParticipantthere is a technical data sheet where some latency scenarios described…
I will try to find it
2017/02/22 at 10:46 pm #61534SteffenRParticipantLatency 0.7 ms (MixRack XLR in to XLR out, Input to Mix)
+ 5 samples, Surface to Mixrack (GigaACE hop)
+ 8 samples, DX32 to Mixrack (DX hop)Samplerate is 96kHz
2017/02/24 at 9:54 am #61557torParticipantYeah, I was looking for the Tieline functionality, which is not subject to processing… So should be lower I would assume…?
2017/03/06 at 8:30 pm #61873SteffenRParticipantit is lower
converter latency plus GigaACE hop -
AuthorPosts
- You must be logged in to reply to this topic.