Please do!mpodrug wrote:Shocking news is that here are some utterly fanboys waiting to be busted. Just kidding. But gary...this is way beyond your level. I will prepare audio examples in line with files and screenshots so once for all we will kill this summing myth. I am really interested to read your comment after that. But today is the day and i will have some party just as you guys. Then i have my birthday soon etc.etc.. So see ya soon in a week or so.
I am glad that here are people that actually know technical side. Thank you Schroomz...
The rest of this post if a mix of info and questions that are rattling around in my head...
Here is an interesting little bit of info from the Live manual. It is from the section of the manual that goes into depth about Lives audio quality. ...
"Please note that, while 64-bit summing is applied to each single mix point, Live’s internal
processing is still done at 32-bit. Thus, signals that are mixed across multiple summing
points may still result in an extremely small amount of signal degradation. This combination
of 64-bit summing within a 32-bit architecture strikes an ideal balance between audio quality
and CPU/memory consumption."
I am trying to think of when I would be summing across multiple points. Would creating summing busses and summing them into the master qualify as summing across multiple points? If so then I would be getting this extremely small about of degradation in just about every single one of my mixes. This leads one to ask if the Scope mixers suffer from this same problem. Anyone know if this is the case?
Getting back to the delay issues when using inserts and so on in the scope mixer......
Is there not an automatic delay compensation built into the scope mixers? I am going to get into the manual again today if I can to see if I can answer my own question but thought I would throw this one out there just in case there is more to it that what the manual covers.
Another thing that came up in this thread that has been running around in my head is the talk of entering and exiting the Scope environment via ASIO drivers. Is there room for degradation in signal there? I get the idea that if you are running at different bit depths and sample rates there is dithering going on but if you where to work with 24bits files and set the host program to run at 24 bits would it not just be a direct digital transfer? I did not even consider this in the past but I suppose it is a possibility. Again I bet even if there is only tiny bits of degradation it is the concern that when you add them all up in one signal chain you start to get errors that are large enough to create a level of degradation work thinking about. For example in my case I would be...
From my host program (having to make sure that all sample rates and bit depths match) via ASIO into the scope environment.
Then straight into the 2448 and from single channels into mix busses and then summing into the master channel.
Once I am happy with the mix and want to print it I have to go back via ASIO into Live or another recording program.
Then last but not least dither it down to 16bits from 24 bits..
It seems to me that there are many places there that problems can creap in and that fails to mention any insert FX and AUX summing.
So it is not just one step, it is when all of a sudden you have dithered two or three times as well as gone through two sample conversions and through two ASIO conversions, if indeed they are non-neutral operations.
Sorry for the ADD thread but I figured I may as keep all this in one thread/post.
P.S. Happy New Year to you and your families!