TaranVH

My feedback

  1. 22 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Premiere Pro » Closed Captions  ·  Flag idea as inappropriate…  ·  Admin →
    TaranVH supported this idea  · 
  2. 76 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  Premiere Pro » Export  ·  Flag idea as inappropriate…  ·  Admin →
    TaranVH supported this idea  · 
  3. 58 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    16 comments  ·  Premiere Pro » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    TaranVH supported this idea  · 
  4. 185 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Under Review  ·  126 comments  ·  Premiere Pro » Essential Graphics  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    TaranVH commented  · 

    @Sergiu Mihalache
    "It's a modern day trend to replace real support with "community support." ... the only option you get is to write on a forum or "board" ... Adobe is deliberately and consistently not providing."

    You're saying you don't like Uservoice?

    I must counter your point. I think Adobe's move to Uservoice has been fantastic. For one key reason: It's a 3rd party website. They don't have control over it. They can't remove stuff that is inconvenient or unflattering.

    Before Uservoice, there was a feature request page on the adobe website. You'd send off a feature request, never to see it again. Some of my feature suggestions defied written explanation, so I included video screen capture of the error. They were not long... just a minute or two.
    But since I uploaded them unlisted to youtube, I can see that many of those videos still have 0 views. Adobe wasn't watching them.

    Uservoice is public. Everyone can see your request. Everyone can comment on it. This is MUCH better.

    Before uservoice, for public discussion of bugs and features, we pretty much only had the Adobe forums. This was a big problem, because, either through negligence or deliberate meddling, many of those threads have been deleted.

    Like this one from 11 years ago, about an issue with track mattes that still persists to this day:
    https://web.archive.org/web/20141202085724/https://forums.adobe.com/thread/767190

    Or this one, containing tons of diagnostic and preventative steps that users can take to battle an error that still persists to this day:
    http://forums.adobe.com/thread/2171535
    (Archived here, by me):
    https://imgur.com/3UUm9nu

    I could go on and on. I have a lot of those links, because I personally had already compiled a public feature suggestion/bug report list, which is still available here:
    https://docs.google.com/spreadsheets/d/1dVJb7kI_ZETLavrplfARgn9gL8HUpvkq6A0jCPxqA3w/edit#gid=1133868629

    But I genuinely think that Uservoice is better than my own list, because anyone can submit, vote, and comment. I'm slowly moving my suggestions over to uservoice, when I have spare time.

    Adobe has made many mistakes. Implementing Uservoice is not one of them.

    An error occurred while saving the comment
    TaranVH commented  · 

    @Mike Berry
    "The large majority of users we have surveyed prefer the standard EGP, un-parented, graphics."

    Careful. Microsoft said the same thing about Windows 8's Metro UI (getting rid of the start menu, among other things.)

    https://www.extremetech.com/computing/99967-windows-8-is-microsoft-flailing
    "Microsoft, instead of dealing with the pain of their existing users directly, has trotted out pages of surveys, charts, tables, and even some college-level calculus formulas to prove why the new system is, in theory, an improvement."

    And they continued using data to justify that Metro UI was good, that people like it, and even to justify the lack of a tutorial. (I still don't know how it was supposed to work)
    https://web.archive.org/web/20121216022723/https://www.technologyreview.com/news/508546/microsoft-has-been-watching-and-it-says-youre-getting-used-to-windows-8/

    But ultimately, enough people hated Metro UI, that Microsoft backed off a year later.
    https://www.extremetech.com/computing/179756-microsoft-finally-admits-defeat-will-bring-start-menu-back-in-future-windows-8-update

    As for Premiere's essential graphics, I still can't so much as draw a line with it. And why do I have to click, move, and click again, just to make a circle or rectangle? Why does Adobe insist on constantly hiding tools inside of dropdown menus? "We feel that this decluttering is a boon," they say. But I, the user, know that it just slows me down.
    And when I've rotated a shape, why does the position change unpredictably when I just want to move the anchor point??
    These are smaller points, but it still makes the legacy titler just that much better/more usable.

    I don't mind losing wacky features like the drop face 4 color gradient...
    But core features like titles in bins, easy duplication and parenting on the timeline, and perhaps most importantly, the ability to easily draw any shape I want... (which I most commonly use for masking) I can't give those up.

    Yes, the parenting behaviour of the legacy titler IS quite confusing when you're first learning to use it. But that doesn't mean Adobe should get rid of that feature, or use that info to justify getting rid of the legacy titler completely. It means that that feature should be made optional, so that those who want it, can still use it. Because once you understand how the parenting works, it can be extremely useful. (To be clear, "parenting" is how you can re-use the same title twice on the timeline, then make a change, and both instances will be updated, right?)

    I've made other comments previously, which I still stand by.

    An error occurred while saving the comment
    TaranVH commented  · 

    @John Graves
    I'll repeat what I posted earlier.
    HOW TO SAVE ALL YOUR LEGACY TITLES PERMANENTLY:
    Create a new sequence with the same resolution as those titles. (If there are many different resolutions, you might want to do this for each resolution, or you can just use the highest vertical and horizontal width for the sequence, and put 'em all in there at 100% scale.)
    Place all the titles onto the sequence.
    Highlight them all, and open up the Clip Speed / Duration panel. (I believe it is CTRL R by default)
    Change the duration to 00:00:00:01 (so, one frame each) and CHECK ON the "ripple edit, shift trailing clips" checkbox.
    Press OK.
    Now you should have a sequence with all your titles one 1 frame each.
    Now, export that sequence as Format: PNG, PNG Sequence with Alpha.
    Make a new folder and let 'em export.
    Now, the exported .pngs will no longer be editable in Premiere's legacy titler, but you will at least have saved them all in full quality. And you can Photoshop them. Yep.
    --------
    You're probably gonna want to keep a copy of Premiere available on a computer somewhere, which CAN still edit those titles, even after this feature is gone. Don't reply on being able to re-download that version of Premiere... versions have gone missing from adobe creative cloud due to things like the Dolby codec no longer being licensed.
    Just think worst case scenario, and prepare for that. I don't expect that the legacy titler will be around much longer...

    ---------
    I still use the legacy titler, because it's quick and easy to create text/graphics, they are stored in bins, and they still render a LOT faster than mogarts... I explained in much more detail in an earlier comment.

    An error occurred while saving the comment
    TaranVH commented  · 

    @Sergiu Mihalache
    You're not gonna like it.
    HOW TO SAVE ALL YOUR LEGACY TITLES PERMANENTLY:
    Create a new sequence with the same resolution as those titles.
    place all the titles onto the sequence.
    highlight them all, and open up the Clip Speed / Duration panel. (i believe it is CTRL R by default)
    Change the duration to 00:00:00:01 (so, one frame each) and CHECK ON the "ripple edit, shift trailing clips" checkbox.
    Press OK.
    Now you should have a sequence with all your titles one 1 frame each.
    Now, export that sequence as Format: PNG, PNG Sequence with Alpha.
    Make a new folder and let 'em export.
    Now, the exported pngs will no longer be editable in Premiere's legacy titler, but you will at least have saved them all in full quality. And you can use photoshop. Yep.

    An error occurred while saving the comment
    TaranVH commented  · 

    Fun fact... the Adobe guys didn't program the "legacy" titler. They bought the code from someone else. That's why it's packed with so many features, and has so many integrated shortcuts.

    I'm just glad that other people are as upset at its potential deletion as I am.

    An error occurred while saving the comment
    TaranVH commented  · 

    Oh, I forgot one of the most important features of the legacy titler: Multiple lines per text box.
    Premiere's new text tool DOES have this, but the Essential Graphics that you create in After Effects and import into Premiere... Do NOT have multiple lines. which is honestly really annoying... deleting just one line in a big list of credits, for example, requires a bunch of copy/pasting across text box fields.

    Also, dang, it really is convenient to be able to click on a (legacy) title style and have all the settings loaded instantly...

    An error occurred while saving the comment
    TaranVH commented  · 

    @andreas For archival purposes, it might be best for you to NOT just have the exported video file. Instead, separate it into layers - one video export will be A-roll, another will be B-roll, and another will be graphics. You'd want minimal compression. Personally, I'd use 10-bit cineform with alpha for this (though I think it does tend to make gradients look banded.)
    At the same time, export a multi-track audio or .ts file, with dialogue on its own track(s), sound effects on its own track, and music on its own track.
    Obviously, this would require more labor, but it makes your content 100% future-proof. Now, no matter what NLE you are using, no matter what year or version, you will easily be able to re-cut an old episode. Even if cineform is no longer supported by any NLE in the future, you will surely be able to transcode it with a program like handbrake or something.
    You can even build new episodes with this process in mind - always keeping all your music confined to specific audio tracks.
    Personally, we even keep ALL of our original assets, like B-roll shots, uncompressed. So if we ever need to use a shot again, it's easy for me to go back to that project, open the B-roll folder, find the shot, and use it in another video. But I doubt you have 2 petabytes of storage like we do...

    An error occurred while saving the comment
    TaranVH commented  · 

    @andreas But you didn't need those codecs and plugins when those projects were originally created. So why would you need them now?
    Every time you update an older project, I certainly hope you are still saving your older .prproj file. You never know what adobe might choose to remove.
    The absolute best solution for you will be to keep an older copy of Premiere, for use with those older projects... which is why it's so important that Adobe should keep them available... which they have not done: https://forums.adobe.com/thread/2413891
    So you better download the version(s) that you'll need, right NOW. And back it up somewhere.

    An error occurred while saving the comment
    TaranVH commented  · 

    It's also worth noting that Essential Graphics turns the timeline red, and is very slow to load and render.
    I'm currently rendering 4K on my top-of-the-line machine:
    Intel Core i7-6950X CPU @ 3.00GHz 3.00GHz
    64.0 GB RAM
    Titan X (Generation 9)
    And it's taking 3 seconds to render a single frame. https://i.imgur.com/JGajDZT.png

    Had I used the legacy titler instead, this would be done rendering by now.

    An error occurred while saving the comment
    TaranVH commented  · 

    "Text ***** control! "
    That's odd, it looks like uservoice censored the word " s I a n t ." I had no idea that was a naughty word. :P

    An error occurred while saving the comment
    TaranVH commented  · 

    I must agree. I'd absolutely hate to lost the legacy titler tool. Even as a very advanced user, I use it every day. It's simple. Effective. Quick and dirty.

    The legacy titler tool is basically a WYSIWYG (what you see is what you get) raster-based tool... like having a better version of MS Paint right inside of Premiere.
    Essential graphics is basically a vector-based tool. You can do a lot of cool stuff with it, but there is a lot to learn and keep track of, a lot of ways for it to go wrong, and even a lot that is still (AFAIK) missing:
    Gradients!
    Underline?
    Text ***** control!
    Small caps size control!
    Rounded rectangles with X and Y distortion and fillet size adjustments
    Multiple inner and outer strokes
    Title styles to instantly change font/color/stroke/etc
    The PEN TOOL!!
    The list goes on.

    The legacy titler tool is like an axe. The axe head might be a little loose, (it's still a bit buggy) but it gets the job done when you just need to hack off a few branches.

    Don't force your users to use a chainsaw, when they just want to use an axe.

    TaranVH supported this idea  · 
  5. 44 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  After Effects » General  ·  Flag idea as inappropriate…  ·  Admin →
    TaranVH supported this idea  · 
  6. 214 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    19 comments  ·  After Effects » Workflow & interoperability  ·  Flag idea as inappropriate…  ·  Admin →
    TaranVH supported this idea  · 
  7. 65 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    10 comments  ·  After Effects » Workflow & interoperability  ·  Flag idea as inappropriate…  ·  Admin →
    TaranVH supported this idea  · 
  8. 87 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  After Effects » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    TaranVH supported this idea  · 
  9. 181 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    46 comments  ·  After Effects » Performance  ·  Flag idea as inappropriate…  ·  Admin →
    TaranVH supported this idea  · 
  10. 619 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    65 comments  ·  Premiere Pro » Effects & Transitions  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    TaranVH commented  · 

    Yes, there are currently two 3rd-party methods for doing this.
    The easiest way is with Excalibur, but it can be slow, and it costs $75. Here's my review of it:
    https://www.youtube.com/watch?v=jQmkyM4CCy4

    A faster method is with my AutoHotKey preset() function, for which I've just finished a step-by-step tutorial that even a beginner can follow:
    https://www.youtube.com/watch?v=T3vG8U5RoFw
    This method is free, but if you've never used AHK before, it will take a few hours of scripting to set it up on your computer. Also, this solution is PC-only.

    For most people, I would recommend Excalibur.

    I still want this as a real feature in Premiere, though.

    An error occurred while saving the comment
    TaranVH commented  · 

    @Brecon
    You can have keyboard navigation in the effects panel.
    Open the keyboard shortcuts panel.
    Assign the keyboard shortcut "F1" to Window > Effects.
    Assign the keyboard shortcut "F2" to "Select Find Box"
    Hit "OK."
    Now, hit F1 and then F2. The Effects panel's find box is now highlighted. Now you can search for effects and presets by typing away to your heart's content!

    An error occurred while saving the comment
    TaranVH commented  · 

    Haha, don't forget, guys, you CAN have this feature if you use AutoHotKey. I use it every day. I'll make a tutorial video showing EXACTLY how to install it for super noobs. But in the meantime, here's the code:
    https://github.com/TaranVH/2nd-keyboard/blob/master/Almost_All_Premiere_Functions.ahk#L304

    ALTERNATIVELY, the Palette Gear DOES have this feature - but only for effects, not presets. It's pricey, though. https://palettegear.com/
    You can even add transitions with the Palette Gear. And delete transitions!

    An error occurred while saving the comment
    TaranVH commented  · 

    BTW, my scripts have improved, and the filenames are a bit different. Here's the latest and greatest preset() function:
    https://github.com/TaranVH/2nd-keyboard/blob/cd1f9f44790c12f924d2ff0ad556f104ea3c839a/Almost_All_Premiere_Functions.ahk#L299

    An error occurred while saving the comment
    TaranVH commented  · 

    @Matyáš Levíček
    lololol, you don't NEED to use a second keyboard to make it work. You can just assign it to an unused function key. like this:
    F4::preset("crop left preset")

    An error occurred while saving the comment
    TaranVH supported this idea  · 
    An error occurred while saving the comment
    TaranVH commented  · 

    Arrr, ye poor *******!
    One of these features already exists: It's called 'selection follows playhead.' It's in the Sequence menu. You can also assign a shortcut. I use "CTRL P"
    As for the other, there are two ways to do it:
    Using the Palette Gear. It's kinda expensive. But they've got it implemented at the SDK level.
    Don't have 100-200 bucks to spare?
    Use my AHK scripts. Get ready to learn some basic programing. The one you want is called preset()
    I use these scripts ever day. They're quite stable if set up correctly.
    https://github.com/TaranVH/2nd-keyboard/blob/93cfeaa7f6462b915421ffb60e8cf4807b3d79e0/All%20Premiere%20Functions.ahk#L122

  11. 201 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    22 comments  ·  Premiere Pro » Playback  ·  Flag idea as inappropriate…  ·  Admin →

    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.

    Cheers,
    Patrick

    An error occurred while saving the comment
    TaranVH commented  · 

    @Pierre Louis Beranek
    Those are some really interesting ideas that I had not considered. They could definitely help in some situations.
    But, they would not fix the problems that I pose in the explanatory video. In my example, the "where gaming begins.m4v" AMD video is in the source monitor. It has no effects on it at all. But it still has very high (slow) prefetch latency, because of the way it was encoded. The "downloading high sierra (mac).mp4" is even worse. Again, it had no effects, and was in the source monitor at 1/2 resolution.

    I don't really need to scrub through footage quickly to find stuff once it's already been placed onto the timeline. I already know where everything is on my timeline... I put it there!

    You might think that automatically lowering the quality to 1/4 or 1/8 or even 1/16 would help, but in my experience (all 8+ years of it) that only helps with all-I-frame video, like cineform, .r3d, and .braw. For H.264, I believe that a decoder still needs to load the entire frame BEFORE it can determine what it would look like at a lower resolution. Like, go look up "DCT zigzag pattern" and you'll see why. Each of those 8x8 blocks of pixels is a "macroblock." The decoder can't just SKIP 3/4 of the pixels. It needs to go through ALL of them or it'll get the values wrong.

    It is possible that only loading and displaying the luminance data would be faster than loading and displaying the luminance + chrominances, but I don't know enough about H.264, H.265, etc, to say for sure.

    An error occurred while saving the comment
    TaranVH commented  · 

    @Pierre Louis Beranek
    You clearly did not watch the accompanying video. I recommend that you watch the whole thing.
    The delay from prefetch latency can be enormous -- multiple seconds, in some cases.
    https://youtu.be/XeFezzmG22c?t=378
    In those cases, it is impossible to know if the frame you're looking at, is /actually/ the frame that you have selected. Especially with screen capture footage. Thus, the ghost playhead would show which frame IS being shown. Premiere already knows which frame it's showing... it just has no way of telling the user.

    An error occurred while saving the comment
    TaranVH commented  · 

    @Thomas Berglund
    I have not tried that. Interesting idea... will do..

    TaranVH shared this idea  · 
  12. 44 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  Premiere Pro » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    TaranVH commented  · 

    Premiere conforms to the Windows UI scaling. This is relatively new.
    Have you tried increasing it in the windows control panel "Display" section, under "scale and layout" ? I've attached a picture.
    Set it to 150% or something. Everything will get bigger, but slightly blurry, since it's a kinda lame bilinear upscale. However, when you restart, Premiere will use its own native scaling instead, so it'll no longer be blurry.

    TaranVH supported this idea  · 
  13. 118 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    21 comments  ·  Premiere Pro » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    TaranVH commented  · 

    @Tyrese Taylor
    are you using just regular trim, rather than RIPPLE trim, which does keep the clips snapped together?
    Try it - I believe it is on Q and W by default. Or you can use the ripple trim tool. It's yellow instead of red.

    An error occurred while saving the comment
    TaranVH commented  · 

    @Sami I snap to transitions occasionally. But I still totally want the OPTION to turn that functionality off. The 2-3 frame transitions sound AWFUL for the current snapping behaviour.

    An error occurred while saving the comment
    TaranVH commented  · 

    @Morten Bredal
    There is a way to turn snapping off. The default shortcut is "S."
    This feature request is about getting more options for what is and is not included in that snapping.

    TaranVH supported this idea  · 
  14. 124 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    20 comments  ·  Premiere Pro » Export  ·  Flag idea as inappropriate…  ·  Admin →
    TaranVH supported this idea  · 
  15. 50 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    30 comments  ·  Premiere Pro » Stability  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    TaranVH commented  · 

    @guy bashan
    TO AVOID THIS ERROR AND FULLY RENDER YOUR PROJECT,
    Don't render straight off your timeline. Create render previews first.
    First, click on your sequence, then go to Sequence > sequence settings.
    Make sure that your video previews Width and Height are the SAME as your Video Frame size horizontal and vertical values.
    Also, you may wish to use Preview File Format: GoPro Cineform (YUV 10-bit) rather than the default .mpeg.
    say OK.
    Now, put your In and Out points around your entire video, and select Sequence > render in to out.
    Now sit back and watch it pre-render. If you hit the error again, you can just dismiss it. The rendering will stop, but you'll still keep almost everything you rendered so far. SAVE your project, and then move your IN point much closer to where the render failed. Try render in to out again. If it still gives you that error, save and restart premiere.
    Keep doing this until the whole timeline has green render previews.
    Now, you can smart render directly to .mov if you render with "use sequence settings" and "use previews" checked ON. It'll happen in mere minutes. Then, you'll convert that .mov file to whatever you want, using media encoder.
    Alternatively, you can just turn on "use previews" and render directly to H.264 .mp4 or whatever else you like.
    Keep in mind that render timeline previews can take up a lot of storage space. They live in a folder named "\Adobe Premiere Pro Video Previews"

    An error occurred while saving the comment
    TaranVH commented  · 

    @Amédée
    I know this is no help to you, but I actually haven't encountered this bug in over a year. so I think they've been making progress in fixing it.

    TaranVH shared this idea  · 
  16. 143 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Premiere Pro » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    TaranVH shared this idea  · 
  17. 346 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    33 comments  ·  Premiere Pro » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    TaranVH supported this idea  · 
  18. 109 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    17 comments  ·  Premiere Pro » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    TaranVH supported this idea  · 
    An error occurred while saving the comment
  19. 28 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Premiere Pro » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    TaranVH commented  · 

    This actually seems to have been fully put in Premiere. See attached screenshot.

    An error occurred while saving the comment
    TaranVH commented  · 

    I agree with this. I have some custom macros, but they're a big PITA to set up, and don't always work. Yes, it's easy to add yellow, red, and green markers, but I'd like dedicated shortcuts for ALL the colors.
    Don't even try to figure out my spaghetti code...
    https://github.com/TaranVH/2nd-keyboard/blob/93cfeaa7f6462b915421ffb60e8cf4807b3d79e0/ALL%20MULTIPLE%20KEYBOARD%20ASSIGNMENTS.ahk#L122

    TaranVH supported this idea  · 
  20. 19 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Premiere Pro » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    TaranVH supported this idea  · 
← Previous 1 3 4 5 9 10

Feedback and Knowledge Base