@lplr I just started using Figma to design the UI for my next plugins. It's mainly vector but you can drop images in there too.

It'll work fine with any of the assets from the aforementioned UI design services.

The main advantage for me is speed of iterations. You can easily nest and group things, and use constraints to keep things evenly spaced and shrink/grow as you modify your layout. You can't do this very easily in the HISE Interface Designer.

Once you're happy with the design, you can take the UI elements' position and sizes straight into HISE scripts that create the UI.

I know it's an extra piece of software to learn, but the flexibility of this way of designing is a winner for me. It keeps a nice separation between functional and visual design.

Additional bonus is I can share the progress of the visual design with someone else (stakeholder, collaborator, etc) without having to either share the HISE project or having to continually take new screenshots of the UI in HISE to email/message to them.

If you have a team it's even better. The UI designer can work on the visual design in parallel with the plugin/DSP developer, and as long as they have a central interface document - showing what parameters and displays the plugin exposes in the UI along with ranges, units, etc. - then combining them near the end of development should be cake.

@bendurso great, thanks

@d-healey nvm i coded smth wrong but i fixed it thanks for the help guys

UPDATES:

Implemented developer branding info (Brand Color, support email/webpage) from the Tools > Branding section to display directly on the GUI.

Logo can be added to this as well by simply adding your logo to SoundSyncLogo image in HISE. If you dont have a logo added to the project, it will display initials for your Brand (example: SS for SoundSync) instead.

@HISEnberg I think the part that gets me is understanding what arguments to use and why, and in what order. I can assume, but I dont feel sure in my choices just yet. I've been using helper functions so Im barley starting to understand how to pass arguments to other functions but im still getting comfy with everything. Appreciate the advice! 🙏

@d-healey ah crud. Yeah we did. Ok I fixed it. Thank You! Sorry for wasting just a little bit of your time. I'll make it up to you in enthusiasm! haha. Hope you're having a great day! 🙏

Oh in fact I guess I should better make a midi sequence and get the rectangle list...

Looks like there’s no easy path, but thanks a lot!
I’ll explore the possible approaches, including WD and Wavenet. Appreciate the pointers!

Thank you very much, actually I'm glad that my logic was quite ok and I am not isane:) Your example was claryfing some stuff too. Thanks!

@Christoph-Hart

alt text

@Christoph-Hart The tables really, really need an update

All value currently set above 85% are shifting up at each mouse click ! 😱

zrg.gif

And setting the value is so rough, often jumping by 2% with no possibilities to get more precision.

This is making me think

What about the possibility of opening all current point in an array/table like popup so we can edit the point numerically?

Or expand the area for more precision?

would there be possible to show the values with a custom range (even if 0-1 behind the scene) so we would be able for instance to set frequencies or gains precisely?

A table for the real guys 💪

Of course all of that can be made from the UI, but when you design a network, you might not have/need a connection. And I can't imagine making a connection, dropping the table because you make another design choice, put back a table because, well, wasn't so bad... In short network design is no time for creating a UI connection + script just for testing things...

@ustk Thanks for the suggestion. I just tried calling th.setSyncMode(th.SyncInternal) and it does trigger setOnTransportChange the first time the DAW is stopped. After that, the function is not triggered again by playing or stopping. The clock actually stops altogether.

Back by popular demand (I‘ve removed the post with the email address as this was probably the intention).

@Christoph-Hart Amazing! So what I've said is just wrong!

Yep wanted to do that kind of thing a while back but it seems Juce doesn't have a method to read the pixel under the mouse (or any pos..)

@Lindon Worked for me, but im not using the latest version of HISE, maybe a bug?