unintentional bit reduction effect using play~
Hi,
My Max4Live patch is a looper with 6 play~ objects at its core, randomly picking loop length and location based on the length of the file. It works very well (aside from a few kinks I’m still working on) but I’ve noticed an unintentional side effect; namely, there is a bit-reduction sound when the thing really gets going. Now, in most cases this sounds great, and it definitely gives the instrument a bit of character. But for cases where I don’t find it desirable, can anyone tell me why this might be?
Cheers,
Jay
It is due to loss of precision as the location signal at the input gets bigger. There is no way around but use another object like groove~ or wave~. Of course there is the nonstandard hr.play~ object. By the way, it is not bit-reduction, but downsampling what you hear.