Hi, sorry for late followup, been busy recording footsteps…
Can you switch to x11 and tell me if it works properly?
Unfortunately it’s the same behavior there:
I’m not able to decipher any consistent behavior
I’ve done tests on other Linux systems (Ubuntu and Fedora) and I can’t reproduce the problem (except when I reboot the system on Wayland). Can you provide more information on the configuration of the machine? And what version of ASAP are you using? Are you sure you rebooted with x11 and not Wayland? Once Reaper has been launched, what does the “xlsclients” command return?
I appreciate very much you looking into this, i only hope i’ll be able to help debugging.
Here’s some output (sigla is hostname):
[andersvi@sigla ~]$ echo $XDG_SESSION_TYPE
x11
[andersvi@sigla ~]$ xlsclients
sigla gsd-keyboard
sigla gsd-color
sigla gsd-power
sigla gsd-media-keys
sigla gsd-wacom
sigla gsd-xsettings
sigla ibus-extension-gtk3
sigla ibus-x11
sigla evolution-alarm-notify
sigla xdg-desktop-portal-gtk
sigla gnome-terminal-server
sigla main.py
sigla reaper
sigla emacs
sigla firefox
sigla mutter-x11-frames
sigla gnome-software
sigla xdg-desktop-portal-gnome
sigla gnome-calendar
Not sure what might be useful…
Can you provide more information on the configuration of the machine?
Not sure what would be relevant, if there are particulars which might prove helpful, like e.g glibc-version etc, please ask me. Here’s some basic facts:
[andersvi@sigla ~]$ uname -a
Linux sigla 6.7.10-200.fc39.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Mar 18 18:56:52 UTC 2024 x86_64 GNU/Linux
What about window shortcuts etc.? Perhaps unlikely since it works some of the time before stopping to work?
Forgot ASAP-version…
“About” says:
ASAP Spectral Surface - v1.2.2 (19131)
There could be several causes, but since I can’t reproduce the problem, it’s difficult to understand what it is (with Wayland, the global application is laggy and glitchy, so it’s hard to figure out if the problem is related). But I will look for a machine as close as possible to your configuration to try to reproduce it. If you can find a set of actions that consistently leads to an issue, I can try to find out what’s going on. In the meantime, I’ll continue to dig into it.
About the ASAP version, I doubt that it will fix the problem but you can update to v1.2.3.
Using v1.2.3 now, but same behavior, as you suggested.
It seems to be somewhat dependent on workflow, and involves:
Seems there’s a consistent ‘flip’ in behavior between polygon and Ctrl-x working
or not:
I’ve tried finding consistent patterns in the workflow, without luck:
Worth to point out: when polygon tool works, i can (mostly, not always…) enter several polygons in sequence, if not interrupted by square tool, or closing and re-opening instance
Sorry to not be much of help. If you have suggestions for sequences of operations, please tell me
Thank you for your feedback. It helps a lot! I’ll work on it. I may send you a version that generates logs to facilitate investigations. I’ll keep you informed.
I’ve compiled a new version 1.3.0-dev3 that generates log files (there are a few new features, but they shouldn’t change interactions). Can you try it and send me the log file when you encounter the bug?
The files should be located in ~/.config/Ircam/ASAP_Spectral_Surface/.
If not in this directory, replace ~/.config with the path specified following the XDG_CONFIG_HOME value in the ~/.config/user-dirs.dirs file.
Thank you!
An output log is attached. And just in case - a screencast of the actions used while making the log.
Steps used here:
Log_2024-04-12.tar (20 KB)
Forgot to say, the steps used fails in the same way every time
Thank you very much for your feedback. I can see in the log that it works the first time then once you restart the plug-in editor, it doesn’t work anymore, the polygon never manages to be created (exactly like in the video). I’ll try to retrace the way that leads to this. Maybe I will send you another version with more logs. Sorry for the inconvenience and thanks again for the feedback!
Again I downloaded another version, ASAP-v1.3.0-dev3b-Linux. If you could clean up the logs folder, do the same test, and send me the new log files back, that would be great 
!
Moreover, the log pointed out to me that on your system the plug-in cannot check the new version and that certain actions are executed on the wrong thread. I’ll sort this out later but I should probably ask you for new tests, sorry 
.
After being recreated, the plug-in editor loses keyboard focus after each mouse click. This shouldn’t happen, because losing focus resets the current action, which is why you can’t have more than one point. I need to find the cause of this problem, but it’s possible that it’s independent of the plug-in and is a bug in the focus management. Once I’ve found out exactly what’s going on, I’ll try to find a fix or forward the detailed problem (to the Reaper team if the problem comes from their side, for example). I’ll probably ask you for some more tests, sorry for the inconvenience.
I see. If i keep clicking ‘randomly’ - some very few times (1/100?) a polygon (triangle) appears, only to disappear upon the next click. Haven’t been able to distille any pattern.
For the sake of it I tried now changing my preferred ‘hover’ behavior in my window-manager, from ‘hover-window-to-focus’ to ‘click-window-to-focus’, without any change in the polygon-tool.
Yes, please ask for more tests. I’d be very happy to help!
I’ve uploaded version 1.3.0-dev4 which contains the ARA plugins in a standalone application version. For various reasons, the Spectral Surface plug-in has been renamed Psycho Filter, so if you can test the Psycho Filter application 
If you can test it, it would help to understand where the problem comes from.
Good news, if you can do a 
it’s a good sign and at least you have an alternative. On the other hand, the problem surely lies with Reaper, so I’ll pass the information on to them. If you have any other feedback or suggestions, don’t hesitate!
Great work. Pls. ask if you need some special-case-debugging-stack-tracing of any sort, short of replacing my OS
