Skip to content

TaranVH

My feedback

147 results found

  1. 135 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    TaranVH commented  · 

    I think the easiest way for Adobe to "fix" this would be to add two more shortcuts, and name them thusly:
    Ripple Trim Next Edit To Playhead (repeat to trim 1 more frame)
    Ripple Trim Previous Edit To Playhead (repeat to trim 1 more frame)

    So, editors who are used to working the old way, could assign "Ripple Trim Previous Edit To Playhead (repeat to trim 1 more frame)" to Q, and "Ripple Trim Next Edit To Playhead" to W.
    Also, editors could try putting "Ripple Trim Next Edit To Playhead (repeat to trim 1 more frame)" on W and see if it's just as useful as the complementary shortcut is on Q.

    Anyway. So long as experienced editors know about it, this will make everyone happy. No need to add another weird setting. All we need are two extra shortcuts to use. (or just the one for Q, but now I'm curious to know how useful the same functionality would be on W.)

    Adobe, I hope this makes sense! Okay, bye! Sorry for talking about the console! (They don't like that)

    An error occurred while saving the comment
    TaranVH commented  · 

    Hello, all.
    I also greatly miss this "feature." Even though it only ever worked with Q. That is, hitting W multiple times does not and has never trimmed off one frame at a time from the RIGHT side of a clip. So I can see that maybe Adobe wanted some consistency up in here.

    Anyway, I wanted to be able to tell you guys that I found a fix for this in the console debug database, but I didn't.
    If you don't know, you get to it by hitting CTRL F12, clicking the triple line "hamburger" on the panel that appears, and selecting "debug database view."

    WARNING: THIS IS DANGEROUS. DO NOT FIDDLE AROUND IN HERE OR CHANGE ANY DEFAULTS UNLESS YOU REALLY KNOW WHAT YOU'RE DOING. IF PREMIERE CRASHES HORRIBLY, IT'S YOUR OWN FAULT. DON'T CALL ADOBE ANDD WHINE ABOUT IT. HERE BE DRAGONS.

    Anyway, the only setting I've ever changed in here was "FE.AllowMultipleOpenProjects" to false. Though, these days, I leave it at "true," as I actually prefer it now.

    I was hoping that perhaps this behaviour change would also have been added to the console.
    I took screenshots of the entire console database in Premiere 2021, and also of Premiere 2022. Then I stitched them together in photoshop, and sent the whole thing through a free online optical character recognition program. Now I have the plain text of both. Putting them into notepad++ and running the "compare" plugin, now I can see what items were added, deleted, or had their default values changed!

    And so can you! Here you go!
    https://pastebin.com/xEqkWyp1
    https://pastebin.com/uKr6YrrG

    "Use AdobeCleanUX in V7" is a new item, for example. I tried changing its value from TRUE to FALSE, but the ripple trim behaviour was unaffected. Maybe you'd have to restart premiere before it'll actaully take effect. I have no idea.
    I tried changing several other commands, but each time, the ripple behaviour remained unchanged. It is POSSIBLE that it's in here, but might even need multiple lines to be changed... but it's just not worth the risk.

    I've put all of mine back at the default values. Someone else may wish to continue my "research," which is why I uploaded the lists. Good luck! Be super careful!

    TaranVH supported this idea  · 
  2. 95 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    TaranVH supported this idea  · 
  3. 67 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    TaranVH supported this idea  · 
  4. 700 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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

  5. 70 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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  · 
  6. 131 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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  · 
  7. 205 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    TaranVH supported this idea  · 
  8. 56 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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  · 
  9. 165 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    TaranVH shared this idea  · 
  10. 437 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    TaranVH supported this idea  · 
  11. 119 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    TaranVH supported this idea  · 
    An error occurred while saving the comment
  12. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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  · 
  13. 20 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    TaranVH supported this idea  · 
  14. 84 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    TaranVH supported this idea  · 
    An error occurred while saving the comment
    TaranVH commented  · 
  15. 52 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    TaranVH commented  · 

    It's worth noting that this only happens for me if I have my click visualization script running. I figured that out after I posted this feature request.
    https://github.com/TaranVH/2nd-keyboard/blob/master/Taran's_Windows_Mods/Both_Accelerated_Scrolling_1.3_AND_Cursor_click_visualizer-100UI.ahk
    If it is disabled, I do NOT get this behavior.
    This .ahk script is available on github, but I suspect that for the other people who have voted on this, it is being caused by something else. Maybe different UI settings, or Windows Pointer Speed, or mouse DPI.
    Can someone else who is experiencing this issue, please confirm that you are NOT running any .ahk scripts?

    TaranVH shared this idea  · 
  16. 100 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    TaranVH commented  · 

    @roger averhahl
    I noticed literally just today that you can save bin view presets. This might help you, try it out!

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

    Ah, yes... I know what you mean.
    My current workaround is to always save a backup workspace (or two) whenever I create a workspace I am really happy with.
    https://i.imgur.com/FMsVXm6.png
    Odds are, at least one of these will always function properly!
    Also, assign a shortcut to the command "reset to saved workspace." This has saved my bacon many times!

  17. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    TaranVH supported this idea  · 
    An error occurred while saving the comment
    TaranVH commented  · 

    I don't know for sure, but it's possible that Finder does something like my "I-frame-first" fast scrubbing.
    Item 162 on my spreadsheet:
    https://docs.google.com/spreadsheets/d/1dVJb7kI_ZETLavrplfARgn9gL8HUpvkq6A0jCPxqA3w/edit#gid=1133868629

  18. 430 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    TaranVH commented  · 

    I don't think Adobe should listen more to "influencers" than anyone else. while I do have a reputation for good ideas, the idea itself is what is valuable, not the person suggesting it.

    An error occurred while saving the comment
    TaranVH commented  · 

    Okay, people are telling me they're COLOR PICKERS, not "eye droppers." Yeah. That's probably a better name for them.

    TaranVH shared this idea  · 
  19. 15 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 » Audio  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    TaranVH supported this idea  · 
  20. 470 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    TaranVH commented  · 

    I STRONGLY suggest that you have to click on the wrench, then enable "layer dragging mode," before this behavior becomes available. Then, you can drag tracks around with left click+ drag, and turn it back off when you're done.

    If this feature cannot be turned off, AND it uses left click + drag, that's far too EASY to accidentally set off. Everyone's going to have to be super careful to not move the cursor at all when they're just trying to click to lock tracks or solo or make them invisible or whatever. And then Adobe is gonna get a lot of angry people complaining on the forums that their tracks keep getting out of order.

    By making it a toggle-able setting, everyone's needs are satisfied.

    An error occurred while saving the comment
    TaranVH commented  · 
← Previous 1 3 4 5 6 7 8

Feedback and Knowledge Base