In versions 3.3.5 and below, you are able to tweak an existing preset, and then re-save it under a different name. This functionality is extremely useful because you can set up a bunch of “starter Presets” as a foundation. I make presets for everything because the program crashes sometimes, and I want to make sure those settings are stored.
Having to create a brand new preset only from the “None” position is very annoying because it resets everything back to default.
It appears this functionality was intentionally(?) removed from versions 3.3.6 - 3.3.8, as noted by the message in this screenshot.
Having to create presets only from the “None” position is a major step backwards. Can you please restore the ability to tweak an existing preset and save it under a different name?
i would like to make an additional suggestion that may help users who have very specific settings for each video to process without the need to create tons of settings in the software.
If you have a lot of files you need to transcode but you need to figure out individual settings for all files first it would be very useful if you could save those settings as a configuration file. Having tons of presets in the software itself for each individual video does not make much sense. The name of the configuration file could be suggested as the name of the source video file (but could be changed in the “save as” dialogue if you want to save different methods).
If you quit the software and import the video the configuration file being in the same path with the same name would be loaded automatically. This would also allow to test and save settings on one machine and do the rendering on another machine without the need to set up presets and import them to the second installation.
@tony.topazlabs It appears 3.3.9 still has this problem, as noted by a message from another user “pinkdong”:
“…I did run into a little inconvenience: I want to create a preset for upscaling to 4k at a fixed 8k bit rate so I select the built-in “Upscale to 4K” then I changed the encoder bit rate from “Auto” to “8k”. Now to create a custom preset, I have to change the preset to “None” first before I can create a new one. I wish that create function (+ icon) is added to all the built-in presets in the future.”
Why is this marked “Solved” when it’s completely broken?
As a new Topaz licensee I ended up here because there was no “save as new preset” option after adjusting an existing one, and I couldn’t believe such an obvious feature had been omitted. Then I read Presets | Topaz Video AI but what it described didn’t match the UI I was seeing.
So I searched for “preset” in these forums to learn that we have to click the preset drop-down back to “None” to activate saving presets at all. That is super counterintuitive, so whoever thought that was a good idea… here’s your feedback: it wasn’t. The + button to Add Preset now appeared. Alas, when clicked to bring up the dialog, and entering some basic metadata, clicking the now-active “Create” button did … diddly-squat. No preset created, no error message either, dialog not dismissed.
At this point I can’t tell if the preset save/edit “feature” is buggy, wholly unimplemented, or I’m somehow doing it wrong, but in any case, the user journey I just described is a travesty.
Version/Platform: this is with v3.3.9 on a 10-core iMac Pro with macOS 13.5
I marked it as such because they said they are working on it in the 3.3.9 thread, I have been highlighting other users who are also experiencing the same issue, such as this person.
I feel your frustration though, and have refused to update until this is fixed. It’s a deal breaker for me. I just try to be a little more understanding as I am also a developer myself.
