XHip--Please finish your synth!!
-
- KVRAF
- 8519 posts since 7 Apr, 2003
aciddose; i checked all the samples. pretty nice stuff. so what is next step? flat mockups? schematic layouts?
- KVRAF
- 12615 posts since 7 Dec, 2004
anything you want, to be honest i dont have much idea. if it were me, i'd start by looknig at the parameters and grouping them in a fashion i can handle.
http://xhip.cjb.net/temp/public/param.exe
unfortunately there isnt any really practical way to print all the possible settings for each parameter. i should really make improvements to the systems so there is information available about parameter type (range, switch, etc) to allow this.
to use that, try:
param > param.txt
which will give you this (here, let xhip squirt you a readout of it's parameters):
http://xhip.cjb.net/temp/public/param.txt
(that was a balmer reference)
you can specify a patch to load if you like, [param mypatch.adxi]. i think it works correctly.
next i'd probably want to think about a combination of what types of widgets to use so that we can get to work togeather on designing them, and the basic layout. it is very easy for me to implement stuff thanks to the highly developed systems i have, so it is no problem to go back and fourth making changes and testing the designs. it is even possible to use the registry-type format i discribed before to let you position controls on the gui, although to do that i'd have to set up the whole thing anyway so it is nearly as quick to write the code directly.
every element on the gui exists within local coordinates. if you have the full window, the top left of the window will be [0,0]. if you insert a region (a plain background/container element) at [64,82], any elements you then add into that region will be at an offset of [64,82].
so, this lets you do things like: offset((container.width + object.width)/2, (container.height + object.height)/2) in order to center the widget in the container. most importantly, it lets you design each section of the gui seperately. if you put all your widgets in a region element for some part of the gui, the stuff in that region then doesnt need to know anything about where the region is located. the widgets inside the region just start from [0,0].
http://xhip.cjb.net/temp/public/param.exe
unfortunately there isnt any really practical way to print all the possible settings for each parameter. i should really make improvements to the systems so there is information available about parameter type (range, switch, etc) to allow this.
to use that, try:
param > param.txt
which will give you this (here, let xhip squirt you a readout of it's parameters):
http://xhip.cjb.net/temp/public/param.txt
(that was a balmer reference)
you can specify a patch to load if you like, [param mypatch.adxi]. i think it works correctly.
next i'd probably want to think about a combination of what types of widgets to use so that we can get to work togeather on designing them, and the basic layout. it is very easy for me to implement stuff thanks to the highly developed systems i have, so it is no problem to go back and fourth making changes and testing the designs. it is even possible to use the registry-type format i discribed before to let you position controls on the gui, although to do that i'd have to set up the whole thing anyway so it is nearly as quick to write the code directly.
every element on the gui exists within local coordinates. if you have the full window, the top left of the window will be [0,0]. if you insert a region (a plain background/container element) at [64,82], any elements you then add into that region will be at an offset of [64,82].
so, this lets you do things like: offset((container.width + object.width)/2, (container.height + object.height)/2) in order to center the widget in the container. most importantly, it lets you design each section of the gui seperately. if you put all your widgets in a region element for some part of the gui, the stuff in that region then doesnt need to know anything about where the region is located. the widgets inside the region just start from [0,0].
-
- KVRAF
- 8519 posts since 7 Apr, 2003
aciddose; i'll start some mocks this weekend.
going to do schematics first to group like you say. sound scool man, i'm excited to work with you. should i start a new thread or just post the stuff in here?
going to do schematics first to group like you say. sound scool man, i'm excited to work with you. should i start a new thread or just post the stuff in here?
- KVRAF
- 6478 posts since 16 Dec, 2002
-7! (me and my 6 other personalities)funkadil wrote:+1 to keep using horizontal sliders!
go for the knobs. takes a whole lot less space, allow control with any axis (to be selectable from a menu says aciddose). as a continuation of tradition (if for no other reason), it would be nice to see vertical ENV knob configuration.
dear mr. grymmjack, I would also vote for one-page GUI, initially, with only setup/options hidden outside it.
Somebody please dig out the initial Gsoto GUI mockups from the old thread. They had *very* nice and clean, if even unique thing going on.
-
afreshcupofjoe afreshcupofjoe https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=94815
- KVRAF
- 1838 posts since 17 Jan, 2006 from Portland, OR
Wow! This is going to be fantastic. I can't wait.
+1 for knobs, they take up WAY less space and the entire GUI could probably fit on one page if knobs were used instead of sliders, although I love the knob/vertical slider thing, like the implementation in synth1.
+1 for knobs, they take up WAY less space and the entire GUI could probably fit on one page if knobs were used instead of sliders, although I love the knob/vertical slider thing, like the implementation in synth1.
"The Juno 60 was often incorrectly referred to as a synth. It is, in fact, a chorus unit with a synth attached." -PAK
- KVRAF
- 6478 posts since 16 Dec, 2002
Also aciddose, here's a good ergonomics tip,
That way you can easily set arbitrary mouse sensitivity and the cursor won't bother on screen. If you want to take it further (just for the visual gimmick), display the 'hand' cursor while mouseover (and not mousedown).
Then again, you knew this already. Just wanted to contribute *something*.
Code: Select all
//on your mousedown() with a knob/fader/slider/numeric control
SetCursor (LoadCursor (0, NULL));//platform dependant obviously
//your mousedelta to parameter controls here
//depending on your control code, windows might release the cursor on mouse up
//other wise load the normal cursor here
Then again, you knew this already. Just wanted to contribute *something*.
-
- KVRAF
- 3928 posts since 23 Oct, 2005 from vassalboro, maine
and soon xhip will destroy mankind.grymmjack wrote:aciddose; i'll start some mocks this weekend.
going to do schematics first to group like you say. sound scool man, i'm excited to work with you. should i start a new thread or just post the stuff in here?
-
- KVRAF
- 2029 posts since 21 Jul, 2004
Knobs just dont seem "precise" to me. They are good for some things but on computers I prefer slider because you can sort of "see" the whole possibility for that values at one place. for me it is position along an axis vs. some measure of angle. I do prefer vertical slider for the envelopes though. Cutoff and Res I prefer horizontal. Anyways, I cannot wait to release a huge preset bank once we are in the release era. I don't mind knobs though and they are great for space keeping.
Do not lick the fablanky
-
- KVRAF
- 10815 posts since 26 Nov, 2004 from UK
i think it should have a new thread like the Oatmeal skin!
it was lots of fun watching that grow,
i think it deserves its own thread,
I'm very excited, & i trust grymm will come up with the perfect layout
Subz
it was lots of fun watching that grow,
i think it deserves its own thread,
I'm very excited, & i trust grymm will come up with the perfect layout
Subz
-
- KVRAF
- 8519 posts since 7 Apr, 2003
wow no pressure huh guys? 
thanks for your confidence. it should be a fun ride. i think this may be more fun because aciddose actually is present and able to craft stuff in code that we envision collectively. one thing about the pots and precision -- we could do an overlay on drag like synth1, i really love that about it. i love how mousewheel adjusts the controls too. i'm sure whatever happens it should be fun and interesting!
thanks for your confidence. it should be a fun ride. i think this may be more fun because aciddose actually is present and able to craft stuff in code that we envision collectively. one thing about the pots and precision -- we could do an overlay on drag like synth1, i really love that about it. i love how mousewheel adjusts the controls too. i'm sure whatever happens it should be fun and interesting!
- KVRAF
- 9590 posts since 17 Sep, 2002 from Gothenburg Sweden
That is about the one thing i really hate with Synth1.grymmjack wrote:we could do an overlay on drag like synth1, i really love that about it.
I can't stand that overlay thingie.Please reconsider.
-
- KVRAF
- 5703 posts since 6 Dec, 2003 from Mission Control
Oh Boy! Oh Boy! Oh Boy!grymmjack wrote:wow no pressure huh guys?
thanks for your confidence. it should be a fun ride. i think this may be more fun because aciddose actually is present and able to craft stuff in code that we envision collectively. one thing about the pots and precision -- we could do an overlay on drag like synth1, i really love that about it. i love how mousewheel adjusts the controls too. i'm sure whatever happens it should be fun and interesting!
- Let It Whip -
My Site, Music and Free EFM Plugins
My Site, Music and Free EFM Plugins
-
- KVRAF
- 6241 posts since 26 Sep, 2003 from right here, as you can see ...
on your side completely with this ...Kingston wrote:-7! (me and my 6 other personalities)funkadil wrote:+1 to keep using horizontal sliders!
go for the knobs. takes a whole lot less space, allow control with any axis (to be selectable from a menu says aciddose). as a continuation of tradition (if for no other reason), it would be nice to see vertical ENV knob configuration.
dear mr. grymmjack, I would also vote for one-page GUI, initially, with only setup/options hidden outside it.
knobs prefered, and one sited gui ...
however, in general i feel safe if grym is on the gui thing, as he usually just does great stuff ...
can't wait to see results ...
grym, as soon you got something, post a screenie please ...
regards,
brok landers
BIGTONEsounddesign
gear is as good as the innovation behind it-the man
brok landers
BIGTONEsounddesign
gear is as good as the innovation behind it-the man
-
- KVRAF
- 6241 posts since 26 Sep, 2003 from right here, as you can see ...
it's getting better and better ...grymmjack wrote: one thing about the pots and precision -- we could do an overlay on drag like synth1, i really love that about it. i love how mousewheel adjusts the controls too. i'm sure whatever happens it should be fun and interesting!
grym, that would be just too cool ... i absolutely love the way synth1 handles the parameters ... gogogo ...
but make ti switchable ...
@jupiter8: you can turn that off in the options of synth1 ...
regards,
brok landers
BIGTONEsounddesign
gear is as good as the innovation behind it-the man
brok landers
BIGTONEsounddesign
gear is as good as the innovation behind it-the man
