Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[cooldude234]

To my way of thinking (with minimal print experience) there's two ways to define the resolution of an image:

1) Specifying the size of the image (in mm or inches) and specifying a DPI resolution; or
2) Specifying the number of pixels in the X and Y dimensions.

The DPI figure is of no value if referring to the image by it's X/Y pixels, it will be determined by the printed/displayed size of the image (ie. DPI = X/W where X is the width of the image in pixels and W is the width in inches).  Conversely, a printer requesting a certain DPI makes sense only if the printed size of the image is known, so if you need a 5 X 8 printed image and the printer needs 300DPI you'd need to render an image 1500 x 2400px.  Or am I missing something?

DPI and resolution are two separate things all together. You can have any resolution and any DPI to get the actual width and height of the final image, or you can have any resolution and any size (eg 11 x 8.5 inch) to get the dpi.
I'm pretty sure what the op's concern is the encoded number (the meta data) within the image file its self. Which as I know not every printer uses meta data (they ask you when making a print request to state the dpi).
I may be wrong but I feel like the concern is more of an inconvenience rather than a problem (since you can easily edit meta data with many different types of software).

[Alpha2]

Yeah, it's mostly just an inconvenience, not specifically a bug or anything just something causing more confusing than I'd like. As I said most of the art programs I use give you control over the size and resolution at the very start, eg. Need an image to be exactly 3000 pixels wide or even a 7x10 image at 600dpi? You get it before a single pixel is drawn. Here it's a matter of figuring out how many pixels you need the finished art to be based on the pixels per inch of the file type of the finished render and hoping that was composed so that it provides enough to achieve the dimensions you need if you reduce the size of the image to fit and placed into an existing page layout is exact. It can get to be a bit time consuming so I was looking for a workaround to speed things up.

In printing (at least on paper), I'm guessing people have just merged DPI and PPI for the sake of simplicity when dealing with more widely available Print on Demand services. it's been Hammered into me from the beginning that 300 ppi results in an image that doesn't show jaggies or stair stepping on rounded or diagonal lines when going from a digital medium to a printed one where I'd assume DPI originated, so rather than wade into the details with laymen they just seem to use the different terms to mean the same thing. After a while they just became interchangeable except for people who are much more technically versed in screen resolutions.

[slex]

It would be great if Animator saves images in 300ppi by default, that way the quality of rendered pictures be perfect.

Youtube seems to be making some readjustments after I upload video rendered within Anim8or which looks crystal clear on computer, but it always lose a lot of quality in YT. That never happens when I render animation in png pictures and connect those pictures into video with some other program. Maybe that's also related to unusual ppi values. 

[cooldude234]

It would be great if Animator saves images in 300ppi by default, that way the quality of rendered pictures be perfect.

Youtube seems to be making some readjustments after I upload video rendered within Anim8or which looks crystal clear on computer, but it always lose a lot of quality in YT. That never happens when I render animation in png pictures and connect those pictures into video with some other program. Maybe that's also related to unusual ppi values. 

Nah that would probably be something entirely different. The problem you are probably encountering has to do with codecs. That and you-tube compresses everything down to crap.
It took me a while to get you-tube to accept my 4k 60fps recordings and even then it still looks like garbage compared to the lossless original (but mind you the original did take 10 gigs just for a minute of video )
Shameless plug here

[/youtube]

[slex]

10 gigs for a minute  , were you been using fraps? I'm sure it records uncompressed videos- not sure what codec it uses. youtube uses MP4-H264-AAC codec (that's why we can watch every new uploads on all devices), and I guess it 'killed' the quality during conversion, that happened also to my animations while I've been recording them into AVI format within Anim8or. I've been installing k-lite codec pack and tried to render videos in many codecs but that didn't help much- video's quality were always degraded on YT.
 Finally, after experimenting with a lot of software I've started rendering in PNG pictures and connect them into video with Blender. That way I do slow renders of scenes with Anim8or only once, and can experiment with video editing with Blender (I find Blender very complicated and slow for simple 3D animation and I don't use it for that- it gave me a lot of headache).

 I've noticed something interesting with Blender- it also saves images at 72ppi by default and that value can't be changed, it has that same value within various picture formats. Having 254ppi in BMP format Anim8or is superior when you render BMP image but I guess the difference should be only visible on printers and ultra HD monitors.
72ppi is the optimal value which works great for pixel density of average computer monitors. I don't have ultra HD monitor so can't tell the difference, but if someone does I'd like to hear that, just render some image in 4K resolution with anti anti-aliasing and save them in BMP and PNG format for comparison.
 

[cooldude234]

but I guess the difference should be only visible on printers and ultra HD monitors.
72ppi is the optimal value which works great for pixel density of average computer monitors. I don't have ultra HD monitor so can't tell the difference, but if someone does I'd like to hear that, just render some image in 4K resolution with anti anti-aliasing and save them in BMP and PNG format for comparison.

Well once again the DPI of an image doesn't matter when your viewing those images on a computer (because you can scale them up or down in real-time). You could set the dpi on the image to be 23408329084 if you wanted to and it would look the same on your computer as long as the output resolution is the same.
Also DPI was term coined for printing, and PPI was a term coined for computer monitors. Both values work pretty much the same but they both refer to something slightly different.

As for the codec I was using. I used Nvidia's hardware encoder/decoder with their hvenc codec through the terrible mp4 container format at 4k 60fps with the quality ratio set to a 100.
Doing the math

3810x2160 at 8 bits per channel at 3 colour channels (which is 24 bits for all channels)
24 x 3810 x 2160 = 197510400 bits per image
197510400  / 8 (convert to bytes)
24688800 / 1000 (convert to kilobytes)
24688.8 / 1000 (convert to mega bytes)
= 24.6888 mega bytes

Now we have 60 of these for each second and we have 60 seconds in a minute so...
60 * 60 = 3600
Multiply how many frames we have by how much each frame is...
24.6888 * 3600 = 88879.68 megabytes
88879.68 / 1024 (converting to gigabytes)
= 86.7965625 Gigabytes

Now of course that would be purely lossless and the Nvenc codec was using a variable bit rate with pbuffers and more so if nothing changed in the image in any part it wouldn't have the need to update it so it wouldn't store data for it. On top of that it still was slightly compressing it as a whole. So a 10 gig file over a 86 gig one is still pretty good.
The only codec I've seen come close to quality and space was with the xvid codec where with the same settings I could make that a 2 gig file (but its really process intensive where as Nvenc isn't nearly as intensive).

Trust me, when you are dealing with high quality video expect to deal with the file size that comes with it. I mean if you think about it most bluray movies are about 40 gigs in size and that's at only 1080 at 30 frames a second.

[Alpha2]

I wrestled with a lot of codecs early on trying to get one that wouldn't glitch out or get massacred in the Youtube compression. The Xvid Codec has been pretty good to me for at least 720p at 24 or 30 frames (720pHD profile, single pass) the clarity has always been pretty good for a fair size and reasonable rendering time, But then again I don't use many lights and have never rendered at 60 frames per second in .95, now I kinda want to give it a shot and see if it holds up.

[cooldude234]

I wrestled with a lot of codecs early on trying to get one that wouldn't glitch out or get massacred in the Youtube compression.

As someone who deals with codecs on almost a daily basis, I can tell you they're a pain in the rear and extremely difficult to get working correctly in the way you want; even for an advanced user. So don't feel bad if you are having troubles with them

Also Xvid codec works extremely well at higher resolutions (4k and beyond), but it just gets way to taxing on CPU resources to decode all that wonderfully compressed data in real-time. IE quality vs size is superb but performance is meh.
So I really like it as an archival compression method.

[daniel99]

I had to make some prints for a company few years back, and I've noticed there's amazing quality even with  150dpi for huge banners and prints. Always check antialiased when rendering, though.
I also had no problem rendering videos at 4K resolution with anim8or.
Unfortunately, it seems the max resolution for textures is same as the max resolution for renders 4096x4096.
Sometimes I create my textures as 8192x8192, and I have to size it down to 50% to be able to load it in anim8or.

Overall, anim8or proved to be the perfect choice in every situation for me

[Steve]

Anim8or limits the render size to 4X by 4K. I'll look into increasing this, hopefully without hitting any kind of other limits.

Anim8or limits texture sizes to the OpenGL max for the graphics card, which is a minimum of 4K by 4K. To see what the limits of your card are, run Anim8or form a command line with the parameter -traceinit and look for the line with GL_MAX_TEXTURE_SIZE. On my computer it's 16384.

[daniel99]

Steve: I'll have to look into that, 'cause I don't know how to do that.
Anyhow, I had projects with 4 x 4K textures, but when trying to add another one, it crashed. Fortunately, so far it was enough for me.

[Steve]

Check how much memory Anim8or is using - that might be why it's crashing. Anim8or is not good at managing memory

[Steve]

cooldude234: check out build 1240 - I added a pixel/inch attribute for saving .BMP, .PNG and .JPG images.  Let me know if it does what you need.

Note: .PNG files only support pixels/meter as far as I can tell so I use the closest equivalent.

[Alpha2]

I had to make some prints for a company few years back, and I've noticed there's amazing quality even with  150dpi for huge banners and prints. Always check antialiased when rendering, though.
I also had no problem rendering videos at 4K resolution with anim8or.
Unfortunately, it seems the max resolution for textures is same as the max resolution for renders 4096x4096.
Sometimes I create my textures as 8192x8192, and I have to size it down to 50% to be able to load it in anim8or.

Overall, anim8or proved to be the perfect choice in every situation for me

Antialiasing is fine when you're not editing. But it's a hassle when you get into photo shop and go to select an area of color and you get spotty edges. I've worked on projects that have required pixel perfect accuracy and the kind of "halo" effect you get on aliased images list the last thing you want to deal with.

cooldude234: check out build 1240 - I added a pixel/inch attribute for saving .BMP, .PNG and .JPG images.  Let me know if it does what you need.

Note: .PNG files only support pixels/meter as far as I can tell so I use the closest equivalent.

I gave it a spin with one of the projects I'm working on, and it seems to work perfectly! Thanks for looking into this Steve. The test file properties read exactly as I'd hoped in their properties tab. The compression on jpg seems a bit more aggressive than I remember, but it's probably just been a while since I last rendered a simple jpg in Anim8or. I'll probably just stick to BMP and PNG for any serious still image output.

[Steve]

Alpha2: Try setting the JPG quality to a higher number.  The default of 90 isn't really 90% - I don't know how they apply this number - it's just a parameter to the compression function.  Try 100 and see if that's OK (or just use .png -it's better than .bmp because it's losless but compressed).