![]() If MP3tag mainly treats files that get accessed on the same HDD (or be it an SSD), via the same LAN interface or even in the cloud via a WAN interface, then the access is sequential (HDD = SATA = Serial AT attachement). ![]() Īnd multiple instances of MP3tag would probably not speed up things. if such files were selected for further treatment in one instance but get modified in another?. That MP3tag has to update all instances of a running MP3tags all the time - and if that does not happen, coping with a lot of error messages as files could be moved, filter criteria would not match any more as the underlying data got modified - how should MP3tag react, esp. The effect that locked files do not get processed. I find this wish list a little irritating as no-one envisions how to overcome the imminent dangers and drawbacks:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |