ElJay_Bronx
My feedback
-
5 votesNeeds More Info · 3 comments · Premiere Pro » Essential Graphics · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment ElJay_Bronx
supported this idea
·
An error occurred while saving the comment ElJay_Bronx
commented
This is now enabled in 13.1.1...but it's not consistent. sometimes I have a "snap" and red borders on the edges of my image, sometimes I just have the blue edge. The way I work on these clips is as follows: In the Effects Controls Panel, highlight "Motion" and controls appear around the image in the Program Monitor, Sometimes setting for the entire clip and sometimes animating with keyframes, I'll use the visual controls rather than adjusting the values in Position or Scale. Using Guides (another GREAT new feature of 13.1.1) and a template where I have vertical guides set at 33.33, 50 and 66.66 percent, and a horizontal guide at 50%, I get the image exactly how I want it. Sometimes it pins correctly (showing RED borders where I'm in danger of the clip edges being within the image and resisting allowing that to happen) and sometimes it's still blue. I can work with it the way it is, but SO wish it would always snap and give the red cues.
-
6 votes
An error occurred while saving the comment ElJay_Bronx
commented
I haven't had this happen with new versions...or since I upgraded my video card (I am "anonymous" below and have long ago upgraded everything else - using i7-8700, 32GB DDR4 but.I was still using a GTX 1050 Ti which I upgraded to a RTX-2070. Haven't had an encoding error since...knock on wood.
ElJay_Bronx
supported this idea
·
An error occurred while saving the comment ElJay_Bronx
commented
Just a note to say that I inadvertently was signed in as Anonymous and posted the below comment; it was me (ElJay_Bronx) not sure how that happened. I just hope the problem gets identified and fixed.
Jay -
40 votesElJay_Bronx
supported this idea
·
An error occurred while saving the comment ElJay_Bronx
commented
Running Premiere 13.1, the same thing happens; a workaround is to switch to a different application and then back. Shouldn't be happening!
-
90 votesElJay_Bronx
supported this idea
·
-
167 votesElJay_Bronx
supported this idea
·
An error occurred while saving the comment ElJay_Bronx
commented
This happens to me constantly.
My system:
Win 10 Pro, up to date
i7-8700
32GB RAM
RTX-2070There is a workaround which is to switch to some other application. It's clear that the mouse cursor acts BEHIND the Premiere window...can even see evidence of it as it rolls over elements in the Premiere application...but it's necessary to see the cursor and the app-switch is necessary. It's a productivity issue and needs to be addressed.
-
7 votesElJay_Bronx
shared this idea
·
-
2 votesElJay_Bronx
supported this idea
·
-
181 votes
While we are not considering removing this long-requested feature, we hear you on the room for improvement.
Thank you for your feedback
ElJay_Bronx
supported this idea
·
-
73 votes
As we look at our current captions workflow, we will use this feedback to keep us informed
An error occurred while saving the comment ElJay_Bronx
commented
The way that I find works best is to copy the time code at the moment you want the caption to start and paste it into the "in" box, then do the same with the "out". Works perfectly for me, and I don't have to worry about dragging the handles around. I have the underlying script in a Word file and simply go to the beginning of the first word on the timeline, copy time, press + to add a new caption, highlight "in", paste, go to end of the line, highlight timecode, copy, select "out", paste, then copy/paste the line(s) from the script. Time consuming but this kind of work IS time consuming!
-
2 votes
An error occurred while saving the comment ElJay_Bronx
commented
Sam, have you tried RENAMING the caption clip in the Project Manager? I don't frankly have time to test but believe that if you duplicate the existing clip, and then rename i.e. <<sequence_name>>_eng dup to <<sequence_name>>_ger the link would be broken, the timings would be the same and you'd be able to simply drop the new language in place of the original...very similar to what I need to do when duplicating Essential Graphic items when re-using and needing to change dates or other information.
-
255 votes
Thanks for all the feedback so far.
It is one of many areas we are looking into.
ElJay_Bronx
supported this idea
·
-
5 votesElJay_Bronx
shared this idea
·
-
558 votes
Thanks for the suggestion(s).
ElJay_Bronx
supported this idea
·
-
50 votesElJay_Bronx
supported this idea
·
-
470 votes
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.
ElJay_Bronx
supported this idea
·
-
43 votesElJay_Bronx
supported this idea
·
See the comment I made in "Snap in Program Monitor". Commenting here because this wonderful feature was added in 13.1.1. Pointing out that it works sometimes but not always, and it would be good for it to be more consistent. The desired behavior, which it does about 50% of the time: border changes from blue to red and resists dragging beyond the edges of the clip. The other 50% it doesn't snap, just shows the standard blue border and it's up to me to notice that the edge is showing.