XHip--Please finish your synth!!
- KVRAF
- 12615 posts since 7 Dec, 2004
i probably wont mind exactly how they're written - probably i can get you set up with mingw and the source and you can build the gui directly yourself. i'll probably have to help quite a lot, but when tweaking things we can maybe work together rather than you simply writing up the numbers and then me trying to figure out how to fit everything the way you wanted it.
i'll actually put together the gui parts of the source into a small project with a makefile and i'll upload it so everybody can play with it.
i'll actually put together the gui parts of the source into a small project with a makefile and i'll upload it so everybody can play with it.
-
- KVRist
- 499 posts since 9 Oct, 2005
Nice work gsoto... maybe a bit hard on the eyes, but very nice he he.gsoto wrote:Sure:disturb wrote:did i hear anyone say 'sneak peak' ?
I had to resize it a bit, hope you don't mind.
- KVRAF
- 12615 posts since 7 Dec, 2004
it is quite similar to his previous design, but i think the arrangement at this point is a good bit easier to look at and follow when you're editing parameters.
there are still a couple significant issues to work out that i noticed, and maybe a few he knows about himself that i didnt.
i think it would be bad to post any example images until we've got some amount of code working since people will definite complain about "why isnt the color-scheme X" or "why doesnt it have background image Y". those sorts of things will be user-configurable using the cc configuration files i've already designed. we want to avoid complainers who push the thread off-topic about how they want the gui to have a fluffy-pink-clouds color scheme or whatever, and completely ignore what i tell them about "you can configure that".
anyway next thing on the list is going to be event routing since i'm not making progress on the new patch format. i need to store the event routing stuff in the patches anyway so it might be best to design it later.
rearranged the to-do, http://xhip.cjb.net/xhip/todo/
there are still a couple significant issues to work out that i noticed, and maybe a few he knows about himself that i didnt.
i think it would be bad to post any example images until we've got some amount of code working since people will definite complain about "why isnt the color-scheme X" or "why doesnt it have background image Y". those sorts of things will be user-configurable using the cc configuration files i've already designed. we want to avoid complainers who push the thread off-topic about how they want the gui to have a fluffy-pink-clouds color scheme or whatever, and completely ignore what i tell them about "you can configure that".
anyway next thing on the list is going to be event routing since i'm not making progress on the new patch format. i need to store the event routing stuff in the patches anyway so it might be best to design it later.
rearranged the to-do, http://xhip.cjb.net/xhip/todo/
-
- KVRian
- 930 posts since 21 Mar, 2006
Talking about colour-scheme's how easy will it be to change these? You mentioned the configuration files, but will the colours be bitmap-driven or set in config files as well?

- KVRAF
- 12615 posts since 7 Dec, 2004
they're all set in config files - everything is. everything.
to be honest, everything "can be". not everything "will be" initially. it is just that for anybody who wants anything to be different apart from the main configuration of the layout (where the controls are) everything about it will be configurable. you should even be able to replace gsoto's sliders with knobs if you really want that. you can replace the background with a photo. you can change any of the text or replace the text with photos. if anything needs to be changed, it can be changed, so it isnt a concern to be discussed at this point in time.
sorry i'm being so defensive, it's just i'm sure you've seen where this goes in previous parts of the threads
as for the color scheme, that is already possible to change in the gui i wrote and if anybody expressed some interest in it and desire to manipulate other properties of the elements on the gui i could add that stuff without much effort.
currently you can load files named .ini which are actually plain text files. they function similar to css files, i call them "cc" (control class) files. they're basically text based registry database files, just like the windows registry. my implementation of them at this point has been very simple with only numbers, but with minimal effort i can allow them to contain strings or other data-types like colors in hls or other formats.
press the "load class" button on xhip's control page and load any of these files (available on the releases page http://xhip.cjb.net/xhip/releases/ ):
http://xhip.cjb.net/xhip/releases/xhip_gui_blue.ini
http://xhip.cjb.net/xhip/releases/xhip_gui_kvr.ini
http://xhip.cjb.net/xhip/releases/xhip_gui_red.ini
this gives only a very small example of the amount of configuration you can do. try editing them - there shouldnt be any way to crash xhip with them, invalid files should simply not load.
to be honest, everything "can be". not everything "will be" initially. it is just that for anybody who wants anything to be different apart from the main configuration of the layout (where the controls are) everything about it will be configurable. you should even be able to replace gsoto's sliders with knobs if you really want that. you can replace the background with a photo. you can change any of the text or replace the text with photos. if anything needs to be changed, it can be changed, so it isnt a concern to be discussed at this point in time.
sorry i'm being so defensive, it's just i'm sure you've seen where this goes in previous parts of the threads
as for the color scheme, that is already possible to change in the gui i wrote and if anybody expressed some interest in it and desire to manipulate other properties of the elements on the gui i could add that stuff without much effort.
currently you can load files named .ini which are actually plain text files. they function similar to css files, i call them "cc" (control class) files. they're basically text based registry database files, just like the windows registry. my implementation of them at this point has been very simple with only numbers, but with minimal effort i can allow them to contain strings or other data-types like colors in hls or other formats.
press the "load class" button on xhip's control page and load any of these files (available on the releases page http://xhip.cjb.net/xhip/releases/ ):
http://xhip.cjb.net/xhip/releases/xhip_gui_blue.ini
http://xhip.cjb.net/xhip/releases/xhip_gui_kvr.ini
http://xhip.cjb.net/xhip/releases/xhip_gui_red.ini
this gives only a very small example of the amount of configuration you can do. try editing them - there shouldnt be any way to crash xhip with them, invalid files should simply not load.
-
- KVRAF
- 1958 posts since 16 Jan, 2005 from France's Dirty South
hmm that's embarassing...aciddose wrote:can you find which version that starts to occur with?
i tired all most all version starting from 12.7 and they all worked fine up to 14.5, so i thought it was just the latest one, but now it loads fine, what the hell...
probably just a hicup with my pc
- KVRAF
- 12615 posts since 7 Dec, 2004
no problem - just always make sure to try the latest version and if you find a "new" bug, try older versions until you find where the bug was introduced. that'll help me _a lot_ to fix it since i can check through my logs of exactly what changes i made between the versions.
i'm much more happy to hear the bug was imaginary in the end though
i'm much more happy to hear the bug was imaginary in the end though
-
- KVRian
- 889 posts since 10 Jul, 2004
aciddose u said earlier that the reskinnin tool by asseca wouldn't really work with xhip.
but he tried and thougt that was possible
more info here
http://www.kvraudio.com/forum/viewtopic.php?t=149319
but he tried and thougt that was possible
more info here
http://www.kvraudio.com/forum/viewtopic.php?t=149319
- KVRAF
- 2910 posts since 26 Jul, 2005 from dun unda
It'd work, but there are possibilities that the wrapper may miss certain elements present in the GUI that's already there in plain bar colour and text, if not capable to conflicting options that are meant to be disabled when a certain option is enabled etc.
Anyway, I'm comfortable with the boxed XHip at the moment, however it's not a very good way to work with when making sounds hence the coming GUI.
Anyway, I'm comfortable with the boxed XHip at the moment, however it's not a very good way to work with when making sounds hence the coming GUI.

