Support

If you have a problem or need to report a bug please email : support@dsprobotics.com

There are 3 sections to this support area:

DOWNLOADS: access to product manuals, support files and drivers

HELP & INFORMATION: tutorials and example files for learning or finding pre-made modules for your projects

USER FORUMS: meet with other users and exchange ideas, you can also get help and assistance here

NEW REGISTRATIONS - please contact us if you wish to register on the forum

handling triggers and gate with code component

For general discussion related FlowStone

handling triggers and gate with code component

Postby NightmareDream » Sun Jun 02, 2013 6:29 am

i'd try to fix the clicking i get in my sound and empty the buffer softly... With some trigger gate combinaison that could just make sure the note is killed and softly released... I really don't get "why" but when i bought my new computer, it ran really softly but after the latest flowstone(FL) updates it became unstable again... It is really surprisingly unpredictable to work with it... Sometimes it is soft, sometimes it clicks from i cant figure out where, the polyphonic notes doesn't clean themselves and stacks up into memory until there is an overflow of notes that messes themselves together and prevent some from embarking. To audibly isolate the clicking sound, i shut all envelopes. Still clicks. It stops clicking when i unconnect oscillators. Whatever the point i connect the output of oscs, the clicking sustains. Sometimes, it will click when the oscs are disconnected also. I really feel like the midi freq data passes throught and ghostly make feedback - backward signals or something. It really feels like backward signals but i can't figure out how to clean them since a few years already. Yet, i managed to perfect most other aspects which is great :)
The envelope *could end elsewhere than zero but even with suggestions reading and all i still can't figure out how to apply a clever fix... I use a lot of selectors. I use some selectors to mute channels but this also seems to let some signals throught at some moments... I must find cleverer ways to handle this too... :P

So well... Any way i could fix around the existing envelopes and anything else with using triggers and gate in a separate module and have it to kill notes before they stick in memory?
NightmareDream
 
Posts: 2
Joined: Mon Dec 20, 2010 11:58 pm

Re: handling triggers and gate with code component

Postby MyCo » Sun Jun 02, 2013 9:46 am

I've never heard of such a problem... even some thousand users of my plugins never reported something like this.

Schematic? When there's something wrong with in your project, how can we find it without investigating?

Just a blind guess: Have you set the "hold" options in your envelopes right? Hold should only be checked in the Volume Envs but not in the Modulation Envs(for Filter or other params).
User avatar
MyCo
 
Posts: 718
Joined: Tue Jul 13, 2010 12:33 pm
Location: Germany


Return to General

Who is online

Users browsing this forum: No registered users and 78 guests