Customizable api_base for OpenAI: URL is not used

[faspie]

Thank you for adding customizable API support to buzz!

I tested the new version yesterday. The new URL does not seem to be used for

• open AI key testing and
• in the "record" mask - data is not sent to my internal whisper server

[raivisdejus]

Please provide more info of your local setup. Internally we use python OpenAI python API. Is your internal whisper compatible with it?

[faspie]

My local setup is tiny openai whisper api (https://github.com/morioka/tiny-openai-whisper-api) which should be compatible with the official openai api.

The main problem is that the parameters provided by "preferences" are not used by the record mask.

The "check key" button in preferences leads still to a connection to the openai server

[raivisdejus]

Ignore the "check key" for now, that part indeed has an issue, but I think the actual recognition should work.

Or wait a few days, I'll look into the check key part as well

[raivisdejus]

Use of custom base url has been added to API key check as well. If the custom API used does not support it API key check will give an error, but should still work.

Please test and let us know if it works as expected.

[faspie]

Unfortunately, here is no option for using the api. If Model "Whisper" is selected, buzz is downloading language models locally so I guess it does not use the api

[raivisdejus]

Whisper API is not supported for Live recordings, "OpenAI Whisper API" option will be available for file recording transcriptions. Will look into making API work for Live recordings

[faspie]

OK, is there any reason why live recording is not supported? It should not make any difference whether a local whisper or an API is transcribing...

[raivisdejus]

Support for Open AI API has been added to live recordings. Let me know if you spot any issues.