mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-06 10:58:17 -05:00
[GH-ISSUE #23444] issue: wrong audio file path on Windows #19984
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @daniporr on GitHub (Apr 6, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/23444
Check Existing Issues
Installation Method
Pip Install
Open WebUI Version
v0.8.12
Ollama Version (if applicable)
No response
Operating System
Windows 11
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
Ensure the audio file is loaded correctly.
Actual Behavior
The audio file failed to load.
Steps to Reproduce
As you can see, the final path separator is different, which prevents it from working on Windows. I suspect there is an issue with how the path is constructed; it appears someone has hardcoded a '/' instead of using the appropriate system path separator.
Logs & Screenshots
The relevant section has been reported above.
Additional Information
No response
@D2758695161 commented on GitHub (Apr 7, 2026):
PR Submitted: #23464
I've identified and fixed the root cause of this issue. The bug is in ackend/open_webui/routers/audio.py in the split_audio() function at line 1112.
Root Cause: The chunk path was built with f-string concatenation which doesn't handle Windows path separators correctly.
Fix: Changed from:
python chunk_path = f'{base}_chunk_{i}.{format}'To:
python chunk_path = os.path.join(os.path.dirname(base), f'{os.path.basename(base)}_chunk_{i}.{format}')PR: https://github.com/open-webui/open-webui/pull/23464
@daniporr commented on GitHub (Apr 7, 2026):
@d2758695161, there was already a PR for this issue created by @theshivam7, who implemented the exact same change as yours but modified only 14 lines instead of the 2,688 you changed.
Is there a good reason to modify all those lines?
@daniporr commented on GitHub (Apr 11, 2026):
@Classic298 I noticed you closed #23464.
Should we proceed with merging #23456?
@tjbck commented on GitHub (Apr 12, 2026):
Addressed in dev.
@theshivam7 commented on GitHub (Apr 13, 2026):
Thanks for the note! Could you point me to the commit where this was applied? I'd love to reference it in my portfolio.