BillyZeppa
Power User
Doesn't the cab block have a delay function.
A micro-delay type in the delay block would be an easy addition. I'll look into it.
It does, but only for sub 1ms adjustments.Doesn't the cab block have a delay function.
Although you can accomplish it with various blocks, I still wish for a lightweight block devoted exclusively to time alignment or micro delay. Many of my presets have lots of parallel paths that need to be time and polarity aligned. Especially presets that combine my vg-99 modeled guitar output with the real pick up.EDIT: The compressor block lookahead is working fine for this right now, so I guess this isn't a major wish
That would only work in a subset of scenarios, and sounds like a nightmare to implement. I'd prefer minimum latency in every block, and manual control over time alignment blocks placed where I choose.Would it be possible for the axe to calculate and compensate for latency per column, i.e. automatically applying a calculated delay offset to all shunts/blocks in parallel, in order to match whichever block in a column has the highest latency?
The problem there is that you have to sacrifice a delay block. Is adding a new block type problematic? The total delay time need not be more than 10 milliseconds or so.A micro-delay type in the delay block would be an easy addition. I'll look into it.
Add to the filter block? Delay by sample (1/48k)...The problem there is that you have to sacrifice a delay block. Is adding a new block type problematic? The total delay time need not be more than 10 milliseconds or so.
If it had to be added to an existing block, I guess the filter block would be the best choice. Mainly because there are four instances. But you need more than one sample of adjustable delay, even though the total time required 4 worst case would be small.Add to the filter block? Delay by sample (1/48k)...
Ideally, I'd like to have a lightweight dedicated block, with polarity inversion. It would solve so many problems without sacrificing other useful blocks or adding significant load.+1 for accurate sub 1000 millisecond delay
I.e up to 3 significant figures ex. 0.420 milliseconds
I do see the compressor block look ahead function with ratio 1:1 as an alternative
But having it in the delay block with 3 significant figures of delay accuracy would be nice to deliberately make or prevent comb filtering as much as possible