You can try external proxy generator, like ffmpeg. Assuming your OS is Windows, I've uploaded ready to use solution. Instructions inside, it's just as simple as drag-and-drop. Output is .mp4, just in case Premiere refuse to import it as proxy, so you can workaround it by replacing files manually. But you can edit script to get .mov if needed. https://1drv.ms/u/s!Andr88T403Spe4Olgh1kEKt7gl8?e=m8m4pp       ... View more

At least you know now that it's not a some unknown issue, but just encoder. Have you tried to switch between SW/HW-acceleration? Any difference? What about HEVC, does it work? If anything, you can transcode ProRes via external encoder, like this: ffmpeg.exe -hide_banner -y -i "input.mov" -pix_fmt yuv420p -c:v libx264 -tune film -crf 18 -c:a aac -b:a 320k "output.mp4" ... View more

Could it be that Premiere now is using integrated GPU instead of GTX 780M? I dunno how it's in CC2019, but previous versions have an option [text deleted] Also, when comparing speed vs old projects be sure the effects are identical, otherwise you may come to false conclusions. For example, just a change in order of effects could switch renderer to SW-only mode. Details here: Re: Order of filters/effects and drop in CUDA-rendering speed, is it a bug or a feature? Moderator Note: text removed. Sorry. Please do not use Console to change the application. It is against our corporate guidelines and is a request from Adobe Premiere Pro engineering. ... View more

Your timeline is "red", I guess that it renders in "software-only" mode, and likely because of a bug in Premiere. Details here: Re: Order of filters/effects and drop in CUDA-rendering speed, is it a bug or a feature? Also, your plugin(s) could be not well optimized for multi-threading. Try to check the CPU/GPU utilization during rendering to get hints where the problem is. ... View more

table30  wrote The sync issue in Premiere is with OBS's .mp4's (not it's .mkv's) Ok, but as a workaround for disabled .mkv support, have you tried to remux/repack your mkv's into mp4/mov via ffmpeg, as I suggested in my 1st reply? Does a repacked clip have the same audio sync issues in Premiere as the mp4 generated by OBS or not? ... View more

table30  wrote No, just straight 29.97 fps capture. In that case I don't see why there should be any sync issues. Have you tried direct (not in OBS) re-muxing via ffmpeg as I suggested? Are there audio sync issues still? ... View more

Are your mkv's of variable framerate? ... View more

I have no answer to your (rhetorical?) question, but I can suggest a workaround for anyone interested: Re: problem with mkv format ... View more

As a workaround you can remux .mkv files in a mp4/mov container. It's much better way than transcoding: Re: problem with mkv format ... View more

Since you are already familiar with FFmpeg perhaps the best option for you is to convert the sources to Prores format. But be sure you have enough free space for it. Your GTX1080's will be used for effects anyways, regardless of input format. But beware of this bug: Re: Order of filters/effects and drop in CUDA-rendering speed, is it a bug or a feature? Also you can use NVENC during final export. I prefer constant quality mode (cq18 .. cq16) instead of VBR. p.s I've heard that ffmpeg 'cuvid' decoding mode is rather buggy and that 'dxva2' is more forgiving, so beware. ... View more

I wonder why the correct answer says " Set the intel dll to 1 to disable", while "1" in the registry usually means "ON/Enabled." And people reports it's working. Hmm.. mystery ... View more

Adobe Premiere does not use dedicated/external GPU to decode h.264 videos. Only Intel's iGPU can be used for that. So don't expect butter smooth playback if iGPU is disabled. Another possibility is iGPU driver issue, when it's enabled but doesn't work for some reason. Consider updating it manually from Intel site: Downloads for Intel® Core™ i7-8650U Processor (8M Cache, up to 4.20 GHz) and when removing DCH-drivers remember this: Learn How to Roll Back Your Driver to a Previous Version ... View more

here is version I have, zipped 1GB: OneDrive ... View more

Also if you are running Premiere Pro as a user without admin rights, try to run the GPUSniffer.exe as Administrator. Default file location: C:\Program Files\Adobe\Adobe Premiere Pro CC 2019 One more possibility: Re: About the stuttering playback in Premiere 2019 ... View more

When you said "GPU driver is up to date", do you mean that you  manually downloaded and installed latest Nvidia driver,  or it's just a Windows build-in function says you that driver is up to date? If latter, you need to do manual driver update from Nvidia site. ... View more

You mentioned that your timeline is "red" after adding effects. In that case your project may be affected by this bug: Re: Order of filters/effects and drop in CUDA-rendering speed, is it a bug or a feature? Also, if you exporting to h264, consider using HW-encoding via your graphic card. For that you need to install export plugin (freeware) : https://github.com/Vouk/voukoder/releases/download/1.2.3/voukoder-1.2.3.zip. Just copy the "Voukoder.prm" file in the folder: C:\Program Files\Adobe\Common\Plug-ins\7.0\MediaCore Try this Voukoder settings: Video tab => Match source, Nvidia NVENC h264, CQP16, RC lookahead 20 Multiplexer tab => Container:  QuickTime / MOV (And don't update to v2 unless there is something that does not work) ... View more

Regarding GPU usage during rendering, there is a bug in Premiere. Seems it's an old one, though discovered only recently. Check the info, you may find it useful: Re: Order of filters/effects and drop in CUDA-rendering speed, is it a bug or a feature? ... View more

So, as a summary, until Adobe will fix the bug (or change the processing logic in one way or another), below are recommendations how to get maximum use of a dedicated GPU and thus make the rendering faster: - Ideally don't use CPU-effects at all (keep a timeline "yellow"). This is maximum speed mode. If you can't avoid using CPU-effects: - Don't mix CPU and GPU effects in the same adjustment layer. Doing so will cause rendering in "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 be actually working. - 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. Here "GPU-effect" means GPU-accelerated effect, when added it makes a timeline "yellow", "CPU-effect" - any that makes a timeline "red". ... View more

Kyle, thanks for the insight. That explains a lot. But I can see one inconsistency in the adjustment layer processing. Seems, it is processed soley by CPU regardless of where in the effect stack a "cpu-effect" is placed. At the beginning or at the end - no difference, adj layer always renders at SW-only speed. But, if the same stack is applied to the clip itself, we have an expected speed difference (~10 times for my case). Could it be a bug or it's just another flaw in architecture? What do you think? ... View more

Folks, has anyone tested the issue, any results, positive or negative? If it's a bug, the more statistics the better. Meanwhile, I've tested OpenCL renderer instead of CUDA (all on GTX1060). Sure, absolute numbers are different, but relative performance is the same - about 10 times difference on my setup. ... View more

One thing to remember is that Unsharp mask is a non-accelerated effect, so placing such an effect in "wrong" place can slowdown rendering significantly. Well, at least in my experience. More details here: Re: Order of filters/effects and drop in CUDA-rendering speed, is it a bug or a feature? ... View more

First, about Youtube and quality, things to be aware of. YT is intended for speed, not for quality. It always recode videos you uploaded, and does it with "fast" settings and low bitrate. And it seems they decided that 1080p and below is for mobile screens only. 1080p usually encoded in ~1.5-2Mbps, of course it looks ugly on a bigger screen. 2160p and 1440p variants are OK more or less, not good really, but acceptable. So, even if your screen is only 1080, but you wanna see maximum quality - select 1440 in YT player. I've heard that Vimeo is somewhat better, but never tested it myself. Regarding rendering and export speed. I assume you have enabled CUDA renderer in project settings. Then, in case your timeline is "yellow"  (means you are using only accelerated effects) and considering your HW, the export speed should be at least at realtime speed or faster. But, If your timeline is "red", and rendering is way too slow, try this trick I described recently: https://forums.adobe.com/thread/2626976 To make export even faster, consider using HW-encoding via your graphic card. For that you need to install export plugin (freeware) : https://github.com/Vouk/voukoder/releases/download/1.2.3/voukoder-1.2.3.zip. Just copy "Voukoder.prm" file in the folder: C:\Program Files\Adobe\Common\Plug-ins\7.0\MediaCore Try this Voukoder settings: Video tab => Match source, Nvidia NVENC h264, CQP16, RC lookahead 20 Multiplexer tab => Container:  QuickTime / MOV (And don't update to v2 unless there is something that does not work) p.s. Just a little reminder, when troubleshooting always use "New sequence from clip" method instead of creating the sequence manually. ... View more

https://forums.adobe.com/people/Ann+Bens  wrote Officially mkv is not supported but there are users who can import mkv without an issue (like me). Easiest way is to convert with HandBrake to mp4. Maybe converting is the easiest, but hardly the best way, imho. I'd just remux files instead of converting. ffmpeg can do it nicely (https://ffmpeg.zeranoe.com/builds/​) How to: - place the .mkv's in a separate folder along with ffmpeg.exe - in notepad create a pair of .bat files there: StartRemux.bat  with a string:   for %%F in (*.mkv) do remux_settings_.bat "%%F" remux_settings_.bat  with a string:   ffmpeg.exe -i %~d1%~p1%~n1.mkv -c:v copy -c:a copy %~d1%~p1%~n1.mp4 Now you can just run the StartRemux.bat , and in a minute you'll get your videos in .mp4 container, without loosing quality and time. If you like, you can change .mp4 to .mov in the settings. Sometimes it's needed ( as in case when .mp4 does not allow uncompressed audio). p.s. Important note - thoose .mkv filenames should not have spaces, or wont work. ... View more

now solved - in LR3.6 / ACR6.6 final Thx! ... View more

recently i try to use LR 3.6rc1 / ACR 6.6 - problem still here. (see green areas) ... View more

I rechecked all affected files, and all of them have next settings: iso100, 6Mpx, auto selected DR=200%. yet another sample - there highlights is ok, but green areas still here: https://rapidshare.com/files/11493922... Seems it is some kind of blending error. ... View more