On 2025-02-28 19:53, Greg Oliver wrote:
On Thu, Feb 27, 2025 at 11:49 PM Vladimir Mishonov via ffmpeg-user <
ffmpeg-user@ffmpeg.org> wrote:
Sorry - that link I referenced actually did not have the whole thread.
The
piece I intended to be included was:
https://lists.ffmpeg.org/pipermail/ffmpeg-user/2024-September/058652.html
Unfortunately, the -noautoscale option does not work either, I've
already tried that before.
It is, however, not surprising that it has no effect because
-noautoscale is an output option. And in my scenario, the output
resolution does not change over time.
As for the patch linked in that thread, I have yet to try it. Not sure
if it's already been merged into master; if not, it means I have to
compile a build myself, and setting everything up for that is likely
going to take a while...
If that does not solve it - sorry - I do not use QSV (except in Plex)
for
anything - I just remembered seeing that email thread a while back, so
looked it up. This one has a resolution, but I am unsure if it is
software
or hardware.
No problem. What I still cannot understand is whether this is some kind
of fundamental limitation or an outright bug. For some reason, I could
find very little information about this particular scenario. Whenever I
search for that error message ("impossible to convert between..."), it
always seems to concern a completely different use case.
_______________________________________________
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
_______________________________________________
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
