RJHollins wrote:Tried to download and run .... got an 'Access Error'.
biilv wrote:I made that Pre-set manager a few years ago. It writes and reads to text file
billv wrote:I'm on XP.
I wonder if these might be related. I noticed that GreySynth automatically saves a small text file containing the current preset names at startup. For a plugin export, this gets saved in a 'GreySynth' folder alongside the plugin DLL; and from within FlowStone, it gets saved to the user's default VST export folder (wherever you last exported a VST plugin to, unless explicitly set by a 'VST Plugin Info' primitive in the schematic.)
Later Windows versions are far more fussy than XP about which folders applications are allowed access to, even if you're logged in as an Administrator, so this might be causing problems writing to the folder (or its parent folder may not exist). Everything works fine on my Windows 10 machine running FS 3.0.6, where I keep my shared plugins in a separate 'all-access' drive partition. However, the canonical VST plugins folder is usually somewhere within 'Program Files', to which access will be restricted.
To test this, here's a version which defaults to the schematic folder rather than the VST plugins folder when you're working within FlowStone (just one primitive added - a 'Schematic File Path' to set the 'Test' folder of the 'Start Folder' primitive within 'Preset Manager_BV/Save_Load/File save'.)
NB) This may not be a complete fix - it's just intended to test whether my hypothesis about the access error is right.