You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm actually not quite sure if OVD was built for compatibility with Premiere but I'd like to know if this is a common issue and if it possibly has any solutions.
Whenever I download (video), or (video + audio) from the downloader, Adobe doesn't appear to recognize the video segment, and the error message it always gives me goes as follows: Unable to import video (video name) File uses unsupported compression type "vp09".
Reproducing this behavior:
Use the downloader for anything video-related
Find the video in the media browser
When opening the folder of its location, an error message will appear in the bottom left of the screen, stating: Unable to import video (video name) File uses unsupported compression type "vp09".
Video will be unable to be dragged into the timeline
Preview of the video in the media browser won't render the video's thumbnail:
Audio seems to be unaffected by this issue in general:
I'd like to receive some feedback to what is hopefully an easy fix.
The text was updated successfully, but these errors were encountered:
Premiere doesn't support vp09, no matter what downloader you use. You have to download video using avc codec or use some not Adobe encoder like ShutterEncoder to convert your vp09 video to other codec which Premiere can read.
I'm actually not quite sure if OVD was built for compatibility with Premiere but I'd like to know if this is a common issue and if it possibly has any solutions.
Whenever I download (video), or (video + audio) from the downloader, Adobe doesn't appear to recognize the video segment, and the error message it always gives me goes as follows: Unable to import video (video name) File uses unsupported compression type "vp09".
Reproducing this behavior:
Preview of the video in the media browser won't render the video's thumbnail:
Audio seems to be unaffected by this issue in general:
I'd like to receive some feedback to what is hopefully an easy fix.
The text was updated successfully, but these errors were encountered: