code your own sampler (SynthEdit)

[xoxos]

rugby is a great foundation for being able to bollock others tomorrow

(i remember the 'cv + gate button' issues from ~2004.. can't remember what the solution was.. putting the whole thing in another container set to "show gui on parent" and putting the buttons with midi triggers in the outer layer iirc..)

(edit.. gotta add i'm always fascinated by the 'thread view' figures.. purportedly something like 500 people checked in to read your last two posts haha)

[spacedad]

500 people reading my jibber-jabber.

i wonder how many were mad with me for talking crap and not giving them a new free thing.or something.

[spacedad]

really though,everyone should get this and make stuff.
it's sample-tastic.

[spacedad]

i meant to ask you,if it can't find a sample,where does it start to look?(on someone else's computer?)
does it have a default folder?

[xoxos]

man, i didn't intend for this post to be more than a few lines... you may want to schedule several breaks through it, get up and stretch out, do a Bong Hit Break.



check the source code for sample0

no, really... just open module.cpp in a text editor and browse through it. i really expect you'll be able to identify the audio process loop and the sample loading process. it's verbose but simple.

but answer to your question in a way that should be useful as a se developer:

the filename is passed to the sdk as a text string from a pin. it tries to load a file when the pin value changes.. which i guess is when the user hits enter and when the vst/sem goes active. if it can't find what is expected it stops loading (you can see the various checks.. a ! before something means "not" like != "not equal", or !myvar "not my variable" which occurs when the variable (bools or ints) equals zero.)

pins have a "datatype extra" parameter where you put whatever the sem pin is set to when you load it, eg. how the level adjust loads with 8 on each pin.. (i must have changed that to '10' several thousands of times..)


i was going to say about the gate detection pin -

there's nothing 'weird' about gate pins inside the sdk.. they work the same as any other pin and feed values in. to detect a gate, i record the pin value from the last sample and compare them.. if current sample is larger than 0 volts *and* the last sample is 0 volts or lower, then do whatever.

in these modules, for some reason (brevity lol) i did the gate pins differently.. the comparison between the two is only "if current sample is higher than previous sample, then do stuff..." it's a "bad" method if someone is using an abnormal gate source, eg. a smoothed signal or ramps.. because an upward ramp will have this condition be true and retrigger on every sample.. it works fine with a cv gate (or by adding a comparator before it of course).

so when something doesn't wake when it gets a gate signal, it's not due to a malfunction at the pin. in the old version i use, the midi>cv module does something with voice activation that is above the sdk. my guess is when you add a button it's due to something between the gui and the poly engine...

it's reader bong hit time. i'm dry.

[spacedad]

that's cleared that up then.

[spacedad]

looking at the code for sample0,it is surprisingly short and concise.
it looks a bit like css code.

[xoxos]

looking at the code for sample0,it is surprisingly short and concise.

isn't it?

$99 license fee please, 50% discount for license transfers!

over 200 views! i hear real men don't require artificial inflation

now some people may think that's paranoia, but i remember last summer when some of my threads were accumulating several thousand views in the course of twenty minutes posted in the site stuff forum, never got an answer, but my thread views dropped back radically to a more credible volume...

[xoxos]

i uploaded jpegs

inverted the gui at the last minute.. makes more sense dark but i like it like this.
http://www.xoxos.net/vst/element.zip

no manual, not tested.

what's to know.. the sample loading routine is still primitive.. 8 and 16 bit only, if it doesn't load a wav, you won't hear any sound. i don't really know if it will explode. wear a hat.

modulation heirarchy is:
lfo2 > env2 > sends1-5 > env1 > lfo1 > main stuff

heave fun

[spacedad]

sorry,i've been offline.my puter's power supply exploded.(nothing do do with your sampler!)

looks great,i'll check it out.

[xoxos]

http://www.xoxos.net/vst/element.zip

added manual (it's a crap one) zip includes light and dark gui versions, and i got rid of that bit on the gui where it says 'nce' (don't spend all day looing for it, right side, about the middle..)

well gary i'm going in the kitchen to have a nibble, have a nice sleep, same time tomorrow.

[spacedad]

you have a kitchen? cool.

[annode]

I am so excited about this. If I lived nearer to Gary i'd be in 'hog heaven'. But i'm a little higher up on the map so I guess i'm 'totally freaked'.
I'm no developer, even if it's 'Synthedit', I think your creativity deserves high marks. I know your modest on the feature complexity...those things I know little about...but the realization of this thing and implementing it, not to mention sharing it so me and Gary can go 'hog wild', deserves a round of applause.

Will give it a test drive later on.

[spacedad]

just a quick test drive.
some great features.lots of fun with loop points and filters.
really nice gui.
though some of the text knobs take a bit of pushing to change,maybe some should be just clickable.
but a minor point.
need to throw more sample types at it,but this is great work.
class.

[xoxos]

ta both (& agree at least on the poly selector but it's consistent..) i chucked it in eXT, made sure it made a noise, uploaded it and went back outside


gotta be one of the better track openings..

..and endings..