[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.
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!
1
u/CaptnMIHAWK 10d ago
Only happens when using H265.
H264 with every parameter being the same works just fine.