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
Accuracy of Ticks and Timers
8 posts
• Page 1 of 1
Accuracy of Ticks and Timers
Hello,
Just decided to check whether it makes sense to replace Timer component (the green one used for trigger delays) by Ruby delay.
So the first question - does both ways has the same accuracy?
Checking this in schematic I've detected that 1 ms delay leads to much higher delay (depending on set latency/buffer size of ASIO).
(schematic attached)
Concerning accuracy of Ruby timing: If it is really accurate, then with a period of 1 second the time of incoming trigger in the schematics hould be changed with each new trigger only in "integer area", but actually there is variance also in ms (up to 20ms).
So is it true, that Ruby timer with 0.001 step will provide ticking with 1ms period? or there will be something like this:.....!....!..!......!..!...!.... ?
Just decided to check whether it makes sense to replace Timer component (the green one used for trigger delays) by Ruby delay.
So the first question - does both ways has the same accuracy?
Checking this in schematic I've detected that 1 ms delay leads to much higher delay (depending on set latency/buffer size of ASIO).
(schematic attached)
Concerning accuracy of Ruby timing: If it is really accurate, then with a period of 1 second the time of incoming trigger in the schematics hould be changed with each new trigger only in "integer area", but actually there is variance also in ms (up to 20ms).
So is it true, that Ruby timer with 0.001 step will provide ticking with 1ms period? or there will be something like this:.....!....!..!......!..!...!.... ?
- Attachments
-
- wtf.fsm
- (6.89 KiB) Downloaded 1422 times
- user_fm
- Posts: 8
- Joined: Sat Dec 24, 2011 5:55 pm
Re: Accuracy of Ticks and Timers
Well i also posted a question about that and the reply i got was verry simple:
If you do something with grenn Triggers it is not accurate. It will be only accurate if you do it within ruby modules.
If you do something with grenn Triggers it is not accurate. It will be only accurate if you do it within ruby modules.
100% accuracy is the guarantee to your success. The value alters if you combine it with musical creativity.
-
chackl - Posts: 233
- Joined: Tue Aug 17, 2010 8:46 pm
- Location: Austria / Salzburg
Re: Accuracy of Ticks and Timers
Thanks, chackl
That's terrible.
That's terrible.
- user_fm
- Posts: 8
- Joined: Sat Dec 24, 2011 5:55 pm
Re: Accuracy of Ticks and Timers
Indeed, it is that simple: Ruby values and MIDI use the new event system to pass values, everything else uses the trigger system as before.
So you need to keep time critical elements within MIDI or Ruby Value sections of schematic to preserve timing accuracy. Not everything needs this kind of accuracy so those sections will probably be quite small though there's nothing to stop you doing everything in Ruby using the events system if you want to.
I've attached an adjusted version of your schematic that keeps everything in the events system. As you can see, the timing difference is preserved extremely well.
So you need to keep time critical elements within MIDI or Ruby Value sections of schematic to preserve timing accuracy. Not everything needs this kind of accuracy so those sections will probably be quite small though there's nothing to stop you doing everything in Ruby using the events system if you want to.
I've attached an adjusted version of your schematic that keeps everything in the events system. As you can see, the timing difference is preserved extremely well.
- Attachments
-
- wtf explained.fsm
- (7.28 KiB) Downloaded 1482 times
-
support - Posts: 151
- Joined: Fri Sep 07, 2012 2:10 pm
Re: Accuracy of Ticks and Timers
Thanks, support, that's just the kind of example I've been looking for to get this clear in my head.
All schematics/modules I post are free for all to use - but a credit is always polite!
Don't stagnate, mutate to create!
Don't stagnate, mutate to create!
-
trogluddite - Posts: 1730
- Joined: Fri Oct 22, 2010 12:46 am
- Location: Yorkshire, UK
Re: Accuracy of Ticks and Timers
Clock Accuracy
If you have any of the DirectSound or ASIO primitives in your schematic and these are switched on
then the clock will automatically switch to run in sync with the audio processing. You can then schedule
events to occur with sample precise timing within any audio frame.
but this is also valid for the vst?
If you have any of the DirectSound or ASIO primitives in your schematic and these are switched on
then the clock will automatically switch to run in sync with the audio processing. You can then schedule
events to occur with sample precise timing within any audio frame.
but this is also valid for the vst?
- Tronic
- Posts: 539
- Joined: Wed Dec 21, 2011 12:59 pm
Re: Accuracy of Ticks and Timers
Yes Tronic, it uses the callback from the audio host in that case.
-
support - Posts: 151
- Joined: Fri Sep 07, 2012 2:10 pm
8 posts
• Page 1 of 1
Who is online
Users browsing this forum: Google [Bot] and 50 guests