Audio Quality Issues (crackling)

@howinteresting can you give it a shot now?

It’s certainly better now - polysynth only gets the odd crackle and pop but changing instruments still results in audio that is extremely unstable - there’s still a bit of reverb on it so maybe a switch to disable it entirely for lower-powered devices would improve the issue? :slight_smile:
Edit: your previous post about no animations and single velocity sounds like a good idea - turning reverb off as well would make it better!

darn…

I’ve identified some opportunities to improve CPU usage for the visualizer and the button press animations which I’m going to do before I disable them completely.


The visualizer right now has distinct objects for each “bar” you see and it’s updating all of those sizes/positions individually so (if you’re curious), I’m going to make it a unified shape and just update the vertices together.


I am also going to try and add a “health” debugger that will indicate if the app is struggling and will show you information that will be helpful to pass on for all bug reports. That feature will also allow me to dynamically turn off/downgrade certain functionality.


Mobile safari also has an issue that causes it to crash as more presets are selected, so the cause of that might be the fix for the one you’re experiencing.


The reverb I’m using now shouldn’t be contributing to the performance problem itself, but I’ll revisit that after all of the above are addressed.

That sounds like it might work. I do notice lag in the visualiser and when I change notes I can play them as long as I let the visualiser stop - sounds like the culprit.

As you said, integrating the bars into one big thing would work or perhaps (i’m not sure how this would work or if it’s even possible) prioritising the audio over the visualisers / shutting them off if they slow down too much would help reduce lag.

I noticed that there was no lag in the legacy version and the new version has introduced some; I know the visualisers changed which is further evidence to say that they could be the cause.

Windows 7
Chrome
Toshiba i3 8g Ram
all presets especially the ensemble

All: I’ve released another big change set that should reduce memory usage/leaks, and CPU usage.

Let me know if things are better/worse for you.

Sorry for the late reply.
I have just checked out the main site and although there is a little bit of GUI lag the audio works perfectly. :+1:

nice. I have more improvements coming on this front.

I’ve been a bit busy over the past couple of months but i have now come back to see what’s up and although it takes a little bit to load now, the audio is not buggy at all and changing presets does not affect the quality. Great job :slight_smile:

1 Like

yeah, this is starting to perform really professionally.

The audio on a chromebook deteriorates and gets VERY choppy extremely fast after just a few keypresses.

Can you paste the output from chrome://system

When I use synth strings, it makes a crackling sound. This happens with many other instruments as well such as the string ensemble and the grand piano.

I’ve merged your post and a few other with a topic thread for this issue.

Any issue related to crackling (on any browser) is most likely caused by a bottleneck in the CPU – whether that’s because the site is using too much CPU, your hardware not being able to keep up, or other CPU intensive software you’re running at the same time.

Watch this thread to get updates on CPU optimizations. I’ve been inactive for a while but have some big changes coming soon.

new to this, and the first thing i noticed is, when i tried anything the audio was EXTREMELY laggy.

1 Like

I am new too and I am experiencing the same difficultie. It makes it inpossible to actually play a song. Hopefully it can be repaired. Could also depend upon the quality of the internet connection.

Very happy to have come acrosss this site though, because in does enable me to play the sounds using my Nord Elektro in combination with my Focusrite audio interface.

hi @icantmakemusic and @Keyboardkid – can you describe the issues you’re facing a bit more?

Can you share with me as much of your computer’s specs as possible?

Hi Jack,

This is Michael from Holland.

First let me tell you, you are doing a great job. You have develloped and still are developping just the thing I have been looking for for a long time, though I would like all of it to be available in a downloadable form, because I merely use it for live performance and therefore it needs to be 100% available and of constant quality at all times. I am more of a musician than I am a technician.

Back to the specific bug. I have uploaded my laptop’s spec’s hoping you will find them usefull.

Keep up the good work.

Bye,

Michael

Hoi Michael,

I appreciate the kind words – I’m putting a lot of work into making midi.city work on wider range of devices right now which should resolve a lot of the open issues.

In the meantime, I would take a look at your windows Task Manager to make sure that you have low CPU and memory usage outside of your browser.

Stay tuned for updates on better performance.

doei,
Jack