Early look at the GUI

[kv331]

The new GUI is slick, however, there seems to be a huge amount of aliasing in the majority of knobs:


Is there a way to make them look like this?


Or is it the way the GUI editor is programmed?

Anyway, great skin! it inspires to tweak the synth.

Btw, song 14 still doesn't work here. 15 is fine now though.

Yes at last a couple of minutes ago I figured out how to do that, EUREKA! Will test on Saturday, and a new build is coming on Sunday!

[matt42]

Hi Hlis93,

Sorry I'm late to the party. Nice work as usual! It's looks so good I might just have to try out the software.

[Hlis93]

I've been adjusting the GUI, this is the first batch of graphics I changed. Still many things I have changes even for this one screenshot. I guess the quesiton is if users prefer the currently installed GUI or this one. They are the almost the same GUI it just the way things are spaced and I've made the text brighter, the fader will be next.

[acousticglue]

Text brighter is good.

[Hlis93]

made a bunch of changes to the GUI. Things are re-organized repositioned, Text is much brighter, etc, etc still working on it.

[FragileX]

Just wanted to say thanks for your fantastic work on the skin.

Man, I had a glimpse at how much work it has to be, to come up with a complete skin - I looked into the editor to see if I could make a skin that would fit on my netbook (being able to play on the road). But there is no chance i could come up with something useful in the next years (even if I leave away the 2nd layer); toooooo... many elements (and we user want more nevertheless )

Hats off!

[Hlis93]

If I understand correctly you are able to make a skin that uses various controls and you can set that up to control a patch. Say for example that you know you will be working with a set of presets and you will want visual feedback on certain objects. You could make a skin that has just to those controls. so after you open SM you would use the skin tab and selector your customized GUI for that and your set.

I do have sets of GUI elements that I have been putting together so user could use prefab animation, and some templates etc to make a customized skin just for that purpose. It will be a while till I can finish it, I have to actually finish the current GUI first.

[kv331]

Hi everyone,

There's a change I'd like to add hopefuly this week regarding skins/presets:

When user clicks on the "New" button he'll see the presets under category "Templates". This might help preset building I thought.

And we will introduce a Skin selector on the top header: The user will be able to change the current skin.

[Hlis93]

?????

thats a good idea, I was trying to get the toggle that I have to display the current skin name but couldn't figure it out. did you see this thread? Might be a good idea to be able to link a particular gui to a patch, and be able to toggle that option on or off depending on the circumstances.

http://www.kvraudio.com/forum/viewtopic ... 32#3846032

many of the things being said there apply here as well in terms of GUI. The hate for menu's and all. But honestly as much as I consider seeing how much of this I could fit on one screen view and more to toyed with it the more I realized it would be insane. Perhaps the only change I;m still holding out on it to place the menus for the MV pages at the top of the sections instead of to the side, it might make the distance the mouse as travel more convient esp since there are so many pages.

[kv331]

Might be a good idea to be able to link a particular gui to a patch

That's already implemented in SynthMaster So different templates will be associated with different skins.

[kv331]

The new GUI is slick, however, there seems to be a huge amount of aliasing in the majority of knobs:


Is there a way to make them look like this?

EDIT: There WAS a bug in the rendering code for this one. Instead of loading numbers unsigned I loaded them signed

Here's how the fixed version looks:



As good as it gets. What do you guys think?

[deraudrl]

Here's how the fixed version looks:



As good as it gets. What do you guys think?

Am I the only one who thinks having two indicator rings is redundant to the point of fussiness?

[FragileX]

The new GUI is slick, however, there seems to be a huge amount of aliasing in the majority of knobs:


Is there a way to make them look like this?

EDIT: There WAS a bug in the rendering code for this one. Instead of loading numbers unsigned I loaded them signed

Here's how the fixed version looks:



As good as it gets. What do you guys think?

Yep looks much better than before.

Am I the only one who thinks having two indicator rings is redundant to the point of fussiness?

The rings are indicators for the modulation - so two rings means two different modulation sources are possible.

[deraudrl]

Am I the only one who thinks having two indicator rings is redundant to the point of fussiness?

The rings are indicators for the modulation - so two rings means two different modulation sources are possible.

Ok, I'm away from my 'big' machine so I can't try this "live", but explain please what the two rings are actually indicating. If it isn't the position of the (single) knob, I suggest they are more confusing than not having them there at all.

And if they are indicating the control position (which is what one would expect looking at that picture), then there are three separate indicators, counting the index line on the knob itself.

(And yes, in case you can't tell, I think combining static controls with dynamic readouts is generally a Bad Idea.)

[FragileX]

No no, this lines are not dynamic, they are describing the range of the modulation and they are very useful (imho of course).

So you got the knob read out and the range of two different modulations...