Thanks for trying it and calling out problems — it helped us find and fix the bug. The issue has now been resolved and DevicePrint should give much more sensible results going forward.