Christopher Hill
My feedback
-
103 votesChristopher Hill
supported this idea
·
-
116 votesChristopher Hill
supported this idea
·
-
255 votesChristopher Hill
supported this idea
·
-
374 votesChristopher Hill
supported this idea
·
-
583 votesUnder Review ·
AdminPatrick Palmer
(Director of Product Management, Pro Video and Motion Design, Adobe DVA)
responded
All,
first of all I wanted to thank everyone for making this a productive conversation over the last couple of days.
As several people responded to my comment about keeping the tone civilised, I need to dwell on that for a minute. Please hear me out, this is important to everyone on my crew and I hope it will be to you.
Saying that we shouldn't be surprised when things get heated is very problematic in my opinion. How do you expect a junior person on my team to respond to a technical question when it is combined with something that can easily be described as hate speech? How do you think we can actually come together on actual issues when there's already the assumption that we're a big faceless corporation, not even listening to our customers?
People on my team have received threats. I've been there over the years,…
Christopher Hill
supported this idea
·
-
34 votesChristopher Hill
supported this idea
·
-
160 votesChristopher Hill
supported this idea
·
-
295 votesChristopher Hill
supported this idea
·
-
459 votesChristopher Hill
supported this idea
·
-
667 votesUnder Review · 65 comments · Premiere Pro » Effects & Transitions · Flag idea as inappropriate… · Admin →Christopher Hill
supported this idea
·
-
707 votes
This is something we are looking into. Thanks for the feedback.
Christopher Hill
supported this idea
·
-
1,618 votesUnder Review ·AdminPatrick Palmer
(Director of Product Management, Pro Video and Motion Design, Adobe DVA)
responded
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.Patrick
Christopher Hill
supported this idea
·
-
203 votes
While we are not considering removing this long-requested feature, we hear you on the room for improvement.
Thank you for your feedback
Christopher Hill
supported this idea
·
-
268 votesChristopher Hill
supported this idea
·
-
240 votesUnder Review ·AdminPatrick Palmer
(Director of Product Management, Pro Video and Motion Design, Adobe DVA)
responded
Hi Florian,
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
PatrickChristopher Hill
supported this idea
·
-
516 votes
Thanks everyone for your feedback. I am moving this to Under Review.
Christopher Hill
supported this idea
·
-
855 votesIn Progress ·
AdminFergus Hammond
(Product Manager, Video & Audio Cloud Workflows, Adobe DVA)
responded
Hi all,
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.
Regards,
Fergus
Christopher Hill
supported this idea
·
-
20 votesChristopher Hill
supported this idea
·
-
213 votes
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.
Multiple speakers:
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?Multiple languages:
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 :)
Christopher Hill
supported this idea
·
-
461 votesChristopher Hill
supported this idea
·
