Thanks for the detailed reply RA ..
Ive had some time to think about the issue (and workarounds) as this might relate to alot of different issues in a "workflow":
1) DSP placement
- is there any way to do specific (or force single dsp/board) for an effect in PCI5.1 ? (No SDK)
- Will using an insert INSIDE the STM (while the stm is set to "board rpiority") keep the inserts on the same board as well ?
- will a loaded multifx (or other) be treated as a "single device" and will be placed on 1 board/dsp ? (Probably not, but asking
This relates to all "manual" phase compensations (e.g. will I get 6msecs delay per insert next time I load the project because the placements have changed ? ... I think that this is the problem I had with my project that I couldnt really replicate ... Because I was adding some compressors and eq as final effects on a loaded project - which was mostly loaded by summing and a "mastering chain")
2) FX-send tracks coming from the sequencer (that are made up of audio from many many different tracks (at different levels) - like a reverb.
Once I introduce (differing) delays to some of the original tracks in scope - those tracks are out of sync (in differing amounts) from the vrb - which can cause noticable artifacts .... Currently the main workaround I can think of is houncing each original track with its send returns and then summing the effected track - but then that means any vrb I add in scope will "vrb the vrb" already on that track ....
If I dont - I have to keep all tracks phase-coherent throughout the summing .... At first I thought I will process them all "symmetrically" (adding a compressor and eq to all busses - even if they are not effecting the audio) - but then there is issue#1 ... Which can change delays each time you load/optimize the project ...
How do you guys deal with this ??
3) synths - im guessing they might be spread out on different boards, right ? Can that scenario cause delays if the signal needs to bounce (maybe several times) between boards ?
(Currently I am getting timing irregularities with most of the recorded synth lines I scrutinized .... But they are not a fixed delay - but rather some sort of "jitter" - I will look deeper into itmand try to meausre the "timing jitter amplitude" to try and understand where it comes from ...
On another note (and one of my suspects of the synths issues )
- Gary said scope works at 48K internally - now, in a 44.1K project - does that means it converts my sequencer's 44.1 audio to 48 - process it - and reduces back to 44.1 ? (Where do these SR changes take place ?)