Or maybe you'll have better luck in a week when somebody familiar with RAW and a 20 year grudge against Adobe chooses to spend a day of tokens on the problem. Maybe me.
Rome wasn't built in a day, nor Adobe destroyed in a single git push. But they both shall fall.
And 500 levels of org tree, and grumpy customers that freak out if you change anything about their workflows, and decades of legacy code across dozens of micro-services, and backwards compatibility requirements with 20 year old formats...
Those customers are already pissed off, yet record sales every quarter. This will be great to offer this diminished experience to them until they start using AI to do all of their editing.
I'm going to revel coming back to this arrogant comment in a couple years.
Seriously, you have no idea the kind of goodwill you've squandered, and the kind of resentment you've created. I expect it will bite your company squarely in the ass.
Anyone would be insane to pay for Adobe pdf over pdf xchange, but plenty of companies do. I'm not sure how/why the world pays for Adobe with so many good options but they do.
That's exactly what I was thinking. It's only a matter of time. Surely the models, when well directed, can get most or all of the way there in short order.
I did this a few months ago and it's not simple: different sensors have different pixel arrangements, files can have different data structures, and the default tone mapping is provided by the app (so opening the same raw file in darktable vs preview will have different results). There are different algorithms for how you assemble the raw data as well, and the issue is that you can get something _passable_ that isn't _optimal_, and it's really hard for the LLM to recognize that something isn't right. Is it the pixel processing, or is it the tone mapping, or is that just how the image looked?
And on top of that, you need a bunch of different files from different sensors to test with. Canon, sony, apple, fuji, nikon, olympus, etc. -- if you're building a truly general application, that's a concern.
Or if you're like me and you shoot fuji, you just build a fuji raw parser and call it good. The "TAM of 1" world of software development...
All the camera companies offer custom software that works better (mathematically) than the Adobe versions. They're just trapped in godawful UX. It's a one day job to do the brain transplant.
I chose "both shall fall" (future tense) on purpose. And likely in the same manner: a self-destructive period of reactive fascism, followed by becoming a nostalgic name noted for its crumbling architecture.
Rome wasn't built in a day, nor Adobe destroyed in a single git push. But they both shall fall.