Waveform 8.2.0 available, Not Beta

[terrynoakes]

Waveform 8.2.0 available, Not Beta

[AndreasH]

Edit:
Reinstalled 8.2.0 and now it works fine.


Crashes if i try to open vst plugins (GUI) - i even have to restart Linux Mint
Going back to 8.1.4.

[Kott]

Crashes if i try to open vst plugins (GUI)

cannot confirm, works fine on opensuse tubmleweed

[zzz00m]

8.2.0 is stable here on Windows 10 x64.

[AndreasH]

I gave it another try, reinstalled it and this time everything works fine. I edited my first post.

[Hermu]

- Fixed a problem where Linux plugin UIs would be incorrectly be positioned in their windows

NOT FIXED!!

Ubuntu 16.04 LTS
all other tested 3rd party plugin works, except Collective and BioTek opens now only as ghost gui and freezes Waveform. Waveform must be killed!!
i never had this problem with any previous version before!
double open gui looks also not really professional (open and refresh)!
behaviour is still different to MacOs and Windows, because all opened GUIs are now always open and lock has no effect.

[Uhotug]

Ubuntu 16.04.
Waveform 8.2.0

As long as I switch to "Search", Waveform start to eat 100% CPU and slowly consume the whole RAM (and then it is killed by OS).

Installing second time, installing 8.1.14 and again 8.2.0: no difference.

Back to 8.1.14

EDIT: forgot that I had 8.1.16 before, so installed it. As with 1.14, no problem.

[dRowAudio]

Ubuntu 16.04.
Waveform 8.2.0

As long as I switch to "Search", Waveform start to eat 100% CPU and slowly consume the whole RAM (and then it is killed by OS).

Installing second time, installing 8.1.14 and again 8.2.0: no difference.

Back to 8.1.14

EDIT: forgot that I had 8.1.16 before, so installed it. As with 1.14, no problem.

What do you mean by "Switch to search"? Do you mean show the "Search" side panel?
Do you have to select the search text before the CPU starts being eaten or just have the panel visible?
If you close the side panel or switch to another panel (e.g. "Files") does the CPU load reduce?
How are you measuring the CPU load? "System Monitor"?

Hopefully with a bit more info I can take a closer look. Thanks.

[Uhotug]

I have localized when that happens: when in the Search browser I click on Step sequencer preset.
I have already tried with regenerated Presets.trkpresets, still the same. After I click, Waveform is completely locked till it is killed (manually or by system, after consuming the whole RAM). CPU is measured by "top" (100%), it also shows how RAM consumption is growing.

Originally I had freezes just in attempts to open some edits, I have deleted the project thinking it is corrupted (was scratch with nothing useful in any case). Now I understand it could be better to keep it for analysis...

[Uhotug]

Well, I also understand why my test project was crashing...
Wav plays fine. But if I insert Collective (1.0.6):
* GUI opens fine
* NO sound is coming out when I press keys on it
* if GUI is closed, an attempt to open it again creates a "ghost" window of the Collective GUI size (so, no content, just shadow from transparent window, no borders). Only "kill" can exit Waveform then.

[dRowAudio]

Well, I also understand why my test project was crashing...
Wav plays fine. But if I insert Collective (1.0.6):
* GUI opens fine
* NO sound is coming out when I press keys on it
* if GUI is closed, an attempt to open it again creates a "ghost" window of the Collective GUI size (so, no content, just shadow from transparent window, no borders). Only "kill" can exit Waveform then.

I'm looking in to window issues on Linux but they behave very differently to other OSes.

[Uhotug]

If you think that looking at my screen with Teamviewer can help, no problem from my side.

[dRowAudio]

Thanks for the offer but I think I know the problem you're talking about. The problem is that when I make some changes to fix that issue, I'm now getting plugins appearing just a few pixel wide and high so I need to figure out why that is.

The main problem is that on Linux there's no way (at least with the framework we're using) to set a window to "always on top" without re-creating it. Re-creating it is crashing some plugins for some reason. At the moment I'm trying to figure out a way to create a window as always on top and leave it like that. Hopefully that will solve all problems but again it's proving more tricky that I would hope.

[tonedef71]

Always-on-top windows are not always a good idea in a DAW. A plug-in like Kontakt 5, which likes to pop up dialog confirmation windows (e.g. "Are you sure you want to reset this multi?") that are modal, can effectively freeze up a DAW. While the modal dialog window is active, the always-on-top window cannot be moved or minimized; if the always-on-top window has obscured the plug-in's modal dialog window, it will prevent the user from being able to acknowledge and dismiss the modal dialog window. If the user cannot somehow bring the modal dialog window in front of the always-on-top window, the only recourse he/she has is to forcibly kill the DAW process. No fun!

[dRowAudio]

Always-on-top windows are not always a good idea in a DAW. A plug-in like Kontakt 5, which likes to pop up dialog confirmation windows (e.g. "Are you sure you want to reset this multi?") that are modal, can effectively freeze up a DAW. While the modal dialog window is active, the always-on-top window cannot be moved or minimized; if the always-on-top window has obscured the plug-in's modal dialog window, it will prevent the user from being able to acknowledge and dismiss the modal dialog window. If the user cannot somehow bring the modal dialog window in front of the always-on-top window, the only recourse he/she has is to forcibly kill the DAW process. No fun!

Yes, this is precisely why modal dialogs in plugins are evil and should never be used.
In the host, we have to set the plugin windows to always on top however, otherwise they constantly fall behind the main UI which makes them very difficult to use.