Keep up to date with changes in the engine regarding TTS configuration

[marisademeglio]

daisy/pipeline-modules#66

[marisademeglio]

This will require backend changes only: this will have to be specified either at launch time, or through the settings API (like is already the case for other settings such as speech-rate)

https://daisy-dev.slack.com/archives/C064GB8U9/p1723476887384829?thread_ts=1723476120.081709&cid=C064GB8U9

[bertfrees]

Setting the "org.daisy.pipeline.tts.config" property at launch time is already possible and will be the most straightforward solution, and should give us exactly the same behavior.

Setting the property dynamically through the settings API is not possible yet today, but I'm about to change that. The main benefit of this approach is that changing a property affects the jobs created after the change, but not the jobs created before the change (but still in the cueue). So through the dynamic approach, you could in theory create a new TTS configuration file after each change.

[marisademeglio]

Instead of using a script option to point to a TTS configuration file, the TTS configuration file can be passed at launch time via the org.daisy.pipeline.tts.config property.

[marisademeglio]

@bertfrees will the scripts still have a tts config option? Not that we would use it. But I need to know if I still need to filter it out on the script form.

[bertfrees]

I will keep it around for now. An alternative the the script option is also still needed for the command line interface.