When specifying a custom outDir in RenderSettings, relative paths in project.tsx unexpectedly gain an additional public directory prefix. This results in file resolution errors such as:
test-revideo/public/2025-06-25/public/video/1.mp4: No such file or directory
Through investigation, I noticed the resolvePath() utility in packages/ffmpeg/src/utils.ts appears to hardcode the public path segment. This behavior seems to propagate to the generateAudio functionality.
Would you kindly advise on the intended approach to handle path resolution here? I'd appreciate guidance on how we might adjust this logic to properly respect the configured outDir while maintaining compatibility with existing functionality.
When specifying a custom outDir in RenderSettings, relative paths in project.tsx unexpectedly gain an additional public directory prefix. This results in file resolution errors such as:
Through investigation, I noticed the resolvePath() utility in packages/ffmpeg/src/utils.ts appears to hardcode the public path segment. This behavior seems to propagate to the generateAudio functionality.
Would you kindly advise on the intended approach to handle path resolution here? I'd appreciate guidance on how we might adjust this logic to properly respect the configured outDir while maintaining compatibility with existing functionality.