I have had a problem for years: I like to use samplers, and also to rename / reorganize my samples. These two things don't really go together... renaming or moving a file means the sampler can no longer find it.
Well, tonight I had a simple idea: use MacOS file aliases! I can create an alias to my sample, and put the alias in a place where it never gets renamed or moved. Then I can move the original sample anywhere I want, rename it, etc. Note: These are the aliases created in Finder by using cmd-opt when dragging a file. They're different from symlinks - they connect an alias to an actual file on disk, as opposed to another path.
This approach works great! On Falcon, anyway... it stores a reference to the alias path, resolves it perfectly, and I can move the original file around without breaking anything.
MSF, on the other hand, gives me this error:
So here's my request: please allow MSF's sampler module to read MacOS Finder aliases. And it should keep the path to the alias, rather than the original.
Request: Let MSF sampler use MacOS aliases as sample sources
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122 - KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Well, to be honest, I don't like the idea, but I'll check. I assume you mean symlinks, right? It's actually surprising it doesn't load it in the first place, macOS should resolve that automatically, hmmm
Anyways I'd recommend putting all plugins in the single sample path, which you set as sample root in the setings or downloader and whenever you move it, you just change that one path and you are done!
Anyways I'd recommend putting all plugins in the single sample path, which you set as sample root in the setings or downloader and whenever you move it, you just change that one path and you are done!
-
- KVRian
- Topic Starter
- 754 posts since 27 Nov, 2011
No I mean Finder aliases. They are similar to symlinks but not the same. It’s what happens when you hold cmd-alt while dragging a file.
The problem with your suggestion (as I understand it) is that I’m not just changing the path of my sample library. I’m talking about changing the file name and paths of specific samples. So I start with “samples/distorted bass.wav” and over time that same sample moves to “samples/bass/distorted/E1 grunge bass.wav”.
With aliases I can create a fixed folder structure of aliases that don’t move, but I can reorganize and rename the source samples however I want.
The problem with your suggestion (as I understand it) is that I’m not just changing the path of my sample library. I’m talking about changing the file name and paths of specific samples. So I start with “samples/distorted bass.wav” and over time that same sample moves to “samples/bass/distorted/E1 grunge bass.wav”.
With aliases I can create a fixed folder structure of aliases that don’t move, but I can reorganize and rename the source samples however I want.
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
I understand now. Sadly this would need a hell of a lot of changes and testing... at some point it will probably naturally work, but who knwos when.