SynthMaker

Code component lock (SDK replacement)

Archive · 2005 5 old posts

From the original SynthMaker forum (2004–2014), with its members’ names and dates.

Nu Audio Science ·

I asked about an SDK the other day but it seems the complexity involved because of the per sample calculations is enormous, On reflection it isn't actually needed at all, The code component is all that is needed, Obviously it needs to be advanced a bit more but the guys have already stated elsewhere that that will happen.

What is needed though is a way to put a lock on a code component, This could be set up so that with a keypress a duplicate of the selected code component was created but without the text editor interface and showing non of the code, In effect it would look just like any other component.

What is the point of this you ask, Well i know comparisons with SE aren't really relevant with most things SM but here it is, SEs SDK brought us

UNKARGHERTH - We all know this name here now and he made some great modules for SE but they were all free i think, These included delays some really nice filters and a Freeverb module he built in conjunction with Dhaupt.

DHAUPT - Dave creates unbelievable ammounts of modules that completly changed the way SE looked literally, His GUI modules stopped SE plugs looking like SE plugs, His utility modules are great as are all of his modules, While dave creates a huge range of free modules he also spends extra time on creating some really stunning Donationware modules for a very very small fee (He has about ten times as many free modules as pay modules though)

CHRIS KERRY - Chris creates some stunning very low CPU modules covering most things, He creates most of his stuff in asembler so it is very efficient, Chris is also on a donationware scheme at a very small cost.

There are a lot of others i haven't mentioned but these guys were the first big hitters as it were, At one stage i think every single plugin out there had a CK module in it 🙂

Pulling coders like these into SM would be great for the community and just help to bring more people in, Now quite a few coders would prefer for you not to see their code even on free stuff (Perfectly OK by me) and if they wanted to make donationware components obviously showing the code is a no no and that is where this idea stems from, A very simple thing to achieve i would say, Obviously at the moment this isn't too relevant but as the code component becomes more and more advanced i think this is a perfect way to offer third parties the ability to develop free or comercial hassle free, Think about it, Write the code press a button to duplicate and collapse and save as OSM and the component is ready 🙂

Nu Audio Science ·

Just as a quick example Dhaupt created a custom unreleased SF2 loader for the plugin below, It actually allowed you to load a SF2 bank or instrument directly and included some mapping ability, The controls on the plugin controlled the synth completly, Nothing special right ? WRONG it wasn't loading the SF2 into the plugin but directly onto a Sounblaster Live or Audigy 🙂 , Absolute zero CPU hit for 64 note polyphony and 16 part multitimbrality , I also added in a few controls for the KX project, We may release it in the future but were not sure yet (Some GUI tidying issues and so on)

PS A lot of people said this couldn't be done 🙂

Tom7777 ·

If you get a feature like this then you should be able to set a label also that cannot be edited becuase like everything you get the people that like to digitally steal things and say "i made this" when they did not so i think that a name label would need to be added so credit could be given each time the modules were used. Although this would make somethings pointless as certain code requires slight mods to run well depending on where it is placed in a schematic. Its a good idea though, it sounds like you want SM to steal all of the best SE users 🙂 Im sure that good things would happen but at the end of the day its there choice what apps they want to use. SM being by far the best of course 🙂

Nu Audio Science ·

Some SE users just wont come until they can do there thing as it where. This would help, I agree though an about box with name and so on would be ideal.

Nu Audio Science ·

Just wanted to add to this

Put something in the code component so that devs could release a demo version that popped up a little screen saying uses demo code by such and such, So payed for code could be tryed out before buying.

[demo=Contains code by NAS(Yeah right 😀 )] It could be that simple

Wrote something here? To have a post removed or your name hidden, write to [email protected].

Before your first post

A few rules keep this a friendly place. You agree to them once.

Shown next to what you post, here and in the app. It doesn’t have to be your real name: 3–24 lower-case letters, digits or _ (capitals become lower case, spaces become _).

    Then your post goes up straight away.

    Delete this reply?

    Open it in SynthMaker?

    It goes on the track you’re editing there, in place of that track’s sound, and into My sounds. Your other tracks stay as they are.

    Want to keep that track’s sound? Start a new song in SynthMaker first (Song › New song), then open this.

    Report this reply?

    Only the developer reads reports. The person isn’t told who reported them.

    What’s wrong with it?

    Block this person?

    You won’t see their posts and replies here any more. They aren’t told, and you can unblock them at any time.

    People you’ve blocked

    Their posts and replies are hidden from you. Unblock someone to see them again.

    The community rules

    A few rules keep this a friendly place. Everyone agrees to them once, before their first post.