Joe
My feedback
6 results found
-
7 votes
An error occurred while saving the comment -
76 votes
This is considered by the team for the roadmap. More updates will be posted when anything becomes known. Thank you all for the push — please keep being vocal about things that matter to us, upvote and comment.
An error occurred while saving the comment AI being thrust in our faces just comes hand in hand with using a computer nowadays and it's already too much, but can we please make sure that in the pursuit of pushing these AI features at users we aren't obstructing normal use.
It's really disruptive to my everyday workflow when I'm trying to crop an embedded image in Illustrator, only for me to accidentally leave part of the crop box just outside the available image and be prompted to use a credit to generate the blank area.
This never used to be an issue because the crop box bounds were constrained to the existing available image. There is no option to force the constraints to stay within the available image now, because Adobe are so hot on pushing their AI capabilities that it feels like they want us to accidentally just use them. I NEVER use AI expand in Illustrator as part of the crop tool. If I needed generated expanded areas I'd do it another way, it's frankly laughable that it's been incorporated into a tool meant for CROPPING in the first place.
I'm glad for some of these features, but I almost never use them. I don't need AI when I'm just trying to crop an image for my job, so it's actually counterintuitive and harmful to the user experience to have AI pushed at me when I wasn't trying to use it.
The bottom line is, in my opinion, it's fine to market and advertise the generative AI capabilities that are now present in this software, but these features should NEVER get in the way of professional users who don't need them and weren't going to use them. If a principle of non-obstruction of normal features were adopted overall by the Adobe devs, it would create a more harmonious environment where, dare I say it, the ever-controversial AI could exist side by side with the normal features used by professionals who don't use AI as much, if at all.
-
84 votes
-
76 votes
This is considered by the team for the roadmap. More updates will be posted when anything becomes known. Thank you all for the push — please keep being vocal about things that matter to us, upvote and comment.
-
High Sierra (macOS 10.13) GPU rendering issues with RGB document - Intel Graphics
-
AI_2018_CC.png 39 KB -
Screen_Shot_2018-02-28_at_7.46.38_PM.png 419 KB -
Screen_Shot_2018-02-28_at_7.39.44_PM.png 1934 KB -
Bug_Error.mov 4356 KB -
Captura_de_pantalla_2018-01-16_a_las_10.53.56.png 12 KB -
Captura_de_pantalla_2018-01-16_a_las_10.53.41.png 14 KB -
Screen_Shot_2018-01-10_at_8.32.52_am.png 479 KB -
Screen_Shot_2017-12-30_at_4.50.20_PM.png 1155 KB -
Logo_problem.ai 384 KB -
Screen_Shot_2017-12-19_at_15.23.06.png 362 KB -
Screen_Shot_2017-12-08_at_10.32.01_PM.png 658 KB -
Screen_Shot_2017-12-08_at_10.31.57_PM.png 568 KB -
Screen_Shot_2017-12-08_at_10.31.50_PM.png 614 KB -
Untitled-2.ai 1618 KB -
Screen_Shot_2017-11-27_at_10.45.11_AM.png 862 KB -
Screen_Shot_2017-11-13_at_12.47.27_PM.png 188 KB -
Screen_Shot_2017-11-10_at_11.47.47.png 164 KB -
Screen_Shot_2017-11-01_at_09.14.56.png 322 KB -
Screen_Shot_2017-10-25_at_19.30.32.png 441 KB -
Screen_Shot_2017-10-09_at_8.00.22_PM.png 777 KB -
Screen_Shot_2017-10-09_at_8.00.16_PM.png 1122 KB -
Screen_Shot_2017-10-03_at_9.08.53_PM.png 422 KB -
system_information.png 282 KB -
Illustrator_information.png 294 KB -
Screen_Shot_2017-09-18_at_7.16.12_PM.png 266 KB -
Screen_Shot_2017-09-15_at_1.35.45_PM.png 16 KB -
Screen_Shot_2017-09-15_at_1.35.34_PM.png 18 KB -
Screenshot_2017-08-03_09.21.02.png 33 KB
393 votesthe issue has been resolved by Appple in macOSX 10.13.4
Please upgrade to resolve the issue -
-
7 votes
Hi Valerii,
Thanks for the confirmation. Since we are able to reproduce the issue, so we will review it and prioritize accordingly.
Thanks
AnishAn error occurred while saving the comment I'm having the same problem. The assets are still fine once dragged into the document, but it's just the thumbnail displaying it too small, right? It's functional and all, but it's quite annoying.
A workaround is to place the object into a document (preferably in the app you made it in) as a copy (by right clicking on it in the Libraries window). You will see the edited, most up-to-date version of your asset appearing just as it should in the document. Then, delete the object in your CC library. Now, drag the object back in from the document to save a new version. Theoretically, this MAY cause you to need to relink it in other documents (if you ever placed it as a linked object in other documents instead of a vector copy as I just described), but as long as you name it exactly how it was before, you may not encounter this problem.
I agree strongly with this post, and I believe masquerade below has drawn the discussion to an important fundamental issue; that Adobe seems intent on making AI features so hard to ignore that we end up using them by accident because they're so closely (something physically) intertwined with the professional tools that we've used for decades that a stray click is inevitable.
I'm almost resigned to the reality that AI being pushed in our face from every piece of software is part and parcel of participating in the digital age at present, but it's getting ridiculous and desperate if the aim truly is to make AI tools inescapable when using features in the software that have been there for decades and have not been modified or improved for years prior to AI's introduction.