Been using latest build -- very nice and is working really well, so thanks for all your hard work
I have two suggestions, one I think is pretty minor and probably (at the moment) marginal, the other comes about from using RMTM with a large collection.
Suggestion 1 is a request really, and suggestion 2 is more a thought - something to consider - more than anything else.
1) Is it possible to add support for lossy.flac files (see here: http://www.hydrogena....php?showtopic=56129
) or really any lossy.wav file compressed with a lossless codec, ie files with the following extensions:
*.lossy.* (i.e. *.lossy.flac; *.lossy.wv; *.lossy.ape; *.lossy.wav)
It looks like the lossyWAV project is going to really take off due to a) transparency b) avoiding transcoding issues from psychoacoustic lossless compression formats (MP3 etc) and c) major reductions in the compression performances of lossless codecs on lossy.wav files.
I tried to add a lossy.flac file to my must have list and it wasn't having any of it - so it looks like RMTM doesn't yet recognise this format (hardly surprising - though I thought it might just look at the last part of the extension i.e. .flac).
My one other suggestion is to do with getting round RMTM's relatively long initial scan time (for large collections) to create a playlist.
It seems to me that there would be 2 possible approaches:
1) The easy (fix) method:
Have an option to load RMTM at startup and allow it to do a low resource/idle time only background scan while in the system tray. So when you choose to run it, it already has scanned the directories and only need to respond to the filters applied. Don't know if that makes sense - or is possible.
2) The nightmare method (in term of work - I would have thought - though don't know)
Use an SQL-Lite database which is refreshed on opening. Thus for collections > 10,000 tracks the processing is relatively fast. But I imagine this would require a re-write?
That said, I've been using foobar's foo_custom_info component which reads and writes additional info to an SQL database which is completely outside of foobar's core program. Thus wouldn't it be possible to use a similar method whereby after the scan RMTM writes the gathered info to a SQL DB and then queries that in the future, leaving it for the user to decide when to re-scan and thus refresh the DB of tagged and filename info. Anyway - I'm not technical enough to know if this is feasible or not.
Like I say, just ideas really.