Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

[Feature request] Portable projects: move a .recordly project between computers without broken paths

オープン
  • 何か問題がありますか？
#1,104 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 2 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
説明が足りない
活発さ
活発
技術スタック
electron, typescript
領域
backend, desktop

調査の方向性

Start by reading electron/ipc/project/manager.ts, especially resolveProjectMediaSources, and electron/ipc/recording/library.ts around belongsToRecording. The issue offers several alternative approaches but does not choose one or define a complete scope; first clarify which portability behavior is intended and how it should be verified. Done would require an agreed solution that preserves the project and its related media when moving between computers.

索引モデルが issue の本文から書いたものです。

説明

Problem

I edit the same Recordly projects on two Windows computers. Moving a project between them regularly breaks, even when I copy the files carefully.

From what I can see in the code, the reasons are:

  • The .recordly file stores absolute paths to media: videoPath, editor.webcam.sourcePath and audioPath for audio tracks. Paths differ between machines (different user names, drive letters, OneDrive locations), so after copying, opening the project fails with Project video file not found (resolveProjectMediaSources in electron/ipc/project/manager.ts).
  • There is no "locate missing file" / relink step, so the only fix is editing the JSON by hand.
  • A project depends on more files than the video itself: <video>.cursor.json, separate .system/.mic/.webcam audio/video files, <stem>.recordly-session.json, <stem>-webcam.* (see belongsToRecording in electron/ipc/recording/library.ts). It's easy to miss one, e.g. losing cursor effects or audio.
  • Recordings live in the hidden userData/recordings folder by default, so users don't know where the media files are.
  • Paths with non-ASCII characters (e.g. Polish ń in a Windows user name) may also be stored as encoded file:// URLs, which makes manual editing error-prone.

Proposed solution (any of these would help)

  1. Export / Import project bundle: "File → Export project…" creates a single archive (e.g. .recordlybundle / zip) containing the .recordly file plus all media and sidecar files; "Import project…" unpacks it to the local projects/recordings folder and rewrites paths.
  2. Relative paths: if media sits next to (or below) the .recordly file, store paths relative to the project file and resolve them on open.
  3. Relink missing media: when a file isn't found, show a dialog to locate it, and automatically look for the same file name in the project's folder.
  4. Configurable storage location for recordings (similar to the closed #788), so projects and media can live in one synced folder (OneDrive / Google Drive).

Environment

  • OS: Windows 11
  • Recordly version:
主要言語
TypeScript
スター
32.4k
フォーク
2.6k
平均マージ
1日 19時間
マージ済み PR（30日）
17

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

webadderallorg/Recordly のほかの issue

webadderallorg/Recordly の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。