Unsupported codec with id 0 for input stream 1 If I run ffprobe on the input files I am testing with Topaz, it clearly shows the timecode can be read by FFMpeg: $ ffprobe testTopaz.movįfprobe version 4.4 Copyright (c) 2007-2021 the FFmpeg developersīuilt with Apple clang version 12.0.5 (clang-1205.0.22.9)Ĭonfiguration: -prefix=/usr/local/Cellar/ffmpeg/4.4_2 -enable-shared -enable-pthreads -enable-version3 -cc=clang -host-cflags= -host-ldflags= -enable-ffplay -enable-gnutls -enable-gpl -enable-libaom -enable-libbluray -enable-libdav1d -enable-libmp3lame -enable-libopus -enable-librav1e -enable-librubberband -enable-libsnappy -enable-libsrt -enable-libtesseract -enable-libtheora -enable-libvidstab -enable-libvorbis -enable-libvpx -enable-libwebp -enable-libx264 -enable-libx265 -enable-libxml2 -enable-libxvid -enable-lzma -enable-libfontconfig -enable-libfreetype -enable-frei0r -enable-libass -enable-libopencore-amrnb -enable-libopencore-amrwb -enable-libopenjpeg -enable-libspeex -enable-libsoxr -enable-libzmq -enable-libzimg -disable-libjack -disable-indev=jack -enable-avresample -enable-videotoolbox Is this a known problem? I have tested two source input codecs: DNxHR and ProRes 422 HQ. This is going to make it impossible for me to conform the files written by Topaz back into my Resolve timelines. With timecode turned on, in the app it shows all clips starting at 00:00:00:00. I’m still testing with Topaz and just realised I have a pretty major problem - the timecode of my source clips is not read or preserved! I tested both 2.3 and 2.4, and I have “experimental timecode” turned on.
0 Comments
Leave a Reply. |