Ton
My feedback
271 results found
-
9 votes
An error occurred while saving the comment An error occurred while saving the comment See: https://community.adobe.com/t5/illustrator/missing-transparency-in-placed-pdfs/m-p/11699887?page=1#M257019
The CMYK PDF placed linked in a CMYK document gives the problem. Embedding solves the problem.
When the CMYK PDF is placed linked in an RGB document there is no problem.
The problem can be repeated in older Illustrator versions. -
8 votes
-
11 votes
-
10 votes
An error occurred while saving the comment @merry-cox if that does not work for you, try Export for Screens.
An error occurred while saving the comment Preview is empty, but export works. Happens on all files 28.3
-
66 votes
We have started working on fixing this one.
-
4 votes
-
90 votes
This feature request is completed and it is available in Illustrator 28.0 and above.
An error occurred while saving the comment In Illustrator, Show in Finder does not highlight and select the file, but Reveal in Bridge does.
An error occurred while saving the comment @Egor, InDesign and Bridge do have a Reveal in Finder option that selects and highlights the file in the Finder.
-
6 votes
-
18 votes
The fix is pushed into Global Availability build 28.6.
If it misbehaves still — please comment back.
-
278 votes
Latest Beta Build 29.2.34 now adds Eyedropper in the Color Picker dialog to allow us pick colors from artwork.
Please try to test it and comment on if it works as you expect.
-
50 votes
-
27 votes
An error occurred while saving the comment If Global Colors are still not supported after 6 years, prevent them being added to a CC library.
There is no warning when the box is checked.An error occurred while saving the comment See this example.
An error occurred while saving the comment It is not only spot colors from InDesign that become magenta, Global colors from Illustrator have the same problem.
An error occurred while saving the comment An error occurred while saving the comment It currently also happens with Global RGB colors added to the CC library. When added to another document from the CC library, they lose their name and become a magenta spot color.
An error occurred while saving the comment Spot in Illustrator
An error occurred while saving the comment This is still not solved:
Create a Pantone Spot color swatch in InDesign (I used 321 C for sentimental reasons) and add it to a CC Library.
Switch to Illustrator, double click the swatch in the CC Library to add it to the Swatches panel.
It becomes a Global Process Color CMYK Swatch as 100% Magenta instead of a green Spot color.
Library:
https://shared-assets.adobe.com/link/2dbbba8a-e688-486f-41ee-cba1d77530dfAn error occurred while saving the comment For more problems with sharing swatches see:
https://creativecloudassets.uservoice.com/forums/905281-report-bugs/suggestions/34268938-sharing-swatches-using-libraries-is-totally-unreliable. -
4 votes
An error occurred while saving the comment This goes back to the primeval times before color management existed. You would have specific numbers that would only work on a specific device. Your RGB numbers would give different results on various devices (displays, film) and CMYK values will give different results with various printing processes. As long as you don't tell which ICC profile should be associated with the numbers, the results will be unpredictable.
-
3 votes
An error occurred while saving the comment You will get a warning when you change color mode during creation of the document, but you need to click the warning triangle to see what the problem is.
An error occurred while saving the comment If you create a new document based on a web or art & illustration preset (which are RGB documents) and select CMYK as color mode in the Advanced section, your swatches will have RGB names but will be converted to CMYK.
And for new document, based on a Print preset, if you change the color mode to RGB during creation, you will have RGB color swatches with CMYK names.After doing this, when you create new documents without changing settings, your new documents will inherit those settings.
-
3 votes
-
4 votes
An error occurred while saving the comment Same problem with pixels as unit.
Create an RGB document based on an RGB preset and set in Preferences the keyboard increment to 1 px
Close the document and create a document based on a Print preset (uses mm in Europe), increment becomes 0,3528 mm
All New RGB documents with px as unit will have 1,0001 px as increment.
There is no warning.
It may not look like a lot, but it becomes visible when many objects are repeated using the arrow keys and Cmd (Ctrl) D
Keep the increments consistent in RGB and CMYK documents and don’t change them when another color mode is chosen. -
9 votes
-
15 votes
-
5 votes
An error occurred while saving the comment Chris, we are not Adobe engineers. I tried to explain what is happening. I know that the current way of creating pixels can be improved, but I (and Egor) cannot change that. In the meantime there are only workarounds. The bug report is from 2017, but the problem existed before. Let's hope that this gets more priority.
An error occurred while saving the comment Chris, as long as you use 72 ppi as output resolution and artboards and objects align to the pixel grid you will see no additional pixels.
Changing the output resolution to something other than a multiple of 72 ppi can generate additional anti-aliased pixels caused by rounding.
With your example of a 360 pixel sized object at 25 pixels per inch you would expect an image of 125 pixels (360/72 = 5 and 5X25 = 125).
You will get that when the upper left coordinates of the object can be divided by 72 and the result does not contain fractions. This happens with individual assets on a single artboard, as well as objects on multiple artboards.
If you space the artboards 72 pixels apart you get the expected pixel size.
I think that the behaviour of rounding fractional pixels can certainly be improved (I would prefer rounding down) but this explains what is happening.I see Egor already pointed to the bug report on UserVoice
-
12 votes
This issue is believed to be fixed in the build 28.4.0.20.
Please try to update and generate anything. Comment back if it works.
An error occurred while saving the comment Yes, it works now! Thanks for fixing this.
An error occurred while saving the comment Unfortunately not solved on my machine, still gives a black rectangle after a long wait.
An error occurred while saving the comment It is getting worse:
In 28.0 it takes a minute to generate an error message.
In Beta 28.1 87 it takes about 6 minutes to create a black square without warning or error message.An error occurred while saving the comment Unfortunately 28.1 74 looks promising, but it is giving the same black square.
An error occurred while saving the comment Unfortunately it still does not work on my machine. A 100x100 px with the default hamburger.
It takes longer, create a black square, but the error message is gone.
Looks like this works fine in 28.4.1
Linked or Embedded
GPU as well as CPU Preview