not bad...tidier,
knobs need to be a little bigger to be usable on portable systems.(umpcs)
also please add the delay to the envelopes...no point locking the features just yet.
XHip--Please finish your synth!!
-
- KVRian
- 889 posts since 10 Jul, 2004
-
- KVRAF
- 12615 posts since 7 Dec, 2004
features are locked, i can't really add delay to the envelopes.
http://xhip.cjb.net/temp/public/doooo.png
did a little bit of work to get "scripted" knobs. now i can set up each to draw several layers (as many as i want) to get the different colors and lighting/shadow.
the gui code only works on windows because it uses a callback and it's mostly tied into vst at this point. (it uses the vst windows callback "idle()")
there is no point in the gui being portable since xhip isnt portable.
it's 100% my own code. you should check the main source i linked before, and http://xhip.cjb.net/xhip/xgdb/
(in order for the library to be portable, idle must be replaced with something and windowing/graphics interface modules must be written. i have modules for xlib which work "ok", but in order to eliminate the idle call new controls must be written with direct message handling rather than callback style focus lock. i've already compiled xhip on xlib and it works fine, it just really shouldn't use the callback method on xlib or on macos...)
http://xhip.cjb.net/temp/public/doooo.png
did a little bit of work to get "scripted" knobs. now i can set up each to draw several layers (as many as i want) to get the different colors and lighting/shadow.
the gui code only works on windows because it uses a callback and it's mostly tied into vst at this point. (it uses the vst windows callback "idle()")
there is no point in the gui being portable since xhip isnt portable.
it's 100% my own code. you should check the main source i linked before, and http://xhip.cjb.net/xhip/xgdb/
(in order for the library to be portable, idle must be replaced with something and windowing/graphics interface modules must be written. i have modules for xlib which work "ok", but in order to eliminate the idle call new controls must be written with direct message handling rather than callback style focus lock. i've already compiled xhip on xlib and it works fine, it just really shouldn't use the callback method on xlib or on macos...)
-
- KVRian
- 889 posts since 10 Jul, 2004
i meant portable as in moility.
hand held pcs ,netbooks etc....
7-8-9 inch screens.
on such small screens such small knobs are unusable.
hand held pcs ,netbooks etc....
7-8-9 inch screens.
on such small screens such small knobs are unusable.
-
- KVRAF
- 12615 posts since 7 Dec, 2004
i was replying to Kyran regarding portability.
on such small screens the gui doesn't even fit either, so there is no point in using it at all. for bigger knobs you'd need a bigger screen since this one already takes up the whole screen in 1024x768. i wont make the gui larger than that, i will not make any gui larger than that. the source is available if somebody else wants to.
for a very small screen it's advisable to use something like the paged gui, or the even smaller dx-7 style "gen" gui. i could write a special gui for very small screens if you can come up with some examples of what would work best there. just remember there are 108 controls to fit on the gui so if the knobs are 64x64, the gui must be at minimum 768x576 which is just rediculous. that's why the knobs are currently 32x32. (once you add labels and groups and other stuff it takes a lot more space.. having the knobs forced together with no space, labels or graphics looks horrible!)
none of my designs will ever be compromised now, there is a very good reason that i wrote the code required to make the guis modules. any request for a modification can now create a branch, or additionally i can tell the person to branch it themselves.
after version 1.0 of xhip it will be posted, open source, perhaps GPL. modifications to the synthesizer itself can also become branches at that point, modifications like envelope delay.
it's possible to branch the synth immediately - but you won't be able to take advantage of updates and none of the current patches will load anymore on that special version. you or somebody else will also have to manage the branch themselves.
the synth has been locked for more than six months now so unfortunately nothing in the synth itself is changing until after the 1.0 release.
on such small screens the gui doesn't even fit either, so there is no point in using it at all. for bigger knobs you'd need a bigger screen since this one already takes up the whole screen in 1024x768. i wont make the gui larger than that, i will not make any gui larger than that. the source is available if somebody else wants to.
for a very small screen it's advisable to use something like the paged gui, or the even smaller dx-7 style "gen" gui. i could write a special gui for very small screens if you can come up with some examples of what would work best there. just remember there are 108 controls to fit on the gui so if the knobs are 64x64, the gui must be at minimum 768x576 which is just rediculous. that's why the knobs are currently 32x32. (once you add labels and groups and other stuff it takes a lot more space.. having the knobs forced together with no space, labels or graphics looks horrible!)
none of my designs will ever be compromised now, there is a very good reason that i wrote the code required to make the guis modules. any request for a modification can now create a branch, or additionally i can tell the person to branch it themselves.
after version 1.0 of xhip it will be posted, open source, perhaps GPL. modifications to the synthesizer itself can also become branches at that point, modifications like envelope delay.
it's possible to branch the synth immediately - but you won't be able to take advantage of updates and none of the current patches will load anymore on that special version. you or somebody else will also have to manage the branch themselves.
the synth has been locked for more than six months now so unfortunately nothing in the synth itself is changing until after the 1.0 release.
-
- KVRAF
- 12615 posts since 7 Dec, 2004
-
- KVRAF
- 7170 posts since 19 Apr, 2002 from Utah
It's looking better and better all of the time! I wish I knew how to do gui work, because I have lots of ideas I'd like to do. For example, I'd like to make the ADSR stuff vertical sliders. I'd also rather there be a brushed metal background than a psychedelic LSD induced acid trip background. 
It's just my opinion, but I really think your synth will benefit from a combination of both knobs and sliders. Either way, it is really looking cool!
Thanks for continuing your work on the GUI!!!!
--Sean
It's just my opinion, but I really think your synth will benefit from a combination of both knobs and sliders. Either way, it is really looking cool!
Thanks for continuing your work on the GUI!!!!
--Sean
-
- KVRAF
- 7170 posts since 19 Apr, 2002 from Utah
I feel the same way! A good looking GUI to go along with a good sounding synth makes for a lot of fun!!!aciddose wrote:http://xhip.cjb.net/temp/public/sphnkmaster.mp3
ok, i definitely know for certain that a gui influences your perception of a soft synth. this is absolutely no different from using any of the other guis, but the synth seems to sound for some reason specially awesome just because there are funny little knobs on the screen. even i fall for this, the author of the synth, and i know for a fact the synth hasn't changed in the slightest other than the gui.
damn you, funny little knob devils!
Thanks for keeping up the work on the GUI!!!!!
--Sean
-
- KVRAF
- 12615 posts since 7 Dec, 2004
give me a brushed metal texture, the code can load bmps and jpgs. i was generating a brushed metal texture before also, i'm just generating something at the moment to fill the space.
when you say brushed metal do you mean like this? i can just use this texture generator if you like this one:
(this is my simple drawn knob control)
as for sliders, i'm working on that. i just need to improve the slider control to support vertical as well as horizontal alignment, then i can create a bitmap based control in addition to the current drawn version and use better looking handles and slides for them. i can then do some switches that way, and i'll probably want to implement a rocker-switch control too.
just wanting to play with shadows and stuff now actually, nothing fancy just faked shadows that don't move.
when you say brushed metal do you mean like this? i can just use this texture generator if you like this one:
(this is my simple drawn knob control)
as for sliders, i'm working on that. i just need to improve the slider control to support vertical as well as horizontal alignment, then i can create a bitmap based control in addition to the current drawn version and use better looking handles and slides for them. i can then do some switches that way, and i'll probably want to implement a rocker-switch control too.
just wanting to play with shadows and stuff now actually, nothing fancy just faked shadows that don't move.
-
- KVRAF
- 5375 posts since 22 Jul, 2006 from Tasmania, Australia
Hey AcidDose,
If you are using knobstrips then you can have moving shadows if draw them in KnobMan?
Much appreciate your ongoing work, nix
If you are using knobstrips then you can have moving shadows if draw them in KnobMan?
Much appreciate your ongoing work, nix
I wonder what I want in here
-my site is gone and music a mess
-my site is gone and music a mess
-
- KVRAF
- 7170 posts since 19 Apr, 2002 from Utah
Yeah, I like that! I like the "realistic" look. I'll look around for some GUI examples to show you what I am talking about.aciddose wrote:give me a brushed metal texture, the code can load bmps and jpgs. i was generating a brushed metal texture before also, i'm just generating something at the moment to fill the space.
when you say brushed metal do you mean like this? i can just use this texture generator if you like this one:
(this is my simple drawn knob control)
as for sliders, i'm working on that. i just need to improve the slider control to support vertical as well as horizontal alignment, then i can create a bitmap based control in addition to the current drawn version and use better looking handles and slides for them. i can then do some switches that way, and i'll probably want to implement a rocker-switch control too.
just wanting to play with shadows and stuff now actually, nothing fancy just faked shadows that don't move.
Thanks again!!!
--Sean
-
- KVRAF
- 12615 posts since 7 Dec, 2004
having 100s of bitmaps is just bloody annoying, that's all. if i really wanted realistic shadows i could do real rendered shadows from 3d objects.. i think for now i'll not worry about that sort of thing. currently only a single bitmap is used and any rotation takes place in code, in real time. it's called a rotozoom blitter.
(also, if you didn't realize, i hate sprite strips)
http://xhip.cjb.net/temp/public/one3.png
http://xhip.cjb.net/temp/public/one3.xhipgui
does this meet your needs for brushed metal, or do i need to make it vertical
(also, if you didn't realize, i hate sprite strips)
http://xhip.cjb.net/temp/public/one3.png
http://xhip.cjb.net/temp/public/one3.xhipgui
does this meet your needs for brushed metal, or do i need to make it vertical
-
- KVRAF
- 7170 posts since 19 Apr, 2002 from Utah
-
- KVRAF
- 7170 posts since 19 Apr, 2002 from Utah
Oh this just keeps getting better and better!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!aciddose wrote:having 100s of bitmaps is just bloody annoying, that's all. if i really wanted realistic shadows i could do real rendered shadows from 3d objects.. i think for now i'll not worry about that sort of thing. currently only a single bitmap is used and any rotation takes place in code, in real time. it's called a rotozoom blitter.
(also, if you didn't realize, i hate sprite strips)
http://xhip.cjb.net/temp/public/one3.png
http://xhip.cjb.net/temp/public/one3.xhipgui
does this meet your needs for brushed metal, or do i need to make it vertical
GREAT JOB!!!!
--Sean
P.S. I'll keep looking for samples of things, so that you can see some of the things I like.
-
- KVRAF
- 7170 posts since 19 Apr, 2002 from Utah
Also, I like the layout of synth1 http://www.kvraudio.com/get/214.html
Let me explain what I mean...
I always think of the Oscillators starting in the upper left corner of the GUI and then the amplifier and then filter etc, working on down until the play mode or output stuff is in the lower right. Maybe I'm not explaining myself too well. I'll look for another example to better explain myself.
--Sean
Let me explain what I mean...
I always think of the Oscillators starting in the upper left corner of the GUI and then the amplifier and then filter etc, working on down until the play mode or output stuff is in the lower right. Maybe I'm not explaining myself too well. I'll look for another example to better explain myself.
--Sean
-
- KVRAF
- 12615 posts since 7 Dec, 2004
i know what you mean, i just think that's totally wrong. if you want to use left-to-right and top-to-bottom order, you start at the cv/gate, then the routing and modulators, then oscillators and on through the signal path. i'd put the "output" after the waveshaper if it would fit on the screen. really though it can be arranged in any way you like, the only problem being that the output is 4 tall while the bottom row modules are 3 tall, they don't mix.
http://xhip.cjb.net/temp/public/one4.png
http://xhip.cjb.net/temp/public/one4.xhipgui
http://xhip.cjb.net/temp/public/one4.png
http://xhip.cjb.net/temp/public/one4.xhipgui