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
feat(studio): 「我的视频」库 —— 在 studio 内浏览、回放和管理导出的 MP4(愿意提 PR) #46
Hi @abin0515! This is a well-scoped proposal — building on the existing project.exports history instead of inventing a second store is exactly the right direction.
A “My Videos” view inside Studio makes sense to us, especially the in-browser playback and jumping straight into the exported MP4 after render finishes. We also checked the current flow here: export history is already persisted on the project side, while the Studio UI still mainly surfaces the latest exported path, so the gap you called out is real.
If you open a PR, we'd be happy to review it. For the first pass, I'd suggest keeping the center of gravity on:
browsing persisted export history in Studio
opening the exported MP4 directly after export
adding management actions only if the server/API surface stays straightforward
Rename / download / delete all sound useful too, but if the file-operation edge cases start to sprawl, it's totally fine to land the library + playback path first and follow up on management actions separately.
Activity
lefarcen commentedon Jun 12, 2026
Hi @abin0515! This is a well-scoped proposal — building on the existing
project.exportshistory instead of inventing a second store is exactly the right direction.A “My Videos” view inside Studio makes sense to us, especially the in-browser playback and jumping straight into the exported MP4 after render finishes. We also checked the current flow here: export history is already persisted on the project side, while the Studio UI still mainly surfaces the latest exported path, so the gap you called out is real.
If you open a PR, we'd be happy to review it. For the first pass, I'd suggest keeping the center of gravity on:
Rename / download / delete all sound useful too, but if the file-operation edge cases start to sprawl, it's totally fine to land the library + playback path first and follow up on management actions separately.
lefarcen commentedon Jun 12, 2026
如果有社区同学想接这个,欢迎直接评论
/claim来认领,我们会按这个方向一起 review 🙌abin0515 commentedon Jun 12, 2026
/claim
lefarcen commentedon Jun 12, 2026
收到,感谢你来接这个 @abin0515 🙌
你这边大概预期多久能推进到 PR 呀?比如几小时、1-3 天、约一周,或者更久都可以。
lefarcen commentedon Jun 12, 2026
@abin0515,PR #47 已经按我们在 issue 里收敛过的第一刀范围开出来了:这版先把导出历史浏览、浏览器内播放、以及导出完成后直达播放器这条主路径接通。这样能先把现有
project.exports/lastOutputMp4Path这条数据链真正落到 Studio UI 上;rename / delete 这类文件管理动作先留在后续 PR 继续拆。先把实现和 review 跑完,这个 issue 先保持打开,等 PR 合入后我们再继续收尾剩余范围。
lefarcen commentedon Jun 15, 2026
Re-opening this issue for community contribution because linked PR #47 has had no author activity.
The PR has been left open as draft so @abin0515 can resume later, and others may /claim this issue if they want to take it on.
lefarcen commentedon Jul 8, 2026
补个状态:PR #81 也在处理 Studio 里的 MP4/export 这条链路,改动同样落在
studio-server/project.ts/ Studio 前端这些持久化导出历史与播放相关路径上。这个 issue 先继续保持打开,等哪一条实现先落地、剩余范围更清楚后再收口。