You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm interested in this OpenTabletDriver plugin, but for my use case the grid-based approach didn't work out nicely because of the artifacts it introduces. I have seen you opened #3 which would potentially alleviate my problem, but I wonder if you or others really have tablets that require different scaling factors in different areas of the tablet?
Because a simpler but less general approach is to use the point pairs to fit a single transform for the whole tablet. It's less general, because I'm assuming translation and scaling is enough. I've made a very quick test and put it on https://github.com/leoschwarz/BetterCalibrator/tree/feat-global-transform . For me it's working out fine, but I haven't tried all display modes etc. If you are interested I would port the model fitting to C# at a later time, so it could be integrated into the plugin more easily. In case you want to try it, it's essentially as before, but there's also a Python script that fits the offsets.json point pairs and creates a model.json which should be put in the same folder.
The text was updated successfully, but these errors were encountered:
Hi
I'm interested in this OpenTabletDriver plugin, but for my use case the grid-based approach didn't work out nicely because of the artifacts it introduces. I have seen you opened #3 which would potentially alleviate my problem, but I wonder if you or others really have tablets that require different scaling factors in different areas of the tablet?
Because a simpler but less general approach is to use the point pairs to fit a single transform for the whole tablet. It's less general, because I'm assuming translation and scaling is enough. I've made a very quick test and put it on https://github.com/leoschwarz/BetterCalibrator/tree/feat-global-transform . For me it's working out fine, but I haven't tried all display modes etc. If you are interested I would port the model fitting to C# at a later time, so it could be integrated into the plugin more easily. In case you want to try it, it's essentially as before, but there's also a Python script that fits the
offsets.json
point pairs and creates amodel.json
which should be put in the same folder.The text was updated successfully, but these errors were encountered: