![]() |
QSVEnc question - Printable Version +- Selur's Little Message Board (https://forum.selur.net) +-- Forum: Hybrid - Support (https://forum.selur.net/forum-1.html) +--- Forum: Problems & Questions (https://forum.selur.net/forum-3.html) +--- Thread: QSVEnc question (/thread-3096.html) |
QSVEnc question - Nero - 21.02.2023 Hi. Is there any way to disable "--y4m" from being automatically added to the command line in order to use another reader/decoder supported by QSVEnc? ![]() Thanks for reading. RE: QSVEnc question - Selur - 21.02.2023 No, Hybrid uses: --y4m when Vapoursynth or Avisynth input is used. --avhw when 'QSVEnc->Hardware->Only use encoder' is enabled Cu Selur RE: QSVEnc question - Nero - 21.02.2023 Got it. So, could you please add "--vpp-subburn" to the "QSVEnc->Hardware" tab, so it can be used with "--avhw"? I know that it is possible to do this manually under "QSVEnc->Misc->Custom command line addition", but it's a pain to do this individually with many files. Ref: https://github.com/rigaya/QSVEnc/blob/master/QSVEncC_Options.en.md#--vpp-subburn-param1value1param2value2 Thanks anyway for answering my previous question. ^^ RE: QSVEnc question - Selur - 21.02.2023 Quote:So, could you please add "--vpp-subburn" to the "QSVEnc->Hardware" tab, so it can be used with "--avhw"?Since it seems like you have used the option before, I got a few questions:
All these need to be known before adding this to Hybrid makes any sense to me. (Yes, personally, I'm no fan of hardcoded/burned-in subtitles, which is probably the main reason why I never cared about the option.) => if you can't answer these, this will probably not happen any time soon, since I probably can't motivate myself to spend my weekends testing this. Cu Selur RE: QSVEnc question - Nero - 21.02.2023 Quote:=> if you can't answer these, this will probably not happen any time soon, since I probably can't motivate myself to spend my weekends testing this.I honestly can't answer most of these questions since I basically use it to hardcode subtitles in .ass and sometimes .srt format, so I'm sorry. But take your time, considering an addition for the future is good enough. Quote:(Yes, personally, I'm no fan of hardcoded/burned-in subtitles, which is probably the main reason why I never cared about the option.)Yeah, I personally only use this option because not all devices are capable of detecting subtitle files embedded in the container. ![]() |