Skip to main content
C
chaunceyc
Known Participant
January 5, 2026
Open for Voting

Audio Waveform Generation got so much worse in Latest 2025 versions

  • January 5, 2026
  • 11 replies
  • 369 views

They decided to mess with this for some reason--it used to have the simple little status info in the lower right corner and you could easily see the progress of when the audio file analysis would be completed. The message also just disappeared on its own after a bit, so no wasted screen real estate.  It also started to show you any completed waveforms so you could start editing long clips long before the analysis completed. 

 

NOW: They moved this to the Progress panel, which requires you to functionally use up 12-15 times the amount of space on your screen to be able to read it at all, manually close it afterward to get that space back AND it makes you wait until the analysis is completely finished before showing any waveforms at all, delaying my editing sessions for several minutes after every import.  Can we go back to the old way or is this just another example of software getting worse with every "improvement?"

    11 replies

    Show previous replies
    A
    Community Manager
    Adolfo H.Community Manager
    Community Manager
    January 5, 2026

    Hey @chaunceyc , thanks a lot for taking the time to write this up and for the very clear feedback. I really appreciate you calling out what worked well for you in the previous experience.

    One of the main reasons this moved to the Progress panel is that we added multithreaded waveform generation. Under the hood, we are now processing waveforms in parallel, which makes the overall generation significantly faster, especially on longer clips and on machines with more cores. You can enable or verify this in Audio Preferences. With the old UI, we simply did not have a way to accurately represent multiple parallel processes happening at the same time, which is why the Progress panel became the right surface for this work.

    That said, the Progress panel is fully closable, so it should not permanently take up screen real estate once you are done checking status. The intent was to make progress more transparent without forcing it to live on screen.

    Regarding the behavior where waveforms only appear once the entire analysis is complete, that actually does not sound expected. You should still be able to see waveforms populating as they are generated, rather than having to wait for the full process to finish. If that is not happening on your end, it may very well be a bug. If you are willing, a short screen recording showing that behavior would be incredibly helpful for us to investigate and fix it.

    Again, thank you for the candid feedback. It is exactly this kind of input that helps us improve the experience, and I really appreciate you flagging both the workflow impact and the possible regression you are seeing.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices