paul wedel

My feedback

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

    0 comments  ·  Premiere Pro » Performance  ·  Flag idea as inappropriate…  ·  Admin →
    paul wedel shared this idea  · 
  2. 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

    0 comments  ·  Premiere Pro » Color/Lumetri  ·  Flag idea as inappropriate…  ·  Admin →
    paul wedel shared this idea  · 
  3. 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

    80 comments  ·  Premiere Pro » Playback  ·  Flag idea as inappropriate…  ·  Admin →
    paul wedel supported this idea  · 
  4. 10 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

    5 comments  ·  Premiere Pro » Playback  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    paul wedel commented  · 

    Same problem here, but not even running multicam. Running some 4k R3D footage in an HD timeline. Press spacebar to stop, playback doesn't stop for a good 1-2 seconds. OSX Catalina, CC2020 14.1.0

    paul wedel supported this idea  · 
  5. 9 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 » Performance  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    paul wedel commented  · 

    Yes this is still an issue in CC2020, latest version 14.0.4 // I have to Command-S before double-clicking R3D files in my bin. Infuriating!

    paul wedel supported this idea  · 
  6. 23 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 » Audio  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    paul wedel commented  · 

    Hi there. I posted this in 2018 and now it's 2020 and this still remains a massive headache for us folks who do audio post within Premiere. PLEASE please please add undo functionality to audio track mixer fx changes!!

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

    0 comments  ·  Premiere Pro » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    paul wedel shared this idea  · 
  8. 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

    5 comments  ·  Premiere Pro » Effects & Transitions  ·  Flag idea as inappropriate…  ·  Admin →
    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

    7 comments  ·  Premiere Pro » Color/Lumetri  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    paul wedel commented  · 

    Yeah I do all my offline in Premiere, all my online in Resolve. Can't trust lumetri outputs at all...

    paul wedel supported this idea  · 
  10. 35 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  ·  24 comments  ·  Premiere Pro » Audio  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    paul wedel commented  · 

    Still happening in 13.1.5 // I have Multiband Compressors applied to three audio fx slots. And on playback it's digital pop nightmare. Even after I "Render Audio" the problem remains. There are also digital pops when a clip ends and then pops again when a new clip begins. I've also added a 2frame audio fade transition to all my audio clips, but the digital popping remains. I basically have to do a ProRes runout to listen to my mix...

    PP 13.1.5
    OS Mojave
    iMac (Retina 5K, 27-inch, 2019)
    3.6 GHz Intel Core i9
    64 GB 2667 MHz DDR4
    Radeon Pro Vega 48 8 GB

    Probably shouldn't be happening with this grunty a machine...

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

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

    Still not fixed in 13.1.5 ///

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

    Yep just updated to 13.0.2 to try it out for the first time and no warps on Nests. Workaround is to go into nest, change sequence size, then warp. But after being told for years that you must nest to Warp Stabilize, this is a particularly ironic backwards step......

  12. 29 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 » Color/Lumetri  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    paul wedel commented  · 

    Colour shift on export in 13.1.5 is indeed 100% unfixed on an iMac Pro running Mojave. Try again adoob. And enjoy my money in the meantime, isn’t it great?

    An error occurred while saving the comment
    paul wedel commented  · 

    We encounter this daily as well. Seems to be an OSX / Premiere problem. For example, when viewing the exported clip in Quicktime or on Vimeo in Chrome, Safari, and Opera, the colors are way off. When viewing the clip on VLC or the Vimeo app on a phone, the colors are fine. Don't know if this is Premiere talking to OSX or what exactly. Watching clips rendered from Resolve doesn't seem to have this issue.

    We've dealt with the problem by adding an adjustment layer with a Lumetri fx and adding +7 to contrast and +12 to saturation. Then it's close-ish to what it looks like in Premiere, but watching in VLC or Vimeo app makes the over-saturation fix very apparent.

    Basically adding tons of guesswork to the last stage of post :/

    paul wedel supported this idea  · 
  13. 5 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 » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    paul wedel commented  · 

    Pretty much just rubbish playback in general in CCPP // Davinci demolishes PP in the playback dept.

    All h264 encoded files play back choppy forwards and not at all in reverse in PP. Switch over to Resolve, the same files, the same computer, playback is 24fps smooth forwards and backwards.

    Catch up adobe.

    paul wedel supported this idea  · 
  14. 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 →
    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  · 
  15. 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 →
    paul wedel shared this idea  · 
  16. 10 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 » Export  ·  Flag idea as inappropriate…  ·  Admin →
    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  · 
  17. 32 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

    11 comments  ·  Premiere Pro » Playback  ·  Flag idea as inappropriate…  ·  Admin →
    paul wedel supported this idea  · 
  18. 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

    4 comments  ·  Premiere Pro » Playback  ·  Flag idea as inappropriate…  ·  Admin →
    paul wedel supported this idea  · 
  19. 18 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 →
    paul wedel supported this idea  · 
  20. 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 →
    paul wedel supported this idea  · 

Feedback and Knowledge Base