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

Adds support for creating weighted voice combinations #92

Open
wants to merge 2 commits into
base: v0.1.2-pre
Choose a base branch
from

Conversation

rvuyyuru2
Copy link

Implements a new method to parse weighted voice formulas and generate combined audio outputs based on specified weights.

This enhancement allows for more diverse audio generation by letting users specify multiple voices with respective weights, improving flexibility in voice management.

Updates voice processing logic in relevant API routes to handle weighted formulas seamlessly.

Fixes #123 (if applicable, replace with the actual issue reference)

Implements a new method to parse weighted voice formulas and generate combined audio outputs based on specified weights.

This enhancement allows for more diverse audio generation by letting users specify multiple voices with respective weights, improving flexibility in voice management.

Updates voice processing logic in relevant API routes to handle weighted formulas seamlessly.

Fixes #123 (if applicable, replace with the actual issue reference)
Updates the service name to 'InstaVoice' and introduces multiple server services to enhance scalability.
Modifies GPU resource allocation to use all available devices and adds an NGINX service for reverse proxy capabilities.

Simplifies the structure for better management of the API and UI services.
@remsky
Copy link
Owner

remsky commented Jan 26, 2025

The implementation for the weighted voice mixing looks great.

The full resource usage + nginx serving and setup would be great for anyone deploying at scale, though it might be a lot of additional complexity and load for the average local user

What do you think about having those be in a separate compose file as an option, maybe in a subdirectory, e.g deployment_options or by suffix e.g -nginx

@rvuyyuru2
Copy link
Author

yaa we can do that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants