Fri, Nov 15, 9:31 PM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 15 9:11 am)



Subject: BMP vs JPG


Francemi ( ) posted Fri, 11 June 2004 at 10:38 AM · edited Fri, 15 November 2024 at 7:38 PM

Is there a good reason why I shouldn't convert the BMP to high quality JPG in the textures folder and for the templates? Thanks. France

France, Proud Owner of

KCTC Freebies  


maxxxmodelz ( ) posted Fri, 11 June 2004 at 10:42 AM · edited Fri, 11 June 2004 at 10:42 AM

Nope. As long as it's high quality, there's no good reason. Assuming you mean for P5. P4 might be different.

Message edited on: 06/11/2004 10:42


Tools :  3dsmax 2015, Daz Studio 4.6, PoserPro 2012, Blender v2.74

System: Pentium QuadCore i7, under Win 8, GeForce GTX 780 / 2GB GPU.


Francemi ( ) posted Fri, 11 June 2004 at 10:44 AM

thanks. I meant P5 ;o) France

France, Proud Owner of

KCTC Freebies  


maxxxmodelz ( ) posted Fri, 11 June 2004 at 10:48 AM

One thing you might want to check out... if the texture belongs to a MAT file, it might prompt you to look for the original BMP when you load it. You can select the new JPG instead, and it won't screw anything up. Basically, if it's specific to a MAT file, that might be an annoyance until you correct the paths. Just thought about that.


Tools :  3dsmax 2015, Daz Studio 4.6, PoserPro 2012, Blender v2.74

System: Pentium QuadCore i7, under Win 8, GeForce GTX 780 / 2GB GPU.


Francemi ( ) posted Fri, 11 June 2004 at 11:01 AM

Yes, I know about that but geez! it's well worth the trouble of replacing the bmp with a jpg when (and if) I use the figure that needs it! France

France, Proud Owner of

KCTC Freebies  


RHaseltine ( ) posted Fri, 11 June 2004 at 1:12 PM

Do you BMP or BUM? The latter is a "processed" format and although you can open it as a BMP and save it as JPG, Poser will not use the resulting file correctly: if you don't have the unconverted image from which the BUM was made you will need to stick with it (there is a back-conversion technique, but it is imperfect I believe). If you just mean textures supplied in BMP format then ignore me.


Francemi ( ) posted Fri, 11 June 2004 at 1:19 PM

I meant BMP but now that you mention it, I'd like to know what would happen if I convert a BUM to a JPG. I use Poser5. France

France, Proud Owner of

KCTC Freebies  


diolma ( ) posted Fri, 11 June 2004 at 5:33 PM

France, if I remember correctly, P5 doesn't use .BUMs, it converts them to JPGs anyway. So go ahead and try it (on 1 item to start with, of course, and don't forget to back up 1st) Cheers, Diolma



AntoniaTiger ( ) posted Sat, 12 June 2004 at 2:35 AM · edited Sat, 12 June 2004 at 2:45 AM

For some image maps a JPEG isn't a good format. For Poser 5, PNG is also a good format.

Transparency maps, which usually have a very limited range of grey scales, are better as PNG, I think. Better compession, and no blurring of edges.

Message edited on: 06/12/2004 02:45


Francemi ( ) posted Sat, 12 June 2004 at 2:51 AM

Yes, that's a great idea (save the transmap as png). I am done re-organizing my Runtime and on Monday, I get to try it... that is, if I can use my fingers because they will be crossed until then! loll Seriously, I've converted all the files that I wanted to convert and moved things around, deleted dupes, etc. I saved over 1GiG of hard disk space!!! If I have too many problems because of that, well, it was worth the try. And I have all my original files on CDs so... But I hope I won't have to return to the original files because I would have worked hard all this week for nothing. France

France, Proud Owner of

KCTC Freebies  


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.