None of that has anything to do with the UI itself and honestly nobody cares whether they kept the same UI for v2 and v3 as long as V3 functioned just as well which it did not.
V3 lost the ability to resume, maybe not a UI issue but then again no reason they could not have kept it in V3 if it wasn’t a UI thing.
All of this is moot. If I still had ARC GPUs which I was told would work and Topaz website says they do…I wouldn’t even be able to use the program so why aren’t they fixing that instead?
Can you confirm that multiple GPUs work with Windows and Mac using all current gen AMD, Intel or Nvidia GPUs…if not it’s broken.
The Inverse Telecine is still not working.
Looks like It is not inverting the 3:2 Pulldown and just converts the frame rate from 29.976fps to 23.976fps then applies a Bob or Interpolate deinterlace method after, instead of actually bringing back the original frames.
Please take a look at the difference in the images I uploaded from upscaling a telecined Laserdisc source using Proteus.
Image 1:
I properly reversed the Telecine/3:2 Pulldown with another software before adding it to TVAI. See how the lines are clean!
Image 2:
I loaded the Telecined footage directly into TVAI. Now see the jagged edges on her face and his shirt collar on the same frame of the movie using the TVAI telecine checkbox!
There should not be any jagged edges with IVCT.
Inverse Telecine/3:2 pulldown is supposed to literally INVERSE the telecined film to bring back the original frames from the filler fields.
Please look deeper into this issue, considering the old standard definition videos are most in need of upscaling and they’re usually interlaced, and most movies are telecine interlaced.
So what you’re saying is I should just throw away any chance of being able to use any of the new models, (and ~75% of the licence cost/time), by reverting to v3.1.9 because they screwed up the software?
v3.1.9 has worked on all the latest Intel drivers, something they knew and suggested months ago but seem to have put minimal, (or no), effort into fixing since.
So you can see why Arc owners would be a little pissed off at this and saying “Can you not just reinstall the version that worked?” seems to be just taking Topaz’s line of seemingly ignoring the problem in the hope we’ll go away.
I tried the software, decided if I liked it as it was, then bought it. I would not have bought if I wasn’t happy with it at the time I bought it.
The fact that they offer upgrades for a year is a bonus to me. For instance, I won’t be upgrading to 4.0.0 because it sounds like there are too many issues. I have a version that works well for me, and I’ll stick with it until something that works better is released. (4.0.0 apparently isn’t it)
I believe this is a misunderstanding, Tony. While the In/Out selection does limit playback start/stop times, it does not, in fact, loop.
Previously previews looped automatically and endlessly until users stopped playback. This was fantastic. Sadly, 4.0 does not loop. (at least not that I have found) While the play head from the timeline does reset after reaching the out point, it does NOT continue playback by looping seamlessly as it did pre-4.0.
Additionally, in 4.0 previewing renders is more cumbersome, as the rendered segment is not automatically isolated. Playback pre-4.0 was relatively seamless as all one needed to do was click “preview” and then hit play. Now, however, you not only have to hit play BUT ALSO have to manually isolate the rendered section in the timeline. If you do not isolate the section manually, playback keeps going right after the rendered section ends and into the non-rendered portion.
Why did this change? The new features are certainly a welcome addition. However, some of the default functionality that made previewing previously efficient have now been sadly eliminated.
Please bring back the auto-select section and auto-loop functionality of previews!
Why is the previewing oh, so clumsy? I know it will get fixed and improved in the next 6 months or so, but why was it released this way??? It’s a rhetorical question - I know why! Back to version 3 we go.
Well, it’s about 10 years, but that’s still an eternity in IT. I can understand that they need to move on to improve their product.
Anyway, a clear warning would have been fair before anybody jumps on V4.
Only if you keep the original in one of the 2 comparison windows.
Otherwise it’ll render both model setups, even though one hasn’t been changed (MacOS 14.1).
If someone has time, it would be fun to list all of the useful features and functionality that has been downgraded and removed since version 3 and version 2.
