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
Users are reminded of the forum rules they sign up to which prohibits any activity that violates any laws including posting material covered by copyright
Selector delay
-
dentistguba
- Posts: 13
- Joined: Thu Jan 10, 2013 8:39 pm
Selector delay
I have been looking into setting up an effect shutoff when input and output are below a threshold to save cpu and it seems the only way to do it without doing a lot more in ASM (will be trying that approach once i learn it a bit more) is to use the selector primitive. However, any sounds with a sharp attack are cut off before the effect is connected again (i'm guessing the recompilation is the culprit, green trigger inaccuracy could be a factor too though), a quick fix being to delay the input by somewhere between 500-1000 samples (@44100hz). Obviously for a waveguide already built out of delays that isn't ideal for playability.
I would like to know whether there is any chance of a feature being added which would either allow sample accurate switching or maybe some kind of basic core module which, when turned on, will stop running a plugin when no sound is coming in or out.
I would like to know whether there is any chance of a feature being added which would either allow sample accurate switching or maybe some kind of basic core module which, when turned on, will stop running a plugin when no sound is coming in or out.
-
dentistguba
- Posts: 13
- Joined: Thu Jan 10, 2013 8:39 pm
Re: Selector delay
I have thought further on the issue and some other options would be:
a) to allow precompilation of a section of the scematic into an ASM block so you can hop the whole thing
b) to create 'hop' and 'hop to' modules which are used to encapsulate a section and accept, say, a boolean to determine on or off, this would be more flexible but still ideal for visual programming.
a) to allow precompilation of a section of the scematic into an ASM block so you can hop the whole thing
b) to create 'hop' and 'hop to' modules which are used to encapsulate a section and accept, say, a boolean to determine on or off, this would be more flexible but still ideal for visual programming.