yaml-time: v3 config update - #173
Open
SearchSavior wants to merge 5 commits into
Open
SearchSavior wants to merge 5 commits into
SearchSavior wants to merge 5 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR is still WIP.
This PR implements a full rewrite of the OpenArc configuration system to support a YAML format to make writing config files easier, and decouple logic from the
climodule. There are two goals:For example, openai format accepts an
extra_bodyparameter which can nest json- very nice. I used this to support the fuil suite of options for qwen3-tts, and each setting is configurable at request time. Unfortunately this powerful feature was safely hidden away by terrible UX, since none of the useful tools which integrate openaiv1/audio/speechsupportextra_body. Now, you can define ALL configurable setting in a way that locks in a precedence order:In this way, OpenArc config files are now fully declarative, and can support extension to whatever new architectures we want to support, no matter what they require, and reguardless of how the API standards change. For example, now
max_tokens,temperature,runtime_configandscheduler_configcan be set per model; more interestingly kokoro can now acceptvoice_blendin the yaml, and is resolved at request time meaning you don't have to setvoicefor it to work withvoice_blend; this is powerful because you get the implementation richness of OpenArc in applications that can leverage the inference we provide.Another example to illustrate:
Above you can set the reference audio and reference audio transcription of that audio in the config, so the client only has to send
modelandinput(in the voice clone case). Some of these shouldn't even be changed likestream_left_context, but why not expose it all?to be continued