>>4048652>Dude you are full of shitWhat was incorrect with what I said?
I'll say it again, I think it's a total non-issue for real world use, with plenty of workaround options, and you're absolutely right it has more to do with Adobe than x-trans itself. I guess I see Adobe x-trans compatibility issues as an issue related to x-trans, and you don't. Difference in perspective.
>but pleddit says I've been bamboozled because of the xtrans sensor. What are they going on about?How would you answer OP? Just say, there's no issue?