Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Frontend] Add OpenAI API support for input_audio #11027

Merged
merged 12 commits into from
Dec 17, 2024

Conversation

kylehh
Copy link
Contributor

@kylehh kylehh commented Dec 9, 2024

Added support for OAI's input audio API

# Use type 'input_audio` inside the message
messages=[
        {
            "role": "user",
            "content": [
                { 
                    "type": "text",
                    "text": "What is in this recording?"
                },
                {
                    "type": "input_audio",
                    "input_audio": {
                        "data": encoded_string,
                        "format": "wav"
                    }
                }
            ]
        },
    ]
  1. The format is prefixed to the byte64 string following current vllm format
    f"data:audio/{input_audio_format};base64,{input_audio_data}"
  2. There is no output audio support yet, so no support for modalities and audio
# Not supported
modalities=["text", "audio"],
audio={"voice": "alloy", "format": "wav"},

Copy link

github-actions bot commented Dec 9, 2024

👋 Hi! Thank you for contributing to the vLLM project.
Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can do one of these:

  • Add ready label to the PR
  • Enable auto-merge.

🚀

@mergify mergify bot added the frontend label Dec 9, 2024
@DarkLight1337
Copy link
Member

DarkLight1337 commented Dec 11, 2024

Can you update this page and add some examples here as well? Thanks!

@mergify mergify bot added the documentation Improvements or additions to documentation label Dec 13, 2024
Copy link
Member

@DarkLight1337 DarkLight1337 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for adding this! I have polished the docs a bit before merging.

@DarkLight1337 DarkLight1337 enabled auto-merge (squash) December 16, 2024 15:12
@github-actions github-actions bot added the ready ONLY add when PR is ready to merge/full CI is needed label Dec 16, 2024
Signed-off-by: DarkLight1337 <[email protected]>
Signed-off-by: DarkLight1337 <[email protected]>
@youkaichao youkaichao disabled auto-merge December 17, 2024 06:09
@youkaichao youkaichao merged commit 66d4b16 into vllm-project:main Dec 17, 2024
50 of 52 checks passed
BKitor pushed a commit to BKitor/vllm that referenced this pull request Dec 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation frontend ready ONLY add when PR is ready to merge/full CI is needed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants