Yikes!!!
I print all day every day onto large format printers using images generated from Rhino. Rhino will Render or Screen capture at whatever pixel count you desire. The EXIF data is not required. It may be nice but it’s certainly not essential.
If you would like some help with various ways of dealing with this and you are capable of asking NICELY rather than screaming at everyone, then I will be glad to help.
Steve
This is printed text You cannot scream nor whisper with printed text, there is no audio or sound associated with it, no volume level can be defined. Even with text to speech software there is no noticeable volume change while reading caps. consider it emphasis…
I am perfectly capable of printing at what ever resolution, scale, size, orientation, color, dpi, ppi, I choose.
Here is my origanal post: “I’m trying to print (selection) a tiff image at 300 dots per inch but the resulting image keeps coming out at 72 dpi. Please fix this !”
All I’m trying to ask is that McNeel fix Their broken print dialog and make it work properly, so I dont have to do post processing of the image to make it print with the settings I already defined in Rhino!!!
Work flow! its all about work flow and how I can make it easier and more efficient!!!
This means 1" = 1" is not working correctly either
And the pulldown menu for print quality is just a pointless activity…
You may consider all caps to be emphasis but the majority of people here I would guess would take the more common interpretation of it.
The rules of “netiquette” are not exactly static or undisputed. Are emoticons appropriate in formal emails? Are “trigger warnings” thoughtful or over-the-top? Are you irritating everyone you email with your “signature”? The uncertainty that typically surrounds these questions makes it all the more remarkable that there’s one convention that is incontestable: Typing in all caps is Internet code for shouting, and it is rude.
But what are you actually doing? You’re trying to print a TIFF? Are you taking a screenshot or using the Print dialog or rendering? As has been explained by everyone else in this thread and the fact that this has never been changed in 20 years of Rhino, the fact of that “72” dpi value being stuck in renders by default is meaningless to the the “workflow” of most people. But then what does that have to do with Rhino’s Print dialog and scale setting there? So it’s a little confusing as to where something actually needs to be changed.
I’m not a programmer, I have done a little…
I educate myself on the microsoft operating system inner-workings so i can help myself and others
If I had never used Rhino3d and someone explained to me that Rhino is not printing correctly because of the discrepancy between the print dialog dpi and the actual dpi that is recorded to the EXIF data in the image, I would say: "Yes, you are correct-this print function is not working correctly "
And if I worked for McNeel I would say " Hmm, that is wrong…all these years and no one noticed! I will promptly report this bug instead of torturing you in a public forum "
What is the workflow you are actually doing? What are you trying to print, and from what? Which print dialog? Is it even in Rhino? Seriously, you’re not being clear.
I just checked Ver.6 (Yes WIP, I understand) It also is not writing the correct dpi to the EXIF data while creating a *.tif image file…
I filed the issue as RH-41060.
@stevebaer, we actually do write that information. See the YT issue for information.
/Nathan
Spot on!
Thank You, much appreciated
But what print dialog dpi is being referred to? The Print command for linework has nothing to do with renders, and the Print function in the render window is some bog-basic tool that has no settings, it’s all up to the printer driver. So where exactly is “Rhino” not “printing” renders at the “right” scale? Seriously, please explain, preferably with screenshots.
Screen shots are above…If I tell my printer to print this at 100% it will come out at 83" x 83" not the 20 x 20 I specified, and I don’t want to calculate in my head the proper reduction percentage. if this worked the way it should it would come out the printer at proper size with NO post processing…
So…
I think what is happening is this:
He prints his viewports directly to tiff-format, specifying desired print size and dpi. This results in a given dimensions in pixels (3800x2400 or similar). He then copies this file to a thumb drive, which is inserted directly into a printer. The file is then printed directly from the printer without a media size being specified, based only on pixel dimensions and dpi (ppi, rather). As Rhino doesn’t change the exif data, but leave them at the standard 72, the printer gives him a low-res - but huge - print. Right?
“without a media size being specified, based only on pixel dimensions and dpi (ppi, rather)” <-----Yes, kinda, I tell the printer !00% it then sees the the incorrect 72 dpi/ppi within the exif data of the image and the print size is way large!
The Resolution pull down menu in the print dialog has no effect on print dpi it is always 72
The 1 inch in model = 1 inch on paper has no effect either
entering a custom dpi has no effect it is always 72
Wow this seems a little out of hand for a simple seeming issue.
I tested on v5 for kicks. When saving images through the print dialog (File - Print), no matter what dpi I chose from the drop down list or entered myself, the resulting file was the proper pixel dimension but 72dpi every time. It’s a easy fix in photoshop, but it shouldn’t be a issue in the first place.
Well… again… no where in that dialog box does rhino claim to be asking for the EXIF data. Rhino merely asks you how big (measurable with a ruler) you want the picture to be and at how many pixels per unit this picture will be shown. Then Rhino saves you the trouble and calculates how many pixels it will need to render.
Is this the first time this issue is discussed? No, it pops up again and again.
Is it a bug? Well, since it’s by design, no.
Steve says that Rhino doesn’t set the EXIF and that Windows uses a default. Nathan says Rhino sets this value. I dunno.
Is that the best way / most user-friendly to go about this? Who knows. As you say - and has been said every time this comes up - the EXIF data is easily set in the application where you will be using this picture. Of course, when now a situation comes up where there isn’t another application used, it’s obvious that the current system doesn’t always work…
Any application that generates images and has a print function wants to know what default image size YOU want, therefore it needs two things from you: size dimensions ie inches, mm, miles angstroms, etc AND print quality/resolution/dpi(unit)/ppi without these two pieces of information there is no default size/resolution ALL windows print dialog will collect and use this info for Your albeit arbitrary default size/quality. Rhino is NOT doing this properly it ask you for print quality in three different places and uses it to calculate x,y pixel count but it is not applying the quality variable to the image and that is the dots per inch. If you choose 300 dpi it should NEVER be 72 in the image file. when you interrogate the image properties it should show 300 dpi and when printing at 100% 1 inch should equal 1 inch with however many dpi you choose.
And NO I don’t want to load every rhino print into an imaging program and set the dpi to 300 (that i already defined in Rhino) and save it out just so it will print the correct size, when the print dialog for Rhino is able to and WILL do this if it worked right…