Image import not fit for purpose
I'd like to replace the embarrassing image import code (presumably knocked together by an intern in 1998?) with something that has functional parity with the rest of the Adobe CC apps. Why should a JPG that opens without issue in Photoshop/Illustrator etc. cause After Effects to soil itself? Why can AE still not deal with CMYK bitmaps? Why does AE still not give you actual useable info on which images were not imported, rather than having to dismiss 2, sometimes 3 individual error messages for each image and then having to manually sift through what did import and try to work out what did not?
Utterly moronic. Professional software my ****.
Antoine Autokroma.com (Independent Developer of AfterCodecs, BRAW Studio, PlumePack, Influx) commented
Yeah I agree. Maybe an extension such as AEViewer could help you ? https://aescripts.com/aeviewer/
Hi Antoine, thanks for at least looking.
I confess I was still used to Photoshop's habit of taking an image's file suffix as 'gospel' and only trying to open a .png file with the PNG parser, for example, rather than looking at the image header or simply trying other common containers, so when I checked and found that first file opening ok in PS it seems I wrongly assumed the file suffix was accurate.
But again, and as you correctly surmise, the questions of which images cause problems, and how AE communicates that to the user, are quite separate.
Thank you for those files. image145.png.doesn't work because it's not a png file, it's a jpg file. Once renamed properly to .jpg, it works on my AEfx v22. The second file indeed doesn't work. It works with our Importer Influx for Adobe Premiere Pro and After Effects (I had to rename and suffix it to .jpg.influx for Influx importer to be called), so a workaround exists here for you if needed.
It's true that it would be better if AEfx explains what's wrong with the file and if it tried to import the file with others containers
Here's a JPG which seems to trip AE with its colour profile:
I can't really post any other images as they're client-supplied and have people in them. But as I say, this is less about specific images, and more about how AE behaves (or not) and informs the user in those situations.
Hi Ian, Could you share one of those faulty file through Dropbox or Google Drive public link ?
And since you asked, the kind of work I do is freelance, mostly very ordinary motion graphics, usually corporate, usually B2B. Nothing that's going to set the world on fire or appear in any high-profile case study. Client feedback varies; sometimes it's good, sometimes it's lacking, sometimes I need more info, sometimes they're a bit rude or inconsiderate, especially if they're up against it with a job themselves, but if I tried to give them a lecture in how to give feedback, they'd likely give me a very short lecture in sending all their work to someone else.
But I'm a bread-and-butter customer, and looking through these forums there seem to be an awful lot of customers like me who are fed up with AE, fed up with Adobe, and the minute an app comes along with slightly better performance and responsive support forum? Well the minute that happens, those customers may be _gone_.
PS. I tried attaching examples of problem images, but it seems a 396K PNG and and a 720K JPG are too much to upload. At least I assume that's the problem. Ironically, the upload function just silently fails without giving the user any feedback.
I needed time to think over how best to respond, but I'm also fortunate to be busy with plenty of work at the moment, which delayed my response further. I admit the intern joke was childish, and the choice of language in the last line of my post was unhelpful and irrelevant to the issue at hand. For that I apologise sincerely and without reservation.
But here's the thing (and I, too, am being as diplomatic as I can here) I *don't* apologise for my frustration. It's interesting that you re-frame the issue as me not following "such basic steps… as attaching examples of the files causing problems" when my question requires nothing of the sort.
• Why should a JPG that opens without issue in Photoshop/Illustrator etc. cause After Effects to soil itself?
Well, why should it? Why isn't AE sharing the same file import parser as other apps? If it is, why isn't it put through the same unit tests? Something's wrong somewhere. Why would an expensive piece of professional software be tripped up by files that a $40 utility like GraphicConverter doesn't even blink at? Pretty fundamental issue, not some edge case that needs example files to track down some obscure glitch.
• Why can AE still not deal with CMYK bitmaps?
Well, why can't it? Even more fundamental, and even easier to test. Is it an easy answer? Either way, no sample file needed for that.
• Why does AE still not give you actual useable info on which images were not imported, rather than having to dismiss 2, sometimes 3 individual error messages for each image and then having to manually sift through what did import and try to work out what did not?
This is about user experience, not the idiosyncrasies of particular image files. My whole question was not about AE's ability to open any particular image, but about how it behaves when presented with a file it can't open, for whatever reason.
What does "Bad header 86 :: 1" actually mean? What is a user supposed to think or do when AE tells them an image is damaged or unsupported, but it opens just fine in Photoshop? Importing 10 images that AE doesn't like produces 20 modal alerts. We only just "progressed" from the same situation with missing footage, where AE would show endless identical error messages. Why doesn't AE handle this more intelligently? These things just train users to ignore errors.
The implication is that I'm being rude. That I'm behaving unreasonable. Just "try again and present your issues in a more neutral fashion", yes? Ok, let's assume I *am* behaving unreasonably. Have those behaving reasonably fared any better? Let's see…
Of the top issues in any category, the first 36 (thirty six!!) have had no status change by Adobe, so not under review, not in progress, and no request for more info. In fact only 4 issues in the top 100 have had their status updated. Good grief.
UPDATE: Since my original post, 2 issues have now been implemented in the latest Beta versions. Both issues were over 4 years old. Praise be.
Of those top 36 issues, Adobe staff have only bothered to reply in 7 of them. And most of them were years ago.
What conclusion should I draw from this? What conclusion do *you* think any of us here should draw from this? You make it very clear it's not the squeaky wheel that's going to get the grease, but while some of these posters are undoubtedly as fed up as I am, most are doing their best to present their issues "in a more neutral fashion" just as you request. But it doesn't seem to be doing them a fat lot of good either, does it?
Even the frankly superhuman efforts of people like Sander van Dijk go almost completely unacknowledged.
What's the magic secret to get Adobe to pay attention to their users? Code word? Special hand shake? Just what *would* "motivate" you?
You ever hear of a company called Quark? They had this desktop publishing app. And an attitude. Didn't work out so well for them when something better came along.
Hard to round off a post like this without any kind of request to respond that doesn't come across as passive-aggressive. "Yeah, I bet you won't reply…"
Well I'm *begging* you to reply. I'll happily eat all the humble pie you have, but we need to see some movement. We want to see some feature requests being acknowledged. We want to see some of the many everyday pain points being resolved. I can think of a dozen off the top of my head right now. None of it is stuff that some product manager will be able to stand on stage at Adobe Max and be "super excited" to introduce, but these are things that will actually make a difference. And might shift people like me from using AE because I have to, and back to using AE because I want to.
Would you have example of file that fails to import ?
Paul Uusitalo (AE Quality Engineering) commented
I am being as diplomatic as I can here. I don't know what work you do, or what sort of feedback you get from your customers, but tell me, how motivated would you be to listen to anything they had to say if they addressed you in this fashion?
Now, if you would like to try again and present your issues in a more neutral fashion, taking such basic steps as (in this instance), attaching examples of the JPEG files causing you problems, we would be happy to look into it.