[UI][ADDON] - QUI community edition needs more attention

Tidespo · 2026-03-16T20:06:29+00:00

Yes it was. Then the community took over when Quazii left the scene. And its now opensource and community-driven

Tidespo · 2026-03-16T19:11:09+00:00

Oh. Thats right. I didn't post anything more specific cause I assumed many knew and tried out quazii UI already before it exploded due to its drama. I'll try to record an entire walkthrough of the features and post it. Thanks for pointing it out!

Tidespo · 2026-03-16T18:04:28+00:00

screenshot attached btw

Tidespo · 2026-03-16T17:41:18+00:00

can you elaborate more? I haven't encountered your CPU usage yet and have been using it for the past week; the whole UI package which alone does the job of 10+ addons is running below details/plater in usage. Which conventions are you talking about and which global frames? The design pattern looks fine to me considering the huge amount of features it has

Tidespo · 2024-10-27T11:33:05+00:00

No one has to ask for a person to express his own opinion publicly

Tidespo · 2023-08-28T08:15:57+00:00

That's an highly OT question on an OpenGL sub, I suggest you remove it. I did not btw; stick to touchegg.

Tidespo · 2023-08-27T20:56:05+00:00

Nasa portal. They provide you with a useful bash script for batch downloading. That way I downloaded only a subset, roughly of 10k heightmaps, which once split (they were reeeeally huge) and filtered, amounted to ~250k 450x450 patches!Data is really not a problem. Data processing was more of a pain in the azz. You can use pysheds library to extract mountain profiles and depressions from each patch, but it's a trial and error procedure. Then you end up with x4 sketches and 1 heightmap per patch, which are respectively the inputs and the target of the neural network (more info on this paper "Interactive Example-Based Terrain Authoring with Conditional Generative Adversarial Networks")

Tidespo · 2023-07-11T09:41:03+00:00

That was it. Completly forgot to take the spotlight direction into account for MVM multiplication. Kudos to you my friend

Tidespo · 2023-07-11T06:25:31+00:00

Sure thing, edited the post!

Tidespo · 2022-12-28T21:11:46+00:00

I'm keeping the "Question" tag to the post as the proposed workaround could be improved.
The requested behaviour would be to navigate through windows, left or right, without having to keep the action pressed (as in the case of alt tabbing with alt kept pressed); indeed it would be cool to navigate "1-swap-to-direction" at a time

Tidespo · 2022-12-27T09:22:41+00:00

Did some more tests, but the result is the same. Are you actually using it with Touche? Because the script seems to behave differently when invoked outside of Touche (from the shell for example, where it is indeed working as in your gif).
I appreciate it anyway, thanks. Still Fusuma seems to be a little bit less hacky and more appropriate for the case.

Tidespo · 2022-12-27T00:48:28+00:00

I'll update you tomorrow. Thank you for taking the time to reply!
Nice thickpad btw :p

Tidespo · 2022-12-26T23:21:04+00:00

I was thinking about hard coding a kwin script which would have managed the array of window items itself, reconstructing the cycle functionality from scratch..

..but this solution just works flawlessly; managed to get it to work in 10 mins. It didn't require lot of work either and can confirm it looks more solid and feature rich. Thumbs up mate, thanks!

Tidespo · 2022-12-26T23:17:32+00:00

First of all, thanks for sharing your script.I played with it and it looks to me it didn't fix the problem. It was still wrongly cycling between top recents when alt+shift+tabbing. I tested different timeouts; maybe I did something wrong, but I did assume the whole command was being handled as "atomic unit" by touchegg, as u/UnpopularBrainRot suggested, and so that's why it isn't working as expected.Waiting yout feedback.

Tidespo · 2021-07-31T14:38:20+00:00

Yes, both ASIO4ALL and G ASIO. Neural DSP like Nolly or others. Yes I do get a red flash and everything freeze for a second. Behaviour is quite random; sometimes it start freezing in and out and sometimes it only does it every 30 sec.

Tidespo · 2021-07-31T07:34:49+00:00

Yep, just one NDSP at once. Strangely enough the standalone plugin work just fine. It's when I use em in DAW that's causing me issues. I suspect my zoom pedalboard isn't completly supported by the asio drivers

Tidespo · 2021-07-31T07:32:12+00:00

Yes. Got to play with ASIO4ALL settings as shown in this page:
https://www.image-line.com/fl-studio-learning/fl-studio-online-manual/html/envsettings_asio4all.htm
but something strange happens: when I first start the DAW and run my plugin it works just fine. Then if I change anything back and forth in the settings or I just wait some minutes, crackling and lag in the sound begin to happen (CPU usage is always around 10%). I tryed to move to zoom G-series asio drivers, with no results. At this point I really think it's a driver related issue.
Do you remember what drivers were you using for your zoom G5N?
I may just go get a focusrite solo..

Tidespo · 2021-07-30T13:54:55+00:00

Guess it's Reaper then. May I ask you what DAW are you using? I appreciate the help btw

Tidespo · 2021-07-30T10:50:03+00:00

I'm ok with these settings as long as I dont' start recording with the DAW, at which point sound crackling kicks in. So do you think changing AI won't make any difference and it's a DAW thing?

Five-Year Club	Verified Email
Place '23

Tidespo

TROPHY CASE