Did you try " Preferences > Audio Hardware => set Default Input to None" as suggested above? ... View more

Could you provide small sample of your drone footage, so we try to reproduce the issue?  Or at the least show us screen capture of how that "flicker and roll" looks like, along with file properties (preferably in the form of MediaInfo text report) . ... View more

Here it is, the tool and explanation how it works (so you can do it manually): http://joshcluderay.com/downgrade-premiere-project-converter/ I did manual conversion, by setting version number to 38  ... View more

Well, yes failing GPU is quite likely, though I'd would not exclude some weird Adobes bug. Maybe try to install 2021 version, and check if the gitch is still there. I was able to convert you project to 2020 version and export it without any errors or glitches (on GTX1060) ... View more

Ran Windows Memory Diagnostic, everything seemed to be fine. Still it all sounds like your system have hardware stability issue. Render/export loads the system way more than simple  windows memory test. Points of failure in order of probability  : RAM, GPU, weak/degraded Power supply, SSD/HDD. ... View more

try these simple steps for starter: 1) Manually clear media cache - close Adobe PP/AE/ME, go to cache location and clean/delete folders: Media Cache, Media Cache Files, PTX, Peak Files 2) Turn off hardware accelerated Decoding in Preferences > Media...  (do app restart) 3) try Preferences > Audio Hardware > Default Input => select "No Input" 4) Reset workspace: Window > Workspaces > Reset to saved layout (or just switch to different one) ... View more

Does it lag in this basic test: New project > New sequence from clip..  > (no effects) + full resolution ? ... View more

Did you try different export settings, like using Prores? In some cases h264 VBR does not work well, and CBR fixes it.. ... View more

If you don't mind sharing a small chunk of the source video in question, I can look into it. Should contain both scene types (w/motion - wo/ motion). Don't upload to youtube thou, use filesharing services instead (dropbox, onedrive, googledrive, etc). In the previous comment I meant you to do some obvious visual (=on the video) 'marks' during recording, so automatic scene detection in PPro may actually work. It's just a suggestion, dunno if it will work. ... View more

, and updating my display adapters ,but   Does it mean you downloaded them directly from Nvidia/Intel websites and not via Windows driver update feature? Build-in feature usually does not help here.. ... View more

@Lioba22745708soxt  Do you work with a 3rd party footage or you do the recording too? If the latter, to make PPro build-in feature work consider helping it: make some all-frame change at beginning-&-end of each painting session. Like closing camera lens (or alt-tabbing the app if you do a screencapture). ... View more

As a quick fix try CBR encoding mode ... View more

It's this part  "-vf mpdecimate=hi=64*30:lo=64*15:frac=0.1"  that do the (near)duplicates removal. As I understand it, the logic behind is next: A frame is for dropping if no 8*8px blocks differ by more than a threshold of hi, and if no more than frac of blocks have it between hi and lo ​(defaults are: hi=768, lo=320, frac=0.33). Try to increase thresholds, like "-vf mpdecimate=hi=2300:lo=1100:frac=0.3" To make testing faster you can add downscale filter, eg if your footage is 1920*1080, to make it half-sized just add:  -s 960x540. Another way is to cut a piece of footage with just a few typical "no movement scenes" and use it for initial debug. Some tools for lossless cutting: Avidemux, LosslessCut, Shutter Encoder. ... View more

 Try Preferences > Audio Hardware > Default Input => select "No Input" ... View more

@default4dmdnnfrjcte  I can tell you that for 4K footage the speed of 2-3fps at the "analyzing" stage is rather typical. My current Ryzen 7 1700 shows nearly the same ~2fps. The thing is that this task is single threaded, so the only way to speed it up is to use latest generation CPU, and even then you'll get maybe 4fps at best, lol. Regarding "decoding options" and "restart required" - it's not related to the stabilizer speed issue at all. That hint about restart just tell you that change to that settings won't be active until you restart the program.   @Ann Bens I think you put it in reverse. Actually CPU is used during 1st stage (analysis) and GPU is during 2nd (stabilizing).   ... View more

It depends on what do you mean by 'low quality' and what do you expect to get after restoration.. And Premiere is not really intended for such type of work, it's great tool for edit/postproduction of properly captured footage, but not for restoration of bad from the start or damaged videos. Some 3rd party tool can do miracles at times though, but result is not warranted even there. Below is an example of restoration attempt for badly captured 320*240 video (using avisynth + mvtools +  ...) ... View more

Try to reset workspace: Window > Workspaces > Reset to saved layout (or just switch to other and back ) ... View more

It sounds like you have some heavy, non-gpu-accelerated effect on top of the timeline, so realtime render is just not possible. Does it freezing if you do Global FX Mute? If  the timeline render bar is red, I suggest to check if you can optimize effects order according to this rules: Not all effects are GPU accelerated. And order of effects matters. To make render/export faster follow this:    a) Ideally don't use CPU-effects at all (keep a timeline "yellow" = maximum speed mode)    b) If you can't avoid using CPU-effects - don't mix up CPU- and GPU- effects in the same adjustment layer. Doing so will switch rendering into "software only" mode (=very slow). Instead separate GPU and CPU effects in two different layers. Put "GPU-layer" on top of a "CPU-layer". This way GPU-acceleration will actually work    c) In case of applying effects directly to a clip without adjustment layers: organize effects in a way that all GPU-effects are applied after CPU-effects    d) and if by all means you have to use some CPU-only effect on top of accelerated ones - then split the job on 2 parts: first you export the timeline with accelerated effects, then re-import and add that necessary CPU-effect(s). This way it'll be much faster than CPU-only render in one pass ... View more

Having little details about the project and settings, I can only suggest these general steps: 1) Manually clear media cache - close Adobe PP/AE/ME, go to cache location and clean/delete folders: Media Cache, Media Cache Files, PTX, Peak Files. 2) Turn off hardware accelerated Decoding in Preferences > Media...  (Remember to do app restart) 3) Your timeline render bar is red. Which means that all effects are runnig on the CPU (and may even be bottlenecked by a single thread). This may happen because not all effects are GPU accelerated. And order of effects matters. To make render/export faster, follow these rules:    a) Ideally don't use CPU-effects at all (keep a timeline "yellow" = maximum speed mode)    b) If you can't avoid using CPU-effects - don't mix up CPU- and GPU- effects in the same adjustment layer. Doing so will switch rendering into "software only" mode (=very slow). Instead separate GPU and CPU effects in two different layers. Put "GPU-layer" on top of a "CPU-layer". This way GPU-acceleration will actually work    c) In case of applying effects directly to a clip without adjustment layers: organize effects in a way that all GPU-effects are applied after CPU-effects    d) and if by all means you have to use some CPU-only effect on top of accelerated ones - then split the job on 2 parts: first you export the timeline with accelerated effects, then re-import and add that necessary CPU-effect(s). This way it'll be much faster than CPU-only render in one pass ... View more

There are some 3rd party tools that is able to remove frame duplicates. While their original intent was not for your case, it may work. Below is a sample of a batch-script configured for removing non-exactly dublicate (but very close to) frames: 1) you put it along with the ffmpeg.exe in some folder 2) create a shortcut to the bat-file on a desktop 3) drop your file on the shortcut 4) after encoding is finished check the folder 'NoStaticScenes' Later in Premiere you have to change it's FPS to some std value (via interpret footage). This method should work, assuming you don't use audio track from the video in question.     @echo off TITLE %~nx0 SETLOCAL ENABLEEXTENSIONS set t0=%TIME%, %DATE% for %%F in (%*) do call :main %%F goto finalmessage :main SetLocal echo ----------------------------------------------------------------------------------- echo. Processing file: %~f1 echo. set "newdir=NoStaticScenes" if not exist "%~dp1\%newdir%" mkdir "%~dp1\%newdir%" rem [ cmf: -1=auto, 1=bt709, 6=bt601, 9=bt2020 ] :: set "cmf=-1" :: set "bsf=-bsf:v h264_metadata=colour_primaries=%cmf%:transfer_characteristics=%cmf%:matrix_coefficients=%cmf%" ffmpeg.exe -y -i "%~f1" -vf mpdecimate=hi=64*30:lo=64*15:frac=0.1 -vsync vfr -pix_fmt yuv420p -c:v libx264 -crf 18 -preset veryfast -x264-params ref=1:bframes=0:keyint=15:min-keyint=1:qcomp=0.7:no-dct-decimate=1 -c:a copy -map 0:v:0 -map 0:a? "%~dp1\%newdir%\%~nx1 [nostats].mov" EndLocal goto :eof :finalmessage powershell write-host -fore cyan ======================== Processing is FINISHED ========================= echo ---------------------------- echo Batch processing start time: %t0% echo Batch processing end time: %TIME%, %DATE% echo ---------------------------- pause     ... View more

Can only suggest to make a color corrected version of  the top clip beforehand and so no need to fiddle with the second adjustment layer later.. ... View more

Have you already checked against the infamous *audio input* thing? I meam this:  Preferences > Audio Hardware > Default Input => select "No Input" ... View more

That 'combing' looks like interlacing artefacts ... @Amir2269673222x1 What are your sequence setings? and video file propeties? ... View more

Depending on the goal, usual steps are: - for slow-mo you apply "speed 40%" to the clip right in the project panel (before placing it on the timeline!) - for normal playback you place the clip on the timeline first, and then [if needed] change time interpolation method (using context menu for clip on the timeline). It seems like you tried to change "speed" after putting the clip on the timeline. That could explain dropped frames.. ... View more

Is it the same for all sources? What kind of source footage you are working with? Resolution, codec, HDR/SDR, etc. You can use free Mediainfo tool  to get detailed info and let us know (but set the View to Text/Tree) . ... View more