Hi Michael,

you asked me to open pull requests, because they currently get more
attention than the mailing list. They are open. The automated tests
then brought a number of issues to light, which I had corrected with
Cursor. My question now is how to proceed so that this can still be
integrated in 9.1.

Thank you for the comments. I am replying to them below.

Timo, nyanmisaka: following nyanmisaka's pointer to #22340, I had the
yuvrgb_cuda conversion from #24729 put into scale_cuda. That is what
my local Mapillary workflow uses, on my forgejo branch
pr/scale-cuda-round. #24729 does not need to be merged as a separate
filter.

nvJPEG (#24727) is cleaned up accordingly and gated on --enable-nonfree.
Please consider merging it, so that Mapillary users only have to build
FFmpeg with that option and do not have to carry a patch.

Kacper: the GoPro Max implementation (Max 1, the model before Max 2)
was the template for my work, and I would have asked for that to be
merged in return. I did not know the pull requests you pointed to at
the time. I have since decided to handle the Max 1 geometry inside my
Max 2 filters. Max 1 is then available to mapillary_tools on all three
paths: CUDA, CPU and OpenCL.

On the flush after each log message (#24730): fflush at the end of each
log message is there to get efficient line-buffering behavior on
Windows, where _IOLBF is fully buffered and a newline does not empty
the buffer. Setting stderr to _IONBF once at startup would match Linux,
where stderr is unbuffered.

James: thank you again for the hint. That pull request is already
closed.

Regards,
Reinhard

On Sat, 26 Sep 2026 16:03:59 +0200, Michael Niedermayer wrote:
please open a PR, i do love the mailing list but ATM PRs get more
attention, I do expect that we eventually fix that ML attention issue
and have some LLM keep track to all patches from the ML but ATM iam a
bit overloaded with security reports and other things
_______________________________________________
ffmpeg-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to