XHip--Please finish your synth!!

[Kingston]

http://xhip.cjb.net/temp/public/binary/ ... ter_v8.dll

do not be afraid to crank the saturation to 100% with 100% res now, it will automatically compensate to ensure near-zero aliasing. a sideffect is that noise bursts caused by aliased harmonics lining up with non-aliased harmonics, leading to out-of-range harmonic amplitudes are prevented due to the fact this can no longer happen.

again, works in wavelab, but not in SX3. not even the dry signal goes through - it's completely silent.

v6 was ok, apart from the headroom fluctuation.

[aciddose]

ok, try these then. if these dont work, then i'll be 15% more confused.

http://xhip.cjb.net/temp/public/efftorxor_goc.zip

[_starcraft_]

i guess its the name that appears on the plug....
"filteriiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii(never endin)......."
i remember readin somehwree some hosts dont handle long names well.

[aciddose]

that was one of the five bugs i just fixed in my attempt to figure out what the hell could be wrong with the plugin. can anyone tell me if these ones work ok in live/cubase/etc?


http://xhip.cjb.net/temp/public/zoopzoop000.mp3

[Kingston]

ok, try these then. if these dont work, then i'll be 15% more confused.

http://xhip.cjb.net/temp/public/efftorxor_goc.zip

They all work just fine. What a freaky but clean unique chorus! a keeper!

just those last two filters v7 and v8 don't do anything.

[FragileX]

Thanks for these one acidose (and for xhip).
There working fine here on ext1&2, but I've got weird noisebursts and crackling using the chorus.

[disturb]

ok, try these then. if these dont work, then i'll be 15% more confused.

http://xhip.cjb.net/temp/public/efftorxor_goc.zip

They all work just fine. What a freaky but clean unique chorus! a keeper!

just those last two filters v7 and v8 don't do anything.

same here, everything fine in Live 6.

cheers

[Kingston]

There working fine here on ext1&2, but I've got weird noisebursts and crackling using the chorus.

increase the headroom to stop it bursting into shreds.


aciddose, a few ideas for the chorus,

add more than this one (ramp?) shape for the modulation, and a possible phaser/allpass mode.

[FragileX]

thanks Kingston but I already tried this and it doesen't help. In xt2 I got a rhythmic highpitched noise when i insert the chorus - without playing sound through it.

[aciddose]

dont use this version then, use http://xhip.cjb.net/xhipeffects/data/xh ... ts_wip.zip

i've been making small changes to the chorus to improve it, it isnt a "finished" effect at this point, the control ranges can be set out of bounds. try decreasing the modulation depth to 20% and decrease the phase offset to 40% to get a more typical chorus.

if you want a phaser, use the phaser. as for more modulation possiblities, that is something i'll do later. xhip needs work right now.

[gsoto]

(...) can anyone tell me if these ones work ok in live/cubase/etc?

Cubase LE 1.0.7
efftorxor_goc/chorus: ok, but same as FragileX for high modulation
efftorxor_goc/filter, gate, reverb: ok
filter_v7: same as Kingston, no sound

Chainer (demo)
everything ok

http://www.kvraudio.com/forum/viewtopic ... sc&start=0

comon guys download this utility courtesy of asseca and lets get xhip skinned !

ps:i'm tryin myself but with no luck till now...

I'll take a look, starcraft, but I don't promise anything.

[aciddose]

i wouldnt bother trying to use that type of 'skinning' utility. it might be great to use them for my guiless effects plugins, but there is a significant overhead due to the fact you need to also download the bitmaps and dll files for the skinning app in order to use the skinned plugins.

for xhip it isnt practical at all since you're limited to the controls exposed via vst automation. i cant expose all controls through automation. for example it wouldnt make sense with the event routing stuff since that is dynamic.. i cant even think of any way it would be possible to do through automation.

[aciddose]

http://xhip.cjb.net/xhip/releases/v0/b6 ... 6.12.1.dll

- changed notelogic from static system to a dynamic system. there is now absolutely no limitation on the possible number of notes which can be sent to xhip, and it will be easy for me to implement multitimbrality in the future.

this version requires stress testing to make sure things are working correctly. there is a very small chance a crash might occur, but the linked list class i've used i wrote myself and has had extensive testing so it seems things should be stable.

let me know if anybody can get crashes or hung notes while giving some wild midi note input and changing the notelogic settings around.

next todo entry:

- fix and enable sustain support

[gsoto]

next todo entry:

- fix and enable sustain support

Weeeeeee!

I like the new modulation system. Is it definitive? I will have to redesign my GUI.

I think there's something strange with the note logic. Just by playing in poly mode sometimes I get two particular notes in a state in which they cancel each other.

[aciddose]

that is exactly the kind of bug i was trying to find before uploading this version.. can you figure out how to recreate that state directly so i can debug it? i'll hook up my midi controller and try to see if i can get it like that

"Is it definitive?"

yeah i guess so. it does add a lot more flexablity. every time i add features i'm upset at the increased cpu use, but then i always manage to reduce it again after some time, and the added power for the synth is great.

so, yes i'm definitely keeping it in there. you probably shouldnt do a final version of your gui until we get to the "fully implement gsoto's gui" part of the todo, it is pretty close. before that i'll ask and see if anyone can think of features which could be added.. after that the feature set of the synth will be absolutely locked down until after version 1.0.0.0 so i can work on finishing this version rather than messing with features, backtracking when i make changes and so on.

i do have a few things in the synth section of the todo which i'm not currently working on.. i wrote "audio input", and "envelope follower modulation source" most importantly. i'm not sure if i want to add those for xhip 1 or save them for xhip 2.

with the filter and waveshaper available as external effects it partly removes the need for audio input with xhip anyway i think.

as for your current gui though.. we should do a little bit of practice before we get into trying to do a final design for it. if you spend some time with your design again you should try writing down all the pixel coordinates for all the elements. for example.. the oscillator section could be like..

gui
{
main rectangle 800x600
{
oscillator section
{
main rectangle (156x132) at offset (16,58)
top section
{
main rectangle (156x24) at offset (0,0)
black border lines
{
(1x16) at offset (78, 4)
(148x1) at offset (4, 23)
}
}
}
}

i've only included two borders there, the vertical center line and the horizontal line where the "osc a" and "waveform" text boxes are divided. the whole layout for just the oscillator section is pretty difficult when i have to figure out all the numbers myself. in the full gui you'll really need to help me by providing the exact numbers, and that way i'll be able to recreate your design exactly as well. colors and so on are also useful of course.