Adding to Cart…

Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.You currently have no notifications.
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
In which context? You can also see artifacts on many original DAZ promos, if you zoom in. Recompressing the jpgs as webp, as CloudFlare does to save space and bandwidth, just makes the quality worse.
I've downloaded and re-downloaded tens of thousands of DAZ promos over the years directly from their server, when testing my apps, and I've noticed many promos that have changed size, so it looks like DAZ also sometimes recompresses them to save space or whatever.
These.
Recompressing the jps to webp is exactly the problem! If they accepted uploads as webp to begin then things might be different. But they don't. So what we end up with here is DOUBLE compression. The artist is probably converting their original picture to jpg, and then cloudfare converts it a second time to webp. That is not cool. It doesn't matter if the original has some artifacts, the conversion adds ADDITIONAL artifacts which you admit it does.
How is this acceptable on a website dedicated to 3D art? It simply should not be.
But beyond the compression performance, it wouldn't matter if webp was liquid gold, the best thing since sliced bread, or whatever. If very few programs adopt the format, none of this matters. The matter of convenience should be priority as well.
Going back to the format wars of beta and VHS, the biggest factor that gave VHS the victory was convenience, even though Beta had better quality. Convenience often leads to success. Convenience is a big reason why Daz Studio is as popular as it in this field. It much more convenient than any other similar software.
So webp fails on both fronts. It is not convenient, and compressing images a second time is less quality. There is no reason to use it until these issues get fixed.
Wow, you are right! I thought "That can't be. He must have done something wrong.". Nope. I tried it. You are exactly right. That is quite a change, but your image still looks very good.
Well it was also saved with highest jpg quality (100), so it can be compressed a good deal without it can be seen. I just found out that you can see the compression rate in IrfanView, it's been reduced to 75, which is the recommended size/quality choice. Maybe the forum (which seems to have some rather smart features) checks that value and compresses it if it's higher than 75, and otherwise not. I'll do a new test to see if that's the case:
Well no, it recompresses it to 75 anyway even if it is already 75, and file size even gets a bit larger, so not very smart. OK, lets try 50:
Again, recompressed from 50 to 75, and file size increased from 212 to 301 KB. Not so smart. On the other hand, I don't think many post jpgs with a quality below 75.
Irfanview reports what compression algorithm is used, so it knows a WEBP from JPEG. I did screw up on one download, tho. They were the same file in that case. The webp for that promo is 108K, and the jpeg is 190K. Woop de doo. Big savings there.
network.http.accept.default doesn't show up in my Firefox (latest version).
Search for webp instead. It now shows as "image.http.accept"
Change it to: image.http.accept;image/,*/* and images save as .png
As far as the latest version of Windows 10 goes, the webp format has now native support; which is nice because it lessons the chance people will install security busting plugins into their browsers.
Not sure how much of this relates to file size, or someone pushing their file format, but...
If the promos weren't so "busy" so often, it would cut down a lot of the file sizes. More importantly, though, it'd make it easier to see some of the details in the products.
Maybe it's just me, but I can't focus on a product's features if there's a slew of irrelevant patterns in the periphery, or a jungle of vegetation in the surroundings and right up against the product, itself.
I don't think it's artistic, anyway! I was studying a product recently where the promos had zig-zaggy lines all around them. It was, frankly, ugly. I remember another with chain-link fencing surrounding a woman. It was supposed to promote the clothing, if I remember right. It should have been promoting the fence!
When I save promos for reference I have to run them through GIMP to tediously black out the mess in order to have a quick and easy view of the actual product. This cuts down on file sizes for my hard drive, as well.
So, oh well, just venting. Nothing will change.
If I want just 1 image on a page, I use this extension: https://chrome.google.com/webstore/detail/save-image-as-you-want/laecjkbpbmfmleaiggbaifbaecaifink
If I want all the images on a page, I use this extension: https://chrome.google.com/webstore/detail/download-all-images/nnffbdeachhbpfapjklmpnmjcgamcdmm
Google has definitely been pushing this WEBP format (for what reason I don't know) and several programs have been adding support for it over the past couple of years. Why? Because Google rules the world (or at least the internet). They're the new giant and it's time for a newer giant to come along.
Nifty find. I don't mind webp images, and can convert them easily enough, but this will still come in handy.
Well too late to the party and haven't read all responses so may be someone has already given answer. Daz has nothing to do with it, it's Chrome and may be firefox (use only chrome these days) ... anyway you can get the plugin mod headers from chrome extension store and override two of the headers. At least that's what i did.
Accept : text/html,application/xhtml+xml,application/xml;q=0.9,image/jpeg,image/apng,*/*;q=0.8,application/signed-exchange;v=b3
User-Agent : Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko)
One can suggest lesser changes or better changes, but since these work for me so i don't bother... You can get user-agent for a later version to avoid out-dated browser messages etc.