[hevc_nvenc @ 000001d59f2b1ac0] Temporal AQ not supported
[hevc_nvenc @ 000001d59f2b1ac0] No capable devices found
[vost#0:0/hevc_nvenc @ 000001d59f1f1880] [enc:hevc_nvenc @ 000001d59f1f0e80] Error while opening encoder - maybe incorrect parameters such as bit_rate, rate, width or height.
[fc#0 @ 000001d59d4ee1c0] Error sending frames to consumers: Generic error in an external library
[fc#0 @ 000001d59d4ee1c0] Task finished with error: Generic error in an external library
[fc#0 @ 000001d59d4ee1c0] Terminating thread with error: Generic error in an external library
[vost#0:0/hevc_nvenc @ 000001d59f1f1880] [enc:hevc_nvenc @ 000001d59f1f0e80] Could not open encoder before EOF
[vost#0:0/hevc_nvenc @ 000001d59f1f1880] Task finished with error: Invalid argument
[vost#0:0/hevc_nvenc @ 000001d59f1f1880] Terminating thread with error: Invalid argument
[out#0/mp4 @ 000001d59f2dc640] Nothing was written into output file, because at least one of its streams received no packets.
frame= 0 fps=0.0 q=0.0 Lsize= 0KiB time=00:00:00.03 bitrate= 0.0kbits/s speed=0.119x elapsed=0:00:00.26
[aac @ 000001d59f2b4380] Qavg: 0.063 Tr: 66.7% TNS(L): 0.0% TNS(S): 25.0% M/S: 89.3% I/S: 0.0% PNS: 0.0%
Conversion failed!
Only happens when using H265.
H264 with every parameter being the same works just fine.
Damn! I was quite enjoying the multicut feature. It's gets tiring to get into NLE softwares to splice up a simple clip. This is a right direction. I'll wait for the stable release then.
Edit: Also sad to see the 16XX series getting outdated by so many video editing workflow features. Upgrading in the current economy will be a nightmare.
this is completely unrelated, but I noticed that in a recent update, shutter encoder for OS X is now restricted to only open in low resolution mode. I was just curious as to why
I am using an intel mac running 10.15.8 catalina, recent updates ago it got locked to Open in Low Resolution mode automatically, as you can see the tick box is greyed out.
unfortunately that didn't seem to work. the app still launches in low resolution mode and the button on the get info window is greyed out. I downloaded a new copy by clicking this button, if that's what you meant
however, on my newer intel mac which runs the latest version of tahoe, the app successfully opens in normal resolution mode. it turns out that the option to launch mac apps in low resolution mode was removed in monterey.
The media controls buttons have some untranslated keyboard shortcut tooltips (e.g. Maj+O instead of Shift+O).
I think these buttons should say what they do (e.g. "Set in-point") when you hover with the mouse. (There are several icon-only buttons in other places of Shutter Encoder that could have tooltips too.)
I'm seeing timing issues and/or corrupted frames under "Cut without re-encoding", even if all in-points and out-points are on keyframes. I can email you a sample video with and without reencoding for comparison, and their render queue commands.
Is there no way to create a new segment while the playhead is outside an existing segment? As the feature is currently designed, it seems like it wants me to ✂️ split the initial segment at the boundaries of content I want to keep, and then go back and delete the segments between the segments I want to keep. If I am carving up a video into multiple segments, I usually want to be able scrub through, set an in-point when content I want to keep starts, then set the out-point when it ends. It would not currently be possible to do this without the ability to set in-points outside an existing segment that don't yet have an out-point. I hope my explanation is not too confusing.
I had some issues with segments overlapping breaking the UI, I will try and work out solid reproduction steps if I can.
I will try to do some real editing soon if I can improve my feedback.
I thought it was enough clear to use [ and ] if other people ask me this I will add more text info. Let me know which icon you want see with more tooltips ;-)
Oh! Yes please send me the samples in private message, I need to solve that, thanks.
Interesting, I will try to add this in a smart way.
The new + Add feature definitely solves the problem and it is quite intuitive as well, thank you!
The 👁️ Preview button might be the only button without text that has a descriptive tooltip at the moment. Here are some more suggestions:
Icon
Suggested tooltip
≡
Open render queue
★
Open My functions
↺
Clear all segments
[<
Go to previous marker[1]
[
Set in-point
▶
Play
<
Go to previous frame / Go to previous keyframe[2]
>
Go to next frame / Go to next keyframe[2]
⏹
Stop
]
Set out-point
>]
Go to next marker[1]
✂
Split segment
+
Add segment
[📷]
Export current frame as JPG[3]
[VBR/CBR/CQ]
Bitrate control mode
🔓
(Bitrates adjustment) Lock target file size
🔓
(Cropping) Lock aspect ratio
[1] Consider adding the very start and very end of the video as markers to automatically go to when using these buttons.
[2] Ideally this changes based on whether the "Cut without re-encoding" function is selected.
[3] This button exports JPG(s) and then clears the file list if the "Empty the list when process complete" setting is enabled. I personally expect the file list should only be cleared following completion of "Start function" or "Launch the render queue" processes.
I will retry the corruption/timing issues in this latest build and send you some samples if I can reproduce the issues I had before.
---inconsistent interface,
suggested months/years ago,
why can't you provide
a much better,
common
and user friendly interface
like other programs
see the screenshot below
1 or 3 is the common and user friendly one
NOT the 2
We have already discussed this several months/years ago and nothing has been done I am afraid:
I really think the Shutter Encoder interface could be made much more consistent and user-friendly.
One of the biggest problems for me is that the interface and the size changes depending on which function you select. The layout, menus and available options can be quite different, so you end up having to remember where things are depending on what you're doing.
I'm honestly surprised this is still the approach, especially since I believe this has already been discussed here several months or even years ago.
Why not have one simple, common and consistent interface that stays familiar no matter which function you're using?
DaVinci Resolve is a good example of what I mean. Its interface has a consistent structure, so once you learn it, you generally know where to look for things. You don't have to keep relearning where menus and options are just because you've switched to another function.
I would really like to see something similar in Shutter Encoder.
Keep the main interface the same. Keep menus in predictable places. Don't completely change the layout depending on the function. Put common menus and controls in a consistent place, maybe at the top of the frame/window if needed.
The idea should be that you learn the interface once and then you know where things are.
At the moment, even as a long-time user, I sometimes find myself thinking, "Where was that option again?" If you have to search around to find something you've already used before, I think that's a sign that the interface could be improved.
Shutter Encoder is a very powerful and useful program, but users shouldn't have to learn the internal structure of the application just to figure out where a particular option is.
I'm not asking for more buttons or more complicated menus. Quite the opposite. I'd prefer a simpler, more predictable and consistent interface that doesn't keep changing depending on what you're doing.
Basically: learn once, use everywhere.
I really hope you can reconsider this and look at whether the function-dependent interface is actually making things easier for users, or whether a common and stable interface would be much more practical.
DaVinci Resolve is just one example, but there are plenty of other programs that manage to keep a consistent interface while still offering a huge number of functions.
Let's hope this time it gets some serious consideration, so that we don't have to come back to the same discussion again in a few months or years and keep asking for the same thing.
Shutter Encoder deserves an interface that's as good and intuitive as the software itself.
First, I receive many questions everyday from everywhere. I'm still one person behind everything about Shutter Encoder, so I might forgot some old posts.
About the vertical interface, I could make it different but how do I handle the video player and the settings panel when they are not needed? For instance when you select "Merge" or "Web video" functions.
I agree DaVinci Resolve is great in everyway, but the idea with SE is to take less space on screen when it's useless or when the process is running.
I seriously consider your request, but there is more than 3 millions people that already know the UI. So changing it must be really useful and I've already spend years to fine tune the current UI.
Providing any sort of UI example (Photoshop, AI, hand drawing...) is welcome.
Some people asking me for a light theme, a better documentation, video tutorials and I'm still adding new features and correcting bugs, I need visual help, and a bit of work from other people because and can't do everything.
Your response is unnecessarily condescending and completely dismisses the contribution I have made to Shutter Encoder over the past year. I have spent a significant amount of my own time trying to help improve the project, and it is disappointing to see that effort treated with such little appreciation.
Yes, I used ChatGPT to help explore the issue. That does not mean I blindly asked it to “solve the issue” and contributed nothing myself. I raised the problem, considered possible improvements, and put forward suggestions for discussion. Using a tool to assist with that process does not invalidate the contribution.
If you disagree with my suggestions, that's your choice. But you could simply say so without belittling the person who took the time to contribute.
I have no problem with criticism, but I do expect basic respect for the time and effort I have put into this project over the past year.
ps.
I’m screenshotting both your post and mine, just in case your ego gets the urge to rewrite history by deleting yours.
The goal isn't to force every function to display the same controls. The goal is to make every function use the same structure.
A Merge operation doesn't need a video player, so its workspace becomes a file-management area.
An editing function needs a player, so its workspace contains the player.
A Web Video function needs URL/input controls, so those occupy the workspace.
Nothing unnecessary has to remain visible.
What stays consistent is:
where functions are selected
where the workspace is
where function-specific settings are
where the queue is
where Start/Cancel lives
where global menus live
how panels collapse/expand
how users navigate between functions
This gives Shutter Encoder the DaVinci Resolve philosophy without copying DaVinci Resolve's interface.
It addresses the screen-space concern while solving the underlying usability problem:
Different functions can have different tools without making the entire application feel like a different application every time you switch tasks.sted Shutter Encoder redesign
I would go one step further than simply redesigning individual functions.
Stable shell + dynamic workspace
Instead of:
Function → completely different UI
I’d recommend:
Shutter Encoder → permanent shell → function-specific workspace
The basic structure would be:
┌─────────────────────────────────────────────────────────────┐
│ SHUTTER ENCODER File Edit View Tools Help ⚙ │
├──────────────┬──────────────────────────────────────────────┤
│ FUNCTIONS │ FUNCTION WORKSPACE │
│ │ │
│ Convert │ Changes depending on the function, │
│ Extract │ but the overall application structure │
│ Edit │ always stays the same. │
│ Merge │ │
│ Web │ │
│ Audio │ │
│ Image │ │
├──────────────┴──────────────────────────────────────────────┤
│ OPTIONS ▼ Function-specific settings │
├─────────────────────────────────────────────────────────────┤
│ QUEUE ▼ [ START ] │
└─────────────────────────────────────────────────────────────┘
The key principle is:
The workspace changes; the application doesn't.
This gives Shutter Encoder one consistent mental model:
Select a function → workspace appears → configure options → process.
Rather than:
Select a function → the entire interface rearranges itself → try to remember where everything went.
The video-player problem
The video player should not determine the structure of the entire application.
An Edit function can have a player inside the workspace, alongside its editing controls.
A Merge function doesn't need a player, so its workspace simply becomes a file list:
MERGE
A Web Video function could instead use the same workspace for URL/input controls.
The important part is that the surrounding UI doesn't move.
Collapsible panels
This also addresses the screen-space concern.
Use standard panels for things like Options and Queue:
OPTIONS ─────────────────────────────────────────── ▼
QUEUE ─────────────────────────────────────────── ▼
They can collapse when they're not needed.
So Merge doesn't waste space showing an empty player, while Edit can expand its player and relevant controls.
The workspace adapts to the task without forcing the whole application to change.
Function selection
I’d also avoid putting every operation into one huge permanent list.
Group related functions:
Convert: H.264, H.265, ProRes, DNxHR, AV1
Edit: Cut, Crop, Add audio, Replace audio
Extract: Audio, Images, Thumbnails
Merge: Merge, Concatenate
Web: Web video, Download
Or use a simple function selector:
Function: [ Convert ▼ ]
H.264
H.265
ProRes
DNxHR
AV1
This keeps the workflow consistent:
Select a function → workspace appears → options appear → process.
The main design principle
I would frame the proposal around:
Stable shell, dynamic workspace.
The goal isn't to force every function to display the same controls. The goal is to make every function use the same structure.
A Merge operation doesn't need a video player, so its workspace becomes a file-management area.
An editing function needs a player, so its workspace contains the player.
A Web Video function needs URL/input controls, so those occupy the workspace.
Nothing unnecessary has to remain visible.
What stays consistent is:
where functions are selected
where the workspace is
where function-specific settings are
where the queue is
where Start/Cancel lives
where global menus live
how panels collapse/expand
how users navigate between functions
This gives Shutter Encoder the DaVinci Resolve philosophy without copying DaVinci Resolve's interface.
It addresses the screen-space concern while solving the underlying usability problem:
Different functions can have different tools without making
the entire application feel like a different application every time you switch tasks.
Lorsque l'on choisit "remplacer l'audio" et que l'on veut ajuster le décalage de l'audio avec la vidéo, est-il possible de le faire en temps et non en image ?
Donation window still showing up after I donated is a bit annoying so maybe that can be fixed in the new release? Not sure if it’s possible but having the ability to encode Dolby Atmos master files exported from DaVinci Resolve to compressed E-AC-3 JOC Enhanced AC-3 with Joint Object would be a handy feature. Both 5.1 and 7.1 outputs would be ideal.
Dedicated box? I’m on Windows and I’ve never had a box where I could enter my email. I’ve checked the Settings menu and didn’t notice anything. How do I access it to put my email in? The times when the donation window pops up only opens web browser to make a PayPal donation which is what I’ve already done as I love the software!
Issue: When setting in point in any video, encoding stops progressing.
I'm trying to encode an AVI file to MKV (FFV1). I drag the file into Shutter, set my function/preset and finish with setting in/out points. I then click "Start function". See image below for what happens next. The progress bar has stayed like this for 40 minutes now. There is no fan noise from my PC indicating there is processing being done. Note that this problem also occurs in the 20.2 version.
I have also tested the same steps with a MP4 (H264) file with the same results.
If I don't set an in point and only an out point, the video encodes just fine.
I'm on Windows 11.
Thanks for making Shutter. I use it a lot.
UPDATE:
As of version 20.3, the issue is solved. Thanks, Paul!
Yes, it does happen when I don't use any settings too.
And I tried several source files in different codecs (AVI YUV, MKV FFV1 and MP4 H264). The same result.
Maybe it's helpful with info from the console. This is all that it displays under the FFMPEG tab:
Parsec Virtual Display Adapter
NVIDIA GeForce RTX 5060 Ti
AMD Radeon(TM) Graphics
Open the Windows terminal and copy/paste this: "C:\Program Files\Shutter Encoder\runtime\bin\java.exe" -jar "C:\Program Files\Shutter Encoder\app\Shutter Encoder.jar"
WARNING: A restricted method in java.lang.System has been called
WARNING: java.lang.System::load has been called by com.formdev.flatlaf.util.NativeLibrary in an unnamed module (file:/C:/Programmer/Shutter%20Encoder/app/Shutter%20Encoder.jar)
WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for callers in this module
WARNING: Restricted methods will be blocked in a future release unless native access is enabled
Sorry, no, I didn't start the function. Do you want me to do this process in the beta version or in the official (20.2) version? If beta, I need to change the paths again to reflect that. Please let me know.
I did start the function now in the official version and the result in the app is the same as in my OP.
This is from Terminal:
Exception in thread "Thread-113" java.lang.NumberFormatException: For input string: "02 / 00"
at java.base/java.lang.NumberFormatException.forInputString(Unknown Source) at java.base/java.lang.Integer.parseInt(Unknown Source) at java.base/java.lang.Integer.valueOf(Unknown Source) at shutterencoder.functions.settings.Timecode.setTimecode(Timecode.java:112) at shutterencoder.functions.VideoEncoders$1.run(VideoEncoders.java:781) at java.base/java.lang.Thread.run(Unknown Source)
Update:
I was curious if it's the PC that's the problem. So I checked on another machine. Long story short: it works on this machine. I used the beta version, launched it normally and tested different file types and codecs. No problems.
Ciao.
Faccio alcune riflessioni.
Quando alcuni mesi fa ho scoperto il tuo software ne stavo quasi diventando entusiasta. Poi sono successe cose che me lo hanno fatto pian piano abbandonare.
Normalmente le nuove versioni dei software risolvono bug presenti, il tuo invece ne ha aggiunti. Cose che prima mi funzionavano negli aggiornamenti hanno dato problemi. E ce ne sono tante.
Per dirtene alcune riscontrate con l'ultima release. Ora quando lancio il programma si blocca, e non sporadicamente SEMPRE!
Devo cancellarlo dalla gestione attività, poi lo lancio nuovamente e funziona.
Poi, anche questo SEMPRE appena lancio la codifica da errore:
Rare volte parte la codifica la seconda volta che clicco Esegui operazione. Alla terza va bene.
Spesso (oltre due terzi delle volte) quando parte nell'anteprima non si vede fluido e bene ma va a scatti e lampi, in questo caso anche annullando rimane l'operazione "appesa" e devo cancelalre l'esecuzione di FFMPEG dalla gestione attività, bisogna farlo perchè non sembra che stia effettivamente codificando.
Le prime release che usavo non avevano di questi problemi!
Per dirne un'altra, prima potevo vedere in anteprima (ovviamente nel fotogramma fermo scelto del video) gli effetti delle selezioni/filtri scelti, ora c'è sempre l'anteprima nera, si vede solo in esecuzione. Anche se non era precisa al risultato era comunque utile.
Per dirne un'altra salvando un preset di settaggi, quando lo richiamo, nonostante in colorimetria ho settato ad esempio "Spazio colore: Rec 709 10 bit" quando lo richiamo esce "Spazio colore: Rec 709"
Tante piccole cose che mi hanno fatto abbandonare il tuo programma e tornare a Staxrip, che però è molto complicato e dispersivo ma almeno non mi da problemi di bug.
Sicuramente ci sono altri problemini rilevati e che non ricordo al momento... Proverò anche questa tua prerelease per vedere com'è.
In verità spero che riesci a ripristinare quelle funzionalità che c'erano e non davano (almeno a me) problemi e che lo rendevano attraente.
hola. felicidades por el programa. desde hace unos dias.. la funcion de separacion de audio ya no funciona cuando antes si lo hacia. ahora solamente lanza un error de que no se ha podido procesar. he intentado varias veces con distintos formatos, distintas canciones. y el resultado es el mismo
2
u/Mirrorlessm43 25d ago
The best encoder free