it would be nice if you could allocate a folder for all .mini files to be placed. this would keep things nice and tidy within audio file/sample folders.
In theory a good idea. There are some practical issues like: How are the mini files associated with identical named files from multiple folders. Should the mini filename be encoded with the full path of the sound file, or should subfolders be created within the mini folder. In both cases it can be a nightmare to maintain the mini folder, and to validate it against moved sound files etc.
But perhaps a configurable mini folder could be used as a mini file storage for sound files located outside the project folder. That way you can still move your project folders around without having to redo the mini files.
hi frits 🙂 is a .mini file fulfilling the same purpose as a reaper peaks file? they have an option to store all reapeaks files in one folder. does a .mini file differ in any way? if you did move the audio file to a new location would a new .mini file be created the next time the project is opened? this seems to be what happens with reaper (could be wrong). sorry for all the reaper comparisons! its just that the way they do it with reaper peaks files gave me the idea of the feature request.
@bladerunner wrote:
is a .mini file fulfilling the same purpose as a reaper peaks file? they have an option to store all reapeaks files in one folder. does a .mini file differ in any way?
They probably are comparable.
if you did move the audio file to a new location would a new .mini file be created the next time the project is opened?
If a mini file is not found, it will be regenerated when the sound file is loaded in the project.
@Zynewave wrote:
In both cases it can be a nightmare to maintain the mini folder, and to validate it against moved sound files etc.
the way i think of it (and of course put me right if i have it all wrong 😉 ) there wouldn’t be any need to maintain the allocated folder would there? it wouldn’t bother me at all if lots of duplicate .mini files were happily residing in the allocated folder as a result of moving audio files and podium regenerating a new one accordingly. it’s just the tidyness factor that i am thinking of
@bladerunner wrote:
@Zynewave wrote:
In both cases it can be a nightmare to maintain the mini folder, and to validate it against moved sound files etc.
the way i think of it (and of course put me right if i have it all wrong 😉 ) there wouldn’t be any need to maintain the allocated folder would there?
I’m mostly concerned that the contents of the mini folder could grow out of proportions with thousand of mini files. But maybe it’s not a problem. The user can just delete all the files in the mini folder if he is worried about having too many orphaned mini files. I’ll consider it for a future update.
as .mini files are only a few kilobytes in size it really wouldn’t matter (to me anyway!) too much if there were thousands of them and, like you say, users could always delete them if they are bothered by it. better that they are all in the same place than scattered around numerous folders and such (that’s the way i look at it!).
thanks for considering it :D/
XnView (an image viewing/organizing/editing program) has an option to put all thumbnails it creates into a zip file, and it works without delay when you view a folder. It won’t get around the duplicate file names, but if there’s some other way to specify which wave a mini belongs to, it could work. XnView also has an option for cleaning up and deleting unused thumbnails.
Don’t know if something like this would be thinkable for mini files!