Feedback Thanks for sharing i do not use converters but just wanted to try. Hardware acc is not seen and crash when videobox is set (whatever it is) M. encoder works correct with Cuda and Mercury atm :) OSX 13.6 Nvidia 980TI Web driver for Cuda

please add levels and full range video 16-235 and 0-255 and gamma tags. this will help translating across different NLE's! additionally adding 10 bit h.264. 265 support would be cool. or even .266 when it comes out. btw, this is selling like hotcakes.

@leonbeas i finally added .ass subtitles support to Shutter Encoder. I'm still working for the v14.3 so please let me know if you want a pre-release. It will also helps me to have some beta testers.

Thanks, Paul.

@leonbeas thanks a lot !

That's a very intersting thing, because Shutter use FFmpeg which is 100% compatible with .ass subtitles.

So why you can't ? Because .ass files works totally differenlty, i cannot fully change subtitles options. But most of settings (font, color etc.) are embedded inside.

Well, i will add the ability to use .ass file into Shutter by limiting settings options from subtitles window.

Thanks for your feeback.

Finally something better than AnotherGUI! THANK YOU! (for reference: http://www.stuudio.ee/anothergui/ )

@paulpacifico I made some conversions (mainly MXF and DNxHR outputs) and everything went smooth. I really appreciate the way you organized the presets, it is a great time saver. Still need to test the advanced functions (especially trim/LUT/stabilize), I'd like to finalize some clips libraries without using an NLE.

@paulpacifico I really like that the encoding queue shows the full ffmpeg command. It would be great if there was a copy/paste function to reuse it in a terminal or script, and if it even could be editable in the queue to hand-tweak parameters, such as adding ffmpeg parameters that aren't supported by the GUI.

Is my assumption correct that Shutter Encoder uses a patched version of ffmpeg with the SVT-AV1 encoder? This worked for me once, but later attempts of encoding AV1 via the queue resulted in truncated output files with only a few seconds length.

@theusualeditor

Usage of DNxHD bitrates is a bit weird with FFmpeg, because if you choose for instance 120Mbits with a 24fps input source you will get 115Mbits ouput, that's why most of NLE decided to use LB,SQ,HQ even for DNxHD. But i will add the other bitrates for the next release.

Remaining time should be very accurate, the main thing is at the end FFmpeg has to complete the file by writing MOOV atom and other metadatas which take a bit of time, but the encoding has been reached 100% of conversion.

AV1 still a new codec, and glitch probably happens from decoder also. I try to upgrade everytime FFmpeg to get the most recent codecs update.

You have Mediainfo embedded in Shutter Encoder, use right-click on file then "Informations..."

One more update. I converted an XAVC-S file to a variety of formats: ProRes, DNxHD, DNxHR, XAVC, H.265, AV1, AVC-Intra 100x XDCAM, etc and it all worked perfectly. I was surprised that even H.265 didn't take long on my old system.

A couple of things: in DNxHD for example, NTSC presets appear to be missing, and only PAL (25, 50fps) are available judging by the the codec specifications http://operationalportal.com/wp-content/uploads/AVID_DNxHD_Codec.pdf 45, 145, 220, and 220x presets are missing for example (1080p30 and 720p60). Also 110 and 110x for 720p30

The remaining time and elapsed time are rarely accurate. For example: With XAVC the progress bar reached 100% but the elapsed time kept going because the conversion was not done, until a minute+ later. But to be fair, most conversion programs behave the same.

AV1 took the longest by far, and there were glitches in the resulting file (playback with VLC and MPV, glitch happened in the same position).

Sometimes is hard to tell which codec preset is really putting out 10-bit files, so I will suggest using MediaInfo to identify the correct presets if you need 10-bit. For example: DNxHR HQ is 8-bit, but HQX is 10-bit with the same bitrate/file-size.

Great program Paul, thank you for sharing. I can finally get rid of my text files with ffmpeg commands for different conversions.

@paulpacifico first of all thanks for your effort and the decision to give it for free! It is not an obvious choice and we should all be thankful, regardless of the level of performance of the tool. I do lots of conversions so I'll try it soon and will give you my feedback.

Tutorials:

https://www.youtube.com/channel/UCwzlOLGZAARWzUeNsaeT52Q/videos

Glad to see a developer around here. Can you speak on the catch or compromises of using your tool VS using ffmpeg directly or industry-standards like handbrake?

Thanks for the reminder about shutterencoder.