How scalable is Sermon Speaker?

Dear Thomas,

I am thinking to store our sermons not just for publish, but for long term like a library. I don't know if Sermon Speaker fits the purpose. The library may grow to thousands or tens of thousands of audios.
Does Sermon Speaker scale to that size? What is the best practice for storing and managing sermons for large sites?
What especially worry me is that the "Write ID3 tag" tool which refresh all files, the "Create Sermons Automatically" tool which scans all folders in the path, which are not meant for large sites.
What would you advise? Thanks in advance.

Ken

Since the data is all stored within the database, there should be no issue even with thousands of sermons stored. Usually databases are capable of handling many thousands of items without problems.
If there arises an issue, we could look at optimising the database query a bit. I already found a missing index just a few days ago. Adding that single index did reduce the query time by about 40%. So there may be other places which could be improved, but so far I didn't run into any problems.

Those tools may indeed not work reliably with large amounts of files. However usually you only need those once.
The "Write ID3 tag" is also done when you regulary save the sermon, and there it will only touch that single file you assigned to the sermon entry.
The automatic creation of sermons is best used only for an initial setup of SermonSpeaker. After that is done you should create the sermons using the form. If you really want to use that method regulary, you could change the sermon path in the settings so it points only to a subset of the files (eg to a subdirectory for the year). Then it will no longer scan all files. Changing the path in the setting will have no effect on existing sermons. The paths are stored relative to the Joomla root directory in the database. The path is only used when creating/editing the sermons so SermonSpeaker can populate the dropdown list.

About "Write ID3 Tags" tool.
Dear Thomas,
I find that "Write ID3 Tags" tool updates all sermons files, as seen in system ls output. All files have their ID3 tags written, as seen from output, even only one or even none of the sermons had bee modified. (screen capture attached)

There are 1,000 sermons and it took me about 2 minutes to complete.
Would you modify the function so that either
1. Mark a sermon "dirty" if certain ID3-tag-related fields were changed, and you update only those sermon files.
2. Let me manually update the ID3 tag for just one sermon that I have changed.
(Please don't trash the current "Overwrite ID3 Tags for all Sermons", that I would call it, because some time people might need it.)
Thank you for your advice.

The tools method is meant to update all sermons.
If you only want to update one sermon, just enable the ID3 writing in the SermonSpeaker options (editing tab). It will (over-)write the ID3 Tags each time you save the sermon.

My ignorance. Sorry.