Of course you've got to have a fast enough PC, and it's all personal preference, but I thought I'd mention it in case you weren't aware it could be done. I also assume they'd be faster but lower quality. Some of the scripts use the original version of Interframe (which I think requires MVTools2), some use Interframe2, and some don't require Interframe at all. You might just need to modify the scripts according to where you've put the Interframe plugins. I haven't used it much myself but Potplayer comes configured with scripts for frame interpolation on playback. To be honest I haven't really played with it but it's much like having Interframe installed as a DirectShow filter.Īnother option is Potplayer, and possibly a better option, as it doesn't need to install extra DirectShow filters. Third, specify which rows to update in the WHERE clause. The columns that are not listed in the SET clause will retain their original values. Second, specify the columns that you want to modify in the SET clause. If you can open that script in MPC-HC and your PC is fast enough, it'll display the script in real time, which means you can watch video that way without converting it (my old PC is fine for SD but not fast enough for HD). Code language: SQL (Structured Query Language) (sql) In this syntax: First, indicate the table that you want to update in the UPDATE clause. Not without keeping the original too, because the process of interpolating frames can introduce artefacts and you'll be encoding them forever. I'd rarely convert videos that way myself. Not that it matters now, given you've managed to sort it.īy the way. Settings: -preset placebo -bitrate 3000ĭoesn't seem to be x264 but maybe just handbrake? It's worth noting Handbrake seems to make some changes that deviate from the preset despite changing all I could within the interface.ĮDIT: Updated with FFMPEG results, they seem mostly similar to x264 CLI.Very likely, if you'd opened the script in another program, you'd have seen an error message such as "there's no such function as SetMTMode", because the standard version of Avisynth doesn't have a multi-threaded mode. I just tested the x264 build by VideoLAN and got some interesting results when supplying different thread counts. So take these numbers with a grain of salt. When I'm encoding HEVC or VP9 I can tell that my system is being stressed more heavily than with x264 because the fan speed and noise levels are a bit higher (and also due to the noticable slowdown in other tasks while encoding). A percentage or a number of cores utilised is a simplification. Measuring CPU usage also isn't as simple as one would think. Although even with 4K it doesn't go significantly beyond that and stays at around 6 cores so I'm suspecting it's a hardware bottleneck, not a system one. Can I run updater.exe from memory (updater.exe will be included in mainprogram.exe) and then. Even with the threading improvements added earlier this year, 1080p encoding only fully saturates about 5-5.5 cores on my system. I know that I can have Updater.exe & MainProgram.exe but I want to keep my release in one EXE file. Instead the amount of usable threads directly depends on video resolution. Installation: Please extract the archive to a path without special restrictions (like ProgramFiles in Vista/Windows 7). Then there's VP9 (libvpx) which doesn't use the same kind of parallelism that x264 and x265 use. Encoding 4K can slow the system down to a point where you really wouldn't want to use it for other tasks while encoding. I've seen no such thing happen with x264. With plenty of RAM available, encoding 1080p maxes out the CPU and causes noticable slowdown on the desktop. With x265 I'm pretty darn sure that moving data around fast enough inside the CPU or between the CPU and RAM is starting to become an issue. Can't really tell whether some of these post-720p scaling issues on faster presets are due to a bandwidth limitation or a specific part of the CPU being maxed out. Want to give your CPU a workout regardless of resolution? Use slower presets (slower and veryslow really increase CPU usage). 4K will almost fully saturate an 8-core CPU. Low-res, DVD-level video? Won't really scale beyond 6 cores whatever you do. Not only that, but the settings used and even the video resolution also affect how well the workload scales (at least with x264).
0 Comments
Leave a Reply. |