Repository navigation
Aditor v0.4.6
修正
- VALORANT 分局檔改以正確遊戲分析:將一支含多場對戰的影片「分局」後,切出的檔不再一律標為 Apex,而是沿用原影片的遊戲;同時保留遊戲與畫面比例標籤,4:3 等非 16:9 的 VALORANT 分局檔不再被當成 16:9 分析。
- 無法錄影的混合顯示卡筆電可改用視窗擷取:部分混合 GPU 筆電的螢幕擷取(DDA)回報不支援(
0x887A0004),而 Windows 10 的自動擷取一律選擇 DDA,導致完全無法錄影。現在遇到此錯誤會對同一遊戲程序改用視窗擷取(WGC)重試一次並提示使用者。 - 錄影不再因空的第一段卡住:錄影器等待第一個影格逾時後,只留下空的第一段的工作現在會直接丟棄,不再回報收尾失敗、封鎖錄影直到重新啟動,也不會讓下次啟動的補收尾一直失敗。
- 遊戲重新啟動時改為等待新視窗:視窗擷取開始的瞬間若遊戲視窗已被關閉,現在會等待遊戲的新視窗,不再當成擷取失敗。
- 遊戲偵測不再失敗:遊戲行程查詢改為一次只執行一個
tasklist;先前同時執行多個時,部分電腦會出現0xC0000142(DLL 初始化失敗)而無法偵測遊戲。 - 防毒或同步程式短暫鎖檔不再中斷逐局剪檔:錄影工作的狀態檔被暫時鎖住時,會短暫重試(約 1.5 秒)後再放棄。
- 在檔案總管刪除的錄影可重新產生:已收尾的影片若在程式外被刪除(檔案總管、防毒),只要錄影段落還在,下次啟動會重新剪出,不再每次啟動都補收尾失敗。
- 持續交戰畫面不再切斷對局:Apex 對局切分時,畫面上仍有小地圖與血條等交戰介面就不會誤判為開場畫面,避免把一場對局切成兩段。
- 網路路徑影片不再匯入後無法儲存:
\\伺服器\共用資料夾這類網路路徑的影片與監看資料夾現在會在匯入時就被拒絕;先前可以匯入與分析,但編輯內容、重新分析與匯出都會失敗。請改用對應的磁碟代號。 - 存檔更可靠:分析快取與設定檔改為寫入完整並同步到磁碟後才取代舊檔(與媒體庫、專案相同),避免存檔後立刻斷電或磁碟已滿時留下空白或不完整的檔案。
- 移除影片時一併清除代理檔與縮圖:先前從媒體庫移除的影片,其預覽用代理檔與縮圖會一直留在應用程式資料夾。分析快取仍刻意保留,因為其中包含編輯內容。
- 清除中斷的匯出暫存檔:合併匯出中途當機或被強制結束時留在匯出資料夾的
.aditor-seg-*中間檔,會在下次匯出開始時清除。
錯誤回報改善
- 已不存在的麥克風或輸出裝置改歸類為「找不到音訊裝置」,不再回報為「音訊來源意外停止」。
- 影片解碼完全失敗時附帶 ffmpeg 的結束代碼。
- 硬體編碼送出或接收失敗時保留 FFmpeg 的錯誤原因(僅限可列印 ASCII、最多 200 字元,不含路徑)。
- OBS WebSocket 連線失敗時保留關閉代碼,可區分驗證失敗與無法連線。
- 錄影服務失敗附帶失敗的系統呼叫名稱(不含路徑)。
已知限制
- 尚未驗證:以真實 VALORANT 多場錄影實際分局、1440p/超寬螢幕錄影的分析準確度、遊戲 FPS 影響。
- Windows 執行檔未進行程式碼簽章。
更新方式
- 0.2.2 至 0.4.5 安裝版可透過自動更新升級。
- 0.2.0/0.2.1 安裝版請手動下載並執行
Aditor-Setup-0.4.6.exe。 - 免安裝版請下載
Aditor-0.4.6-Portable.exe手動更新。
Fixes
- VALORANT split parts are analyzed as VALORANT: splitting a multi-match video no longer tags every part as Apex; parts keep the source video's game, and the game and aspect tags survive the cut, so 4:3 and other non-16:9 VALORANT parts are no longer analyzed as 16:9.
- Hybrid-GPU laptops that could not record fall back to window capture: on some hybrid-GPU laptops Desktop Duplication (DDA) returns unsupported (
0x887A0004), and Windows 10 auto capture always picks DDA, so recording never worked. On that error the same game process is retried once with window capture (WGC) and the user is told. - An empty first segment no longer blocks recording: when the recorder times out waiting for the first frame, a session holding only that empty segment is now discarded instead of failing finalization, blocking recording until restart, and failing startup recovery.
- A game restart waits for the new window: if the game window disappears just as window capture starts, the app now waits for the game's new window instead of reporting a capture failure.
- Game detection no longer fails: game process queries run one
tasklistat a time; running several at once made some PCs fail with0xC0000142(DLL initialization failed). - Brief antivirus or sync-client locks no longer abort per-match cutting: replacing a session state file retries for about 1.5 s before giving up.
- Recordings deleted in Explorer are cut again: if a finalized video is deleted outside the app while its segments remain, the next start cuts it again instead of failing recovery on every launch.
- Ongoing fights no longer split an Apex match: match splitting no longer classifies a frame as an opening screen while combat HUD (minimap, health bars) is visible.
- Network-path videos are rejected at import: videos and watch folders on network paths such as
\\server\shareare now refused at import. They used to import and analyze, but saving edits, reanalysis and export all failed. Use a mapped drive letter instead. - Safer saves: the analysis cache and settings are now written in full and flushed to disk before replacing the old file, like the library and projects, so a power loss or full disk right after saving cannot leave an empty or truncated file.
- Removing a video also removes its proxy and thumbnail: preview proxies and thumbnails of removed videos used to stay in the app data folder forever. Analysis caches are still kept on purpose because they hold edits.
- Interrupted export leftovers are cleaned up:
.aditor-seg-*intermediate files left in the export folder by a crashed or killed concat export are removed when the next export starts.
Better error reports
- A microphone or output device that no longer exists is reported as a missing audio device instead of an audio source that stopped unexpectedly.
- Decode failures include ffmpeg's exit code.
- Hardware encoder send/receive failures keep FFmpeg's reason (printable ASCII, at most 200 characters, no paths).
- OBS WebSocket connection failures keep the close code, separating authentication failures from an unreachable OBS.
- Recording service failures carry the failing system call name (no path).
Known limitations
- Not yet verified: splitting a real multi-match VALORANT recording, analysis accuracy on 1440p/ultrawide recordings, and game FPS impact.
- Windows executables are not code signed.
How to update
- 0.2.2 through 0.4.5 installs can upgrade through auto-update.
- 0.2.0/0.2.1 installs need to download and run
Aditor-Setup-0.4.6.exemanually. - Portable builds: download
Aditor-0.4.6-Portable.exeto update manually.
完整變更 / Full changelog: v0.4.5...v0.4.6