Show extension in file loaders

[38github]

I am using a plugin that can load both .nam and .wav files and Pipedal puts all these together. Do you have any idea how to differenciate these from each other in the listings or may an icon to the left of them, like a square, with the extension in it be something that is doable?

[maarthome]

Hi @38github,

Which plugin is that?
With AIDA-X I can load also both... model and IR files.

For that I created separate linked directories:

It becomes a little bit 'messy' but at least not everything is in the same directory when selecting.

Cheers,
Maarten

[38github]

I use Ratatouille. Maybe I have missed that I can navigate through different folders. I will look into that. Thank you!

[maarthome]

Hi, I is not navigating, it is creating links to directoriess where the model and IR files are located using symbolic or hard links....

Cheers,
Maarten

[maarthome]

Here I am again,

i see that ratatouille puts everything in one directory....
But in the selection window it filters on extension....
That is workable?

Cheers,

Maarten

[38github]

Yes, filtering would be really good! Tack!

[rerdavies]

@maarthome:

The directories you are simlinking to... Where are they located, and who/what created them? Did you create separate directories for IR files and models? Are there separate directories for .nam, .json, and .aidx files?

[rerdavies]

@maarthome

Nvm. I see the sources for your simlinks. Could you do me a very great favor, and run the following commands for me.

      grep -r --include "*.ttl"  ROOT_DIRECTORY_OF_YOUR_LV2_PLUGINS

     find ROOT_DIRECTORY_OF_YOUR_MEDIA_FILES -type d 

[rerdavies]

Looking at both plugins now. Doing this right is going to be complicated. :-/

Does anyone have other examples of plugins that use file path properties?

The outcome is really going to depend on how consistently plugins indicate what file types they expect using an extended attribute from the MOD project (mod:fileType). Ratatouille, apparent does use the mod:fileType extension. The current version of Mike's NAM also uses the mod:fileType extension, although previous versions did not. I'll get back to you with a draft spec for a better implementation to see what you think.

Likely features:

• shared directories for audio files/
• shared directories for .nam/.nammodel files.
• per-plugin Isolated directories for .json files (Toom ML/Proteus).
• per-plugin isolated directories for everything esle.
• File extensions displayed.
• Filtering by extension,
• A migration tool for existing media files. presets and banks (with the ability to revert).

Per-plugin isolated directories for everything else.

[rerdavies]

Just as an aside, to perhaps provide useful context in this conversation, one of the features that recently went in to PiPedal (actually v1.3.53, but first announced in v1.3.54) :-/

No more splatting of huge number of files into the root upload directory. Uploaded .zip files always get a containing directory (either the root directory of the zip file, or the name of the zip file itself.

That doesn't in any way fix the problems you're having. But it at least makes it easier to not commingle .nam and .wav files in the same directory, which reduces your suffering slightly.

[maarthome]

Hi Robin,

grep -r --include ".ttl" /usr/lib/lv2 -> did not result in anything....
so I did.... grep -r --include ".ttl" . (while in .usr/lib/lv2)

Pipedal.zip

Hope it is of some use,

Maarten

[rerdavies]

Exactly what I needed. Thanks.