Yes, it's best practice which was introduced since a lot of players did not honor the flagging of a source but either always used 601 or 709 or if you were lucky at least used 601 for SD and 709 for HD. When you perform a HD => SD conversion, you typically perform a 709=>601 colormatrix (or equivalent) conversion. When you upscale SD=>HD, typically you perform a 601=> 709 colormatrix or similar conversion. I would post in another thread or selur's forum, because this is the wrong thread to deal with those topics
Usually HD is "709" by convention, otherwise the colors will get shifted when playing back the HD version Usually the filter argument overrides the frame propsĪlso, there is no 601=>709 matrix conversion. I don't use hybrid, but the ffmpeg demuxer also makes a difference -f vapoursynth_alt is generally faster than -f vapoursynth when more than 1 filter is usedĪlso "DV" is usually BFF, and you set FieldBased=1 (BFF), but you have TFF=True in the QTGMC call. Ideal settings are going to be different for different hardware setups You have to switch out filters, play with settings, remeasure. You can use vsedit's benchmark function to optimize the script. When i check on a windows laptop, it's a few times slower using iGPU than discrete GPU or CPU (in short, iGPU OpenCL performance is poor) Is it a discrete GPU or Intel GPU on the Macbook ? If it's Intel GPU, I suspect znedi3_rpow2 might be faster in your case than OpenCL using nnedi3cl_rpow2. It might be your GPU's openCL performance causing a bottleneck. What is your CPU and GPU % usage during an encode? Hybrid took 30 minutes to output the file. Just tried a 40 second DV clip to HD with modified settings from above:
0 kommentar(er)
