De-Threader/ Trigger Limiter question
Posted: Thu Nov 28, 2013 12:03 pm
Question for the Gurus ...
Managing 'triggers' throughout a schematic has been something I've tried to stay mindful of.
In the 'toolbox', I have 2 modules ... 'De-threader' and 'Trigger Limiter 25Hz'.
Curious ... I looked inside the 'De-threader' module and noticed that there is a 'Tick 100' clock inside
It is then I looked at this 'Trigger Limiter 25Hz', and sure enough, it had a 'Tick 25' clock
I've been using the Tick 100 De-threader in many parts of my schematic, and never gave it much thought .... until now
I tested both modules in a schematic section, and both of them performed ... so now I wonder ...
Am I wasting resources using the Tick 100 version ?!?
To clarify, I'm not using these 'de-threaders' in any streaming audio section ... I'm mainly dealing with data arrays [strings, numbers, etc].... and I could easily have 50 or 100+ of these throughout a schematic.
What's the potential impact ???
Thanks!
Managing 'triggers' throughout a schematic has been something I've tried to stay mindful of.
In the 'toolbox', I have 2 modules ... 'De-threader' and 'Trigger Limiter 25Hz'.
Curious ... I looked inside the 'De-threader' module and noticed that there is a 'Tick 100' clock inside
It is then I looked at this 'Trigger Limiter 25Hz', and sure enough, it had a 'Tick 25' clock
I've been using the Tick 100 De-threader in many parts of my schematic, and never gave it much thought .... until now
I tested both modules in a schematic section, and both of them performed ... so now I wonder ...
Am I wasting resources using the Tick 100 version ?!?
To clarify, I'm not using these 'de-threaders' in any streaming audio section ... I'm mainly dealing with data arrays [strings, numbers, etc].... and I could easily have 50 or 100+ of these throughout a schematic.
What's the potential impact ???
Thanks!