igohigh opened this issue on Sep 10, 2021 ยท 78 posts
JoEtzold posted Tue, 21 September 2021 at 3:44 PM
My issue when I posted was that Poser is not writing OUT what the operator writes IN.
Thats not completely true. Poser is writing out whats his primary task. A correct rendered image in wished pixel dimensions. And up to version 11 it is also writing out eventually given DPI according with paper size in inch or cm or pixel. on your choice. And this last secondary task seems broken in version 12. I can't proof cause I'm waiting to buy Poser 12 until better solution for use of older python scripts is given and most bugs are solved. (Have never installed any Poser version until min. third service pack was out.) I have all that said just checked with test renders in Poser 2014 Pro (thats the version before 11 and 12 so now called 10).
And b.t.w. as I said before mostly all image formats are not writing DPI and such stuff in their original header specification only pixel dimensions. And this is for JPG, PNG and also PSD the same. DPI as also paper sizes if available are stored in the metadata. And thats a problem cause this metadata are not a fully complete standard. There are some parts which are common and DPI and paper size are not in this. Everyone can add further data in that metadata. So on one hand it's not defined wether to write such data nor is it asured that a particular program can and do read them. In first line metadata was thought for information not for operation. That came later and as everytime if doing something not defined fully in the beginning it's a fine part for may be getting troubles.