SynthMakerJenovah ·
I really dont like drop down menu's, is there a way to make (for example choosing between OSC) buttons instead of drop downs like sine, square and saw each have a seperate button with the waveform on it for example.
drop down menus
From the original SynthMaker forum (2004–2014), with its members’ names and dates.
skOre ·
Yes, there is - Multiply the output of a knob by the amount of options you want it to have and either set a 'snap' in its properties and/or convert the output of the multiplication to an Int (simply route it into an Int field). Instead of multiplying, you could also set the max of the knob to the amout of options.
Jenovah ·
ok thx alot, i'm not sure I really got that, but I'll try to figure it out...
Jenovah ·
ok what you're suggesting is that I use a knob and that each knob position has a different waveform, but what I wanted was a seperate button for each waveform. Ofcourse only one can be on at the time... (I am talking about the Multi Osc)
sambean ·
For the GUI side you need a different on/off button for each instrument: the buttons are switched on by clicking on them, and when they are 'clicked on' a seperate off trigger should be sent to the other buttons to turn them off.
Try experimenting with the 'toggle' switch provided in the toolbox to get the correct properties. Once you have the correct properties, convert the GUIs..
For the OSC switching, the output from each toggle switches can be multiplied by a seperate interger (0, 1, 2,...) so you only get the value of the current swicth pressed..
If you see what I mean..
Sam
Jenovah ·
ok I understand the principle, but it's gonna take some searching to find everything, I only got the prog today and I have absolutly no knowledge about hardly any module or primitive...
anyhow thanks alot
oddson ·
Are you talking about 'radio buttons'?
If so here's a start: OSM
Its the basic toggle with a couple of wireless links tying them together.
The wireless output will talk to the other modules but not itself - so it doesn't turn itelf back off when you turn it on.
Other than that it's a small change in the control module.
The label section needs some work but, like I said it's a start.
Jenovah ·
YEAH THATS IT!
Great that's the one. The point is for each button to represent a different osc in the 'Multi Osc' instead of using the dropdown menu
oddson ·
The labels should be static with the OSC name but have some text style change for the selected OSC. I'd say organizing them vertically with the labels to the right would be best.
You'll need to figure out SM's graphics model to do this - that took me quite a while as it's not like anything I was used to.
Post in 'Help' if you run into specific problems. 🙂
posh ·
edit: nvm. 😀
Jenovah ·
thx for that posh, but I dont want a knob, I think it's a lot nicer having a button with the shape on it for each waveform seperatly like this
only i REALLY cant do it!!!
oddson ·
OH! 😮 That's a cool idea!
I'll post here a little later with a new file to help you get there.
If you could get ready with the graphics for on and off states for each wave type. (Including the Triangle if you're going to support it.)
Jenovah ·
alright 😀 i'll make the graphics, you make do the programming 😉 I'll post one for standard in the following order: Sine, saw, triangle, square, noise
oddson ·
Cool...
BTW - I've hit a small SM bug that's stopping this from being easy (as well as a crash report for Malc that's adding some time).
I have to come up with a work around. Could be a while.
Jenovah ·
Good luck with the bug
Here are the images
These images should have the exact size of a default drop down osc menu. I thought that might make it easier for replacement for people who use the original one. The colors and design are made to fit with my first VST (ever) which I'm working on now... (The GUI still needs a lot of work...)
Thx alot in advance, my VST will look way better with those OSC buttons there than the stupid drop down menu 😀
oddson ·
I'm an idiot!
Here I am trying to adapt the toggle switch thinking we'll replace the filled rectangle with an image for up and down for each button.
Now, because you've given the graphics for each state, I'm realizing it would be easier to just make a single control that reads where you're clicking.
It'll take me a little bit of time to start over. But I've learned a bunch!
Jenovah ·
im sorry, was I suposed to give each button seperatly? or is it easier like this, either way, I can do both
anyways good luck! and do you like the GUI I'm making ^__^
Shifrin ·
Having the images as posted would make this pretty simple to realise. A mouse area which you can use to generate a 0,1,2,3 or 4 based on the x-value, and a selector with the five bitmaps as inputs being chosen using the output of the mouse area calculaton 🙂
I did something very similar in the 'tabbed/paged' gui example I posted a while back 😉
BTW, nice graphics there Jenovah!
Shif.
Jenovah ·
Having the images as posted would make this pretty simple to realise. A mouse area which you can use to generate a 0,1,2,3 or 4 based on the x-value, and a selector with the five bitmaps as inputs being chosen using the output of the mouse area calculaton
well I've always found buttons cooler then menus, also using logos that lit up when selected looks way cooler than selecting text with your mouse, if it's that simple to make, ITS GREAT! 😀
BTW, nice graphics there Jenovah!
thx alot (atleast something I do good cause I'm horrible at SM)
Shifrin ·
Jenovah wrote: thx alot (atleast something I do good cause I'm horrible at SM)
I'm sure in time you'll get a lot better with SM, enjoy the journey 😉
Shif.
oddson ·
...im sorry, was I suposed to give each button seperatly?
That's what I was expecting, but what you gave is actually better. Hence the 'I'm an idiot' comment.
Here it is. OSM
The image selector needs some work. I've got it working with the bitmap array but not very smooth.
Here's how the selector works.
First you made it easy by having each functional area of the switch be 16 px square and offset (H & V) by 2 px from the upper left.
So in the 'Switch' module a funcational area is defined as offset by 0.25 grids and 2 grids H & W.
Then I just need to divide the mouse X value by 2 and drop any remainder by coercing to an integer. That integer then becomes the index without further manipulation.
do you like the GUI I'm making
It's very good! Very slick. I love that you've added 'dirt' to the greys so its not flat. Looks very industrial.
Did you get that knob working yet?
Jenovah ·
man, nice job!!!
Did you get that knob working yet?
yes I did, but now I'm having other problems (ofcourse) LOL[/img]
skOre ·
Hmm, these look just like the Fruity GUI 🙂
Jenovah ·
yeah I took the waveforms from FL, the rest is custom (and the little side thing next to the name) not very nice saying 'they look just like it' I put quite some work into it...
skOre ·
Nah, just found them to be alike, this small symbol thing, these handles on the boxes... Not saying you copied it (well apart from the stuff you did copy 😉), just that I got reminded of it.
Jenovah ·
:-p :-p :-p :-p :-p
you must have been a bully as a kid 😉
hehehe 😀
skOre ·
heh, no, I was quite anti-social though 🙂
Tom7777 ·
Hmm, these look just like the Fruity GUI 🙂
Are you allowed to re-sample synth graphics like this then, i always thought that doing so would lead to trouble with certain companys if you edit the graphics slightly, theres a load of controls and stuff i would like to use but havent for that reason.
posh ·
aye, you should be careful about stealing graphics from other software companies, cause you might just end up with more shit over your head then you can handle.
Jenovah ·
I didnt steal anyting, only the waveforms are left now, rest is original no trouble about some standard waveforms
skOre ·
Well, even if you have not stolen that much directly, there is this very FL-Studio feel to your graphics:
And you always have to keep in mind that we won't bother, yet if you want to go other places with this, people will immediately recognize this feel to it as well.
Jenovah ·
ok like I said, the side thing and the waveform buttons rest is not same
anyways, I will post 'legal' 😉 asap
Tom7777 ·
I didnt steal anyting, only the waveforms are left now, rest is original no trouble about some standard waveforms
Well i don't think you stole anything exactly but it is simple enough to see that you have used fruity loops as a template in your graphics app and as Sk0re says people will immediately recognize this, its best to make you GUIs original and not do this as it could lead to problems for you if you release the plugin.
Jenovah ·
nope no release, just personal use
Wrote something here? To have a post removed or your name hidden, write to [email protected].