Hello, when I have samples which may be used in a project, I put them in a "samples" project with their original name under that specific project folder. that means it is already sorted when first downloaded, and if some more information on the source is needed, I'll add a text file with the information. Later on, the folder is cleaned up if some samples are finally not used. As for a stock of samples, the folders will often have the name of the source (website, or author's name), with a text file detailing licences. Raphaël Le 14 oct. 2016 à 13:53, Dave Phillips <dlphillips@xxxxxxxxxx> a écrit : > Greetings, > > On 10/14/2016 07:38 AM, jonetsu wrote: > >> I guess that it would be possible to run a script an extract sfinfo data for each single file and construct a database with the filenames and sffile data and occasional notes about the files... Or if a file manager allows hooks, to add a sfinfo hook. > > Thanks, that gave me an idea. I might be able to customize a lightweight file manager to do some of what I want. > > I think that what I'm looking for is a standalone version of the file management found in Ardour, Bitwig, or Rosegarden, complete with waveform display, playback option(s), and a display of metadata and other file data (e.g. as reported by sfinfo). > > Best, > > dp > > _______________________________________________ > Linux-audio-user mailing list > Linux-audio-user@xxxxxxxxxxxxxxxxxxxx > http://lists.linuxaudio.org/listinfo/linux-audio-user _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
