About adding your WebUI to audio.cpp

[0xShug0]

Hi @kigner,

First, thank you for creating this WebUI! it is a great addition to the audio.cpp ecosystem.

I’m the author of audio.cpp. A contributor opened 0xShug0/audio.cpp#70 to add your WebUI to the main audio.cpp repository, together with cross-platform support and English localization. Are you comfortable with us including it in audio.cpp and continuing development there? We will keep clear credit to you and your repository.

If you are interested, we would also be happy to collaborate with you on the WebUI compoent in audio.cpp.

Please let me know if you have any concerns.

[kigner]

Hi! Thank you for reaching out, and I'm glad to hear that you're interested in including my WebUI in the main audio.cpp repository. I'm happy for my WebUI to be merged into audio.cpp, including the cross-platform support and English localization. I really appreciate that you'll keep clear credit to me and my repository. At the moment, though, I have a full-time job, and most of my spare time is dedicated to creating AI-related YouTube videos. Because of that, I probably won't be able to guarantee timely responses for WebUI bug fixes or new feature development in the main repository. That said, I do plan to continue maintaining and periodically updating my own WebUI repository. If there are useful improvements or fixes, you're welcome to bring them into audio.cpp as well. Thanks again for the invitation, and I hope the WebUI can continue to improve with everyone's contributions! 0xShug0 ***@***.***> 于2026年7月19日周日 01:59写道：

…

*0xShug0* created an issue (kigner/audio.cpp-webui#2) <#2> Hi @kigner <https://github.com/kigner>, I’m the author of audio.cpp. A contributor opened 0xShug0/audio.cpp#70 <0xShug0/audio.cpp#70> to add your WebUI to the main audio.cpp repository, together with cross-platform support and English localization. Are you comfortable with us including it in audio.cpp and continuing development there? We will keep clear credit to you and your repository. If you are interested, we would also be happy to collaborate with you on the WebUI compoent in audio.cpp. Please let me know if you have any concerns. — Reply to this email directly, view it on GitHub <#2?email_source=notifications&email_token=A7GE3T7OAD2JLTFT5EFKDTL5FO3HZA5CNFSL4Z3JMQ5C6L3HNF2C22DVMIXUS43TOVSS6NBZGE4TIMRQG43DNJTSMVQXG33OU5WWK3TUNFXW5JLFOZSW45FMMZXW65DFOJPWG3DJMNVQ>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A7GE3T75CDIX2L5B5C2BCR35FO3HZAVCNFSNUABGKJSXA33TNF2G64TZHMYTEOJYGEZDINJTGY5US43TOVSTWNBZGE4TIMRQG43DNILWAI> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/A7GE3T4BH4KAUZ7RMS3AKAL5FO3HZA5CNFSL4Z3JMQ5C6L3HNF2C22DVMIXUS43TOVSS6NBZGE4TIMRQG43DNJTSMVQXG33OU5WWK3TUNFXW5JLFOZSW45FKMZXW65DFOJPWS33T> and Android <https://github.com/notifications/mobile/android/A7GE3T5YIV6ETGNTNAGI4FL5FO3HZA5CNFSL4Z3JMQ5C6L3HNF2C22DVMIXUS43TOVSS6NBZGE4TIMRQG43DNJTSMVQXG33OU5WWK3TUNFXW5JLFOZSW45FOMZXW65DFOJPWC3TEOJXWSZA>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[0xShug0]

@kigner We’re discussing a framework contract refactor to simplify UI deployment and integration: 0xShug0/audio.cpp#89

Any thoughts on the schema? Would it make UI deployment easier?

[kigner]

Thanks for tagging me. Yes, moving this metadata into a single validated, machine-readable model spec would make WebUI integration and maintenance much easier. At the moment, audio.cpp-webui has to maintain separate model catalog, parameter-control, required-file, and download/install definitions. These can easily drift when audio.cpp adds a model or changes an option. For deployment, the most important requirement is that the production specs are shipped with the same release as the binaries and can be discovered from the runtime—through CLI JSON and ideally a server API. If the UI has to bundle or fetch its own copy of the specs, deployment would still require manual synchronization. A few points I think are important before the schema is frozen: - Package/variant-level metadata is needed. One family may have several packages with different tasks, capabilities, default options and VRAM requirements—for example Qwen3-TTS Base, CustomVoice and VoiceDesign. - A companion should reference a typed option so the UI knows whether it belongs to load, session or request scope. - Conditional dependencies should be machine-readable, such as return_timestamps=true requiring an aligner or audio_chunk_mode=vad requiring Silero VAD, instead of relying only on free-form required_for strings. - Companions should support bundled defaults, external files/directories, and preferred target packages. - Download/install definitions need to support composite packages, multiple sources, subdirectory placement, conversions or post-install steps, gated/manual downloads, and required-file validation. - Stable IDs, schema versioning and backward-compatibility rules will also be important for third-party UIs. I agree that the typed model_specs system is a cleaner long-term home for companions than duplicating the information in C++ loader code. Since no production models use the new schema yet, I would not change the WebUI immediately. I would be happy to test the integration with one or two real specs, such as qwen3_asr and miotts, once they are available through a stable runtime interface. 0xShug0 ***@***.***> 于2026年7月24日周五 11:46写道：

…

*0xShug0* left a comment (kigner/audio.cpp-webui#2) <#2 (comment)> @kigner <https://github.com/kigner> We’re discussing a framework contract refactor to simplify UI deployment and integration: 0xShug0/audio.cpp#89 <0xShug0/audio.cpp#89> Any thoughts on the schema? Would it make UI deployment easier? — Reply to this email directly, view it on GitHub <#2?email_source=notifications&email_token=A7GE3TZZPWRSHHKGUIN5YSD5GLL2LA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBWGU4TGNJRHAZKM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5065935182>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A7GE3T2SULMIKOLQ37FZVID5GLL2LAVCNFSNUABGKJSXA33TNF2G64TZHMYTEOJYGEZDINJTGY5US43TOVSTWNBZGE4TIMRQG43DNILWAI> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/A7GE3T7VB6FVFSYKFVHME3T5GLL2LA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBWGU4TGNJRHAZKM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/A7GE3TZVIEVZVX6FVEZOA535GLL2LA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBWGU4TGNJRHAZKM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[0xShug0]

Great! Thank you for the feedback!