SynthMaker

Click Env Problem (New Env!)

Archive · 2008 9 old posts

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

kirkagur ·

Hi Every One!

I need help to make my env not to click when re triggering a voice and the env is still running. the deal is i need it to be sharp as a knife or in other words in sample rate 😀

the env is an point to point env and you can add or remove points any where! thank to MyCo. AND if any one wants to make improvements .......... 🙂 🙂 🙂 🙂

thank you in advance!

OSM

oddson ·

A zero-attack envelope will click unless the sound has a lot of high-frequency content -- where the click tends to get masked by the upper frequency component. That's just what you hear when there is a jump in the signal that's not typical of the rest of the signal. You can low-pass the envelope signal or you can impose a minimum attack time or you can have clicks but you can't have 1/SR attack time and not have a click unless there is a lot of signal in the very high end.

kirkagur ·

the click appears when the env is in high gain and the new trigger jumps it back to 0 in 1 samp how can i make it release (1ms) and then attack ?

oddson ·

😕 At first I thought it was just the problem of a zero attack but now that I've looked more at it more I have no idea what's going on in there.

kirkagur ·

oddson wrote: 😕 At first I thought it was just the problem of a zero attack but now that I've looked more at it more I have no idea what's going on in there.

i cant explain myself very good in English.... 😊 😊 😊 😀

the idea is: 1.a ramp drives the wave with the FA2P (point to point (interpolation?)) . 2.the ramp progress at the attack stage is limit by the sus point. 3.when release the ramp progress Continus until the end of the wavtable. 4.at the end it sends kill message to the Env (primitive) .

hope you understand it better ,because i dont know how to sort the problem. 😕 i think that its something with the fast release in the Env (primitive)

at the end you will be able to modulate this attack&release times. its have a great effect (and looping,osc,lfo).

and thanks so far.

kirkagur ·

oddson wrote: A zero-attack envelope will click unless the sound has a lot of high-frequency content -- where the click tends to get masked by the upper frequency component. That's just what you hear when there is a jump in the signal that's not typical of the rest of the signal. You can low-pass the envelope signal or you can impose a minimum attack time or you can have clicks but you can't have 1/SR attack time and not have a click unless there is a lot of signal in the very high end.

You right about this stuff !!!!

i added attack env (in sample rate) and there is no more clicks !!! 😀 🙂

thanks!

oddson ·

There is at least one other problem with it... if you gliss through a full range of notes (32 or more) all the voices will remain active indefinably. You can see this as CPU usage goes up (to about 10% on my machine) and does not come back down.

With the Env Control primitives hold boolean input set to 'False' this no longer happens. This seams to suggest your kill polyboolean output is not working.

BTW- a simple low-pass on the envelope's output will prevent clicks but uses CPU all the time.

kirkagur ·

oddson wrote: There is at least one other problem with it... if you gliss through a full range of notes (32 or more) all the voices will remain active indefinably. You can see this as CPU usage goes up (to about 10% on my machine) and does not come back down.

With the Env Control primitives hold boolean input set to 'False' this no longer happens. This seams to suggest your kill polyboolean output is not working.

BTW- a simple low-pass on the envelope's output will prevent clicks but uses CPU all the time.

I notice that too!!!!! thanks! 😀

here is the results for this topic.........for now. Low Cpu ASR Env ! that sounds 1,000,000$ 😀 (this one close the voice when finish 😀 )

OSM

aliasant ·

Very Nice Stuff!. Thanx. Comes in handy in my synth project I think.

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.