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
Ruby Ticker behaving badly
-
Perfect Human Interface
- Posts: 643
- Joined: Sun Mar 10, 2013 7:32 pm
Ruby Ticker behaving badly
More observations (hoping someone actually finds this useful and I'm not just annoying everyone spamming the forums):
I've been doing loads of testing with triggers and tickers lately, and one thing I've noticed with the Ruby Custom Ticker and my stuff based on it is that, despite normally being a very time-accurate ticker, it seems to be able to get into a state where it loses accuracy after a while. Meaning it may tick slightly slower or faster. The numbers I get start going off. If I save the project and then reload it, then everything is dead on again. Not sure if it will just do this on it's own over time while running in a schematic or not (it's difficult to test), but it's something to consider if you use these.
Other thing I found out just now: I put one of the stock Custom Tickers into a current plugin project and set it to .01 sec (100/second). We all know that ruby is rather slow and the faster you set this thing the more it eats CPU. But while just switching this on at this somewhat reasonable setting doesn't cause a big hit to CPU, as soon as I go to the plugin's top panel where all the drawing is going on (and there's a good amount of it) the CPU meter in FL Studio jumps up from 1 to 7-8. The ticker isn't even connected to anything, it's just in the schematic somewhere and turned on. Note though that the Task Manager CPU doesn't seem to be effected significantly.
I've been doing loads of testing with triggers and tickers lately, and one thing I've noticed with the Ruby Custom Ticker and my stuff based on it is that, despite normally being a very time-accurate ticker, it seems to be able to get into a state where it loses accuracy after a while. Meaning it may tick slightly slower or faster. The numbers I get start going off. If I save the project and then reload it, then everything is dead on again. Not sure if it will just do this on it's own over time while running in a schematic or not (it's difficult to test), but it's something to consider if you use these.
Other thing I found out just now: I put one of the stock Custom Tickers into a current plugin project and set it to .01 sec (100/second). We all know that ruby is rather slow and the faster you set this thing the more it eats CPU. But while just switching this on at this somewhat reasonable setting doesn't cause a big hit to CPU, as soon as I go to the plugin's top panel where all the drawing is going on (and there's a good amount of it) the CPU meter in FL Studio jumps up from 1 to 7-8. The ticker isn't even connected to anything, it's just in the schematic somewhere and turned on. Note though that the Task Manager CPU doesn't seem to be effected significantly.
Re: Ruby Ticker behaving badly
It's because ruby depends on FS and ruby, while standard (green) ticker depends only on FS?
Need to take a break? I have something right for you.
Feel free to donate. Thank you for your contribution.
Feel free to donate. Thank you for your contribution.