Questions & Answers

DISCRETE ARTIFACTS (Crackling) from Send/Return level automation ( Not a latency/buffer problem at all)

+1 vote
asked Sep 16, 2017 in Studio One 3 by slavasemenikhin (730 points)
edited Sep 16, 2017 by slavasemenikhin

So, i ran this tests on a multiple computers on S1 vers 3.2 and 3.5.1 (i5 macbook pro, i7 macbook pro and i7 PC desktop) and please don't tell me it has something to do with latency and buffer size, because it doesn't! I am not a beginner at all. 

Since i can not attache my test song to the question please run this simple test:

1. Create a new song (where your CPU will feel easy so no one can say it is a latency problem) 

2. Create an audio or instrument track with a pure sine wave, doesn't matter in what key, but low end is preferable. 

3. Create an FX channel with any reverb or delay (whatever plugin actually will illuminate the issue) plugin and bypass or power off.

4. Create an automation track for send/return level to your FX channel and draw some different curve shapes under that sine wave.

5. Boost the level on your speakers ( Headphones is better) and get your jaw dropped from how crappy is the noise you are hearing! 

5. Save your test song and GO CREATE A TICKET and attach the file so they will start working on the fix asap.

The more tickets they will get the faster this problem will be sold i believe. But i am honestly just want my money back right now. 

Because when those crackles fly into reverb or delay tail it sounds 10X more terrible and it is totally not acceptable for a DAW of such level as S1.

It took me a while to notice this issue, because usually these artifacts are being masked by mid and high range content. So you should run this test to make sure what i am talking about. Imagine working on an ambient sound track for a video game, and then try to prove to your client that you added those terribly digitally sounding things purposely ;) 

Thanks for attention! 

1 Answer

0 votes
answered Sep 19, 2017 by PreSonuSupt4 (220,900 points)
Best answer

This issue has already been submitted to the development team as you noted.   If this is changed in a future update you will see it in the release notes.