Put an illegal filename character (like in my case, a colon) into a VST preset
name, and it fails on the first run, attempting to create a filename exactly
the same as the VST preset names.
VST 2.4 has no stipulation that the program names need to be valid filenames.
Any characters are allowed in them. You'll probably want to add some
translation or at least filtering of illegal characters when generating the
.aupreset filenames.
I replaced the colons in my preset program names with dashes and now it works
fine. (Though I wish I still had the colons!)
Symbiosis version 1.3
Here's what auval -a showed where it failed, and a few preceding lines. Mac OS
error code -37 is "bad filename", so I should have known. But it took me about
6 hours to finally clue in as to what was happening. Live and learn... :)
[AdmiralQuality: Poly-Ana](0xa080d540) VST getCurrentProgramName
[AdmiralQuality: Poly-Ana](0xa080d540) VST setCurrentProgram: 0
[AdmiralQuality: Poly-Ana](0xa080d540) Bundle retain count before releasing: 3
[AdmiralQuality: Poly-Ana](0xa080d540) Bundle retain count before releasing: 2
[AdmiralQuality: Poly-Ana](0xa080d540) Caught Mac OS exception in
SymbiosisEntry: Mac OS error code -37
[AdmiralQuality: Poly-Ana](0xa080d540) AU kComponentCloseSelect
Cannot open component: -37
Original issue reported on code.google.com by AdmiralQuality@gmail.com on 16 Jul 2014 at 1:28
Original issue reported on code.google.com by
AdmiralQuality@gmail.comon 16 Jul 2014 at 1:28