You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Video with a remote (https) src is read as a local path #57
From #13's run of snapcn's free components through raea: a video whose src is an https URL is read as a path in the media folder, and the render is refused.
REFUSED <work folder>/https://media.snapcn.dev/demos/answer-stream.mp4: No such file or directory
This hits 7 of the 61: hero-launch, laptop-frame, phone-frame, phone-stack, reel-collage, reel-wall and screen-recording. All of them play a remote demo clip through <Video>, which they import as OffthreadVideo. Chrome plays them.
There's a choice to make here. One option is to fetch a remote src once into a cache keyed by its URL, so renders stay offline and repeatable after the first. The other is to refuse with a message that says to download the file into the media folder. Either is better than the path error.
Fixed in ffd2738, thanks to @kevinschaich, whose #13 report sent us through snapcn's components.
An http(s) src on a <Video> is now fetched once into raea's URL cache (keyed by the URL, under $RAEA_CACHE), then played from there. Renders stay a function of the composition's code, and play offline once cached. A src that can't be fetched refuses with the reason instead of being read as a path:
video https://…/x.mp4: HTTP 404 Not Found
video https://…/x.mp4 (not in raea's cache): not sent, because RAEA_OFFLINE is set
Before: all seven components (hero-launch, laptop-frame, phone-frame, phone-stack, reel-collage, reel-wall, screen-recording) refused with <dir>/https:/…: no video track, so 0 fps. After: laptop-frame renders its 240 frames at 7.0 ms a frame (about 143 fps). The bench is bench/remote-media/check.sh.
Activity
shinyobjectz commentedon Nov 8, 2026
Fixed in ffd2738, thanks to @kevinschaich, whose #13 report sent us through snapcn's components.
An http(s)
srcon a<Video>is now fetched once into raea's URL cache (keyed by the URL, under$RAEA_CACHE), then played from there. Renders stay a function of the composition's code, and play offline once cached. A src that can't be fetched refuses with the reason instead of being read as a path:video https://…/x.mp4: HTTP 404 Not Foundvideo https://…/x.mp4 (not in raea's cache): not sent, because RAEA_OFFLINE is setBefore: all seven components (hero-launch, laptop-frame, phone-frame, phone-stack, reel-collage, reel-wall, screen-recording) refused with
<dir>/https:/…: no video track, so 0 fps. After: laptop-frame renders its 240 frames at 7.0 ms a frame (about 143 fps). The bench isbench/remote-media/check.sh.A <Video> whose src is an http(s) URL plays it, fetched once into rae…
raea pins raea-skills main d71042f (#57): the fingerprint page says w…
raea pins raea-skills main d71042f (#57): the fingerprint page says w…