PWESynthMaker Projects
Posted: Fri Oct 27, 2023 6:14 pm
PLEASE TAKE THE TIME TO READ THIS FOLOWUP FOR THE BENEFIT OF "FLOWSTONING" AT ITS BEST!
NOTE: All PWESynthmaker FSM (FlowStone Schematics) Files are created with Flowstone v3.0.6 'Pebble'
including 'standalone executable' effects/instruments for legacy compatibility.
Executables are also created with v3.0.6
There are optionally 3 .fsm schematic versions with different file names.
The main container module ID tag name (top left corner) for all three is the same.
The three different actual filenames *.FSM are each for specific different use.
EXAMPLES:
FlowStone Schematic filename_tst.fsm
This schematic file normally has audio/midi in/out connectors and addtional
test equipment mods for realtime testing within the Flowstone Program.
FlowStone Schematic filename_vst.fsm (or "_vsti.fsm" for midi instruments)
This schematic .fsm file has been re-sized to allow fit within a host DAW
(Digital Audio Workstation). Large modules are significantly reduced to maintain
visibility of and accessibility to a host DAW controls.
FlowStone Schematic filename_exe.fsm (for export as standalone executable).
MPORTANT!
With the exception of an additional folder named "v3.06x86_32bit"
containing one legacy VST2 .dll exported with Flowstone v3.0.6 'Pebble'
all other VST2 and VST3 Plugins (both 32bit & 64bit *.dll and *.vst3)
are now exported with FlowStone Alpha v3.0.9b2-3484-g7792583 ...
The files are not modified or saved in the Alpha version, only exported as
plugins. This allows re-opening same in v3.0.6 or higher.
Updated VST & VSTi Plugins with significant changes are created with
new 32-bit ID (4-character alpha-symbol-numeric format) for VST2s.
Also, a new GUID is generated for VST3s.
BEFORE REPLACING AN OLDER VERSION VST/VSTI PLUGIN:
It is advisable to backup the previous version of a plugin by storing it in a separate
folder inaccessible to the DAW's plugin scanner (such as "Documents").
Then replace the old with new rather than overwriting the old version.
This will ensure a 'new vst scan' is accepted in most DAWs and in the event of
non-functionality the previous version can then be reverted to.
USE THIS METHOD ALSO FOR NEW INSTALLED STANDALONE EXECUTABLES.
NOTE: All PWESynthmaker FSM (FlowStone Schematics) Files are created with Flowstone v3.0.6 'Pebble'
including 'standalone executable' effects/instruments for legacy compatibility.
Executables are also created with v3.0.6
There are optionally 3 .fsm schematic versions with different file names.
The main container module ID tag name (top left corner) for all three is the same.
The three different actual filenames *.FSM are each for specific different use.
EXAMPLES:
FlowStone Schematic filename_tst.fsm
This schematic file normally has audio/midi in/out connectors and addtional
test equipment mods for realtime testing within the Flowstone Program.
FlowStone Schematic filename_vst.fsm (or "_vsti.fsm" for midi instruments)
This schematic .fsm file has been re-sized to allow fit within a host DAW
(Digital Audio Workstation). Large modules are significantly reduced to maintain
visibility of and accessibility to a host DAW controls.
FlowStone Schematic filename_exe.fsm (for export as standalone executable).
MPORTANT!
With the exception of an additional folder named "v3.06x86_32bit"
containing one legacy VST2 .dll exported with Flowstone v3.0.6 'Pebble'
all other VST2 and VST3 Plugins (both 32bit & 64bit *.dll and *.vst3)
are now exported with FlowStone Alpha v3.0.9b2-3484-g7792583 ...
The files are not modified or saved in the Alpha version, only exported as
plugins. This allows re-opening same in v3.0.6 or higher.
Updated VST & VSTi Plugins with significant changes are created with
new 32-bit ID (4-character alpha-symbol-numeric format) for VST2s.
Also, a new GUID is generated for VST3s.
BEFORE REPLACING AN OLDER VERSION VST/VSTI PLUGIN:
It is advisable to backup the previous version of a plugin by storing it in a separate
folder inaccessible to the DAW's plugin scanner (such as "Documents").
Then replace the old with new rather than overwriting the old version.
This will ensure a 'new vst scan' is accepted in most DAWs and in the event of
non-functionality the previous version can then be reverted to.
USE THIS METHOD ALSO FOR NEW INSTALLED STANDALONE EXECUTABLES.