Get it here and provide your feedback. I am not going to be in a position to make major changes to the new features, but I could be convinced to remove or temporarily hide some 
While testing some things while preparing this, I noticed that VA-API hardware encoder on Linux is not working. Also, the Flatpak cannot run things outside of its container; so, the HTML generator, Text to Speech, and Open With features will not work. The Flatpak release build will have those features removed.
LinuxMint 22.2, Cinnamon
I can’t figure out how the (image/video from HTML) function works. What am I doing wrong? Neither the video nor the image are generated, and after restarting Shotcut, when I try to use this function, it asks me again for the Chromium path.
The “typewriter” filter has green letters by default, but if I move the length of the clip, the color of the letters turns white.
It seems logical to me to add a third option, “typewriter”, in the “new generator - text” window.
Text: Typewriter filter: On my screen (1920 x 1080) when moving the scrollbar all the way down, a small part of the settings is always hidden at the bottom of the panel.
On Linux, I tested this with the Flatpak Chromium previously. Now, I just tested it with the Ubuntu 22.04 chromium-browser package, and that works for me as well. I see you are choosing “chromium” What exactly is that? Why is it not chromium-browser? Try that. If it keeps asking you to choose, it is because it failed and reset your selection, which could be bad. There might be a hint in View > Application Log. Also, your testing is going to be deceptive because it will generate black text on a transparent black background. In preview that is going to look all black.
I tried selecting Google Chrome or Google Chrome Stable, but nothing happened. Video generation requires virtually no CPU usage. PNG generation creates an .html file, which doesn’t work with shotcut.
log.txt (38.8 KB)
Shotcut does not read HTML directly! Generate Image is supposed to generate an image file it does know how to read. The HTML file is to be read by the browser, which from your log is crashing on startup. Maybe it does not like the command line args. I tested it with Google Chrome on macOS and Windows and Chromium on Linux (Flatpak, chromium-browser Debian package, and chromium Snap).
I do not know why it does not work for you. I am not going to provide much support for this feature. Either it works for you or not. And you can try to debug it yourself and submit a pull request.
I fixed the default Typewriter text color changes unexpectedly and added it to the New > Text dialog.
with AppImage and /usr/bin/chromium. I reproduced the problem, and I figured out a change to get it working. It also affects portable and Snap. To answer my question, chromium is a shell script (so is chromium-browser on Ubuntu and Pop) for the binary. For technical details, the LD_LIBRARY_PATH environment variable needed to make the Shotcut app bundles work was leaking into the child process environment, and I had to clean that. Somewhat, frustrating though, is that fix does not seem to fix the Open With features also plaguing Linux. I updated the GitHub Beta page with new Linux builds 25.10.11
There is one thing that I’d like to request on this new update. I was working on the new movie which I shared two days ago. There’s something I noticed on Shotcut. If you go to Export, you can export an audio file of the actual video, so you can edit the audio on any preferred software and come to align the mastered audio on Shotcut.
But if you exported the audio on Shotcut using the export function next to Subtitle, then when you go to Menu and go to Export and select MP4, it will export as an MP3 because you used it last time when you were exporting as an MP3, although under the menu option I clearly selected Export as MP4.
I’m not sure if this makes sense, but if it doesn’t, I am willing to make a video showing you what I am trying to say. I kindly ask that this be checked or fixed in this version.
Suggestion ↩︎
That is not going to change. The File menu option is basically a link to the Export > Export File button, which uses current settings. The menu item says “Video” because it needs to disambiguate from the other exports, and video is the majority use case. Simply giving a .mp4 extension is not enough information to tell something what to do. As you know, there are a variety of ways to make a MP4. The menu item also exposes a keyboard shortcut for that button/action.
Beta period is not a time for asking for anything and everything. It is to verify changes.
Okay, Thanks for clarification 
I understand the confusion and weak association. I changed both the menu item and the button to say “Video/Audio.” I think that will tighten the association and reflect that it could be exporting audio–as well as not only video. It is also a small, safe change to make during beta.
Thanks,
This helps alot, so that people can clearly know. Thanks so much. 
Now everything works fine! Thank you.
upd. The generated 10-second video file uses the Ut Video Lossless Codec and takes up 150 MB of storage. Will you allow users to change the codec to a more efficient one, or is video generation strictly tied to this codec?
Not that I need it, but spotted this topic and attempted to try out the feature. On Win 11 it just crashes SC, not showing any popups.
Thank you, again, for your continued work to make this excellent software even better!
I am interested in the limitations of the flatpak version. I have switched to flatpak because it is better integrated into the Gnome/Debian UI. But if I am understanding correctly, there are inescapable limitations to the flatpak version. So … just to be clear, let me be sure I understand our options:
flatpak (will have some limitations)
AppImage (any limitations??)
snap? (do you publish a snap version? any limitations, frustrations, with that?)
other … ?
I have gotten very frustrated with snaps, causing me to switch from Ubuntu to Debian - but if Shotcut is available via snap, and does not have the limitations … this might be a reason to re-evaluate!
Our Snap uses the option “not confined” whereas the Flatpak has a container sandbox with no option without. Like AppImage, the Snap is simply a different packaging of the portable but with automatic updates. Containers can only launch executables included in the container such as we do today for the bundled ffmpeg and Glaxnimate since those are also integrated with the Shotcut engine, MLT.
Thank you!
Text: Typewriter filter:
These settings revert back to the default values.
Also:
These settings revert to the previous values.