post #9014497 asset #25252510 The artist initially sent out only the white background file and after I asked for a transparent background export, they send out both files with a lighting revision around the face and flower. Normally I would save the transparent variant for myself but I feel like I want to be generous a bit more this time. Also I do not want to waste another upload ID.
Regardless of where they come from? (Commissioner uploads)
Yeah, just parent/child the duplicate.
Final two CE replacement requests for rounded corners. Going to do the old-fashioned route of childing and exploding for the upscaled CEs when I get to them.
Normally, I one-up these, but this one is lacking a source, and I got the media asset from a proper official ZIP file with all the artwork in it, so I figured it couldn't hurt to ask for a replacement in this case.
Just went ahead and checked my media assets for all these, and yeah this is apparently a reoccuring problem now. Joy!
By the way, there were a few in there (not in the ones I'm posting about right now) where the sourceless post is superior to the copies I have. What should be done in that case? Leave it alone?
By the way, there were a few in there (not in the ones I'm posting about right now) where the sourceless post is superior to the copies I have. What should be done in that case? Leave it alone?
@staxu - The linked twitter image is 341 KB, so I don't know where you're pulling that 3 MB asset from. I tried to replace using the twitter version but got a CookieOverflow exception.
@not404 - No, different site. I don't accept bad id as an excuse.
@staxu - The linked twitter image is 341 KB, so I don't know where you're pulling that 3 MB asset from. I tried to replace using the twitter version but got a CookieOverflow exception.
I had to convert the original Twitter file to a PNG via ImageMagick then re-export said PNG via GIMP because the original file seems to fail with Danbooru's libvips (something about a PCS illuminant is not D50 error). Edited forum #343621
@staxu - The linked twitter image is 341 KB, so I don't know where you're pulling that 3 MB asset from. I tried to replace using the twitter version but got a CookieOverflow exception.
staxu said:
I had to convert the original Twitter file to a PNG via ImageMagick then re-export said PNG via GIMP because the original file seems to fail with Danbooru's libvips (something about a PCS illuminant is not D50 error).
Hi just chiming in from the Discord to confirm that yeah, with a VIPS error the best shot we have is to just recompress it as a PNG to get rid of the problematic data. In this case it was inadvertently recompressed as a JPEG, leading to a loss of pixel data. The PNG should be a pixel-perfect duplicate with the original, problematic file, it's just larger because JPEG artifacts compress poorly.