yes, but obviously the routing and everything will be extremely slow. it'll be a modular version, basically. i've always said the next synth i do will be a modular. just don't think of cables and that sort of nonsense. (unless you want to...)
think more of programming your synth by adding destinations for the lfo, for example.
that's a long way in the future, let's worry about the current code for now.
XHip--Please finish your synth!!
-
- KVRAF
- 3928 posts since 23 Oct, 2005 from vassalboro, maine
i was just wondering hypothetically. i mean, of course sometimes you'd only want one lfo. i was wondering because i've been [trying] to learn some things about object oriented programming... (omg it's the trippiest thingy) - and i just rtealized that in essence if you had an lfo object, you could create as many as you needed and destroy them at will as well... just a matter of having someone with the balls to do it.. (i mean, you have it in the grand modulars, but thats a little different of a concept.. i guess the same could go for adding straight oscs as well too...
-
- KVRAF
- 12615 posts since 7 Dec, 2004
i think most people don't realize that about software. the only reason a software synth has X number of lfos, envelopes or oscillators is because the author designed it that way. it's intentionally limited. if i wanted i can make a synth with 192 oscillators and 49 lfos, 42 envelopes and 6943 noise sources.. but that would be mostly useless. most patches need about two oscs, two lfo, two envs and some kind of processing.
that's how i designed xhip, as a general purpose synth. it was never made to do sounds like a minimoog (3 oscs, although extremely limited modulation routing and waveforms) or a virus or any of that nonsense. those synths are ok at those 'fat' sounds, but not highly regarded for the general sounds like roland style phase-locked sub osc sounds. they're not regarded for great ranges of sounds, sound effects, pads, synth stuff, realistic stuff.. shit xhip can even do a model of am radio transmission if you feed one oscillator with the modulator, use the other for a carrier, simulate transmission losses with the main filter and use the waveshaper and filter as a receiver.
so when i hear requests for more oscillators, more unison, more filters or whatever i say "nonsense, use something else" in my head while trying to say something else like "well that isn't practical" or "maybe in the modular version" in the thread. from an honest point of view i'm being an asshole by saying "maybe in x version of it", but the perception of a figure in a crowd is strange. everybody is happy when i say that stuff, but if i said "that just isn't xhip's design" i'd be an ass
i really do want to do a modular version eventually, though. that won't satisfy everyone because somebody always wants something no matter how insane or impractical it is, but at least it'll satisfy most people. uh, except for the ones who say "can't you just do a synth with the modular oscs, filters and stuff but only two of each thing so it's simple to patch???"
that's how i designed xhip, as a general purpose synth. it was never made to do sounds like a minimoog (3 oscs, although extremely limited modulation routing and waveforms) or a virus or any of that nonsense. those synths are ok at those 'fat' sounds, but not highly regarded for the general sounds like roland style phase-locked sub osc sounds. they're not regarded for great ranges of sounds, sound effects, pads, synth stuff, realistic stuff.. shit xhip can even do a model of am radio transmission if you feed one oscillator with the modulator, use the other for a carrier, simulate transmission losses with the main filter and use the waveshaper and filter as a receiver.
so when i hear requests for more oscillators, more unison, more filters or whatever i say "nonsense, use something else" in my head while trying to say something else like "well that isn't practical" or "maybe in the modular version" in the thread. from an honest point of view i'm being an asshole by saying "maybe in x version of it", but the perception of a figure in a crowd is strange. everybody is happy when i say that stuff, but if i said "that just isn't xhip's design" i'd be an ass
i really do want to do a modular version eventually, though. that won't satisfy everyone because somebody always wants something no matter how insane or impractical it is, but at least it'll satisfy most people. uh, except for the ones who say "can't you just do a synth with the modular oscs, filters and stuff but only two of each thing so it's simple to patch???"
-
- KVRAF
- 2258 posts since 25 Jun, 2008 from Montreal, Canada
Can't wait for your modular version! But instead of a complete modular why can't you just do a synth with the modular oscs, filters and stuff but only two of each thing so it's simple to patch???
Thanks!
Thanks!
-
- KVRAF
- 3928 posts since 23 Oct, 2005 from vassalboro, maine
i understand the practicality of it. i'm glad my brain was on the proper track though.
-
- KVRAF
- 12615 posts since 7 Dec, 2004
http://xhip.cjb.net back online: lesson, never use your production server to play with nonsense that isn't server related, either use an imaged server (where you can instantly revert) or use another damn machine!!
-
- KVRAF
- 12615 posts since 7 Dec, 2004
http://xhip.cjb.net/temp/public/ahhdfltbnk.mp3
this patch is in the default bank - for really good ahh pads you might consider using pcm. it'll really help when i get the "event routing" junk implemented so you can do panning spread and that sort of thing. to start, you could just use two instances and pan them manually. the synth signal path will always be in mono so there won't ever be any advantage to using event routing for this other than that it might make it slightly easier to set up. (two voice unison with left/right, or a basic multi-timbral configuration rather than using two instances..)
this patch is in the default bank - for really good ahh pads you might consider using pcm. it'll really help when i get the "event routing" junk implemented so you can do panning spread and that sort of thing. to start, you could just use two instances and pan them manually. the synth signal path will always be in mono so there won't ever be any advantage to using event routing for this other than that it might make it slightly easier to set up. (two voice unison with left/right, or a basic multi-timbral configuration rather than using two instances..)
-
- KVRAF
- 12615 posts since 7 Dec, 2004
http://xhip.cjb.net/xhip/releases/0/6/1 ... 6.17.0.zip
- use this version, all the stuff people have complained about in the guis are fixed.
- i've inserted branis' gui as "default.xhipgui" in this version. if you have any problems, just replace it with http://xhip.cjb.net/xhip/releases/xhipg ... rd.xhipgui . the others are available if you click "show all releases" on the releases page.
- the patches and banks now store in floats, although they're still using the old format. i'm working on a chunk format to be introduced soon. please report any issues loading patches, none should exist although i won't discount the possibility of bugs...
- the velocity and bender routing is disabled currently until the event routing system is implemented correctly. after which the default routing configuration will be set up to be interfaced from the old velo/bender points by the new versions of the GUIs. eventually the GUIs will implement a proper dynamic routing page and you'll be able to load text files containing the configuration as well as having this info stored in patches.
- since all parameters now work in floats it's easily possible to crash xhip by using automation out of the range of 0.0 to 1.0.. i haven't bothered to clip or do any other type of checking. it's also possible to crash xhip by loading bad patches with out-of-range values. if you experience this type of problem IT IS NOT A BUG... i just have not yet finished implementing the new parameter functions and patch storage format.
- i might have fixed a bug with keyboard tracking and glide in the filter, or i might not have. please report if you notice any synth bugs that i haven't fixed yet because these REALLY need to be fixed now or at least put on the todo list since i'm working on interface stuff now like event routing and patches. it's nice to have the synth working 100% stable and as intended so i don't need to worry about it.
- a positive aspect of having parameters in float is that they have a much more accurate response. it's now possible to enter exact values if the GUI supports it for any parameter. a negative aspect is that you'll be stuck sometimes with "impossible" values offset slightly from zero (0.00053031), just use ctrl-click to reset in this case, if it occurs.
- use this version, all the stuff people have complained about in the guis are fixed.
- i've inserted branis' gui as "default.xhipgui" in this version. if you have any problems, just replace it with http://xhip.cjb.net/xhip/releases/xhipg ... rd.xhipgui . the others are available if you click "show all releases" on the releases page.
- the patches and banks now store in floats, although they're still using the old format. i'm working on a chunk format to be introduced soon. please report any issues loading patches, none should exist although i won't discount the possibility of bugs...
- the velocity and bender routing is disabled currently until the event routing system is implemented correctly. after which the default routing configuration will be set up to be interfaced from the old velo/bender points by the new versions of the GUIs. eventually the GUIs will implement a proper dynamic routing page and you'll be able to load text files containing the configuration as well as having this info stored in patches.
- since all parameters now work in floats it's easily possible to crash xhip by using automation out of the range of 0.0 to 1.0.. i haven't bothered to clip or do any other type of checking. it's also possible to crash xhip by loading bad patches with out-of-range values. if you experience this type of problem IT IS NOT A BUG... i just have not yet finished implementing the new parameter functions and patch storage format.
- i might have fixed a bug with keyboard tracking and glide in the filter, or i might not have. please report if you notice any synth bugs that i haven't fixed yet because these REALLY need to be fixed now or at least put on the todo list since i'm working on interface stuff now like event routing and patches. it's nice to have the synth working 100% stable and as intended so i don't need to worry about it.
- a positive aspect of having parameters in float is that they have a much more accurate response. it's now possible to enter exact values if the GUI supports it for any parameter. a negative aspect is that you'll be stuck sometimes with "impossible" values offset slightly from zero (0.00053031), just use ctrl-click to reset in this case, if it occurs.
-
- KVRian
- 889 posts since 10 Jul, 2004
thanks very nice.
a few issues:
- it's still right click + ctrl for reset values..which makes it tricky to use with touchscreen/stylus.
- values to which parameters are reset is questionable. i think it should always go to middle value.vertical position. (cos going to max positive and negative values is easy without need of a reset parameter-as the knobs locks up and down hehe)
- paypal is still missing on site....i owe u a few beers at least as i just use your synth and effects now. (basically in the project i have opened apart from the limiter everything is your plugins )
a few issues:
- it's still right click + ctrl for reset values..which makes it tricky to use with touchscreen/stylus.
- values to which parameters are reset is questionable. i think it should always go to middle value.vertical position. (cos going to max positive and negative values is easy without need of a reset parameter-as the knobs locks up and down hehe)
- paypal is still missing on site....i owe u a few beers at least as i just use your synth and effects now. (basically in the project i have opened apart from the limiter everything is your plugins )
-
- KVRAF
- 12615 posts since 7 Dec, 2004
http://xhip.cjb.net/xhip/releases/xhipg ... is.xhipgui
- left+ctrl reset
- right click update/print value without changing
- vertical primary, horizontal 1/16ths, on shift it reverts to vertical fine
- the available modes are then {vertical, horizontal, circular, hybrid-vertical}, a simple matter of flipping a flag. i could scan for cubase's knob-mode flag, but it only has the three basic modes and not all hosts support it.
the value that a parameter gets reset to is dependent upon the "default" patch. i'll add the ability to load into this position from the config file in the future. perhaps i could quickly implement something like default.adxi for this, i'll think about it. you won't be able to reset the control parameters until the new patch format is updated and supports that. i can just change the offsets to zero for you now if you really want - the drop boxes need the ability to reset also, i'm not sure if you've noticed they don't have that.
as for paypal, if you really want to send me some bucks give me a private message and we'll discuss it. you definitely don't need to feel obligated, though.
this type of stuff is supposed to be up to the gui designer, not me!
- left+ctrl reset
- right click update/print value without changing
- vertical primary, horizontal 1/16ths, on shift it reverts to vertical fine
- the available modes are then {vertical, horizontal, circular, hybrid-vertical}, a simple matter of flipping a flag. i could scan for cubase's knob-mode flag, but it only has the three basic modes and not all hosts support it.
the value that a parameter gets reset to is dependent upon the "default" patch. i'll add the ability to load into this position from the config file in the future. perhaps i could quickly implement something like default.adxi for this, i'll think about it. you won't be able to reset the control parameters until the new patch format is updated and supports that. i can just change the offsets to zero for you now if you really want - the drop boxes need the ability to reset also, i'm not sure if you've noticed they don't have that.
as for paypal, if you really want to send me some bucks give me a private message and we'll discuss it. you definitely don't need to feel obligated, though.
this type of stuff is supposed to be up to the gui designer, not me!
-
- KVRian
- 889 posts since 10 Jul, 2004
horizonatal movement (left right) don't seem to be working here at all.
vertical faster movemnt
horizonal slower movement
shift vertical very slow movement
that should be pretty much all beahviours required....circular i dont think its needed.
vertical faster movemnt
horizonal slower movement
shift vertical very slow movement
that should be pretty much all beahviours required....circular i dont think its needed.
-
- KVRAF
- 12615 posts since 7 Dec, 2004
it already works like that, try again or maybe you haven't correctly installed the new version. it might have copied out of cache in your browser.
works fine for me...
http://xhip.cjb.net/xhip/releases/xhipg ... branis.png
i just added the funny xhip logo as well. that doesn't really do anything though, it's just graphics. i might add the fractions to the coordinates later. i apparently need to write a oversampling (sub-pixel) polygon filler as well.
works fine for me...
http://xhip.cjb.net/xhip/releases/xhipg ... branis.png
i just added the funny xhip logo as well. that doesn't really do anything though, it's just graphics. i might add the fractions to the coordinates later. i apparently need to write a oversampling (sub-pixel) polygon filler as well.
-
- KVRian
- 889 posts since 10 Jul, 2004
the horizontal movement is very difficult to use as it conflicts with the vertical movement.....right now its not implemented in a workable way. not sure how it can be donee right.
ps: that t-racks advert on kvr is so fuckin annoyin... (flashing lights with tired eyes is last thing needed)
ps: that t-racks advert on kvr is so fuckin annoyin... (flashing lights with tired eyes is last thing needed)
-
- KVRAF
- 12615 posts since 7 Dec, 2004
you suggest a better way and i'll implement it. there is no simple way to do it. they do NOT interact or interfere with each other at all, it's just that you can't move the mouse in a perfectly straight line very easily at all. find another piece of software that does it and then figure out how it manages to work any better than what i've done.
-
- KVRAF
- 4737 posts since 20 Feb, 2004 from Gothenburg, Sweden
Would it be enough to just check if delta-x is larger than delta-y and if so ignore delta-y, and vice versa?
Stefan H Singer
https://dropshotaudio.com/
https://dropshotaudio.com/