same here, 403 error. I even created a topic thinking I could be doing something wrong rather then being lack of authorization to the modal. With more people having the same issue, I’m less worried about doing something wrong and more inclined to think that the modal hasn’t been released yet.
Same here . I guess if it doesn’t show on playground means it’s not supported yet . and also whether you’re received a notification email as usual or not !
Ok, now thinking about the firefox error on the openai-realtime-console repository, the delay could be because they are not resampling the PCM data and are working on it prior to the release of the modal.
There are two ways to go about this, one of them is to resample it via the API and the other is via the client.
the API way:
This is a good approach if you need complete control over the quality of the data being fed into your model or if your clients are too diverse to reliably handle resampling on their own.
the Client way:
If you expect many clients with varying capabilities (some of which may be on devices with ample processing power, others not), this can be a way to optimize server-side resources.
f they prioritize consistency and control, do the resampling on the API side. If you want to offload work and ensure your API remains lightweight, client-side resampling would make more sense, especially if you have control over the clients and can enforce this behavior.
Personally, I’m not sure which way they are going to go about this, as the client repository wasn’t taking this into consideration. Might be after though that they realized once the openai-realtime-console and openai-realtime-api became public.