Auto resolution not adapting to zoom level

As the title states, the resolution does not adapt to the zoom level dispite having Auto selected.
I also checked in the advanced composition options and preserve resolution when nested is selected.
This issue happens in every comp and different project files.
I'm running CS5 on Mac OS X 10.6.
Any help would be greatly appreciated.

Auto Resolution doesn't do what you apparently think it does. Here's a quote taken from AE's Online Help about Auto Resolution:
"Adapts the resolution of the view in the Composition panel to render only the pixels necessary to preview the composition at the current zoom level. For example, if the view is zoomed out to 25%, then the resolution automatically adapts to a value of 1/4—shown as (Quarter)—as if you had manually chosen Quarter. If a panel contains multiple views, the resolution adapts to the view with the highest zoom level. This setting gives the best image quality while also avoiding rendering pixels unnecessary for the current zoom level."
Thus, if you look at your AE comp at something like 800%, you will see the pixels. You're simply looking at the comp as you would with a magnifying glass.
If you are scaling up a layer beyond 100% or if you're animating a camera to see only a very small section of a layer, AE will not automatically add resolution to the layer to make it nice and sharp. It can't. The only exception is when you use text layers, or use vector graphics with the Continuously Rasterize switch turned on.

Similar Messages

3.4: keyword auto-completion not working for multiple levels

Auto-completion does not work with higher level keywords, which used to work in LR 3.3 (IIRC).
Example:
I enter in the "Click here to add keywords" field:
"He" then LR tries to complete the keyword by showing keywords starting with "He". Fine.
But this is a keyword which does not exist so far, so I enter "Heldenplatz > W" because I want to have sorted it under Wien. If I'm not mistaken, LR 3.3 showed after entering the "W" a list of existing keywords starting with W (auto-completion for the one level higher tag). This is not the case anymore. I have to enter "Heldenplatz > Wien" completely, which makes it slow and error-prone.
Am I mistaken or can you reproduce it?
Cheers

GaryRowe wrote:
How can it be, after all this time, that they still do not have effective regression testing in place ? Any sane development team (who wants to remain sane ;-) builds this as a priority ... unless they aren't given the resources?
I think (don't remember though) that this never worked, so regression testing would not have helped.
What is really to worry, that features aren't consequently and completely implemented (and tested). With a new option in Lightroom 3, Adobe has offered support for keywords with spaces. It seems that this feature as neither been thoroughly analysed or implemented. Thus, we face the currently inconsequent support of it:
keyword completion only works with the first entered word, but when you enter a complete keyword hierarchy using the ">" letters
filtering seems to have problems too

Programmatically reset IE zoom level

I have a web page that I display in a kiosk setting using a touch screen. Viewers, often use the multi-touch "pinch" feature to zoom in on images, then walk away, leaving the page zoomed in. Is there any way through css, javascript,
vbscript, etc. to make this system reset to 100% zoom level periodically or whenever the page is reloaded (I have it auto-refresh every two hours)

Hi,
Based on your description, I would like to share the link below with you:
New Internet Explorer windows do not respect reset zoom level when using script
http://support.microsoft.com/kb/2741211/en-us
Meanwhile, I would suggest you to post the same question in Microsoft MSDN IE Development Forums for further assistance as Rob mentioned.
As IE development forum focuses on questions about web development including HTML, CSS and Script for Internet Explorer, your issue can be fixed efficiently.
http://social.msdn.microsoft.com/Forums/en-US/iewebdevelopment/threads
Thank you for understanding.
Hope it helps.
Regards,
Blair Deng
Blair Deng
TechNet Community Support

Premiere Elements 11 - Video Stabilizer does not limit to zoom

The description in the help and tutorials document for this effect indicates that selecting limit to zoom will limit the degree of stabilization applied to the selected bounds of zoom. The intent is to limit the appearance of moving edges in the final video. I have a dive video where I am attempting to use the stabilizer function. I believe I have entered the stabilization parameters correctly (Smoothing 24, use original background, zoom 121, correction limit to zoom). I save the video as an MP4 file using the default settings. I view the resultant file in Windows media player and all the edges of the video dance in and out of the image. Am I doing something wrong or are my expectations wrong? Help!

Ideally you should set Smoothing and check the Limit to Zoom box only. Do not set the Zoom level.

CS4 NOT capable of sharp displays at all zoom levels

I must have been asleep, until now, and missed the significance and importance of what follows.
In post #11 here:
http://forums.adobe.com/thread/375478?tstart=30
on 19 March 2009 Chris Cox (Adobe Photoshop Engineer - his title on the old forums) said this, in a discussion regarding sharpness in CS4:
"You can't have perfectly sharp images at all zoom levels.". Unfortunately, my experience with CS4 since its release late last year has repeatedly confirmed the correctness of this statement.
What makes this statement so disturbing is that it contradicts an overwhelming amount of the pre- and post-release promotional advertising of CS4 by Adobe, to the effect that the OpenGL features of CS4 enable it to display sharp images at all zoom levels and magnifications. What is surprising is that this assertion has been picked up and regurgitated in commentary by other, sometimes highly experienced, Ps users (some unconnected with, but also some directly connected with, Adobe). I relied upon these representations when making my decision to purchase the upgrade from CS3 to CS4. In fact, they were my principal reason for upgrading. Without them, I would not have upgraded. Set out in numbered paragraphs 1 to 6 below is a small selection only of this material.
1. Watch the video "Photoshop CS4: Buy or Die" by Deke McClelland (inducted into the Photoshop Hall of Fame, according to his bio) on the new features of CS4 in a pre-release commentary to be found here:
http://fyi.oreilly.com/2008/09/new-dekepod-deke-mcclelland-on.html
Notice what he says about zooming with Open GL: "every zoom level is a bicubically rendered thing of beauty". That, when viewed with the zooming demonstrated, can only be meant to convey that your image will be "sharp" at all zoom levels. I'm sure he believes it too - Deke is someone who is noted for his outspoken criticism of Photoshop when he believes it to be deserved. It would seem that he must not have experimented and tested to the extent that others posting in this forum have done so.
2. Here's another Adobe TV video from Deke McClelland:
http://tv.adobe.com/#vi+f1584v1021
In this video Deke discusses the "super smooth" and "very smooth" zooming of CS4 at all zoom levels achieved through the use of OpenGL. From the context of his comments about zooming to odd zoom levels like 33.33% and 52.37%, it is beyond doubt that Deke's use of the word "smooth" is intended to convey "sharp". At the conclusion of his discussion on this topic he says that, as a result of CS4's "smooth and accurate" as distinct from "choppy" (quoted words are his) rendering of images at odd zoom levels (example given in this instance was 46.67%), "I can actually soft proof sharpening as it will render for my output device".
3. In an article by Philip Andrews at photoshopsupport.com entitled 'What's New In Adobe Photoshop CS4 - Photoshop 11 - An overview of all the new features in Adobe Photoshop CS4',
see: http://www.photoshopsupport.com/photoshop-cs4/what-is-new-in-photoshop-cs4.html
under the heading 'GPU powered display', this text appears :
"Smooth Accurate Pan and Zoom functions – Unlike previous versions where certain magnification values produced less than optimal previews on screen, CS4 always presents your image crisply and accurately. Yes, this is irrespective of zoom and rotation settings and available right up to pixel level (3200%)." Now, it would be a brave soul indeed who might try to argue that "crisply and accurately" means anything other than "sharply", and certainly, not even by the wildest stretch of the imagination, could it be taken to mean "slightly blurry but smooth" - to use the further words of Chris Cox also contained in his post #11 mentioned in the initial link at the beginning of this post.
4. PhotoshopCAFE has several videos on the new features of CS4. One by Chris Smith here:
http://www.photoshopcafe.com/cs4/vid/CS4Video.htm
is entitled 'GPU Viewing Options". In it, Chris says, whilst demonstrating zooming an image of a guitar: "as I zoom out or as I zoom in, notice that it looks sharp at any resolution. It used to be in Photoshop we had to be at 25, 50 , 75 (he's wrong about 75) % to get the nice sharp preview but now it shows in every magnification".
5. Here's another statement about the sharpness of CS4 at odd zoom levels like 33.33%, but inferentially at all zoom levels. It occurs in an Adobe TV video (under the heading 'GPU Accererated Features', starting at 2 min 30 secs into the video) and is made by no less than Bryan O'Neil Hughes, Product Manager on the Photoshop team, found here:
http://tv.adobe.com/#vi+f1556v1686
After demonstrating zooming in and out of a bunch of documents on a desk, commenting about the type in the documents which is readily visible, he says : "everything is nice and clean and sharp".
6. Finally, consider the Ps CS4 pdf Help file itself (both the original released with 11.0 and the revised edition dated 30 March 2009 following upon the release of the 11.0.1 update). Under the heading 'Smoother panning and zooming' on page 5, it has this to say: "Gracefully navigate to any area of an image with smoother panning and zooming. Maintain clarity as you zoom to invididual pixels, and easily edit at the highest magnification with the new Pixel Grid." The use of the word "clarity" can only mean "sharpness" in this context. Additionally, the link towards the top of page 28 of the Help file (topic of Rotate View Tool) takes you to yet another video by Deke McClelland. Remember, this is Adobe itself telling you to watch this video. 5 minutes and 40 seconds into the video he says: "Every single zoom level is fluid and smooth, meaning that Photoshop displays all pixels properly in all views which ensures more accurate still, video and 3D images as well as better painting, text and shapes.". Not much doubt that he is here talking about sharpness.
So, as you may have concluded, I'm pretty upset about this situation. I have participated in another forum (which raised the lack of sharp rendering by CS4 on several occasions) trying to work with Adobe to overcome what I initially thought may have been only a problem with my aging (but nevertheless, just-complying) system or outdated drivers. But that exercise did not result in any sharpness issue fix, nor was one incorporated in the 11.0.1 update to CS4. And in this forum, I now read that quite a few, perhaps even many, others, with systems whose specifications not only match but well and truly exceed the minimum system requirements for OpenGL compliance with CS4, also continue to experience sharpness problems. It's no surprise, of course, given the admission we now have from Chris Cox. It seems that CS4 is incapable of producing the sharp displays at all zoom levels it was alleged to achieve. Furthermore, it is now abundently clear that, with respect to the issue of sharpness, it is irrelevant whether or not your system meets the advertised minimum OpenGL specifications required for CS4, because the OpenGl features of CS4 simply cannot produce the goods. What makes this state of affairs even more galling is that, unlike CS3 and earlier releases of Photoshop, CS4 with OpenGL activated does not even always produce sharp displays at 12.5, 25, and 50% magnifications (as one example only, see posts #4 and #13 in the initial link at the beginning of this post). It is no answer to say, and it is ridiculous to suggest (as some have done in this forum), that one should turn off OpenGL if one wishes to emulate the sharp display of images formerly available.

Thanks, Andrew, for bringing this up. I have seen comments and questions in different forums from several CS4 users who have had doubts about the new OpenGL display functionality and how it affects apparent sharpness at different zoom levels. I think part of the interest/doubt has been created by the over-the-top hype that has been associated with the feature as you documented very well.
I have been curious about it myself and honestly I didn't notice it at first but then as I read people's comments I looked a little closer and there is indeed a difference at different zoom levels. After studying the situation a bit, here are some preliminary conclusions (and I look forward to comments and corrections):
The "old", non-OpenGL way of display was using nearest-neighbor interpolation.
I am using observation to come to this conclusion, using comparison of images down-sampled with nearest-neighbor and comparing them to what I see in PS with OpenGL turned off. They look similar, if not the same.
The "new", OpenGL way of display is using bilinear interpolation.
I am using observation as well as some inference: The PS OpenGL preferences have an option to "force" bilinear interpolation because some graphics cards need to be told to force the use of shaders to perform the required interpolation. This infers that the interpolation is bilinear.
Nothing is truly "accurate" at less than 100%, regardless of the interpolation used.
Thomas Knoll, Jeff Schewe, and others have been telling us that for a long time, particularly as a reason for not showing sharpening at less than 100% in ACR (We still want it though ). It is just the nature of the beast of re-sampling an image from discrete pixels to discrete pixels.
The "rule of thumb" commonly used for the "old", non-OpenGL display method to use 25%, 50%, etc. for "accurate" display was not really accurate.
Those zoom percentages just turned out to be less bad than some of the other percentages and provided a way to achieve a sort of standard for comparing things. Example: "If my output sharpening looks like "this" at 50% then it will look close to "that" in the actual print.
The "new", OpenGL interpolation is certainly different and arguably better than the old interpolation method.
This is mainly because the more sophisticated interpolation prevents drop-outs that occurred from the old nearest-neighbor approach (see my grid samples below). With nearest-neighbor, certain details that fall into "bad" areas of the interpolated image will be eliminated. With bilinear, those details will still be visible but with less sharpness than other details. Accuracy with both the nearest-neighbor and bilinear interpolations will vary with zoom percentage and where the detail falls within the image.
Since the OpenGL interpolation is different, users may need to develop new "rules of thumb" for zoom percentages they prefer when making certain judgements about an image (sharpening, for example).
Note that anything below 100% is still not "accurate", just as it was not "accurate" before.
As Andrew pointed out, the hype around the new OpenGL bilinear interpolation went a little overboard in a few cases and has probably led to some incorrect expectations from users.
The reason that some users seem to notice the sharpness differences with different zooms using OpenGL and some do not (or are not bothered by it) I believe is related to the different ways that users are accustomed to using Photoshop and the resolution/size of their monitors.
Those people who regularly work with images with fine details (pine tree needles, for example) and/or fine/extreme levels of sharpening are going to see the differences more than people who don't. To some extent, I see this similar to people who battle with moire: they are going to have this problem more frequently if they regularly shoot screen doors and people in fine-lined shirts. Resolution of the monitor used may also be a factor. The size of the monitor in itself is not a factor directly but it may influence how the user uses the zoom and that may in turn have an impact on whether they notice the difference in sharpness or not. CRT vs LCD may also play a role in noticeability.
The notion that the new OpenGL/bilinear interpolation is sharp except at integer zoom percentages is incorrect.
I mention this because I have seen at last one thread implying this and an Adobe employee participated who seemed to back it up. I do not believe this is correct. There are some integer zoom percentages that will appear less sharp than others. It doesn't have anything to do with integers - it has to do with the interaction of the interpolation, the size of the detail, and how that detail falls into the new, interpolated pixel grid.
Overall conclusion:
The bilinear interpolation used in the new OpenGL display is better than the old, non-OpenGL nearest-neighbor method but it is not perfect. I suspect actually, that there is no "perfect" way of "accurately" producing discrete pixels at less than 100%. It is just a matter of using more sophisticated interpolation techniques as computer processing power allows and adapting higher-resolution displays as that technology allows. When I think about it, that appears to be just what Adobe is doing.
Some sample comparisons:
I am attaching some sample comparisons of nearest-neighbor and bilinear interpolation. One is of a simple grid made up of 1 pixel wide lines. The other is of an image of a squirrel. You might find them interesting. In particular, check out the following:
Make sure you are viewing the Jpegs at 100%, otherwise you are applying interpolation onto interpolation.
Notice how in the grid, a 50% down-sample using nearest-neighbor produces no grid at all!
Notice how the 66.67% drops out some lines altogether in the nearest-neighbor version and these same lines appear less sharp than others in the bilinear version.
Notice how nearest-neighbor favors sharp edges. It isn't accurate but it's sharp.
On the squirrel image, note how the image is generally more consistent between zooms for the bilinear versions. There are differences in sharpness though at different zoom percentages for bilinear, though. I just didn't include enough samples to show that clearly here. You can see this yourself by comparing results of zooms a few percentages apart.
Well, I hope that was somewhat helpful. Comments and corrections are welcomed.

Make table of contents links keep current zoom level, not zoom out to full page

When Indesign creates tables of contents, they automatically link to the paragraphs the links point to, so that in an interactive PDF, clicks and prods take the user to that page. Great.
What's not so great is, that the hyperlinks / cross-references / jump-links / whatever that are created behind the scenes within the table of contents appear to:
...be automatically set to reset the zoom to full page width
...not be editable in any way
Normal cross references retain the zoom level that the user has chosen, and normal hyperlinks that point to a page in the document have a range of settings about what zoom level change (if any) should be imposed on the user, which can be set to 'inherit zoom'.
How do I set up a table of contents that doesn't annoy users by resetting their chosen zoom level to an artitrary default when they use the interactive table of contents?
I'm really hoping I don't have to ditch Indesign's table of contents feature and create every cross reference manually.

(editted) So it turns out that you can 'expand' a table of contents by copying and pasting it - this fills the hyperlinks panel with links that can be editted (like above) but breaks the auto-update - they're no longer a TOC, they're just a text frame full of links. (I had got different copies mixed up when I thought the frame holding the editable links was also auto-updating)
The greying out of the links was a red herring, just something to do with the fact they were on a master page.
It does mean that one possible TOC workflow is:
Create a TOC on the pasteboard somewhere.
Before finalising the document, update this TOC and alt-drag the 'live' TOC creating an editable 'dead' copy in an appropriate place in the document
Edit the link properties of the links in the 'dead' copy (don't forget that you can select multiple hyperlinks at once by holding down shift, and edit things like the Zoom Setting all at once with Hyperlink Options in the Hyperlinks flyout menu. )
Then, if you make other changes to the document later on, delete the dead copy, update and re-copy the live original, and re-do the changes to the new copy
This isn't a bad method - it just adds about a minute's work each time you export a PDF (delete, update TOC, alt-drag, shift-select the new batch of .XXXX links at the bottom of the Hyperlinks panel, > Hyperlink Options, Zoom Setting > Inherit Zoom, done).
Alternatively, you could manually build a TOC using cross-references if you want links to the exact position on the page, not just the top of the appropriate page.

Hi, how can I keep the same zoom level for all the pages I view in Safari and even when I close and open it. Indeed with a 27 inch Imac I have a lot of space, most of the websites are built for smaller resolutions and my sight is dropping !   Thx

Hi, how can I keep the same zoom level for all the pages I view in Safari and even when I close and open it. Indeed with a 27 inch Imac I have a lot of space, most of the websites are built for smaller resolutions and my sight is dropping !   Thx

Hi, how can I keep the same zoom level for all the pages I view in Safari and even when I close and open it. Indeed with a 27 inch Imac I have a lot of space, most of the websites are built for smaller resolutions and my sight is dropping !   Thx

Why does not safari allow to keep the zoom level over the whole website? This is universal problem for all ipad browsers.

This is a big problem on sites like Tomshardware and Sweclockers and probably many more that Safari is not capable of keeping the zoom level the same over all website pages. And it makes the browsing experience on the IPAD an annoyance.
You have to constantly double tap to see the website clearly for each webpage load. There should be settings to allow to remember the zoom level
for a whole website. So you don't have to double tap on every new page of the website.
The other browsers like ICAB and Mercury are not handling this any better and seem to be limited by the webkit rendering options available.
It's instantly visible on Sweclockers and it becomes a problem on tomshardware when you click on a review link.
I have included pictures here that showcase the problem.

We are all just your fellow users here. If you intended this as a suggestion to Apple, your best bet would be to submit it at this link:
http://www.apple.com/feedback

Acrobat Pro X stamps, comments do not display at certain zoom level

A user found a bug in Adobe Pro 10.1.6.
We have both Adobe Reader and Pro installed on Server 2008.
A document stamped with dynamic signature: "APPROVED" do not show in Adobe Pro when opening.
If the zoom level is being change then the stamp do show.
Same document show the dynamic stamps in Adobe Reader.
I reported the bug through this form https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
Is there a workaround until a fix is comitted ?

> Well, "Default" is what's in the maker.ini file as it exists "out of the box".
That's to be expected, as up until the program is run for the first time, there's no opportunity at all for it to discover the screen size. I suppose Adobe could ask during the install, but not only is that annoying (and would complicate blind installs), the answer might be impossible to know (running FM in a VM window rather than on a real display, or historically, in an X-window on Unix).
Even after FM is running, and even if using EDID API calls, I doubt FM is making such calls. When FM was first written, it was impossible for an ap to discover screen size. Up until VESA DDC2 in 1996, monitors were rarely capable of reporting anything to the attached computer. Had FM implemented DDC calls, it would have needed to add DDC/CI, then E-DDC, then several generations of EDID calls. And APIs for any of these would have been different for Unix, Mac and Windows, plus normal Windows churn.
Most users don't care. Those that do have traditionally made inquiries and discovered the maker.ini entry for this.
I might add that FM apparently can detect the aspect ratio of the screen (4:3, 16:9, 16:10), because it must know the raster extents in order to paint the windows and place the dialogs (it just doesn't know what inches or mm that corresponds to). This, I presume, is why it doesn't need to encode the A/R in maker.ini.

Zoom level not works on horizontal orientation

Hi, i've this issue : when i set crystalReporViewer.zoom(2) on a report with horizontal orientation, zoom not works. If i set vertically orientation, my zoom level is applied.
Thanks !

Hi Paulo,
It's not clear in the steps you are using. Are you setting the zoom level first before previewing or setting the zoom after previewing?
First post you said you were setting zoom to level 2, now you say you are setting zoom to level 300????
And Horizontal is Landscape and vertical is Portrait correct?
If you set the Zoom to 300 % you will have to scroll across, horizontal bar should be enabled.
If I set it to 1 then it fits the width:
This is a landscape report.
Don

Nosquint's Global zoom level setting can not be saved

I change the Global zoom level setting 140 from 150, and it works a 140. after I quit FF and back again, the Global zoom level is changed back to 150 again, it seems that can not be saved. it is working under V21
I am using ff 24.0 now
any solution?

You can check for problems with preferences.<br />
Rename or delete the prefs.js file and possible numbered prefs-##.js and user.js files to reset all prefs to the default value.
*http://kb.mozillazine.org/Preferences_not_saved
*http://kb.mozillazine.org/Resetting_preferences
You can rename the content-prefs.sqlite file to content-prefs.sqlite.old (or delete the file) in the Firefox profile folder to reset the page zoom for all websites.

Zoom Level Setting Does not Stay Constant

HP Pavilion dv7-6163us Entertainment Notebook PC
The zoom level is set at 125 but keeps changing as I go to different screens. It bounces to 150 and I have to cycle it thru 100 and then 125. It will not stay at 125 and I cannot find a solution to the problem. In fact when I ask a HP forum for 'zoom level' I get no responses. Sometimes the screen will be at 150 but the zoom level indicates it is at 125. I unchecked PINCH ZOOM in the mouse setting for Synaptics Touch Pad Device but it had no affect. In Opions, advanced settings I have checked the Reset Zoom Level (but could that be a problem?) This just started after I removed a program that was not working correctly.

zoom level keeps changing as i am typing..hate it sometimes to goes clear down to the lowest level..also i can't set the blinking curser to stop..it disapears when i go to use it..this is my second hp laptop and my other one did the same thing..drives me crazy....

I am really having a horrible time when trying to do our Church announcements in FCP X. When I try to take a clip from the event to the timeline my clips expanded and my timeline zoom level does not stay in the original place. Help

I am really having a horrible time when trying to do our Church announcements in FCP X. When I try to take a clip from the event to the timeline my clips expanded and my timeline zoom level does not stay in the original place it moves to the right and is max out which makes every clip that I bring to the timeline expanded.

What format etc. are the video clips and what were they shot on?
Before you do anything else, trash the preferences with this free app:-
http://www.digitalrebellion.com/prefman/

When I 'zoom' my browser, it does not hold the zoom for the next view and I have to 're-zoom, it used to stay at a chosen level of zoom, any ideas?'

I used to be when I zoomed the view using Ctrl and mouse wheel that the next page would be at the sam elevel of zoom. Now I have to re-zoom every time I open a page.

The Firefox Page Zoom feature does a domain by domain level of saving the users preferred zoom level settings, there is no default Page Zoom level setting in Firefox.
Try the Default FullZoom Level extension: <br />
https://addons.mozilla.org/en-US/firefox/addon/6965
Or the NoSquint extension: <br />
https://addons.mozilla.org/en-US/firefox/addon/2592/

Image Format to PDF, when zoom --resolution not good enough eventhough image is 300dpi

Hi Guys,
Anyone here know how to achieve a good image resolution when it is zoomed in? Doesn't matter the size but the quality of the image.
I have tried 170dpi and 300dpi, it seems almost the same in image quality..
Please help.
Thank you.

Hi Mobly,
The resolution is still the same, do you have any other idea?
I think Adobe is the one controlling the PDF resolution.
Hi Adobe,
Please can we have the option on whether we want to compress the pages exported as PDF?
It's really important to us the quality and resolution of the image. We want to retain the resolution of the image eventhough it is zoomed.
Thanks.

Auto resolution not adapting to zoom level

Similar Messages

Maybe you are looking for