I just updated VP365 to build 187. I have never used the Text to Speech feature before, but I have a need to use it now. I logged into the Hub and selected Tools | Text to Speech. A window appears and there is a brief animation then a blank window. What could be going on here?
Did you select an event with audio on the timeline?
Hub has been flaky lately so you could try logging in and out and see if that helps.
I just tested it and at least here it's functioning. Hub itself is not working and just says "bad request." Bizarre.
Did you select an event with audio on the timeline?
Hub has been flaky lately so you could try logging in and out and see if that helps.
Is that what you have to do first? The help content just says to select Tools | Text to Speech. I figured it would just create audio that I could place anywhere. I'll try logging out and back in tomorrow morning.
Hold on, what exactly are you doing? The tile says text to speech but your first post says speech to text (captions).
For captions you need audio.
For text to speech you just need to type in some text.
It seems to be working.
Hold on, what exactly are you doing? The tile says text to speech but your first post says speech to text (captions).
For captions you need audio.
For text to speech you just need to type in some text.
Sorry, slip up on my part. It was late. The original post has been updated.
I logged out and back in. No joy. I even updated my NVidia drivers and set the app to use Alternate DPI settings.
Text to Speech is launch via the Hub...basically a webpage within VEGAS. Perhaps something is blocking the request?
Text to Speech is launch via the Hub...basically a webpage within VEGAS. Perhaps something is blocking the request?
I run a Pi-Hole on my network, but I don't see anything being blocked. I even disabled it temporarily, still no joy.
All my DNS request are eventually sent to the Cloudflare DNS servers.
I've created a support ticket for this, as I can't seem to find a solution. One of the main reasons for buying VP365 was the text to speech feature.
Just used Text to Speech again, works perfectly, copy/paste text and generate audio with a voice of your choice:
This is interesting. If I run VP version 20, Text to Speech works fine. It's when I use version 21 that it does not work.
'Text to Speech' worked intermittently in the last build of Vegas 21 and only once right after I updated to build 187. Now it only displays a blank 'Text to Speech' window with a perpetual hour glass after the "Checking log-in state" display,
OTOH, 'Speech to Text' consistency works with no problems.
'Text to Speech' worked intermittently in the last build of Vegas 21 and only once right after I updated to build 187. Now it only displays a blank 'Text to Speech' window with a perpetual hour glass after the "Checking log-in state" display,
OTOH, 'Speech to Text' consistency works with no problems.
Pretty much the same symptoms I'm having. In a way, it's good to know that others are having the same problem. It's odd that version 20 works fine.
This is interesting. If I run VP version 20, Text to Speech works fine. It's when I use version 21 that it does not work.
This should not be, but from a technical point of view explainable: Text to speech in Vegas 20 (365) is a local implementation (no network needed, speech is generated on your own PC), in Vegas 21 (365) it is going to the cloud for generating the speech files, I presume going to Microsoft azure services and servers.
The advantage on doing it the Vegas 21 way is that all development (new stuff, improvements extra languages) all becomes Microsoft's responsibility, as Vegas would only act as a "glorified" postbox for sending your requests and receiving the result. The user can benefit from future improvements without having to have a new Vegas build. The disadvantage of course is the dependency of the network: your own hardwire & software network setup, internet lag and congestion, Microsoft's own server and services availability, priority ques etc..
So focus on your network setup (including security, web settings, anti-virus settings, DNS, ports etc. and it should "normally" work most of the time, given the occasional network hiccup's.
I looked into my network setting security. I'm running Windows 11, use the built in security features, no 3rd party addons. I have a Pi-Hole on my network, but I'm not seeing anything being blocked. Even when I disable the Pi-Hole, Text to Speech does not work. DNS goes to Cloudflare servers, which should not be an issue. Accessing Azure certainly is not an issue, as I have my own services I have developed on Azure and connect with it often.
Speech to text works normally, and I'm assuming it uses the same service based approach..
@jyoungl6 I just tried, and got a black screen as well for text to speech, then I noticed I had a faint "bad request" text at the Vegas hub tab screen, next I logged out of the hub which was obviously not working, and logged back in, so the hub was functional again, and then I could use successfully speech to text.
So make sure you do not have an issue with the hub...
@jyoungl6 I just tried, and got a black screen as well for text to speech, then I noticed I had a faint "bad request" text at the Vegas hub tab screen, next I logged out of the hub which was obviously not working, and logged back in, with worked, and then I could use successfully speech to text.
So make sure you do not have an issue with the hub...
I've logged in and out of the hub many times now, trying to resolve this issue. I just tried logging in an out again, same result. One odd thing is that after logging back into the hub, I am asked again which hub account I want to use when starting Text to Speech.
One thing to try is to reset Vegas to it's default, the procedure eludes me for the moment, but can be found in the forum here...
Yet another trick to try is to start Vegas elevated (as administrator)...
I've logged in and out of the hub many times now, trying to resolve this issue. I just tried logging in an out again, same result. One odd thing is that after logging back into the hub, I am asked again which hub account I want to use when starting Text to Speech
Same here.. though I am not asked again which hub account I want to use when starting 'Text to Speech'. As I stated, 'Speech to Text' works without issue.