630 votesUnder Review · 64 comments · Premiere Pro » Effects & Transitions · Flag idea as inappropriate… · Admin →
This is something we are looking into. Thanks for the feedback.
Thanks for all the feedback. It’s pretty clear that we’ve got to look into the workflow using this format more closely, there are enough reports about gaps at this point to reopen this item. I’ll post more info about next steps shortly. In the meantime, a couple of questions are easy to answer:
- The plugin is designed for Premiere Pro. It currently doesn’t provide support for After Effects.
- It does work with AME, so if you want to use it for batch processing, that’s very doable
- If you’ve started a project with Autokroma, there’s no easy way to transfer it to be running with the new plugin.
While we are not considering removing this long-requested feature, we hear you on the room for improvement.
Thank you for your feedback
while this is a rather critical and large change to the way the application works and will take some time to be implemented, we’ll definitely put this under consideration.
There’s more than one solution to this problem, though.
A good short term opportunity is to use the parallel install feature in the creative cloud application. It should help to at least take away some of the issues working with people on a different version of the application.
Another thing worth keeping in mind is that you can install CC on two different machines (if you’re on an individual subscription). That gives you additional opportunity to keep different versions around for compatibility reasons.
I’ll update the status of this request as we move along.
If you have further thoughts on this matter, please keep them coming.
Thanks everyone for your feedback. I am moving this to Under Review.
793 votesIn Progress · AdminFergus Hammond (Product Manager, Video & Audio Cloud Workflows, Adobe DVA) responded
MKV support is actively being worked on. I don't have a release date to share currently but when that changes, I will update this message.
This is not a bug, it’s as designed. We specifically limit the visibility to one track at a time to avoid accidentally burning in multiple tracks. Also, when exporting to a format that only supports one captions stream like SRT or STL, we need to know which is the active track in order to export the correct track.
But I understand why you might need two tracks visible at the same time.
If we could automatically identify speakers and designate a style associated with them, would that help? For example speaker 1 is blue and on the left, speaker 2 is yellow and on the right?
Do you ever need to burn in both at the same time or is it just a matter of being able to see both to aid in translation and alignment?
Thanks for the feedback, we really are listening :)
This is by design. We always keep captions within safe margins (10%). Would an option to defeat this restriction be useful or is it better to remove this safeguard all together. Opinions welcome.
An error occurred while saving the commentChristopher Hill commented
I won't repeat all the current justifications, only that I support removing the restriction. Most professionals know when their titles need to be within safe margins and can determine where those are on their own.
1 voteChristopher Hill shared this idea ·