Tweet
I am still having issues when tagging (or reading tags or indexing files with Asset) m4a/m4b files. I do have a lot of self-created audiobooks (encoded them with dbpoweramp from CDs as one file), the resulting files are in the region of 100 - 350 MB (duration up to 10 hours with 64kbs/low complexity).
When editing a tag, it takes more than 1 Minute, until the tags are displayed, and even longer for the changed tags to be stored in the file. Using MP3 tag to do the same job, it is a matter of less than a second.
When indexing my database with Asset, this results in a major "halt" during the scanning process: when Asset comes to indexing the folder, that holds my ~300 audiobooks, task manager shows 100% processor load and the scanning process takes forever, as you can imagine. flac, mp3 or wma-files (even the hour-long ones) are indexed with much less processor load and really fast.
Could it be, that MP3-tag does look for the tags in a specific region and therefor is that fast, and that dbpoweramp/Asset needs to scan the whole file?
Is there any way to improve scanning speed for those files?
I know, that you, Spoon, have looked into this a longer time ago and made some changes, but just now, encoding a new batch of audiobooks, it came to my attention, that there still is this real slow indexing/editing speed.
You can imagine, that due to this - when Asset is reindexing etc. - the server itself sometimes gets sort of unusable until the scanning of audiobooks is done. Speeding that up and avoiding the high processor load would be a great help!
Thanks for considering to do some changes...
When editing a tag, it takes more than 1 Minute, until the tags are displayed, and even longer for the changed tags to be stored in the file. Using MP3 tag to do the same job, it is a matter of less than a second.
When indexing my database with Asset, this results in a major "halt" during the scanning process: when Asset comes to indexing the folder, that holds my ~300 audiobooks, task manager shows 100% processor load and the scanning process takes forever, as you can imagine. flac, mp3 or wma-files (even the hour-long ones) are indexed with much less processor load and really fast.
Could it be, that MP3-tag does look for the tags in a specific region and therefor is that fast, and that dbpoweramp/Asset needs to scan the whole file?
Is there any way to improve scanning speed for those files?
I know, that you, Spoon, have looked into this a longer time ago and made some changes, but just now, encoding a new batch of audiobooks, it came to my attention, that there still is this real slow indexing/editing speed.
You can imagine, that due to this - when Asset is reindexing etc. - the server itself sometimes gets sort of unusable until the scanning of audiobooks is done. Speeding that up and avoiding the high processor load would be a great help!
Thanks for considering to do some changes...
Comment