Vincent Gustin
My feedback
-
15 votesVincent Gustin
supported this idea
·
-
103 votesVincent Gustin
supported this idea
·
-
241 votesIn Progress ·
AdminFergus Hammond
(Product Manager, Video & Audio Cloud Workflows, Adobe DVA)
responded
Hi all,
The I-frame first idea is implemented in multiple codecs, including anything that is LongGOP in an MXF wrapper, XDCAM in a MOV wrapper, and it's being added for the work that will be released soon that will hardware accelerate AVC Intra on Apple silicon in MXF.
Regards,
Fergus
Vincent Gustin
supported this idea
·
-
61 votesIn Progress ·AdminFergus Hammond
(Product Manager, Video & Audio Cloud Workflows, Adobe DVA)
responded
We have determined the underlying cause of this issue and we're working on a fix for it. I don't have a date when it will be fixed but when I do, I will share it here.
Vincent Gustin
supported this idea
·
-
84 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?
Vincent Gustin
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 :)
An error occurred while saving the comment An error occurred while saving the comment Vincent Gustin
commented
Hello Francis,
for me, it's the users who have to be careful about what they do, both when editing and exporting,...
We need to be able to work with several subtitling tracks visible simultaneously on the same timeline.
You have integrated in the interface the basis to allow this:
see nothing, see only one, see them all and you also reproduced the possibility to activate them individually "on demand"...Unfortunately, it's not really active like that since, for now, it's "nothing or one at a time".
It's a bit the same for the subtitle track order... You can rename them but not organize them as you want: too bad.
Thanks for your attention, Vincent.
Vincent Gustin
supported this idea
·
-
456 votesVincent Gustin
supported this idea
·
-
4 votes0 comments · Premiere Rush » Adobe Ecosystem (Compatibility with Premiere Pro, Adobe Stock, Adobe Fonts, etc.) · Flag idea as inappropriate… · Admin →Vincent Gustin
supported this idea
·
-
2 votesVincent Gustin
supported this idea
·
-
9 votes3 comments · Premiere Rush » Adobe Ecosystem (Compatibility with Premiere Pro, Adobe Stock, Adobe Fonts, etc.) · Flag idea as inappropriate… · Admin →Vincent Gustin
supported this idea
·
-
3 votesVincent Gustin
supported this idea
·
-
21 votesVincent Gustin
supported this idea
·
-
2 votesVincent Gustin
supported this idea
·
-
75 votes
An error occurred while saving the comment Vincent Gustin
commented
Hello,
the fact that it "happens" in the project is already a good idea ...BUT, for "big network" (hundreds of users, multi-sites connected, interconnected NAS-SAN storage, sharing of projects and skins,...), how could we exchange-share-propose a set of styles in a dynamic and permanent way?
Could you consider this in the same way as you did with the Graphic Essentials (integration of a patch with folder management for example)?
Thanks for your attention, Vincent.Vincent Gustin
supported this idea
·
-
1,617 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
An error occurred while saving the comment Vincent Gustin
commented
It seems that Adobe has still not heard its users ...
2 years and still no possibility to use the BRAW in a native and powerful way!
Are we to believe that you don't need us to live?
Vincent Gustin
supported this idea
·
-
315 votesVincent Gustin
supported this idea
·
-
160 votesVincent Gustin
supported this idea
·
-
3 votesVincent Gustin
supported this idea
·
-
126 votesVincent Gustin
supported this idea
·
-
39 votes
An error occurred while saving the comment Vincent Gustin
commented
With RGS from HP, working on remote location works correctly... and, on local network, I'm also using a VNC connection to work remotly without problem.
Vincent Gustin
supported this idea
·
Good evening Francis,
could we be sure that you have seen and read all the additional information and requests, or even proposals below... (the answer to the initial post having not changed since April 16, 2021)?
Unless you expect something else from all of us of course...