Skip to content

Peter

My feedback

4 results found

  1. 58 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Peter commented  · 

    >How does this not have more votes?

    I can answer that.
    Because every now and then the topic is merged with a bunch of other threads (sometimes not even the same issue).
    Then a week or so later an "engineer" comes in and closes the thread. Often citing something completely irrelevant and not addressing the problem whatsoever.

    Then 5 minutes later one of us reopen a new thread with the same problem and the counter is back to zero.

    Also: The problem goes beyond raster graphics, it happens with vectors too - scaled rasters are just far more noticeably degraded.

    An error occurred while saving the comment
    Peter commented  · 

    Unfortunately the admin is wholly incorrect on two counts: DPI is entirely irrelevant and forcing output to 96dpi doesn't solve the problem (nor should it, illustrator shouldn't be compromising quality for workflows that aren't equal to 96dpi.)

    The problem from day 1: JPG format in "Export for Screens" is always using "Type Optimized (Hinted)" as the output even when "Art Optimized (Supersampling)" is selected.

    It's easy to prove too: Just put some text into an illustrator file and change the "Anti-aliasing method" (in the text panel) to None, Sharp or Crisp or Strong.

    In the JPG output from Export for Screens we can see that no matter if we choose Art Optimized or Type Optimized, the output is always as if Type Optimized was selected.

    This is it, this is the whole problem. It's likely an off-by-one programming bug.

    An error occurred while saving the comment
    Peter commented  · 

    Hey all - this bug has been reopened as "Poor quality images from Export for Screens" (there's likely a few of them floating around) up vote them if this issue affects you.

    We are trying again to get some attention to this problem as it's trivial to reproduce and affects ad developer workflows in particular.

    Adobe engineers: I (and others) are willing to demonstrate this issue for you. We're open to dialogue to help get this fixed.

    An error occurred while saving the comment
    Peter commented  · 

    I thought I'd post an update as I've had the opportunity to test this on a new machine.
    Unfortunately I can confirm that Export for Screens -> JPG still exports as Type Optimized (hinted) even when Art Optimized (Supersampling) is selected.

    Exporting to PNG however produces the correct results.

    An error occurred while saving the comment
    Peter commented  · 

    Hi, please find the sample file attached.

    To reproduce the error use the Export for Screens tool, and select JPG output (in the configuration panel ensure that the output anti-aliasing is set to Art Optimized)

    The visual errors are highlighted by the arrows.

    An error occurred while saving the comment
    Peter commented  · 

    Images from artboards containing embedded raster files output using Export for Screens are of decidedly lower quality than those output from Save for Web.

    This is being reposted as it has been closed erroneously by Adobe admins.
    Notes for Admins: This is not a resolution export setting problem. This is also not a rendering intent problem (i.e. changing the anti-aliasing setting does not fix the problem.)

    An error occurred while saving the comment
    Peter commented  · 

    Images from artboards containing embedded raster files output using Export for Screens are of decidedly lower quality than those output from Save for Web.

    This is being reposted as it has been closed erroneously by Adobe admins.
    Notes for Admins: This is not a resolution export setting problem. This is also not a rendering intent problem (i.e. changing the anti-aliasing setting does not fix the problem.)

    An error occurred while saving the comment
    Peter commented  · 

    The "Art Optimised" anti-aliasing method used in Export for Web is poorer than Save for Web. The only current work around is to do each image manually. The problem seems to be that it's always outputting Text-optimised even when art-optimised is selected in the settings.

    While Export for Web is much faster, it's unfortunately not usable for a range of images.

    Illustrator 24.0.1 / macOS Catalina 10.15.1

    An error occurred while saving the comment
    Peter commented  · 

    Hi there, I have just sent an example file for review.

    Perhaps unrelated, but the GPU preview mode also suffers from the same quality issue. (I.E. GPU preview mode displays the images differently than the older software rendering mode.)

    An error occurred while saving the comment
    Peter commented  · 

    Hi,

    I have put together a demonstration file and video of the problem in action. Attached herein.
    Note: The problem applies specifically to JPEG output.

    Reproduction steps:
    1. Create new illustrator file
    2. Place raster image
    3. Resize raster image to be smaller size
    4. Export for Screens, using JPG output
    Compare this to Save for Web and Export for Screens: PNG output.

    Zip file of everything is here (because this service does not allow ZIP files.): https://www.dropbox.com/s/q6y61f4fz2eclao/Sample%20File_Folder.zip?dl=0

    Peter supported this idea  · 
    An error occurred while saving the comment
    Peter commented  · 

    This problem essentially makes Export for Screens useless in any professional setting (e.g. Including a product photo). My workaround is to export at 4x in EfS and resize to 1x in a separate raster package.

  2. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Peter shared this idea  · 
  3. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    There are now several separate requests made, based on the feedback in this thread:

    1. Regarding adjustable color and opacity for 3D shadows:

    https://illustrator.uservoice.com/forums/333657/suggestions/47054086

    2. Regarding presets for each tab in 3D and Materials panels: Object, Materials, Lighting:

    http://illustrator.uservoice.com/forums/333657/suggestions/47350001

    All those who commented on the topic until October 16, 2023, are already added as voters there. If this is something you want to have for 3D and Materials in Illustrator — please upvote it. If possible — create new requests and bug reports about 3D, rather than commenting here inside. This will help the team to better prioritize efforts on making the feature better. As always — thanks for the feedback! It helps.

    An error occurred while saving the comment
    Peter commented  · 

    Ideally pushing the rendering tasks to a background process would help with using this tool. It's a bit of a pain to have to click and unclick cpu-intensive modes just to make adjustments or wait for 10+ seconds when I could be working on another part of the artwork.

  4. 110 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Peter commented  · 

    Currently any field that takes entry of numerical value can be adjusted by scrolling. However for those of us which have mouses with free-wheel or touch-style scrolling this tends to lead to accidental value adjustment.
    An option in the preferences to disable to feature would be useful.

    Arguably these are almost-always fields where scrubber-like value adjustment is not helpful.

    Peter supported this idea  · 

Feedback and Knowledge Base