Since the Studio doesn't run inside a Flash plug-in any more, we face dependencies that can potentially lower the experience in terms of performance. To rule out common issues, here is a list of things to check before getting too frustrated:
First Things First
Install the latest stable version of Chrome. You can check your current version by typing chrome://settings/help into the address bar.
Close any browser tabs you don't need.
Run the Studio in incognito mode to prevent extensions from creating possible interferences.
Quit background software like Skype, WhatsApp, Dropbox, Slack, etc.
Check for CPU intensive, unnecessary processes in your Task Manager (Windows) or Activity Monitor (Mac).
Free up space on your hard disk if your machine runs out of it.
Reduce your browser's window if you have a very high screen resolution.
Arrangements can often contain inefficient effect chains, where several devices could just be removed or merged without altering the final sound. Ideally, you don't need to bother, but every device on the desktop takes valuable CPU time. Here are some tips:
You can often merge combinations of Stereo-Detune and Stereo-Enhancer into one.
Compressors can make you believe that the sound is more powerful. Try bypassing them to see if they are really necessary. Sometimes just increasing the volume achieves the same effect.
The Heisenberg can be very CPU intensive. Try to minimise their amount in your arrangement or, if you don't need any Heisenberg specific feature, use the less CPU intensive Pulverisateur to create your sound.
Quantum as a multi-band compressor is mainly used for mastering and to alter the dynamic of specific frequency bands in complex sounds. If you do not need these features, replace it with Gravity, which uses way less CPU.
When using Curve, switch off the filters you don't need.
Switch the spectrum analyser in Quantum and Curve off once you've adjusted their settings.
If several sounds use the same effect chain, connect it to a mixer as a send/return effects chain instead of duplicating and inserting it after each sound.
Make your arrangement compact. Long cables take longer to draw.
When working on parts of a big arrangement, deactivate any timeline tracks that you don't need to hear.
Did something help? Let us know in the comments. If nothing did, create a topic in the
Help board
.
I am in the new version of Chrome, but when I go to Studio, everything’s works fine, until the Audiotool logo is all white. Then it asks me what I was doing before. And I reload it, but then the same thing happens. Please tell me what I should do. P.S. I just signed up today and I am really excited in using Audiotool and I’m using Incognito.
the new link should automatically open when you click on the studio button IF you have agreed that you have saved your drafts, so there's no need. if you need the old one its
sound , i wondered whats all the bits n bobs stutters , i thought it was the hz rate .. but thanks will give that a go ... also i use firefox .. not had any other problem .. but will look at chrome
Great explanation of the basics of digital audio routing and processing and the relationship between sample rate, buffer size, latency, DSP load, CPU load and how glitchy playback (buffer under-run) happens.
im having the exact same problem starting 2 days ago, when i hit play there is no sound the bar doesn't even move and it didnt even start till 2 days ago literally the night before, i could play sounds just fine.
I originally set up my account by signing into a Google account. I see that I can change my email/password and would like to do that. Unfortunately, the app/site doesn't recognize my Google account password as my current password. When I try to reset the password it doesn't work. It says "We're sorry! Your account was found, but the password reset mail could not be sent. Please contact the staff. Details: (details not available)". How do I reset it plz help before I lose my progress. Can someone in the staff just reset my password and tell me it please!
Plz help. I have done everything you said and it is still really glitchy. I can't use the booster because i have a chrome book and it seems that it doesn't work on my particular computer. I have activated the hardware acceleration and that doesn't seem to make a difference. I am giving up hope...
i also had no such luck with any of these things. isnt there a simple way just to integrate the booster into the studio's coding, making it so you dont need the seperate downloads for different types of platforms?
There is a new experimental flag introduced by the Chrome developers to test a different internal audio-infrastructure for the web-audio-api.
Please visit: chrome://flags/#audio-worklet-realtime-thread and enable it. If you discover any changes (good or bad) with audiotool, please reply to this comment. Thanks.
This is the corresponding issue (link is only visible to registered users) Quote: "WebAudio Rendering Thread for AudioWorklet uses "DISPLAY" priority thread and this causes audio glitches when other graphics tasks (outside of Chrome) dominate the system."
So, it is probably hard to test effects outside from Chrome.
I am in the new version of Chrome, but when I go to Studio, everything’s works fine, until the Audiotool logo is all white. Then it asks me what I was doing before. And I reload it, but then the same thing happens. Please tell me what I should do. P.S. I just signed up today and I am really excited in using Audiotool and I’m using Incognito.