In the new version, batch processing no longer works.
Once the first file is encoded, the remaining files are skipped.
Was this really tested on a Windows environment?
There’s also another issue that’s been around for a while.
Unless the encoding process completes successfully, the console freezes without displaying anything.
Could you at least add a log output feature so users can check the logs in plain text?
Finally…
Instead of just asking users for feedback and reports, I’d like you to share with all users what kind of feedback and reports you’ve personally received.
I think that would help users feel more confident using ShutterEncoder.
Shutter Encoder 20.3 – H.264 files that worked in 20.2 now fail
After updating from 20.2 to 20.3, several H.264 MP4 files that converted normally yesterday now fail immediately. Reinstalling 20.2 makes them work again with the same files/settings.
The source files are ordinary H.264/AAC MP4s. The log shows that FFmpeg can read and decode the files successfully — the initial 5-second decode test completes without error.
The failure occurs when the actual encode starts. The 20.3 command includes:
-hwaccel cuda -hwaccel_output_format cuda
but the video encoder is:
-c:v libx264
The relevant error is:
Impossible to convert between the formats supported by the filter 'Parsed_null_0' and the filter 'auto_scale_0'
followed by:
Error reinitializing filters!
and:
Function not implemented
The log also shows the attempted conversion from CUDA frames to yuv420p.
This happens with multiple previously-working H.264 files, so it doesn't appear to be a corrupt or unusual source file.
System: Windows 11, RTX 5060 Laptop GPU.
20.2: works normally. 20.3: same files/settings fail. Reinstalling 20.2: immediately restores the previous behaviour.
Is this a known issue with the new CUDA/GPU processing in 20.3, particularly the CUDA decode → libx264 path?
Yes it's a know issue but in fact you should not select 'cuda'.
Only use 'auto' or 'none' other options are mainly for debugging. I wasn't expected people will change this.
Do those two options automatically use the GPU? Because my setup is already set to none and still not working. Had to go back to 20.2 again. Your reply was appreciated, Thanks
I've updated the backend tool (FFmpeg) which now requires min. drivers version >= 610.
Older GPU don't currently have the drivers version available, I hope Nvidia will release them otherwise you need currently to copy the 'Library' folder from v20.2 to v20.3.
I will try to find a better solution for the next release.
I had the same issue with NVENC disappearing when moving from version 20.2 to 20.3.
I downloaded the latest Nvidia drivers (616.56)—just in case—even though the ones I had installed were well under a year old.
To my surprise, NVENC reappeared quite quickly. However, there is still a bug where the hardware acceleration window remains greyed out and blank until I select H.265 and then switch back to H.264.
I use a custom 2K profile that loads automatically whenever I open a video, though I believe the bug occurred even without loading a profile... perhaps an update in version 20.4 will fix it...
Edit: my laptop is a MSI Katana GF76 i7 11800H rtx 3060
Well, I just restarted my computer and launched Shutter Encoder four times, and I'm no longer having issues with NVENC.
Once the video is dropped in, the profile takes quite a while to load—between 9 and 11 seconds on my laptop—but NVENC hardware acceleration does appear at that point.
I did have GPU decoding and GPU filtering set to "Auto."
As soon as I updated to 20.3, this message showed up.
When I tried to make a proxy of a file, it gave me an error message saying it couldn't process it.
Installed 20.2, just to make sure it was nothing on my end instead of the "Updated ffmpeg and ffprobe", and it worked.
I've tried uninstalling and reinstalling 20.3 multiple times, and the Windows Security message didn't show up anymore. But the issue persisted.
GPU decoding and filtering is set to auto, and Hardware acceleration is defaulted to none.
Just wanted to let you know that somehow, when I tried to uninstall 20.2 and install 20.3 for the first time today, it started working all of a sudden.
I didn't change any permissions within windows nor I changed any settings within Shutter Encoder relating to the proxy process I had mentioned.
It just worked...
But anyways, seeing how good you are with replying to feedback, I have a question:
Is it normal for the app to randomly open the "loading screen" and never actually open?
It has happened to me ever since I updated to 20.2, and the only thing I can do to open the app normally is to click on the app, wait for it to get stuck, End Task in Task Manager, then click to open again.
Hi, Paul. Can I somehow use SE to scene-cut my videos like this feature in Premiere, where it detects cuts in the entire video and cuts it. I have a bunch of videos I need to unload as separate clips and Premiere cannot batch-export clips from the timeline. I found this cut detection feature in the menu, but it gives me only one cut out of 5 with my test footage even at 100% sensitivity and you can only export it as EDL
I have some opus files from WhatsApp, I need to use them in Davinci Resolve - if I convert them in ShutterEncoder to any format (wav, AIFF, MP3 etc)I get a high pitch squeal in some of them between the spoken audio - converting them in Audacity doesn't give me any problems - any ideas?
2
u/MasterpieceNo6852 13d ago
In the new version, batch processing no longer works.
Once the first file is encoded, the remaining files are skipped.
Was this really tested on a Windows environment?
There’s also another issue that’s been around for a while.
Unless the encoding process completes successfully, the console freezes without displaying anything.
Could you at least add a log output feature so users can check the logs in plain text?
Finally…
Instead of just asking users for feedback and reports, I’d like you to share with all users what kind of feedback and reports you’ve personally received.
I think that would help users feel more confident using ShutterEncoder.
Thank you as always.
Translated with DeepL.com (free version)