search

daisy / pipeline-ui

A user interface for the DAISY Pipeline 2
MIT License
5 stars 2 forks source link

TTS azure not working on 1.2.7-RC2 #174

Closed torchtrust closed 7 months ago

torchtrust commented 7 months ago

Expected Behavior

TTS using Azure settings

Actual Behavior

DTBook to DAISY 3 script reports: WARNING - azure could not be activated: Property not set : org.daisy.pipeline.tts.azure.key (Please see detailed log for more info.)

Steps to Reproduce

  1. In settings set TTS engines: Azure with key and Region
  2. Connect - this connects. ttsConfig.xml is generated and has the same values as 1.2.7
  3. run DTBook to DAISY 3 and enable TTS
  4. WARNING reported azure could not be activated: Property not set : org.daisy.pipeline.tts.azure.key (Please see detailed log for more info.)

Details

None.

Environment

Logs

tts-log.xml.log

bertfrees commented 7 months ago

@marisademeglio It looks like a GUI issue still?

marisademeglio commented 7 months ago

Ah yep it's a regression bug, thanks for reporting it.

We need to set up automated UI testing to avoid these things. I had started it but never got it working. https://github.com/daisy/pipeline-ui/issues/33

marisademeglio commented 7 months ago

I have some new installers here (unsigned so may trigger a security warning): https://github.com/daisy/pipeline-ui/actions/runs/7106856948#artifacts

I tested the Windows version by installing from the link above onto a virtual machine that i have (Win 11) and noticed in the settings dialog that it doesn't list any OneCore voices. If I add Azure connection info, it lists Azure voices, but never OneCore, whereas it used to. I then went back and reproduced this with older Pipeline installers (Rc1, Rc2) so I suspect it's my windows machine at fault. I'd be curious how it works for you.

bertfrees commented 7 months ago

@torchtrust Have you had a chance to test the version that Marisa pointed to?

torchtrust commented 7 months ago

This does produce TTS now without any tweaking of settings, but I did find another bug which I will report seperately Thanks Paul

On Tue, 19 Dec 2023 at 18:04, Bert Frees @.***> wrote:

@torchtrust https://github.com/torchtrust Have you had the chance to test the version that Marisa pointed to?

— Reply to this email directly, view it on GitHub https://github.com/daisy/pipeline-ui/issues/174#issuecomment-1863249636, or unsubscribe https://github.com/notifications/unsubscribe-auth/AASSUUIQFSGEVH6WF4HSDILYKHJKTAVCNFSM6AAAAABAIJ3Y6SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRTGI2DSNRTGY . You are receiving this because you were mentioned.Message ID: @.***>

--

Paul Wood Head of Technical Services Torch Trust Torch House, Torch Way, Market Harborough, Leics. LE16 9HL, UK Direct Line: +44(0)1858 438269 Mobile: +44(0)7521 514212 Tel: +44(0)1858 438260 Email: @.*** Websites: www.torchtrust.org www.sightlossfriendlychurch.org.uk https://torchtrust.org/sight-loss-friendly-church Facebook: Torch-Trust https://www.facebook.com/pages/Torch-Trust/209414622516639 Twitter: @TorchTrust https://twitter.com/TorchTrust YouTube: Torch Trust on Video https://www.youtube.com/channel/UCjh3k2t6SckTWOtQZNmkN8w

[image: Losing your sight? Know someone who is? Order a FREE audio Bible player at torchtrust.org/pathway] https://torchtrust.org/pathway

[image: Registered with the Fundraising Regulator] https://www.fundraisingregulator.org.uk/

Charity No. 1095904

Privileged/Confidential Information may be contained in this message. If you are not the intended recipient please destroy this message and kindly notify the sender by reply email. The computer from which this mail originates is equipped with virus screening software. However Torch Trust cannot guarantee that the mail and its attachments are free from virus infection.