Fix AudioProcessor worker failing on relative media URLs#157
Merged
mfwolffe merged 1 commit intoLab-Lab-Lab:mainfrom Apr 2, 2026
Merged
Fix AudioProcessor worker failing on relative media URLs#157mfwolffe merged 1 commit intoLab-Lab-Lab:mainfrom
mfwolffe merged 1 commit intoLab-Lab-Lab:mainfrom
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
2 participants
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.
Web Workers don't have the page's base URL context, so
fetch("/media/...")inside the AudioProcessor worker blob fails with "not a valid URL". This broke bassline import in Activity 3 — the worker couldn't fetch the proxied media file, the fallback also failed, and the clip ended up with no waveform or duration.Fix: convert relative URLs to absolute (
window.location.origin + url) before passing to the worker. The resolved URL still routes through the Next.js/media/rewrite proxy.