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
osm-fsm and triggers problems
osm-fsm and triggers problems
OSM --> FSM migration problem with triggers. Described/uploaded here:
http://synthmaker.co.uk/forum/viewtopic ... 12&t=11909
Just download the file and open in latest Flowstone.
I'm confused, where to put these cross-grade issues - on SM forum or here?
http://synthmaker.co.uk/forum/viewtopic ... 12&t=11909
Just download the file and open in latest Flowstone.
I'm confused, where to put these cross-grade issues - on SM forum or here?
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.
-
trogluddite
- Posts: 1730
- Joined: Fri Oct 22, 2010 12:46 am
- Location: Yorkshire, UK
Re: osm-fsm and triggers problems
Reply and schematic in the linked SM thread.
PS) e-mailed support with the 'broken' and 'fixed' schematics, and asked if there are any changes to the trigger flow that we need to know about.
PS) e-mailed support with the 'broken' and 'fixed' schematics, and asked if there are any changes to the trigger flow that we need to know about.
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!
Re: osm-fsm and triggers problems
Indeed I see no info in release changes/history, except maybe for this one: "Boolean properties were incorrectly sending a trigger when the properties were opened".
I think it could be a good idea to track cross-grade differences between SM and FS, to prepare folks for required changes in their projects. I noticed for example, that I had to update all editboxes, because the default font size is smaller now (from 1.2 to 1). Or the background color of exe's (default was black, now it's white). On the other hand - FS exports are more stable than from SM (no freezing on soundcard change when a lot of oscillators are operating).
I think it could be a good idea to track cross-grade differences between SM and FS, to prepare folks for required changes in their projects. I noticed for example, that I had to update all editboxes, because the default font size is smaller now (from 1.2 to 1). Or the background color of exe's (default was black, now it's white). On the other hand - FS exports are more stable than from SM (no freezing on soundcard change when a lot of oscillators are operating).
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.