52 votesNeeds More Info · AdminFergus Hammond (Product Manager, Video & Audio Cloud Workflows, Adobe DVA) responded
Davide, can you share a project plus the media that demonstrates this issue?
308 votesUnder Review · AdminAnnika Koenig (Premiere Pro, Motion Graphics) (Software Quality Engineer, Adobe DVA) responded
Thanks for this request. It is under review! For future requests please create single UserVoice posts, e.g. one for gradients for strokes and one for multiple shadows. This way the team is able to update the status of a post much easier. Thanks!
Hi Taran and everyone subscribed to the thread,
first of all: thanks for the incredibly detailed suggestion and the great conversation in the comments. While making such a change for the playback engine has a ton of implications and therefore isn’t done ad hoc, we’re certainly going to create a POC for it and will evaluate if there’s a way to put this into a production build for a test drive in an upcoming beta version.
I’ll keep you posted.
As Wes noted, we are looking at many areas for optimization and have made strides in the last few releases already.
We recognize there are still many areas to improve performance and we are investing in appropriate areas.
Threads that are catch-alls are often non-actionable. Please keep giving us specific feedback on what workflows are slow for you.
Technical solutions may not always be as obvious as some people may be suggesting as the application architecture is often very different than people’s conception.
Short answer. Yes, we want to and will make it faster.
This is something we are looking into. Thanks for the feedback.
794 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 good feedback. Would you be interested in seeing other transitions too, like slide on from the side or bottom?
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.
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 :)