I hope someone can answer this. It is what I use Ae for exclusively. Can any STAFF members shed some light on this issue?
This is a user-to-user forum. If you want to only get help from Adobe staff, you'll need to contact Adobe support.
If you wouldn't mind help from your fellow users, could you please give us some more information?
You mention using the latest version of AE, but sometimes the CC app lies to you. So could you please share your exact version number?
Do you get this error when opening projects with those sequences or when importing them or both?
What happens if you import in CC 2014 and then open the project in your current version?
What OS are you using? What are your other system specs?
Are you still facing this problem? If not, let us know how you solved it. If so, please let us know so we can assist you further.
Thanks for replying. I didn't see the notification from the replies to this thread.
I've been shooting the last few months and ran into the problem again, starting googling it and found my old thread. I'm on a long schedule being that I'm shooting plant time-lapse, but now I need to start assembling the RAW files instead of the jpg proxies. The problem is exclusively with RAW image sequences imports. I haven't tried importing in 2014, then opening in the current version. I think it would work but it would be better if I could just use the current version. Some sequences work, some of them not. I always select force alphabetical order when importing, but when I leave that unselected the problem persists.
Currently this is happening on version 22.214.171.124.
I'm running OSX 10.12.5
Just responded to Szalam. Thanks for reply. I just saw it today when encountering the same problem.
I'd suggest contacting actual Adobe support. They can remote into your machine if needed and try to fix the issue for you.
Note: when you go to Adobe.com/support, you have to click on the Creative Cloud icon. Anything else is JUST THERE TO TRICK YOU! I'm being facetious, but it really is a bit confusing. I've pointed it out to people at Adobe and hopefully it will be fixed soon.