Today I noticed that one of my tracks (https://www.audiotool.com/track/xx6w08gr56n3/) had a rendering error revolving around one specific sample.
The piano sample that can be heard throughout the intro and multiple parts later in the track sounds bitcushed, even though no bitcrusher, nor any other distortion effect, was added to the signal chain. It sounds noticeably clearer in the "Studio" application and didn't get resolved with a republish.
I assume it is connected with a bug/glitch revolving around the signal chain (sampler > reverb > compressor > mixer > output), that causes the rendering process to mess up.
(Around 6 months ago I published this track and because I usually don't listen to the tracks after I make them, I didn't notice until now)
I originally made the track on Firefox, but republished it through Opera, so I don't think it is connected to that.
My OS is WIndows 10 pro, that is running on a AMD Ryzen 7 2700x desktop computer.
Comments (4)
I've seen this reported before, for example: https://www.audiotool.com/board/bug_reports/phantom_bitchrushing. Was the original sample (or during processing before reaching the main mix) clipping in any way? Was it time stretched?
I get a 404 error message when following that link.
That sample was time stretched, as were many others on that track
Sorry, the period after the link became part of it. Here it is again:
https://www.audiotool.com/board/bug_reports/phantom_bitchrushing
If that time stretched sample sounds right inside the Studio, what about bouncing it and using the processed version instead?
I'll try doing that, thanks.