paul wedel

My feedback

  1. 30 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 » Performance  ·  Flag idea as inappropriate…  ·  Admin →

    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
    paul wedel commented  · 

    Yeah everything running much better for me now that I've reverted to 12.1.2 👌Likely won't go back to 2019 ever. I'll wait til their yearly release of 2020 to see if maybe they improve things (but they won't amirite)

    An error occurred while saving the comment
    paul wedel commented  · 

    Literally the worst. I've just advised my whole firm to roll back to 2018. 13.1.4 is such the worst. The worst update in the History of Software Updates. Worse than iTunes 11. And that's saying something. Does anyone at adobe even read these? Come at me

    paul wedel supported this idea  · 
  2. 2 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

    1 comment  ·  Premiere Pro » Essential Graphics  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    paul wedel shared this idea  · 
  3. 12 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  ·  Premiere Pro » Export  ·  Flag idea as inappropriate…  ·  Admin →

    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
    paul wedel commented  · 

    And yes, it seems as though the metadata is the only label. In PP, when Show Audio Names is enabled, you can see the filename followed by A1, A2, A3 etc, whereas in Resolve, you can see the metadata name MixL, MixR, Boom1, Boom2 etc etc, which is much clearer. Another feature for some decades-in-the-future version of PP that already exists in other software;)

    After Merge clips in PP, all the audio channels read as A1, which is the first indicator that something is amiss. Then when you look closely, you can see the waveforms are also all identical for each channel. Such a terrible bug that will seemingly never be addressed by Adobe... In fact, to test my exports to sound, I now export an XML from PP and import it into Resolve to check the labelling of my audio tracks.

    An error occurred while saving the comment
    paul wedel commented  · 

    Hi again Antoine // my exports to the sound department are XML, OMF and AAF, and even with copy entire audio files enabled, the metadata for the audio is gone.

    Instead of the Merged clip feature, I just use timelines now and have all my sync'd takes in a row, rather than using bins with clips in the source window, which is a weird way to edit, but it saves hours and hours of pain down the line.

    No one at Adobe seems to care about this crucial aspect of a "professional" workflow. Seriously going to jump to Resolve now with v16, but have to keep subscribing to Adobe for all my post-house's work. So I guess they have my money already, what do they care? ;)

    An error occurred while saving the comment
    paul wedel commented  · 

    Hi Antoine // when using Merge Clips in Premiere Pro (including the "latest and greatest" CC2019), the resulting outputs to the Sound Dept. are free from all sound-recorder metadata.

    This makes Merge Clips a worse-than-useless functionality, as all sound departments require the metadata included from the field audio recorder to sort out their mixes. Oftentimes, wavs from the sound-recorder are supplied with multiple channels, for example, a wav with 8channels labelled MixL, MixR, Lapel1, Lapel2, Lapel3, Lapel4, Boom1, Boom2 (which one can see in Davinci Resolve, but not PP). After Merge Clips, all 8 channels read as MixL, and indeed, contain only the audio from MixL, making the outputs to the sound department unusable.

    I solved this problem by reconnecting all the sound clips, for a feature film, by hand; match-framing from the cut to the source window and replacing the Merge Clip audio in the timeline. This process took days, for which I was not paid as it was "my fault" for using Merge Clips in the first place.

    Merge Clips is a function I can never use, as my workflow usually includes handover to Sound departments and indeed, I tell all editors to never use it.

    An error occurred while saving the comment
    paul wedel commented  · 

    https://helpx.adobe.com/nz/premiere-pro/using/synchronizing-audio-video-merge-clips.html

    Nothing here about metadata loss. Would have been good to know 11 months ago....

    paul wedel shared this idea  · 
  4. 34 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

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    paul wedel supported this idea  · 
  5. 13 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 » Playback  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    paul wedel supported this idea  · 
  6. 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

    0 comments  ·  Premiere Pro » GPUs  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    paul wedel supported this idea  · 
  7. 6 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

    1 comment  ·  Premiere Pro » GPUs  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    1 comment  ·  Premiere Pro » Performance  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    paul wedel supported this idea  · 
  9. 11 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 » Performance  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    Seriously troubling update. 13.1.4 is likely the worst update in the history of PP...

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

    4 comments  ·  Premiere Pro » Performance  ·  Flag idea as inappropriate…  ·  Admin →

    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
    paul wedel commented  · 

    Literally the worst update in the History of Software Updates. This is even worse than iTunes 11... Long live 12.1.2!

    paul wedel supported this idea  · 
  11. 4 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 » Performance  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    paul wedel shared this idea  · 
  12. 2 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

    2 comments  ·  Premiere Pro » Projects  ·  Flag idea as inappropriate…  ·  Admin →

    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
    paul wedel commented  · 

    Hello?? Something that's been broken since 13.0 is that everytime CC2019 crashes (which is A LOT), PP no longer opens until you rebuild your Documents/Adobe/Premiere Pro folder. Had two long live chat sessions with your agents (both very friendly, both very helpful by the way!) on version 13.0.1 and it's still broken in 13.1.4...................... actually fix this.

    But no one reads this anyways so I can say whatever I want here hahhah ******* hahahah

    An error occurred while saving the comment
    paul wedel commented  · 

    Yes 2019 is The Worst Update Ever. I've found that if you have a 2019 project that hangs on open, you just need to rename your documents/adobe/premierepro folder to "premierepro.old" . PP will create a new "premierepro" folder upon opening.

    All your favourites, keyboard shortcuts, workspaces will be gone, but at least your project will open.

    paul wedel shared this idea  · 
  13. 7 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 » Effects & Transitions  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    paul wedel shared this idea  · 
  14. 25 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

    1 comment  ·  Premiere Pro » Effects & Transitions  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    paul wedel supported this idea  · 
  15. 43 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

    23 comments  ·  Premiere Pro » Effects & Transitions  ·  Flag idea as inappropriate…  ·  Admin →

    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
    paul wedel commented  · 

    Yeahhhhhh Morph Cut doesn't want to render in CC2019 anymore for me. It crashes my PP build everytime I try to render. And because 2019 is actually terrible, I'm forced to also rebuild my Documents/Adobe/PremierePro folder everytime there's any crash in CC2019.

    I've been compelled to take my clips I want morphed and copy them into a fresh sequence, export an XML, open CC2018, apply the morph, export a Quicktime from CC2018 and import that into CC2019.

    Coole workflow, thanks Adobe, my time is not precious at all.

    paul wedel supported this idea  · 
  16. 17 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 » Stability  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    paul wedel supported this idea  · 
  17. 2 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

    2 comments  ·  Premiere Pro » Editing  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    paul wedel shared this idea  · 
  18. 3 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 » Playback  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    paul wedel supported this idea  · 
  19. 1 vote

    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

    2 comments  ·  Premiere Pro » Editing  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    paul wedel shared this idea  · 
  20. 43 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

    26 comments  ·  Premiere Pro » Stability  ·  Flag idea as inappropriate…  ·  Admin →

    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
    paul wedel commented  · 

    It's actually not working at all for me now in 13.1.2 Sometimes it works, sometimes not. Forced to restart PP, then it worked. But the functionality is intermittent.

    Honestly this is one of the few projects that I've cut in 13. I'm pretty stalwart on 12.1.2, as that seems to be the most stable version of Premiere Pro, but someone at my office started this project in 2019 13.1.2 so I'm stuck editing in this buggy buggy version.

    paul wedel supported this idea  · 

Feedback and Knowledge Base