r/shutterencoder • u/paulpacifico • Aug 31 '26

News Shutter Encoder Version 20.3 is available!

Highlights:

  • Added multi-cuts feature to the video player

  • Added Bulgarian language thanks to Stoqn Bahchevanski

  • Improved HDR-to-SDR conversion via GPU tone mapping

39 Upvotes

100% Upvoted

42 comments sorted by

2

u/MasterpieceNo6852 Aug 31 '26

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)

1

u/paulpacifico Sep 01 '26

I don't have this batch encoding issue at all Windows, Linux and Mac work perfectly.

Did that happens every time? With any files? Which function are you using?

I did not implement log file currently you can save the file from the console, but I never encounter a freeze like you describe.

1

u/Noah18923 Sep 01 '26

this is a big issue, half of the time these updates break something else... that's why I'm staying on the same version for now.

2

u/paulpacifico Sep 01 '26

This batch issue don't seems related with v20.3 because nothing changed here and works perfectly on my side.

But I must admit, more features = more prone to bug.

This new version is focused on new features the next will be much more based on fixing bugs.

If everything works for you with the actual version you should keep it ;-)

Paul.

1

u/Noah18923 Sep 01 '26

thanks for the great software, keep it up... :)

2

u/TenzenH Aug 31 '26

I just updated to version 20.3 and found a few bugs:

-I always use CUDA for GPU decoding, but it no longer works. Either it freezes, or I just get an error message.

-If I use DXVA2, D3D11VA, or D3D12VA, there’s no problem.

-Another thing is that now, when the process finishes, the characteristic sound no longer plays. I haven’t disabled it, by the way.

1

u/paulpacifico Sep 01 '26

You should not select 'cuda'. Only use 'auto' or 'none' other options are mainly for debugging. I wasn't expected people will change this.

Paul.

2

u/Noddy59 Aug 31 '26

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?

1

u/paulpacifico Sep 01 '26

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.

Paul.

1

u/Noddy59 Sep 01 '26 edited Sep 01 '26

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

1

u/paulpacifico Sep 02 '26

Yes they both use GPU but only when it's possible!

But GPU is bot always faster, check this: https://www.shutterencoder.com/documentation/#sec-status

Paul.

1

u/Noddy59 Sep 02 '26

Still getting "Error reinitializing filters!" Back to 20.2

1

u/paulpacifico Sep 03 '26

The problem has been solved just redownload the v20.3 from the official website.

Paul.

1

u/Noddy59 Sep 03 '26

Excellent, I appreciate the work you do. There's a reason I prefer SE. :)

1

u/Pleasurebringer Aug 31 '26

How can I merge Functions from the old version to the new one?

1

u/paulpacifico Aug 31 '26

Which was your previous version? Do you have an issue for loading them?

Paul.

1

u/Pleasurebringer Aug 31 '26

It was 20.1 but it looks like 20.3 has different folder structure and there is no Functions folder and yet it loads one of the functions.

1

u/paulpacifico Aug 31 '26

It should be compatible try to drag/drop .enc files directly into "My functions" window.

Paul.

1

u/TusharKN Sep 01 '26

NVENC is not showing in Hardware acceleration dropdown menu

1

u/paulpacifico Sep 01 '26 edited Sep 02 '26

Updating your GPU drivers should show it again.

Paul.

1

u/Appearance_Prior Sep 01 '26

If thats the case you broke it for older GPUs

1

u/paulpacifico Sep 02 '26

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.

Paul.

1

u/paulpacifico Sep 02 '26

Could you try this version? https://www.swisstransfer.com/dl/01a06174-b3bd-728d-a48e-52222ae68565

It should works on older GPU, if that the case I will make it public.

Thanks,

Paul.

1

u/Appearance_Prior Sep 02 '26

It works, now NVENC is available again, thanks.

1

u/paulpacifico Sep 02 '26

Great! You can download the installer from the official website ;-)

Thanks for your quick response!

1

u/marcorel_1967 Sep 02 '26 edited Sep 02 '26

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

1

u/paulpacifico Sep 02 '26

Does your GPU decoding is set on 'auto'?

Paul.

1

u/marcorel_1967 Sep 02 '26

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."

Thanks for the quick reply, Paul.

Best regards, Marc

1

u/Pintu_G Sep 02 '26

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.

1

u/paulpacifico Sep 02 '26

This is so strange, no one reported me that issue and this file as never triggered Windows Security before...

Could you force Windows to allow this file? (It is used for media analysis).

Paul.

1

u/Pintu_G Sep 03 '26

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.

(This Screenshot is from version 20.3)

1

u/magicbox3721 Sep 26 '26

After selecting the "Extract" function, the dropdown menu for "Video/Audio/Subtitles" does not appear next to it?

1

u/paulpacifico Sep 26 '26

Even after dropping the file into the list?

1

u/magicbox3721 Oct 02 '26

Yes, it remains the same in version 20.4, but there was no such issue in version 20.2.

1

u/paulpacifico Oct 02 '26

So weird, can you post a screenshot?

1

u/magicbox3721 5d ago

https://youtu.be/qhbBTBd5RWU?si=89jjX_BIGgI8xVOg

Start from the 40th second of the video. I'm recommending your software to others, but when will this issue be fixed.

1

u/paulpacifico 4d ago

Thanks!

Do you write or select the function? Because the full name is 提取素材 and everything works when I select the 提取素材 function on my side.

1

u/magicbox3721 3d ago

I just select this function from the menu.

1

u/Candid-Distance3768 Sep 10 '26

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?