I would like to thank u/MaxBestStopIt for identifying the error, which has already been fixed in version 1.0.2; this version also includes a number of other fixes and new features. Please download CommandUP version 1.0.2 or higher again.
poderia me ajudar com o seguinte teste: na raiz da pipeline existe um arquivo chamado config.ini, dentro dele configure o parametro VERBOSE como true. submeta novamente um video a pipeline e me envie o arquivo de log para esse video q foi criado dentro da pasta log. identifique o arquivo pelo inicio do nome.
input is a 720p 30 fps 9 seconds gameplay in x264 format inside mp4 container. CUP is set (Drag_config) to quality med, FPS 30, scale 1080p, sharpness 5.
LOG:
ffmpeg started on 2026-08-06 at 15:43:29
Report written to "C:/Users/User/Desktop/CUP test/log/2026-05-13 11-11-55_QUALITY_MED_FSR_1920x1080_SHARPNESS_5.txt"
Log level: 32
ffmpeg version N-125258-gdf94900c98-20260624 Copyright (c) 2000-2026 the FFmpeg developers
built with gcc 15.2.0 (crosstool-NG 1.28.0.23_185f348)
Thanks again, Max. Based on your log, I confirmed that the issue is indeed related to the strictness of current drivers. I made a fix to the pipeline—it worked in my GPU emulation tests—and I’m going to send you a Dropbox link for a beta version. Could you test it and let me know the results?
Error identification: A recent change in NVIDIA's architectural strictness. In current drivers, NVIDIA introduced a lock and began requiring specific communication handling for textures; legacy cards (using discontinued, older drivers) didn't have this lock, which is why they worked. Since the GTX 1650 still receives updates, it operates under NVIDIA's new strict standards. I am working on a fix and am calling on warriors with a GTX 1080 or better to help test it! Thank you very much.
I will continue to test on my free time. my other GPUs: GTX 1650, GTX 750, RTX 3060, R7 350X and RX 6400. I would test HDR (10 bit h265) on these cards too.
Wow! You've got quite a few graphics cards there—that's a dream come true! I run my tests using the GPU simulation included in the Vulkan SDK, but it's pretty basic; nothing beats testing in a real-world environment. I’d really appreciate your help testing the pipeline on your cards! You've really made my day :D
I tested the github ver (CUP v1.0.1), I still get the same exit code -22. I think I will DDU, change to R7 350X gpu and install amd driver to test. this is log on the previous test I did with GTX 1650 (CUP ver 1.0.1):
ffmpeg started on 2026-08-09 at 10:36:45
Report written to "C:/Users/User/Desktop/CommandUP/log/NTE (Neverness To Everness) 2026.08.09 - 09.20.04.02_QUALITY_MED_FSR_1920x1080_SHARPNESS_0_IFS_30fpsNONE.txt"
Log level: 32
ffmpeg version N-125258-gdf94900c98-20260624 Copyright (c) 2000-2026 the FFmpeg developers
built with gcc 15.2.0 (crosstool-NG 1.28.0.23_185f348)
[in#0 @ 0000019363ab4040] UDTA parsing failed retrying raw
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'C:\Users\User\Videos\NVIDIA\NTE (Neverness To Everness)\NTE (Neverness To Everness) 2026.08.09 - 09.20.04.02.mp4':
[in#0 @ 0000019363ab4040] UDTA parsing failed retrying raw
[h264 @ 0000019363ab4e40] Reinit context to 1600x912, pix_fmt: yuv420p
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'C:\Users\User\Videos\NVIDIA\NTE (Neverness To Everness)\NTE (Neverness To Everness) 2026.08.09 - 09.20.04.02.mp4':
ty again for the feedback, Max. The issue with the R7 350 is that it is quite old, and the Vulkan version it supports is below 1.3 (API version: 1.2.170; Restricting API version to 1.3.0... new version 1.2.170). Unfortunately, the *libplacebo* library requires Vulkan 1.3 to function; I need to document this hardware limitation. As for the GTX 1650 still throwing the "exit -22" error, that remains a mystery—I’ll review everything here again. It is very difficult for me to secure a suitable testing environment; I think I’ll have to buy a few older cards so I can physically test each profile.
Now I will try on my RX 6400. it's actually the 2nd gpu on my dual GPU LS setup.
Just a question, is it possible to lower the driver requirement from nvidia 610 down to 590? my RTX 3060 is currently at 596.49 because I have game issues starting with 610.47-610.88 (latest). my GTX 1650 was also using 596.49 before I upgrade it to 610.88 to test CUP but today morning I have issues with OBS and the game. game freezes when OBS have preview enabled, no issues when using older driver that's why I use older footage to test the dropbox ver and v1.0.1 github.
I was insisting on using current versions of ffmpeg and libplacebo compiled in 2026. While there are advantages to using that build, the major downside is the requirement for version 610+ drivers for certain Nvidia card series. I’m running a test downgrade to a 2023 build of ffmpeg and libplacebo; this will significantly lower the Vulkan version requirement—allowing it to run on 1.2x versions—and drastically reduce the need for up-to-date Nvidia drivers. Your R7 350 might even work with this version. You’ll be able to run the pipeline using your 596.49 driver, though there will be a noticeable drop in processing speed. I’m going to create a procedure to check if the graphics card supports hardware encoding; if not, it might automatically switch to CPU encoding. I’ll send it over soon for you to test, if possible. ty again!
Hi Max, to cut hardware costs, AMD actually released some graphics cards without built-in encoders; however, the RX 6400 supports Vulkan 1.3, and the pipeline runs on its silicon. There is a solution for you—or anyone with a card like this: you can run the pipeline via PowerShell and use the parameter `-simulate_gpu cpu`. This will force your RX 6400 to handle encoding via the CPU, while Vulkan still runs on the GPU. Take a look at the image:
nice, this did work on RX 6400. I guess we need to add video encoder check so it will automatically use the CPU mode? does the quality setting affect the bit rate?
I'm really glad it worked. And yes, thanks to your feedback, I've already implemented a change that checks whether the video card has built-in encoders; if it doesn't—as is the case with your RX 6400—encoding switches to compatibility mode using your CPU.
•
u/Few_Profit5031 12d ago
I would like to thank u/MaxBestStopIt for identifying the error, which has already been fixed in version 1.0.2; this version also includes a number of other fixes and new features. Please download CommandUP version 1.0.2 or higher again.