XHip--Please finish your synth!!
- KVRAF
- 12615 posts since 7 Dec, 2004
no idea, download the latest version if you can't come up with a very good reason to use an older one. the latest version is much better and you can use the old gui with it without any problems - you can also just delete the bank if you want and it'll clear memory with square patches.
-
- KVRer
- 15 posts since 20 Aug, 2009
Hi.. Can I get a sample source code for a simple VSTi. This is the first time I'm trying to develop one, for my project at school. Someone on this forum suggested that I can request Xhip source code.
Thanks
Spoorthy
Thanks
Spoorthy
- KVRAF
- 12615 posts since 7 Dec, 2004
xhip isn't simple... which parts do you want?
i can give you the vst interface/wrapper code and lots of other components, but xhip isn't the best place to look.
you could look at this instead:
http://www.linux-vst.com/download/synth4.tar.gz
although that source is an example for a ext2 plugin with a gui in linux, in terms of looking at how to start coding your own this might be a good place to start.
http://www.linux-vst.com/
there are a couple other example plugins there and they lack the complex OO structure that xhip has making them easier to read as a whole. if you need help with something specific like allocating voices for notes, handling midi messages or other similar stuff ask me and i'll let you know what i have that might cover your needs.
i can give you the vst interface/wrapper code and lots of other components, but xhip isn't the best place to look.
you could look at this instead:
http://www.linux-vst.com/download/synth4.tar.gz
although that source is an example for a ext2 plugin with a gui in linux, in terms of looking at how to start coding your own this might be a good place to start.
http://www.linux-vst.com/
there are a couple other example plugins there and they lack the complex OO structure that xhip has making them easier to read as a whole. if you need help with something specific like allocating voices for notes, handling midi messages or other similar stuff ask me and i'll let you know what i have that might cover your needs.
-
- KVRist
- 227 posts since 14 May, 2005 from Atlanta
Hey Acid, I've been meaning to ask you about your ahdsr filter, that behavior that it has in the 25000hz range with the lowpass filters,(I'm loving it in subtleties), and yes its another "I" versus "F" question. I don't even mention those words anymore, anyway, can those frequencies be -easily- achieved in "F" code and still sound as crisp, or am I just bloviating about nonsense.
---------------------------
http://www.thaproducerz.com
http://www.thaproducerz.com
-
- KVRer
- 15 posts since 20 Aug, 2009
Thanks for the reply. First thing, I'm supposed to code in C++ using Windows OS. Part of my project requires generating a sine wave of a particular frequency, when you hit a key on the computer keyboard. VST plugins take/ require an audio input. VSTi needs to generate audio right? So how do I go about it? This is the first time I'm working with VST plugins.aciddose wrote:xhip isn't simple... which parts do you want?
i can give you the vst interface/wrapper code and lots of other components, but xhip isn't the best place to look.
you could look at this instead:
http://www.linux-vst.com/download/synth4.tar.gz
although that source is an example for a ext2 plugin with a gui in linux, in terms of looking at how to start coding your own this might be a good place to start.
http://www.linux-vst.com/
there are a couple other example plugins there and they lack the complex OO structure that xhip has making them easier to read as a whole. if you need help with something specific like allocating voices for notes, handling midi messages or other similar stuff ask me and i'll let you know what i have that might cover your needs.
- KVRAF
- 12615 posts since 7 Dec, 2004
spoorthy, look at the source i linked you to, that's exactly what you need to learn how to do what you need. the plugin works in windows as well, it contains both the linux and windows code. for the synthesizer, just remove everything except for the oscillator and turn that into a sin(phase * pi) rather than the other waveshapes they have. you can completely remove the gui code and that'll eliminate pretty much all the system specific stuff. you only need the aeffect struct definition (get the vst "sdk") and you'll already be done. after you have it working correctly, learn how it all works and then duplicate it in your own code.
filters: i've already written the filters in float. they are slightly slower and there are both advantages and disadvantages to using float to store the integrator values. one advantage is the larger headroom and greater over-all accuracy. one disadvantage is the need to eliminate denormals and to compute using float everywhere. most of the reason i use int code is that certain modulation related operations are faster there and that in xhip i do per-sample modulation making up about 50% of the total cpu cost right now. if the entire synth were done in float it might over-all be slightly slower. most synthesizers use block processing and in those cases there is no significant disadvantage to using float, other than the fact that the core of the filter is slightly slower once you eliminate denormals. it's possible to only eliminate denormals on block edges rather than inside the filter and in that case it's nearly identical in speed, but denormals will be introduced in corner cases at very high frequency and extremes of low/high resonance. if the math is the same az float version of the filter will sound exactly like the int version, there is no practical difference between the formats. the difference is in how you use them.
filters: i've already written the filters in float. they are slightly slower and there are both advantages and disadvantages to using float to store the integrator values. one advantage is the larger headroom and greater over-all accuracy. one disadvantage is the need to eliminate denormals and to compute using float everywhere. most of the reason i use int code is that certain modulation related operations are faster there and that in xhip i do per-sample modulation making up about 50% of the total cpu cost right now. if the entire synth were done in float it might over-all be slightly slower. most synthesizers use block processing and in those cases there is no significant disadvantage to using float, other than the fact that the core of the filter is slightly slower once you eliminate denormals. it's possible to only eliminate denormals on block edges rather than inside the filter and in that case it's nearly identical in speed, but denormals will be introduced in corner cases at very high frequency and extremes of low/high resonance. if the math is the same az float version of the filter will sound exactly like the int version, there is no practical difference between the formats. the difference is in how you use them.
-
- KVRAF
- 3499 posts since 9 Oct, 2004 from Poland
no !Cordelia wrote:The teenage ninja kind?Mutant wrote:i like turtles
the "win a race with a rabbit" kind
(it was just a bump for my friend, so he can find the thread easily)
[====[\\\\\\\\]>------,
Ay caramba !
Ay caramba !
-
- KVRist
- 227 posts since 14 May, 2005 from Atlanta
ahh no christmas present...oh well merry christmas
---------------------------
http://www.thaproducerz.com
http://www.thaproducerz.com
-
- KVRist
- 227 posts since 14 May, 2005 from Atlanta
btw...is your site officially gone for good?
---------------------------
http://www.thaproducerz.com
http://www.thaproducerz.com
- KVRAF
- 12615 posts since 7 Dec, 2004
no, but i need to put it on a new server. i've actually been considering running it out of a VM. i'd just need to copy all the data across to get it working.
i hadn't updated xhip for so long, i figured most people had the latest version already. i'm trying to update the code now and i might release another version of it and the effects in the next few months. some issues with it are the way all controls were previously automatable parameters. i need to rework some of the internals and get the control section for example to work separately. if you needed something i could either plug the server in or send you the files directly.
i hadn't updated xhip for so long, i figured most people had the latest version already. i'm trying to update the code now and i might release another version of it and the effects in the next few months. some issues with it are the way all controls were previously automatable parameters. i need to rework some of the internals and get the control section for example to work separately. if you needed something i could either plug the server in or send you the files directly.
- KVRAF
- 12615 posts since 7 Dec, 2004
i've connected the server pc and updated the dns, http://xhip.cjb.net/xhip/releases
i need to make a copy of a physical disk (or at least some files) and then set up apache running on a virtual machine instead. it's fairly time consuming and there is no real reason to do it yet with so few people asking for xhip.
the latest alpha is new - i added some annoying fancy black knobs drawn in real-time. the gui library is partially rewritten and some bugs are fixed. the "control" section is completely disabled, but you can still use it to get basic sounds.
i really should fix the control section thing, i'm just not 100% sure how to handle it at this point.
(the main issue is that the whole section shouldn't be automatible, yet the code currently uses automatible vst parameters to communicate between the synth and gui.. i need to fix it and it'll take some time when i do, i haven't gotten around to xhip very often lately.)
for the latest version with the black knobs, use "latest revision"
for normal use, get the "recommended" version
i need to make a copy of a physical disk (or at least some files) and then set up apache running on a virtual machine instead. it's fairly time consuming and there is no real reason to do it yet with so few people asking for xhip.
the latest alpha is new - i added some annoying fancy black knobs drawn in real-time. the gui library is partially rewritten and some bugs are fixed. the "control" section is completely disabled, but you can still use it to get basic sounds.
i really should fix the control section thing, i'm just not 100% sure how to handle it at this point.
(the main issue is that the whole section shouldn't be automatible, yet the code currently uses automatible vst parameters to communicate between the synth and gui.. i need to fix it and it'll take some time when i do, i haven't gotten around to xhip very often lately.)
for the latest version with the black knobs, use "latest revision"
for normal use, get the "recommended" version
-
- KVRist
- 447 posts since 23 Mar, 2008 from so whos got a blowfelt?
Hello Aciddose I wonder how you set this up so you can use a real GUI in ableton and not just abletons default?
It turned out the kittens mittens were hidden in the cats pyjamas all along.
suck my dongle
suck my dongle
