This is somewhat related to the missing presets in the Factory Folder - same problem of special symbols in the preset names goofing up the filesystem names, I think. Also, this is from 0.9.37 – I’ll grab the new one a little later today.
On the Librarian page:
Make a new user folder and select it. Drag all the Hardware Presets into the new folder (right column, click one, Cmd-A or Ctrl-A, drag over). Two presets never show up:
5.3 DI^tOR~ED BRA/S
6.6 SYNC/SNARE
So that would be bad if the user thought they were keeping a complete backup of their instrument.
Try dragging one of these over to a user folder by itself. It doesn’t cross over.
Double click on “Sync/Snare” 6.6 in the Hardware Presets column on the right, then click “Save As…” in the Preset Browser at the top. The default filename is just “SNARE”. No biggie.
Do the same with the “distorted brass” preset, 5.3. Its default name becomes “S”. (It chops off everything through the slash, trying to be helpful, but the OS file save panel would sanitize the file names appropriately, wouldn’t it?)
Separate issue, but still on the Librarian page: Select a user folder containing presets. They appear in the middle column. Delete the folder; it’s gone, but the presets are still displayed. The editor lets you try to manipulate them: rename, copy, paste, reveal in finder. A rename will popup a “couldn’t do that” error, but the other actions fail silently. Switching to some other folder will update the column as usual.
yes, same problem occured here too, I had a preset containing some symbols and it was impossible to copy to library.
This is logical, because the name of the preset is used as filename on disc.
One of many strange issues in the librarian … (I will make a list later …)
Bernard
edit:
in the new 0.9.39 editor, the slash / will be replaced by a # (and therefore can be copied).
However, ":;" will not be replaced, so the presetscontaining any of this, can’t be copied.
You probably already know all this, but on the Mac, a slash character in a filename is mapped to a colon character. The UI still shows it as a slash, but the name has a colon in it when viewed from the shell. And if you try to make a file with a colon in the name, the colon gets rewritten to a dash in the Save dialog before ever getting near the filesystem. FWIW.
IMHO the safest way to go about file names is to replace all characters which are neither alphanumeric nor simple dashes with underscores and not use the file name itself to actually store real information (like the preset name). As you have the preset name encoded in the sysex message anyway, there’s no need to use the exact name for the file. I’d also remove any duplicate, leading or trailing white spaces, since they can be confusing as well.
However, I still think the solution is not optimal: In the Librarian listings, any leadings spaces are omitted, therefore they sort completely different than in the directory listing (Finder, Explorer).
Also, when I tried to name a preset in the Editor with a weird name “T^st~Nämø .. /|\ `”, the Editor crashed right away. It wrote the Preset to the disk, but keeps crashing when I want to start the Editor when it tries to fetch that Preset from the Sub 37.
Hi,
I have load the zip and was not empty. It contains a folder with T^st~Nämø .. __
inside this folder there is a preset with the name `.syx.
This preset is also working.
I have no Crash.
Maybe I tried it on Windows 7.
Good luck and wish you a nice day.
Greetings Luloop
It’s not a hidden file on my Mac. Seems there’s a difference between Mac OS X10.9 and 10.11 regarding unpacking files with odd names from ZIP archives.
Anyway. In v0.9.41 the problem is still here, and can easily be reproduced.
Open Editor
create new Init Preset
Save As
Paste this name “T^st~Nämø .. /|\ `” (without the quotes) into the Save As dialog’s name field
