XHip--Please finish your synth!!
-
- KVRAF
- 12615 posts since 7 Dec, 2004
it does partially fix it. the problem is that logic sends invalid vstevent packets, and also calls processevents() multiple times (illegal to do this) between process() calls.
right now i'm simply dropping the invalid packets and all events after non-chronological events, but they can potentially contain important data so this is not an acceptable fix for the problem. what i need to do is reinsert my event sorting code and apply the sort whenever non-chronological event packets are received. when the processevents() function is called multiple times, i'll need to append those events and then allow for the sort to occur if those additional events are non-chronological.
right now i'm simply dropping the invalid packets and all events after non-chronological events, but they can potentially contain important data so this is not an acceptable fix for the problem. what i need to do is reinsert my event sorting code and apply the sort whenever non-chronological event packets are received. when the processevents() function is called multiple times, i'll need to append those events and then allow for the sort to occur if those additional events are non-chronological.
-
- KVRAF
- 1958 posts since 16 Jan, 2005 from France's Dirty South
Forgive me for being such a lazy ass and not reading the whole thread ; but could anyone fill me in on what version of xhip to use ?
Is there any that will be compatible with the future versions (dar i say final) ?
I'm most concerned about not being able to reuse my patches and having to keep the whole history in my vst folder...
cheers
Is there any that will be compatible with the future versions (dar i say final) ?
I'm most concerned about not being able to reuse my patches and having to keep the whole history in my vst folder...
cheers
-
- KVRAF
- 12615 posts since 7 Dec, 2004
if any of the versions were "stable" there wouldnt be multiple versions up on the site.
for the latest (0.6.11.13) you should be able to reuse your patches. you might not be able to load project files with new versions though.
if you're satisfied with the synth the way it already is, just consider that "1.0" and use it without worrying about new versions. people often ask me "when will 1.0 be done so i can use xhip in my projects".. well, 1.0 isnt going to be "done" once it's released anyway. there will be "2.0" and "3.0" and "4.0" and so on. so, you're going to go nuts if you concern yourself with having a "final" version. you should either not use xhip (just because i refuse to stop working on it.
) or take a version you like and consider it your own "1.0".
that said, the next beta (7) will be pretty damn stable, and 1.0 isnt too far away after that.
for the latest (0.6.11.13) you should be able to reuse your patches. you might not be able to load project files with new versions though.
if you're satisfied with the synth the way it already is, just consider that "1.0" and use it without worrying about new versions. people often ask me "when will 1.0 be done so i can use xhip in my projects".. well, 1.0 isnt going to be "done" once it's released anyway. there will be "2.0" and "3.0" and "4.0" and so on. so, you're going to go nuts if you concern yourself with having a "final" version. you should either not use xhip (just because i refuse to stop working on it.
) or take a version you like and consider it your own "1.0".that said, the next beta (7) will be pretty damn stable, and 1.0 isnt too far away after that.
-
- KVRAF
- 6478 posts since 16 Dec, 2002
I would guess people are most concerned about the schedule of implementing your future proof patch format, which AFAIK is near the top of the "to do" list.
care to enlighten the situation on that? I seem to recall you removed some old soon-to-be-obsolete patch conversion code to make room for a proper patch format.
care to enlighten the situation on that? I seem to recall you removed some old soon-to-be-obsolete patch conversion code to make room for a proper patch format.
-
- KVRAF
- 1868 posts since 26 Oct, 2002 from San Francisco
See, that's the problem!aciddose wrote:that said, the next beta (7) will be pretty damn stable, and 1.0 isnt too far away after that.
I really want to start using this synth, but I'm just always seeing you put out a new version with new "crucial"(in my own stupid mind!) features, and I wait, wait, wait till you deem a version worthy of the great 1.0 title 
silly, I know, but hey!
-
- KVRAF
- 12615 posts since 7 Dec, 2004
well a "proper" patch format is something i've wanted to do for a long time. part of the problem with that is i really need to have the synthesizer feature set locked down. backward compatiblity is nice, but when you're constantly adding features it means code bloat in the loader. the loader becomes basically a huge complex converter for old formats.
that conversion part is what i removed, but i've added it back now and it'll stay for a while. i think i'm getting really close to the point where i'm going to lock down the core featureset - i just never know for sure. you cant see what is around the corner until you turn it. every new feature i add i think of two more to add later. tell you what though, i'm going to reorganize the todo list to make locking the feature set the top priority.
that conversion part is what i removed, but i've added it back now and it'll stay for a while. i think i'm getting really close to the point where i'm going to lock down the core featureset - i just never know for sure. you cant see what is around the corner until you turn it. every new feature i add i think of two more to add later. tell you what though, i'm going to reorganize the todo list to make locking the feature set the top priority.
-
- KVRist
- 499 posts since 9 Oct, 2005
How about this (my own .02 €) : you lock down the feature set, make the matching patch format, we then get to that wonderful period of time where all the synth geniuses join forces to make tons of competition-killing patches we can get our not-so-worthy hands on... because I feel in the end that's what a lot of people are waiting for if you read (not so much) between the lines.
Once it's up to your standards regarding stability/bugs/CPU-cycles/whatever-I'm-no-programmer, with all the GUI mumbo-jumbo you call it 1.0 and no KVRians will have died of anticipation in the process.
Sounds like a good plan, no ? I'm sure I'm missing something.
Once it's up to your standards regarding stability/bugs/CPU-cycles/whatever-I'm-no-programmer, with all the GUI mumbo-jumbo you call it 1.0 and no KVRians will have died of anticipation in the process.
Sounds like a good plan, no ? I'm sure I'm missing something.
-
- KVRAF
- 3846 posts since 15 Mar, 2002 from Underworld
Not a bad idea. It leaves some room for version 2.0. This puppy isquite powerful as it is now, just to fix the GUI a bit and I'm thinking more in a line of the various modulations.
It is no measure of health to be well adjusted to a profoundly sick society. - Jiddu Krishnamurti
-
- KVRian
- 533 posts since 16 Jan, 2006 from France
To sum it up with only 2 ascii characters :cheul wrote:How about this (my own .02 €) : you lock down the feature set, make the matching patch format, we then get to that wonderful period of time where all the synth geniuses join forces to make tons of competition-killing patches we can get our not-so-worthy hands on... because I feel in the end that's what a lot of people are waiting for if you read (not so much) between the lines.
Once it's up to your standards regarding stability/bugs/CPU-cycles/whatever-I'm-no-programmer, with all the GUI mumbo-jumbo you call it 1.0 and no KVRians will have died of anticipation in the process.
Sounds like a good plan, no ? I'm sure I'm missing something.
+1
-
- KVRian
- 666 posts since 29 Dec, 2006 from Auckland, New Zealand
Man, I'm always one to belive the hype, but after looking at the screenshot, I dont think I could work this out. Does this really sound that good? the clips soud nice.
A user friendly GUI and a bunch of presets for us lazy laymen would be great
A user friendly GUI and a bunch of presets for us lazy laymen would be great
-
- KVRAF
- 2029 posts since 21 Jul, 2004
Its really a simple synth. Basic design for a patch goes as follows(say a bass patch). Choose the saw wave or something. go to the filter, change it to LP24, change the filter env to env #2. bring down the cutoff, and the envelope depth, bring up the res. Screw around with the envelope in the mods section to taste (basic ADSR). Make it mono(newest) in the controls section. In the first page put on linear glide, make it somewhat fast.
Beyond this you can add various other things for character. There is modulation from the oscs to the filter cutoff and resonance for example, if you want a real farty type of sound. Add some saturation. Maybe route an LFO to the cutoff, change the LFO range to tempo sync, with a ramp waveform. Add a second osc, like a pulse, detuned slightly, Or detuned a lot. And let osc b sync to osc a. Its not very hard to see the effects of a parameter, as this synth is pretty straitforeward. There are many things to do and its not very hard once you try. Add some noise into the mix. Add a modulator for vibrato, with a little delay on the lfo, it will sing nicely. There is a second filter (with keytracking) that oyu can play with too, to further shape the sounds.
Give it a go.
Beyond this you can add various other things for character. There is modulation from the oscs to the filter cutoff and resonance for example, if you want a real farty type of sound. Add some saturation. Maybe route an LFO to the cutoff, change the LFO range to tempo sync, with a ramp waveform. Add a second osc, like a pulse, detuned slightly, Or detuned a lot. And let osc b sync to osc a. Its not very hard to see the effects of a parameter, as this synth is pretty straitforeward. There are many things to do and its not very hard once you try. Add some noise into the mix. Add a modulator for vibrato, with a little delay on the lfo, it will sing nicely. There is a second filter (with keytracking) that oyu can play with too, to further shape the sounds.
Give it a go.
Do not lick the fablanky