Is there an existing issue for this?
Description
Current Behavior
During Editorial clip publishing on Audio products FFMPEG processing fails due to wring arguments
Expected Behavior
Audio products should be published and trimmed to correct frame-range.
Steps To Reproduce:
- in resolve clip publishing turn on Audio product creation
Additional context:
Version
ayon-resolve: 0.6.0+dev
ayon-core: 1.9.0+dev
What platform were you running when you found the bug?
MacOS
You can also provide any additional information relevant to the issue.
Relevant log output:
Traceback (most recent call last):
File "/Users/jakub/Library/Application Support/AYON/dependency_packages/ayon_2602231737_darwin.zip/dependencies/pyblish/plugin.py", line 528, in __explicit_process
runner(*args)
File "/Users/jakub/CODE/__YNPUT/ayon-core/client/ayon_core/plugins/publish/extract_otio_audio_tracks.py", line 134, in process
self.mix_audio(audio_inputs, audio_temp_fpath)
File "/Users/jakub/CODE/__YNPUT/ayon-core/client/ayon_core/plugins/publish/extract_otio_audio_tracks.py", line 409, in mix_audio
run_subprocess(args, logger=self.log)
File "/Users/jakub/CODE/__YNPUT/ayon-core/client/ayon_core/lib/execute.py", line 176, in run_subprocess
raise RuntimeError(exc_msg)
RuntimeError: Executing arguments was not successful: "(['/Users/jakub/Library/Application Support/AYON/addons_resources/ayon_third_party/ffmpeg_darwin_4ed7a974/ffmpeg', '-ss', '0.0', '-t', '9.008999999999999', '-i', '/var/folders/dc/5p9hn2_d43vgvlxsy95hfn680000gn/T/AYON_audio_ht9yy7oj/0c1fd2c8_empty.wav', '-ss', '-9.794482917762554e-05', '-t', '9.008999999999999', '-i', '/Users/jakub/__AYON_PROJECTS/AY01_VFX_demo/resources/footage/reference/sq001.mov', '-filter_complex_script', '/var/folders/dc/5p9hn2_d43vgvlxsy95hfn680000gn/T/tmpwih2dj5f.txt', '-map', '[a]', '/var/folders/dc/5p9hn2_d43vgvlxsy95hfn680000gn/T/AYON_audio_ht9yy7oj/a5528684_timeline_audio_track.wav'],)"Error:
ffmpeg version 7.1 Copyright (c) 2000-2024 the FFmpeg developers
built with Apple clang version 13.0.0 (clang-1300.0.29.30)
configuration: --prefix=/Volumes/tempdisk/sw --extra-cflags=-fno-stack-check --arch=x86_64 --cc=/usr/bin/clang --enable-videotoolbox --enable-libfreetype --enable-fontconfig --enable-gpl --enable-libvmaf --enable-libopenjpeg --enable-libopus --enable-libtheora --enable-libvorbis --enable-libmp3lame --enable-libx264 --enable-libx265 --enable-libvpx --enable-libwebp --enable-libass --enable-libaom --enable-libsnappy --enable-libvidstab --enable-libzimg --enable-libsvtav1 --enable-libharfbuzz --enable-ffplay --enable-version3 --pkg-config-flags=--static --enable-postproc --enable-nonfree --enable-runtime-cpudetect --disable-filter=yadif_videotoolbox --disable-indev=qtkit --disable-indev=x11grab_xcb
libavutil 59. 39.100 / 59. 39.100
libavcodec 61. 19.100 / 61. 19.100
libavformat 61. 7.100 / 61. 7.100
libavdevice 61. 3.100 / 61. 3.100
libavfilter 10. 4.100 / 10. 4.100
libswscale 8. 3.100 / 8. 3.100
libswresample 5. 3.100 / 5. 3.100
libpostproc 58. 3.100 / 58. 3.100
-filter_complex_script is deprecated, use -/filter_complex /var/folders/dc/5p9hn2_d43vgvlxsy95hfn680000gn/T/tmpwih2dj5f.txt instead
[aist#0:0/pcm_s16le @ 0x7fe4b4009f00] Guessed Channel Layout: stereo
Input #0, wav, from '/var/folders/dc/5p9hn2_d43vgvlxsy95hfn680000gn/T/AYON_audio_ht9yy7oj/0c1fd2c8_empty.wav':
Metadata:
encoder : Lavf61.7.100
Duration: 00:00:09.01, bitrate: 1536 kb/s
Stream #0:0: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 48000 Hz, stereo, s16, 1536 kb/s
Invalid duration for option ss: -9.794482917762554e-05
Error parsing options for input file /Users/jakub/__AYON_PROJECTS/AY01_VFX_demo/resources/footage/reference/sq001.mov.
Error opening input files: Invalid argument
Is there an existing issue for this?
Description
Current Behavior
During Editorial clip publishing on Audio products FFMPEG processing fails due to wring arguments
Expected Behavior
Audio products should be published and trimmed to correct frame-range.
Steps To Reproduce:
Additional context:
Version
ayon-resolve: 0.6.0+dev
ayon-core: 1.9.0+dev
What platform were you running when you found the bug?
MacOS
You can also provide any additional information relevant to the issue.
Relevant log output: