XHip--Please finish your synth!!
-
- KVRist
- 499 posts since 9 Oct, 2005
Intimidating is the word. Is anyone working on a bank of presets ? I usually find it easier to start from presets, modify them till they sound way different, learning the effect on the sound each control has all the while (which is not always that easy to decypher)
-
- KVRian
- 511 posts since 8 Dec, 2004 from Belgrade
Aren't there presets already in the current version?
-
- KVRAF
- 12615 posts since 7 Dec, 2004
old default bank in here: http://xhip.cjb.net/xhip/releases/0/6/1 ... 6.16.1.zip
also here: http://xhip.cjb.net/xhip/releases/0/6/1 ... fault.adxb
i was actually just working on updating the bank, i filled out the patches past the "sound fx" part so keep going, it has all 128 now and i've "fixed" most of the older ones that were in there. anybody can feel free to start making patches - they just don't save pcms or event routing or other information yet. the patch format is stable.
this one just needs to be organized better, maybe we should do several banks like one for leads, one for basses and so on. this needs patch names as well! i've already named most of the patches i just keep them in individual files, thus the names are the filenames and i haven't bothered to save the names into the patches themselves.
(the patch stuff is just an excuse not to be working on the event routing stuff since i'm not quite done thinking about how to go about it, yet)
also here: http://xhip.cjb.net/xhip/releases/0/6/1 ... fault.adxb
i was actually just working on updating the bank, i filled out the patches past the "sound fx" part so keep going, it has all 128 now and i've "fixed" most of the older ones that were in there. anybody can feel free to start making patches - they just don't save pcms or event routing or other information yet. the patch format is stable.
this one just needs to be organized better, maybe we should do several banks like one for leads, one for basses and so on. this needs patch names as well! i've already named most of the patches i just keep them in individual files, thus the names are the filenames and i haven't bothered to save the names into the patches themselves.
(the patch stuff is just an excuse not to be working on the event routing stuff since i'm not quite done thinking about how to go about it, yet)
-
- KVRAF
- 12615 posts since 7 Dec, 2004
http://xhip.cjb.net/xhip/releases/0/6/1 ... 6.16.2.zip
updated the default bank. it's still a mess and some of those patches really suck, but it's better than the old one.
fixed some significant errors in the code where modulator depths would be loaded incorrectly. some older patches may not work anymore.. the ones from a long, long time ago, maybe from any time before this time last year when i said the patch format had become stable. unfortunately at that time i forgot to increment the version for the patch files, so i can't apply the modulation depth corrections selectively. older patches had A/B, the new version has independent A and B depths. you can obviously convert older patches using a previous version if you need to do that.
as usual though this shouldn't actually affect anyone. i'm just pessimistic about these things.
updated the default bank. it's still a mess and some of those patches really suck, but it's better than the old one.
fixed some significant errors in the code where modulator depths would be loaded incorrectly. some older patches may not work anymore.. the ones from a long, long time ago, maybe from any time before this time last year when i said the patch format had become stable. unfortunately at that time i forgot to increment the version for the patch files, so i can't apply the modulation depth corrections selectively. older patches had A/B, the new version has independent A and B depths. you can obviously convert older patches using a previous version if you need to do that.
as usual though this shouldn't actually affect anyone. i'm just pessimistic about these things.
-
- KVRAF
- 12615 posts since 7 Dec, 2004
http://xhip.cjb.net/temp/public/prvplsxhipnewbank0.mp3
just testing to make sure everything is working ok - the patch "sound of silence" is actually out of tune, i didn't notice that before. obviously the bank needs some more work but i'll put that off until the next bits are done on the todo list: http://xhip.cjb.net/xhip/todo/
just testing to make sure everything is working ok - the patch "sound of silence" is actually out of tune, i didn't notice that before. obviously the bank needs some more work but i'll put that off until the next bits are done on the todo list: http://xhip.cjb.net/xhip/todo/
-
- KVRian
- 651 posts since 19 Nov, 2006
Some nice sounds there and I like the new gui (had small_gui before).
Is it possible to make ambient spaced out sounds? Stuff designed to just right back in the mix? I couldn't find anything suitable in the bank.
Is it possible to make ambient spaced out sounds? Stuff designed to just right back in the mix? I couldn't find anything suitable in the bank.
-
- KVRAF
- 12615 posts since 7 Dec, 2004
it's possible to make any sound a two osc, two adsr, two lfo, two filter, waveshaper synth with ringmod, sync, xmod (several types), and a heap of other features can do. you can easily do weird little frog sounds if you know what you're doing. don't forget to use external modulation as well. (don't depend upon the synth to sequence a one-note bird song patch.. actually play the bird song melody and just patch the different types of chirping.)
-
- KVRian
- 773 posts since 23 Apr, 2002 from audio/hamburg/germany/earth/space/unkown!
hey aciddose.
i'd be in to make a single paged GUI (for my self in the first place), if it is what i'm thinking, and it has to be "coded" into a dll !?.
i would just use more or less ugly placeholder graphics at the beginning, i just want to pull all (or almost) controls on one page, as xhip (as goog as it sounds) kills my workflow as it is right now.
i'd start right now! (only if the implementation style fits me at least a bit though)
peace
D3CK
p.s.: is (or why isn't) xhip wrapped in some kind of dashboard plug in already btw.?
i'd be in to make a single paged GUI (for my self in the first place), if it is what i'm thinking, and it has to be "coded" into a dll !?.
i would just use more or less ugly placeholder graphics at the beginning, i just want to pull all (or almost) controls on one page, as xhip (as goog as it sounds) kills my workflow as it is right now.
i'd start right now! (only if the implementation style fits me at least a bit though)
peace
D3CK
p.s.: is (or why isn't) xhip wrapped in some kind of dashboard plug in already btw.?
-
- KVRian
- 651 posts since 19 Nov, 2006
Ok cool. Im just not much of a sound designer. If someone has some cool ambient patches let me know!aciddose wrote:it's possible to make any sound a two osc, two adsr, two lfo, two filter, waveshaper synth with ringmod, sync, xmod (several types), and a heap of other features can do. you can easily do weird little frog sounds if you know what you're doing. don't forget to use external modulation as well. (don't depend upon the synth to sequence a one-note bird song patch.. actually play the bird song melody and just patch the different types of chirping.)
-
- KVRian
- 753 posts since 15 Mar, 2002
please !!!
Ive been following this since the beginning, and while xhip sound is killer, its absolutely unusable as is, to me.
A single page skin (dont need real art here, just usable stuff) would increase interest in this synth by a 100 factor, i'm sure !!!
thanks
Ive been following this since the beginning, and while xhip sound is killer, its absolutely unusable as is, to me.
A single page skin (dont need real art here, just usable stuff) would increase interest in this synth by a 100 factor, i'm sure !!!
thanks
dasdeck wrote:hey aciddose.
i'd be in to make a single paged GUI (for my self in the first place), if it is what i'm thinking, and it has to be "coded" into a dll !?.
i would just use more or less ugly placeholder graphics at the beginning, i just want to pull all (or almost) controls on one page, as xhip (as goog as it sounds) kills my workflow as it is right now.
i'd start right now! (only if the implementation style fits me at least a bit though)
peace
D3CK
p.s.: is (or why isn't) xhip wrapped in some kind of dashboard plug in already btw.?
-
- KVRAF
- 12615 posts since 7 Dec, 2004
the code is available. start designing it, i'll give you some help with how to get to work on the code. download mingw, preferably since it's waay easier to use than microsoft's junk (i've already written the makefiles for you, so you just type 'make') and get your thoughts together about the design and i'll get you the code.
see my msn messenger account on my kvr "profile" if you want to get in touch in real-time, or we can chat via messages or email. it's up to you.
there are already single-page guis that i've written.. here is an example:
http://xhip.cjb.net/xhip/releases/0/6/1 ... .14.8b.dll <-- all-on-a-page with sliders
http://xhip.cjb.net/xhip/releases/0/6/1 ... .14.8c.dll <-- dx-7 style
http://xhip.cjb.net/xhip/releases/0/6/1 ... .14.8d.dll <-- large
notice that the number of controls on the all-on-one-page gui is so large that if you include text it's extremely difficult to fit all the controls. that example is using the smallest type of control, a slider, with the smallest possible text labels. if you really want to design a good gui for xhip on one page you'd better take these examples into consideration.
http://xhip.cjb.net/temp/public/gsoto_g ... _1dark.png
gsoto's gui is a good design on one page - mostly everything for the synth is on the one page. it still needs extra pages for the other configuration bits and future features like event routing, pcm editing and so on.
it's possible for you to write a gui completely seperate from xhip, you can use any code you like (vstgui, whatever) and it'll tie in dynamically. this means you can write your gui and have it load on any version of xhip with a compatible vendrospecific() interface. that interface is changing over time, so you have to keep in mind also that you'll need to make small changes or at least recompile your gui.
if you use my code for your gui, my gui library or graphics code and so on i require that you release all source to me, bsd-style at minimum. if you write your own, you can sell the thing if you want.
see my msn messenger account on my kvr "profile" if you want to get in touch in real-time, or we can chat via messages or email. it's up to you.
there are already single-page guis that i've written.. here is an example:
http://xhip.cjb.net/xhip/releases/0/6/1 ... .14.8b.dll <-- all-on-a-page with sliders
http://xhip.cjb.net/xhip/releases/0/6/1 ... .14.8c.dll <-- dx-7 style
http://xhip.cjb.net/xhip/releases/0/6/1 ... .14.8d.dll <-- large
notice that the number of controls on the all-on-one-page gui is so large that if you include text it's extremely difficult to fit all the controls. that example is using the smallest type of control, a slider, with the smallest possible text labels. if you really want to design a good gui for xhip on one page you'd better take these examples into consideration.
http://xhip.cjb.net/temp/public/gsoto_g ... _1dark.png
gsoto's gui is a good design on one page - mostly everything for the synth is on the one page. it still needs extra pages for the other configuration bits and future features like event routing, pcm editing and so on.
it's possible for you to write a gui completely seperate from xhip, you can use any code you like (vstgui, whatever) and it'll tie in dynamically. this means you can write your gui and have it load on any version of xhip with a compatible vendrospecific() interface. that interface is changing over time, so you have to keep in mind also that you'll need to make small changes or at least recompile your gui.
if you use my code for your gui, my gui library or graphics code and so on i require that you release all source to me, bsd-style at minimum. if you write your own, you can sell the thing if you want.
-
- KVRAF
- 12615 posts since 7 Dec, 2004
here is a useful example for you to read to help you understand what is involved in writing a gui, if you use my libraries/code:
http://xhip.cjb.net/temp/public/editor_standard.cpp
this is the current code for the default gui, as released with [0.6.16.2].
http://xhip.cjb.net/temp/public/editor_standard.cpp
this is the current code for the default gui, as released with [0.6.16.2].
-
- KVRian
- 773 posts since 23 Apr, 2002 from audio/hamburg/germany/earth/space/unkown!
kind of more info than needed, thanks, so i could use JUCE for example?aciddose wrote:....you can sell the thing if you want.
how does this vendrospecific() interface look like (i have no idea to be hones
)?i knew the gsoto gui and had something similar in mind
(btw. the link does not work)D3CK
edit: on request.
Last edited by dasdeck on Sat Jun 28, 2008 10:40 am, edited 1 time in total.
-
- KVRian
- 773 posts since 23 Apr, 2002 from audio/hamburg/germany/earth/space/unkown!
really not my kind of coding styleaciddose wrote:here is a useful example for you to read to help you understand what is involved in writing a gui, if you use my libraries/code:
http://xhip.cjb.net/temp/public/editor_standard.cpp
this is the current code for the default gui, as released with [0.6.16.2].
(from the first looks)but anyways. would gsoto give his design, so i can improve and implement it?
D3CK
-
- KVRAF
- 12615 posts since 7 Dec, 2004
could you edit out that quote? it takes up way too much space.
in order to get access to the synth object from the gui (data shouldn't travel away from the synth, only into it), i implemented an interface using VST's vendorspecific() function.
the interface takes two inputs;
1) the function name you want to call, for example xhipfunc::getActiveVoices
2) the parameters to the function, either inputs or outputs as an array of void pointers
functions can return an int, assuming the data is such that it fits into an int without any problems. (a return code, a number of voices, true or false for a string being filled...)
what might change over time is that i'll add more functions and possibly change the order of parameters or number and type of parameters to the existing functions.. perhaps i'll want to make xhip multi-timbral and in such case xhipfunc::getActiveVoices might have a "section" parameter as well, to ask the number of voices in a particular section.
this is definitely more information than you need - assuming you want to write a gui using the c-style idiot-method, you won't need to use the interface at all other than to load/save programs and that sort of thing.
(c-style idiot-method being where you assume you know what parameters there are and all the ranges involved, so you don't need to query the interface to find that stuff out)
you can certainly use gsoto's layout, but he doesn't have any bitmaps, tables or other data available as far as i'm aware. you can double-check with him and let me know when you're ready to try writing a gui and i'll get you the basic interface files, make files and the dx-7 style and default gui source.
in order to get access to the synth object from the gui (data shouldn't travel away from the synth, only into it), i implemented an interface using VST's vendorspecific() function.
the interface takes two inputs;
1) the function name you want to call, for example xhipfunc::getActiveVoices
2) the parameters to the function, either inputs or outputs as an array of void pointers
functions can return an int, assuming the data is such that it fits into an int without any problems. (a return code, a number of voices, true or false for a string being filled...)
what might change over time is that i'll add more functions and possibly change the order of parameters or number and type of parameters to the existing functions.. perhaps i'll want to make xhip multi-timbral and in such case xhipfunc::getActiveVoices might have a "section" parameter as well, to ask the number of voices in a particular section.
this is definitely more information than you need - assuming you want to write a gui using the c-style idiot-method, you won't need to use the interface at all other than to load/save programs and that sort of thing.
(c-style idiot-method being where you assume you know what parameters there are and all the ranges involved, so you don't need to query the interface to find that stuff out)
you can certainly use gsoto's layout, but he doesn't have any bitmaps, tables or other data available as far as i'm aware. you can double-check with him and let me know when you're ready to try writing a gui and i'll get you the basic interface files, make files and the dx-7 style and default gui source.