Quote:
|
Originally Posted by dkatz42 There are lots of separate processes, but they most definitely must have sync points. The system does automatically compensate, or it wouldn't work at all. The art of building any parallel processing system is to tease out the parts that can run in parallel for as long as possible without blocking, but eventually they all have to block. The Logic Node is a good example of a loosely-coupled parallel process. The various restrictions on what you can and can't run on a Node illustrate the synchronization issues.
If there are artifacts in the sound that appear to be load-related (and I will defer to those that hear them, even if I don't) it could be a developer trying to get fancy and doing something to speed up the process (at a sonic cost) rather than rolling over and dying, or it could be a bug (wouldn't be the first one, nor the last.) |
I haven't done any real parallel or plug-in programming myself, so I don't know the ins and outs of thread synchronization. Please excuse my ignorance, but why aren't the threads/processes (and various signal paths) in audio apps sync'd perfectly? Is this even possible?
I haven't noticed this drift that SiliconAudioLab is talking about, so I can't theorize about it. What I have experienced on a couple different platforms that, as far as I know, feature plug-in latency compensation, is a latency/phase problem when using parallel compression. For example, say all your drum tracks are routed to the master outputs and also via an aux to a separate buss/fx channel, which is then routed to the master outputs. At this point there may or may not be any noticeable problems, but if you throw a compressor plug-in on the buss, there will be a definite audible effect on the phase coherency of the two signals.
-Dan.