![]() ![]() ![]() Some Mac users may experience import issues. Saving the presets after that should show the correct settings next time. Switching from Auto to Manual should show the saved settings. Presets with Proteus Manual settings show Auto instead of Manual. Fixed Display Issue with vertical/portrait videos.Fixes Trim and Crop tools when switching videos.Updated the FFmpeg Export Command Dialog.Added a preference option to automatically remove older previews.A new release of Topaz Video AI is now available.A new release of Topaz Video AI is now available.ĭownloads: Windows | Mac (DMG) | Mac (Update Installer).Reworked custom output resolution workflow to better support presets.Seeking/preview may not work well with DPX inputs.Frame number preview length may shorten on app restart.Videos with mismatched metadata and streams will display incorrect duration.Updated the live preview checkbox in preferences.Fixed “proteus” showing up in FFmpeg command and added additional preset migration safeguard.Fixed video setting handling of SAR values for custom resolution.Exports / Previews now show filename when hovering over thumbnail.Added version labels for Proteus and Theia.Fixed integer overflow issue for start frame number.Fixed textbox focus for output resolution.Added tooltip for automatic pillarbox/letterbox removal in crop tool.Fixing Proteus and other sliders text box bug.Fixing Theia to Interlaced Enhancement UI bug.įixed preset migration for video output settings.Added tooltips for video output settings panel. Please upload problem videos and logs here: Submit Files. The Benchmark obviously does not reflect a real world workload. With my Ryzen 7 5800x system and whatever GPU (3060 ti and 4080 specifically) my real world upscaling with Artemis is maybe 30% or so slower than indicated by the benchmarks, with everything else turned off including detail recovery, and audio set to none. Well that’s a lot, and I am sure there is a logical reason for it - but it doesn’t help to maintain confidence in the software claims and makes GPU/CPU combination comparisons very very difficult (you should see my spreadsheet!).Īssuming that others see this too, it seems to me that the benchmark program needs to be re-done to better reflect real world conditions. ![]() That’s for upscaling - but also, comparing slomo and e.g. ![]() Apollo with Chronos, that’s just as difficult for 2x slomo because the benchmarks only do 4x - which flatters the Apollos. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |