5/18/2023 0 Comments Topaz studio 2 nvidia errorNot that will be slow but they probably won't be throwing stuff overboard just to hit some number far out on the diminishing returns power curve.ĪMD will be fully free later to do a '7950' with bigger caches at a higher price point and to close some performance gap. Pretty good chance AMD is going to go for Performance/$ more so than performance at any cost. I really doubt AMD is doing the same thing with the 7900. Nvidia manically was shooting for the benchmark crown here at any cost. Nvidia threw the NVLink complex overboard to add more cores to the to 4090. The notion that the 7900 is going to outcompete the 4090 in total core die area is likely wrong. Apple similar on the other side of the spectrum. Nvidia can sell a relatively few more data center GPUs and make up the revenue easy. This overlap Mac Pro area is really too small. Apple same thing with similar agenda ( Apple solution first ). They spin it as though they are on "your side" but they are really on their own side first and foremost. Nvidia's actions are a major blocker to a mac solution also. ('halt and catch fire with each new OS release' GPU drivers. In the first case Nvidia is a lousy partner, so Apple dump them. The folks who label this "all Apple's fault" are in just about much denial as the folks who label it "all Nvidia's fault". Neither one really needs the other financially so neither side is likely to give in. Two, Nvidia only wants a CUDA first approach to drivers (and they can't really properly write GPU drivers without some help from Apple either). Apple only wants a "Metal first" approach to drivers. One, Apple really can't do a very good job with zero Nvidia help or resources. I think in around 2001 I paid AUD$700+ for RealViz Stitcher, and today PTGui Pro is $465, so it's pretty good value. So it works, and you tolerate it, because it gets results. Capture One has a similar thing - everything feels a little unpolished, and limited by the off-the-shelf cross-platform UI toolchain they had to use (Qt or whatever it is). PTGui feels like "Pro" software, so in other words, the UI is janky, and just suffices to get the job done, because it has to service a small user base. People wanted vector shape masking, and that wasn't what they had to offer. This was APG's biggest failing - at its core it was an image matching engine, and its masking tool was the thing they were effectively selling. The UI/UX follows the tech, not the other way around. It's software that exists to monetise an existing technology, and that's its biggest problem. Like APG, PTGui is (AFAIK) effectively a front end to Helmet Deutch's PanoTools, from the 1990s. I tend to try shooting on narrow footbridges, for example, where you have to get all the alignment perfect, and more often than not, it doesn't quite work, but occasionally I get one dead-on.Īs a stitcher, I've moved to PTGui after a number of years with AutoPano Giga (before that, RealViz / Autodesk Stitcher, earlier still QTVRAS), who folded soon after the GoPro buyout. So I have a masochistic streak with Pano shooting - I've always set myself full 360x180 spheres in the most difficult locations, figuring that if I can get it right with the hardest difficulty, I've got it figured.
0 Comments
Leave a Reply. |