Diego Casorran

er... nope, it doesn't work. ```log $ ncu -g defaultPrefix().prefix = C:\Users\dc\AppData\Roaming\npm No dependencies. ``` ```diff --- npm.js 2023-08-20 15:20:39.816120000 +0200 +++ npm.js.sh 2023-08-20 15:19:16.644871000 +0200 @@ -460,3 +460,3 @@...

Well, the same way the `env` option is overridden or whatever, this `shell` one might be as well (?) Let me know if i should try to hackpatch any of...

Yep, well for the time being i am happy with the `.npmrc` symlink, whenever i find more spare time i may get into the spawn packages to figure what is...

Thanks for your reply. I don't have a stack trace but i can provide a `-v trace` it does segfault after calling `cu->cuImportExternalSemaphore()` trace-log ffmpeg version N-111315-g76a949bf65-gb40324d417+1 Copyright (c) 2000-2023...

Thanks! Just found that priceless info 🙇🏻 `scale_cuda` is working fine here: ```log ffmpeg -hwaccel cuda -hwaccel_output_format cuda -i "%INPUT%" -vf scale_cuda=w=1920:h=-1,hwupload=derive_device=vulkan,hflip_vulkan,hwupload=derive_device=cuda -c:v hevc_nvenc ... ``` But it's right that...

Not exactly, i simplified the commands to post them here, my current goal is just downsampling 2160p to 1080p. Long story short, a few years back i did own a...

Something rather interesting is happening when i run that command here: ```log ffmpeg version N-111339-g36fae75d28-gd694c25b44+1 Copyright (c) 2000-2023 the FFmpeg developers built with gcc 13.1.0 (Rev7, Built by MSYS2 project)...

> PS: There seems to be another issue while using the -crop option, .... I think i just found what broke this, seems it's from commit https://github.com/FFmpeg/FFmpeg/commit/402d98c9d467dff6931d906ebb732b9a00334e0b (Sorry for hijacking...

Well, with `-surfaces 6` the issue does not happens, but i am now realizing a color-space problem in some scenes.  (left: down-sampled to 1080p, right: original 2160p) _edit:_ oddly...

Great suggestion, we've added it to our roadmap, but no promises or estimated time arrival :)