After installing this BETA with Resolve plugin, my Davinci Resolve 19 will no longer open.
I looked at the Davinci logs and this is what it shows.
0x0000cc44] | BtCommon | INFO | 2025-03-30 13:11:46,209 | Memory config: reserved=18401M pinned=8000M log=0
[0x0000cc44] | BtCommon | INFO | 2025-03-30 13:11:46,209 | Using default pooled memory manager
[0x0000845c] | LeManager | INFO | 2025-03-30 13:11:46,211 | 521, 29
[0x0000171c] | BtCommon | INFO | 2025-03-30 13:11:46,211 | BtResourceManager Process Thread Started
[0x00003534] | OpenFX | INFO | 2025-03-30 13:11:46,274 | OFX: loading com.TopazLabs.FrameInterpolation.BETA
==========[CRASH DUMP]========== #TIME Sun Mar 30 13:11:46 2025 - Uptime 00:00:00 (hh:mm:ss) #PROGRAM_NAME DaVinci Resolve Studio v19.1.4.0011 (Windows/MSVC x86_64) #BMD_ARCHITECTURE x86_64 #BMD_BUILD_UUID d512ce47-d15b-4a20-8aa4-3be7e78493e5 #BMD_GIT_COMMIT 755196be3de2c6b815963568c83e02811d250cbb #BMD_UTIL_VERSION 19.1.4.0011 #OS Windows
After uninstalling the beta Resolve works again.
According to the release note it’s back end prep, so most likely they’re looking for new bugs that might be traceable to that before they try hooking a local Starlight model onto it.
Can look at my post just above yours where I’ve also linked my memory tuning. Now compare my x4 benchmarks with rtx 5080 vs any rtx 5090. My 4x speed with rtx 5080 beats any 5090 unless they’ve also tuned their memory to run a lot faster.
My memory tuned with those timings and speed require a dedicated fan to stay below the temperature where they start to throw errors (measured SPB Hub Temperature of >50ºC means that the memory modules themselves are probably around 57-58ºC, as the SPB Hub sensor is located on the motherboard). With a fan pointing at my memory, they reach their max SPB Hub Temperature of about 40C after 10-15min of memory stress testing, which is some 10C below the threshold of when they start to run the risk of throwing errors.
When my memory wasn’t as tightly tuned, but still ran with the same voltage, tREFI and tRFC (the most heat generating timings) and without a fan, they ran at 65-70C and were fine, as with looser timings they can handle higher temperatures.
I had the same problem, so I removed the beta plugins from the common/ofx folder.
From my experience, I think the official version will have the same problem.
I can’t install the official version of TVAI 6.2.0.
This is all great news, I am hoping to see some new generative enhancement-models running locally soon.
By the way, wow is the new fast video player supporting HDR coming along for MacOS? I feel like forever ago since you stopped including the “Mac version coming soon” line in the change log. Have you discontinued work on this or is it still being worked on?
This is something I have been looking forward to as it’s just tedious to have to render a preview and open in an external video player to check the results. Especially when you need to do a lot of small fine adjustments to make it look just right.
Ran some Benchmark on 6.2.0.1, comparing M1 Max and M4 Max. Copied below. When a new section for 6.2 is available I will also copy them. I mostly see almost 2x improvement! APFast is a notable exception !
Comparing against 6.1.0, my 3080 ti is mostly back to the same speeds. There are a few that are still slower according to the benchmark. Nyx is the worst at 6.44 fps compared to 9.74 fps.
Ok, Does anyone have a solution for when MPV starts “acting up” out of nowhere (again)?
This transition to mpv cost me multiple months of updates, a few v6 builds were running, but now my computer just shuts topaz down whenever i try to load a video into to GUI and i am about 100% sure this is an MPV problem because i dowloaded the windows PLEX client (which also uses MPV and also has a ton of people who have a ton of issues with mpv being “very finicky”)
Why can’t we just get an option to DISABLE mpv ? This “feature” is litereally ruining the user experience… I paid for a year license and more than 6 months of it has been downtime due to mpv issues (espseciallly the early ones)
It’s incredibly ridiculous that i have to keep defaulting back to old versions of this program every time mpv acts up
GRANTED – this hasn’t happened in a while, but even once is ridiculosu … having it crop back up randomly is just stupid to have this as part of the program… you guys have to know it is a very finicky thing especially when dealing with a large range of computers.
Unfortunately I still can’t convert my ProRes HQ mov videos to h265 mp4. With AMD Ryzen 9 7900 u 7950 CPUs in combination with RTX 4090 or RX 7900GRE u. 7900XT the process stops at less than 10% completeness. With i9 9900 and Rtx 2080 ti it works .
