![]() Nobody never told that it was made for a professional use. That’s why I was hoping I was missing something, like it works with some input formats but not others or something like that. I understand that it’s labelled experimental, but ‘experimental’ to me implies “works with some caveats”, however right now it seems like it doesn’t work at all. I’m hoping there’s something I’m missing and this can be made to work? But that’s going to be impossible without timecode. If I use it I will want to process several thousand clips and it’s vital that I can reconform them onto my original timelines. ![]() I don’t understand how this software can be usable in a professional context without preserving timecode. 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. ![]() Once I closed Telegram and restarted the render/program, things go up to full speed and I gain a few % more perf.Ĭould you check out the 3.0 betas and see if that makes any difference to your power consumption? Oddly enough I found my 3070’s power usage to drop considerably (same with a A1000 dgpu in a laptop) to keep it at a lower power state, without any performance differences versus the previous version.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. This hurts all GPU compute (Hashcat too, lol!) for no good reason. Dunno why, but it manages to do that, my 3070ti normally runs upscales at a peak of 1985-2040Mhz but occasionally I’ve found it to be bugged with Telegram open (minimized / in tray even!), reducing the clocks to 1765~ MHz which is one of the middle power states. On this note… if you’re using Windows (or just check it anyways), running Telegram can drastically cap clocks for no good reason.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |