Model `gpt-4o-realtime-preview-2024-10-01` should not be hardcoded

[michitomo]

Issue:

• It won't allow using other models than the hardcoded model gpt-4o-realtime-preview-2024-10-01
• A new model gpt-4o-realtime-preview-2024-12-17 has been released with lower price.
• Alias gpt-4o-realtime-preview is also available

Expected:

• Library consumers should be able to specify models they choose
• The library should point model alias instead of a specific dated model

[Van0SS]

+1 this is very strange to discover and appreciate the PR!

[Kotoryu]

+1 totally agree, we should have possibility to change the model.

[yanaocean]

+1 agree!

[hinke]

+1 !!

[NeonNexus0408]

❤A new model gpt-4o-realtime-preview-2024-12-17 has been released with lower price.❤
Thank you.

[jjmlovesgit]

please see: #92
#92 This PR introduces the ability to select a custom OpenAI realtime model in the RealtimeClient. Users can now specify the desired model for more flexibility and tailored API usage.

[sidoh]

As a workaround, you can call client.realtime.connect directly:

export const DEFAULT_REALTIME_MODEL = "gpt-4o-realtime-preview-2024-12-17";
// ...
await client.realtime.connect({ model: DEFAULT_REALTIME_MODEL });
await client.updateSession();

The connect method in RealtimeClient is just a thin wrapper around RealtimeAPI.connect.

[CROprogrammer]

As a workaround, you can call client.realtime.connect directly:

export const DEFAULT_REALTIME_MODEL = "gpt-4o-realtime-preview-2024-12-17";
// ...
await client.realtime.connect({ model: DEFAULT_REALTIME_MODEL });
await client.updateSession();
The connect method in RealtimeClient is just a thin wrapper around RealtimeAPI.connect.

Do you maybe have an idea why function calling does not work when I define model like this instead of using client.connect()

[Dev-lesmemoires]

I've tried the method above, even though you can see chatgpt-4o-mini-model in websocket tab, You still end up getting charged for chatgpt 4 main model on your usage history. No usage logs for 4o mini

[sidoh]

Odd, it's definitely working for me! Are you using a relay?

[Dev-lesmemoires]

Odd, it's definitely working for me! Are you using a relay?

Yup, aren't you getting charged for gpt-4o-realtime-preview instead of getting gpt-4o-mini-realtime-preview?

[sidoh]

Odd, it's definitely working for me! Are you using a relay?

Yup, aren't you getting charged for gpt-4o-realtime-preview instead of getting gpt-4o-mini-realtime-preview?

The code I suggested needs to be run on the relay server, not the client.

Yes, but it's gpt-4o-realtime-preview-2024-12-17, which is different than the hardcoded version (gpt-4o-realtime-preview-2024-10-01).

[sidoh]

As a workaround, you can call client.realtime.connect directly:
export const DEFAULT_REALTIME_MODEL = "gpt-4o-realtime-preview-2024-12-17";
// ...
await client.realtime.connect({ model: DEFAULT_REALTIME_MODEL });
await client.updateSession();
The connect method in RealtimeClient is just a thin wrapper around RealtimeAPI.connect.

Do you maybe have an idea why function calling does not work when I define model like this instead of using client.connect()

Not sure. I use function calling in my application and noticed no difference when I swapped models. The realtime models' tool-calling abilities have seemed far more sensitive to temperature than I've expected. If you're not already, maybe try using the default value for temperature.

[jjmlovesgit]

Quick Fix -- Go and edit the hardcoded Node file and move it to gpt-4o-realtime-preview-2024-12-17 app.js