Ryan Fritzsche

My feedback

  1. 51 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    I'm having this issue arbitrarily. It started way after I was into the edit on two different projects, with different sorts of media, working in 1080p 23.976. One project had 4k .mxf source, the other is all 1080 ProRes, both have PCM audio, both include some use of multicam sequences. If I disable waveform display, then I can see the wireframe when dragging. Re-enable waveforms, can't see it anymore. Has come up in short sequences and long ones, doesn't seem to be particularly connected to either. Issue has persisted in CC 2019, through several updates. Never had this issue in the past (ie: CC 2018 or earlier, going back years), even on large projects with far more disparate and complicated mixes of media types than I've had on these two, relatively tame, projects.

    Ryan Fritzsche supported this idea  · 
  2. 10 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Premiere Pro » Playback  ·  Flag idea as inappropriate…  ·  Admin →
    Ryan Fritzsche supported this idea  · 
  3. 12 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Premiere Pro » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    Ryan Fritzsche supported this idea  · 
    An error occurred while saving the comment
    Ryan Fritzsche commented  · 

    YES YES YES YES YES YES

  4. 8 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Premiere Pro » Playback  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Ryan Fritzsche commented  · 

    Absolutely, this would be very helpful! Please add.

    Ryan Fritzsche supported this idea  · 
  5. 6 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Premiere Pro » General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Ryan Fritzsche commented  · 

    Yeah, I realize it’s not supported but.... this kinda kneecaps the proxy workflow. I mean, this is a major defect. I sure hope it’s addressed soon.

    Ryan Fritzsche shared this idea  · 
  6. 57 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    42 comments  ·  Premiere Pro » General  ·  Flag idea as inappropriate…  ·  Admin →
    Ryan Fritzsche supported this idea  · 
    An error occurred while saving the comment
    Ryan Fritzsche commented  · 

    encountering this problem too. Just took time to render an entire sequence, 1080p 23.98 fps ProRes HQ Max Render Quality and Max Bit Depth both checked. Running v13.1.2 (Build 9) on Mac 6,1 8-core D700 GPUs, OS 10.13.6. certain clips kept un-rendering for no reason while the project was open. Closed, quit premiere and re-opened immediately. virtually ALL render files for the entire sequence gone. huh???

  7. 123 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    This is a massive bug and surely it can't be that hard to fix??!

    Ryan Fritzsche supported this idea  · 
  8. 6 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Premiere Pro » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Ryan Fritzsche commented  · 

    yes!

  9. 5 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Premiere Pro » Export  ·  Flag idea as inappropriate…  ·  Admin →
    Ryan Fritzsche shared this idea  · 
  10. 15 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Premiere Pro » Audio  ·  Flag idea as inappropriate…  ·  Admin →
    Ryan Fritzsche supported this idea  · 
  11. 30 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    11 comments  ·  Premiere Pro » Playback  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Ryan Fritzsche commented  · 

    +1

  12. 200 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Under Review  ·  40 comments  ·  Premiere Pro » Audio  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Ryan Fritzsche commented  · 

    1000% please add this. It's such a huge oversight that I can't at the very least copy-paste track effects.

  13. 7 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    I've switched to i-mpeg instead of Quicktime (QT > DNxHD was actually having the same issue as the ProRes Proxy) and everything is now working fine. Rendering long sequences without failures. So it's definitely a quicktime or ProRes issue. It's still a big problem, b/c being able to render into ProRes in preparation for expedited export of ProRes (or DNxHD for that matter) masters is a key issue.

    An error occurred while saving the comment
    Ryan Fritzsche commented  · 

    I have a large documentary project which I was working on in CC2017 without issue. After moving to CC 2018, renders seem to seize up the program after 5 or 10 minutes, virtually without fail. It means that rendering any long timeline is virtually impossible. There is no freezing or issues exporting these sequences thru media encoder. I have tested in various projects with a wide variety of timelines, running off different drives, writing to a high-speed RAID system, all incorporating different footage, so I know it's not corrupt media, and the fact that Media Encoder handles it fine suggest to me that it's not a hardware issue. Mac Pro 6,1, dual D700, 6GB VRAM, 64GB RAM. Same experience as above - seems to keep rendering but the project loses track of the render files when I have to force-quit. I have to assume this is a result of Adobe having to rewrite the code for ProRes after eliminating legacy 32-bit Quicktime support in CC2018, but it's a huge problem and DESPERATELY needs to be fixed ASAP. My render codec is always ProRes Proxy, but as noted here, I will attempt with DNxHD or some other codecs and see if that's a sufficient workaround. My source footage is a mix of Sony A7S .mp4s, various iPhone, Canon 60D, Canon 5D, and other misc.

    Ryan Fritzsche supported this idea  · 
  14. 11 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Premiere Pro » Import  ·  Flag idea as inappropriate…  ·  Admin →
    Ryan Fritzsche supported this idea  · 
  15. 95 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    105 comments  ·  Premiere Pro » Import  ·  Flag idea as inappropriate…  ·  Admin →
    Ryan Fritzsche supported this idea  · 

Feedback and Knowledge Base