the dudes
My feedback
-
30 votes
An error occurred while saving the comment the dudes supported this idea ·
-
1 vote
the dudes shared this idea ·
-
4 votes
the dudes supported this idea ·
-
2 votes
the dudes supported this idea ·
-
38 votes
An error occurred while saving the comment the dudes commented
Yes please.
the dudes supported this idea ·
-
507 votes
An error occurred while saving the comment the dudes commented
Bump.
the dudes supported this idea ·
-
157 votes
An error occurred while saving the comment the dudes commented
For people where the command opens AME, but nothing is added: If you hit "Add to AME" again, with open Media Encoder, does it work?
An error occurred while saving the comment the dudes commented
Not experiencing this on my end. Still feel bad for this. Happened in the past.
Don't forget the golden rule in professional production:
Never aboard the first iteration of a major release if your work critically depends on it! -
13 votes
An error occurred while saving the comment the dudes commented
Your WeTransfer-link has already deceased. Jeez your venting is bad too :)
An error occurred while saving the comment the dudes commented
Fixing bugs is mainly reserved to the new versions.
-
219 votes
An error occurred while saving the comment the dudes commented
How about not posting a toxic complaint in opposition to the platform we got here. We all get frustrated at some point. But instead of venting, why don't you make a proper request that is recomprehensible for the devs?
-
19 votes
the dudes supported this idea ·
-
2 votes
the dudes shared this idea ·
-
3 votes
An error occurred while saving the comment the dudes commented
When sending the comp directly to AME (= without adding it to the render queue) the problem doesn't occur.
the dudes shared this idea ·
-
7 votes
An error occurred while saving the comment the dudes commented
Still (again?) happening with the newest AE/ME.
the dudes supported this idea ·
-
2 votes
the dudes shared this idea ·
-
3 votes
the dudes supported this idea ·
-
102 votes
the dudes supported this idea ·
-
31 votes
the dudes supported this idea ·
-
3 votes
An error occurred while saving the comment the dudes commented
Disable "Hardware accelerated decoding" in preferences/import.
Then, edit/purge/all cache.But please, ADOBE, do your homework!!!
An error occurred while saving the comment the dudes commented
I got the same problem since about two versions now. It's a huge bummer. Attached is a file that produces said error on my end...
the dudes supported this idea ·
-
5 votes
the dudes supported this idea ·
An error occurred while saving the comment the dudes commented
Switching its display to "float" might do the trick
An error occurred while saving the comment the dudes commented
Completely agree!
-
3 votes
We really appreciate your post, however, User Voice is primarily for feature requests and bug reports. It appears your issue is more of a troubleshooting problem which could be solved more easily by our support team. You can open a case with them via call or chat at this link: https://helpx.adobe.com/contact.html
the dudes supported this idea ·
Yes please. Otherwise, proxy generation gets very messy, or choreful.