I am only now beginning to understand how Reason delay compensation works (and how it does not). It seems the signal path delays can only be compensated at the Main Mixer channels and buses. I ran into a problem of going unsync several times when I used a simple split/merge schematic in the Mix Channel insert fx container. For example:
Code: Select all
(Insert box "To Devices")
v
(-SPLITTER-)
v v
v (FX)
v v
(--MERGER--)
v
(Insert box "From Devices")
In this example, if the "FX" device has a nonzero latency, it is not compensated for in the other idle path and the split signals go out of sync. If I take the scheme out of the box, it does not work either. Only when I use separate Mix Channels instead of a merger, the compensation begins to work:
Code: Select all
(Signal source)
v
(-SPLITTER-)
v v
v (FX)
v v
(CH.1) (CH.2)
This limitation seems too restrictive. I can understand that in order to allow for DC on arbitrary (non-looped) paths they would probably need to have too many delay buffers (which are now only bound to Mix Channels). Yet the current implementation does not allow for using A/B crossfade mixers on paths with different inherent latency.