Display MoreAt the end of the day, I see that we all - regardless whether we support the "foder" approach or the "tag" one - are asking for a "better" implementation. What does it mean?
Both more folders and more tags (namely user-defined ones) have been requested often. We might conclude that, while RM somehow implements both, it doesn't do it in a manner that really gives users power and freedom when mastering their material.
I am "old fashioned" when it comes to file managing, Total Commander having being my user interface for 20 years or more in its various incarnations.
The power of the folder approach is that the user creates their folders and their structure, hence their own whole data structure.
On my computer, the same rig is stored under say MBritt, Commercial, Crunch and Strato, so that I always know where to look for when I need something. I, like many, would like to have the possibility to implement such a structure in RM as well.
Not that I'm not willing to learn or use a new approach. Apparently tho, Kemper has failed to realize that a managing method is as much powerful and versatile as much it gives users freedom\power over their data.
IOW, in order for the Tag approach to work for everyone, the user must have the possibility to establish their own tags. Or to create their own folders without limitations.
I'd say at least two custom tags would be needed, if not an unlimited (or anyway great) number of them.
I feel that most complaints and requests about RM come because of the reasons I've mentioned above.
Actually, here are what i could like to add:
- the RM database need to store the original ash value/MD5 whatever of the original profile: if you import a rig, change some tag (amp name, comment, ...) and re-import the same rig, you have two entries: for commercial pack like the sinmix ones who updates often his packs, importing the update also import the previous ones (because you changed the tags)
- the ability to add filter per column (filter on the author and the pack name for instance)
- adding a field for a user comment
- adding a field for user tags (for the viabcroce example, you could put "CRUNCH;STRATO" in this field : with the column filters, it would be possible to filter the author (MBritt) and the tags)
The fact is we are used to organize things in a folders structure.But it is very limitating: There are several profiles you would like to seen to different "folders"