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
Problems: Graphical, Creating VST, Bypass
1 post
• Page 1 of 1
Problems: Graphical, Creating VST, Bypass
My flowstone behaves very irregular. Working all well in the Flowstone environment, in worst case flowstone crashes while creating a vst.
Maybe anyone knows this behavior.
At the beginning all works well, the komplexer the program gets the more problems I have with Flowstone.
Example: I tried to build a stereo meter with ruby beginning to take one of Flowstones own meters and changing and adding things. For each change I copied the old module and put it into the same .fsm. Then I change something in the new module. This works a while. Suddenly flowstone has problems to create a working vst. Then also the older modules (which worked before) in the .fsm have problems to create a working vst. In the stereo meter module the result (in my DAW) was that only the left meter shows values, the right one does not work (but in Flowstone it works normal). I put two entries in one Ruby element and different calculations that displays two meterbars. Can Ruby handle this? Or should it be two Ruby elements for two meters? As I saw, my problems are in the moment only visual ones, the audio works. The only thing that made problems from the beginning was that the vst created with flowstone easily crash in the DAW after pressing "Bypass", then the vst completely crashes.
Maybe anyone knows this behavior.
At the beginning all works well, the komplexer the program gets the more problems I have with Flowstone.
Example: I tried to build a stereo meter with ruby beginning to take one of Flowstones own meters and changing and adding things. For each change I copied the old module and put it into the same .fsm. Then I change something in the new module. This works a while. Suddenly flowstone has problems to create a working vst. Then also the older modules (which worked before) in the .fsm have problems to create a working vst. In the stereo meter module the result (in my DAW) was that only the left meter shows values, the right one does not work (but in Flowstone it works normal). I put two entries in one Ruby element and different calculations that displays two meterbars. Can Ruby handle this? Or should it be two Ruby elements for two meters? As I saw, my problems are in the moment only visual ones, the audio works. The only thing that made problems from the beginning was that the vst created with flowstone easily crash in the DAW after pressing "Bypass", then the vst completely crashes.
- moppen
- Posts: 5
- Joined: Sat Aug 29, 2015 12:14 pm
1 post
• Page 1 of 1
Who is online
Users browsing this forum: Majestic-12 [Bot] and 63 guests