From the original SynthMaker forum (2004–2014), with its members’ names and dates.
labelwhore ·
I don't know how much interest this will be to anyone, but I thought I'd post it here regardless. I'm working on a VST control surface for my MIDI box SID. I'll update this post with latest version as I update this sucker.
Features:
* Non-destructive real-time editing of many of the MB SIDs parameters
* easily automate parameters that are otherwise hidden within menus on the sammichSID
Please note, this only works with the lead engine as the standard CCs have not been implemented for the bassline, poly, and superpoly engines yet.
To Do:
* test in multiple hosts
* ensure all parameters can be automated
fix osc and filter selectors - DONE
fix bank select knob - DONE
fix VCA sustain knob bug - DONE
fix knob sensitivity - DONE
GUI needs work (possibly add tabs to shrink the overall size) - DONE
currently, only midi channel 1 is used, add selector for other channels - DONE
improve waveform selector - DONE
add filter type selector - DONE
MichaelBenjamin ·
i dont own any of these, but the sid chip is by far my favoured digital synth to listen to and the music thats still being programmed for it is amazing, especially the newer tunes of the last ten years. its like a skateboard, so simple and so many tricks. plus its so limited you do not drown in possibilities. minimal music at its best.
edit i just looked at it, the sensitivity for the knobs seems much too high. one millimeter mouse movement covers the full range.
labelwhore ·
I thought I had the sensitivity for each of the knobs set to 1, is that not correct? what should I be using instead?
MegaHurtz ·
I like 0.08
labelwhore ·
MegaHurtz wrote: I like 0.08
lol awesome, I guess I thought the sensitivity setting related to something else. I made a crap ton of other changes last night, so once I fix the knobs I'll repost the osm.
MegaHurtz ·
Depends on the amount of steps for 4000, steps youd need around 0.05 but thats a lot of moving.
Tough I like having hughe ranges for controllers.
labelwhore ·
MegaHurtz wrote: Depends on the amount of steps for 4000, steps youd need around 0.05 but thats a lot of moving.
Tough I like having hughe ranges for controllers.
I'm using standard CC messages, so there's only 128 steps. That's why I chose 1, fractions of 1 don't really make sense. Unless of course I'm misunderstanding something.
MegaHurtz ·
I beleive it`s due to a ratio of smoothing.. So 1 is no smoothing compared to the mouse input.
trogluddite ·
labelwhore wrote: I thought I had the sensitivity for each of the knobs set to 1, is that not correct? what should I be using instead?
The sensitivity seems to relate to the range of the knob and the grid on the schematic background.
If sensitivity is 1 then moving one grid square (default 8 pixels) will move the knob all the way from the minimum to the maximum value. Likewise, a setting of 0.1 will take 10 grid squares (80 pixels) to get from min to max. Watch out if you use the DragY GUI primitive - pixels in the Y direction are counted top to bottom, so you need a negative sensitivity to make dragging upwards increase the knob towards max. Because it relates to pixels, your setting for mouse sensitivity in windows will also affect how your knobs interact.
labelwhore ·
I see, thanks for the explanation.
labelwhore ·
I updated the files in the first post. Everything should be working fully now 🙂
lukass ·
have you try adding preset manager?
labelwhore ·
lukass wrote: have you try adding preset manager?
Not to this, I don't really need it since the presets are stored within the hardware itself. I really just made this to facilitate automating the parameters that are available via standard CC messages.
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker