사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/remotion-dev/remotion --skill homepage-video-assets시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Homepage Video Assets
Use this workflow for homepage creator strip assets such as:
homepage-assets-masterediting-vp9-chrome/editing-safariwhat-is-remotion
Workflow
- Render a fresh transparent ProRes 4444 master from
packages/brand.
cd packages/brand
bunx remotion render <composition-id> /tmp/<asset>-master.mov \
--codec=prores \
--prores-profile=4444 \
--pixel-format=yuva444p10le \
--image-format=png \
--timeout=120000 \
--overwrite- Convert from the ProRes master, not from a previous WebM/MOV.
Chrome WebM:
ffmpeg -y -i /tmp/<asset>-master.mov \
-vf scale=540:540 \
-c:v libvpx \
-pix_fmt yuva420p \
-auto-alt-ref 0 \
-an /tmp/<chrome-name>.webmSafari MP4:
ffmpeg -y -i /tmp/<asset>-master.mov \
-vf scale=540:540 \
-c:v prores_ks \
-profile:v 4 \
-pix_fmt yuva444p10le \
-an /tmp/<asset>-540-prores.mov
avconvert \
--source /tmp/<asset>-540-prores.mov \
--preset PresetHEVCHighestQualityWithAlpha \
--output /tmp/<safari-name>.mp4 \
--replace- Copy both outputs into both app folders:
cp /tmp/<chrome-name>.webm ../promo-pages/public/img/<chrome-name>.webm
cp /tmp/<safari-name>.mp4 ../promo-pages/public/img/<safari-name>.mp4
cp /tmp/<chrome-name>.webm ../docs/static/img/<chrome-name>.webm
cp /tmp/<safari-name>.mp4 ../docs/static/img/<safari-name>.mp4Verification
Verify the ProRes master has real alpha before converting, and verify the Safari MP4 exists in both folders:
ffmpeg -i /tmp/<asset>-master.mov
ffmpeg -i ../promo-pages/public/img/<safari-name>.mp4
ffmpeg -y -i /tmp/<asset>-master.mov \
-vf alphaextract -frames:v 1 /tmp/<asset>-alpha.pngThe master should report prores (4444) and a yuva... pixel format. alphaextract should succeed, and the alpha image should not be fully opaque. A common failure mode is alphaextract succeeding but every sampled pixel is opaque; in that case, the master was rendered with a black/opaque background or a stale opaque master was reused.
Verify every copied Chrome WebM and Safari MP4 is exactly 540x540:
for f in \
../promo-pages/public/img/<chrome-name>.webm \
../promo-pages/public/img/<safari-name>.mp4 \
../docs/static/img/<chrome-name>.webm \
../docs/static/img/<safari-name>.mp4; do
ffmpeg -i "$f"
doneThe Safari MP4 should look like the known-good file shape: major_brand: mp42, compatible_brands: isommp41mp42, Video: hevc (Main) (hvc1), 540x540, and handler_name: Core Media Video. If it reports h264 (avc1) or dimensions such as 960x540, it is the wrong file and will render differently in Safari.
Do not add ProRes .mov files to the homepage PR; they are too large. Safari should use the small .mp4 fallback. Chrome should use the transparent .webm.




