Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Exit
basil1891
Advocate
basil1891
Advocate
Activity
‎Dec 31, 2020
02:24 PM
1 Upvote
"lesser quality after uploading", if you mean Youtube, that's expected, YT recompress all videos you upload
... View more
‎Dec 31, 2020
10:03 AM
Ok, one more attempt. Here is Khronos OpenCL.dll from my Windows\System32 folder: https://www.dropbox.com/s/bexyjtz9sxlxliv/openclv2210.zip?dl=0 make sure that: 1) path in the registry points to this new dll, 2) you are running GPU Sniffer with admin rights
... View more
‎Dec 31, 2020
03:39 AM
1 Upvote
Try to turn off hw-acceleration for encoding/decoding. If not help, you'll need to use external encoder like x265/x264.
... View more
‎Dec 30, 2020
10:30 PM
1 Upvote
To me it looks like a decoding issue, try to turn off hw-acceleration in preferences
... View more
‎Dec 29, 2020
04:29 PM
HT is for 'Hyper-Threading', so if HT off = > 18 threads remains. Still worth to try.
... View more
‎Dec 29, 2020
03:25 PM
Are you still on 32GB RAM? You likely affected by 'RAM Starvation' problem. It's recommended to have 2GB RAM per logical core, that's for Adobe PP only, plus some for OS. Try to turn off HT and maybe even some cores completely. https://videoguys.com/blogs/news-and-sales/avoiding-ram-starvation-getting-optimum-performance-in-premiere-pro
... View more
‎Dec 29, 2020
10:53 AM
Have you tried this OpenCL registry fix: https://www.ownscene.com/blog/fixing-adobe-premiere-pro-wont-recognize-opencl-amd-gpus-using-registry-editor-windows-machine/ Hit Windows key and type regedit Go to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenCL\Vendors Double click on your amdocl64.dll and change the value from 0 to 1 and hit OK Restart just to be safe.
... View more
‎Dec 29, 2020
12:49 AM
a frame sample to show a difference, likely more complex than yours, but still useful imo Adobe Media Encoder H.264 vs X264 vs X265:
... View more
‎Dec 28, 2020
10:51 PM
Just wanted to clarify for OP, my suggestion about encoding in H.264 apply only if 'new platform' allows streaming of original files. But if there is unavoidable transcoding on the way to end consumer, you really should deliver H.265 in this case, as at such low bitrates (below 0.1 Bits/(Pixel*Frame) it's way better at preserving details
... View more
‎Dec 28, 2020
06:45 PM
YT is aim for speed and availability, not for quality. 720p is not considered HD anymore, lol. Well, for YT encoding that's true. You may get better result if you upload up-scaled clip like 2560x1440. Seeminly, YT uses somewhat better encoding parameters for a 2.5K/4K clips
... View more
‎Dec 28, 2020
12:57 PM
1 Upvote
Fitting 1h:25m of footage in 2GB = ~3100kbps for video and ~128 kbps for audio, for 1920x1080 x h264 that's very low. Result could Ok if camera is static, and there is little to no movement in frame. Otherwise 'you have a problem'.
... View more
‎Dec 28, 2020
06:39 AM
Check if you have OpenCL installed/enabled,
Mod: Comment removed. Please do not refer to our internal debug tools.
GPU Caps Viewer: https://www.techspot.com/downloads/4618-gpu-caps-viewer.html
... View more
‎Dec 27, 2020
06:11 PM
NVIDIA Driver Downloads: https://www.nvidia.com/Download/Find.aspx
... View more
‎Dec 26, 2020
07:51 PM
The tool that do actual job is NVEncC64 ( https://github.com/rigaya/NVEnc ) But to spare your time, here is my pack of ready to go presets: https://1drv.ms/u/s!Andr88T403SpgRL5G8nDA5pXK_Vf?e=dwpceJ The one you need is called "Proxy 1080p NVEnc [.mov]", instruction how to use is inside, but I recite it here: 1) Create a desktop shortcut (not a copy!) for a preset file 2) Now just grab the video files you want to process and drop them on that shortcut 3) Wait till done, look for output files in a corresponding folder along with originals: Proxy\, Delivery*\, Remuxed*\ etc
... View more
‎Dec 26, 2020
06:49 PM
Not an answer to the actual question, but with proper tool you can create 1920x1080 proxies at speed 5x faster than real time, ie 300fps+. Probably even more
... View more
‎Dec 26, 2020
05:26 PM
It can be a bad RAM stick. Try to downclock/turn off XMP for a time to find out.
... View more
‎Dec 26, 2020
02:30 PM
Before any suggestions, let's check the "software only rendering" thing: when you create new proj with a simple 1080 clip on a timeline and apply Lumetri to it, the timeline became red and while play preview CPU load is about 100%, and GPU is not loaded at all. Can you verify?
... View more
‎Dec 25, 2020
01:31 AM
1 Upvote
About a week ago someome had similar issue apparently caused by latest Nvidia driver. The solution was a roll back to October release. If not help, likely you'll have to use proxy
... View more
‎Dec 24, 2020
07:21 PM
1 Upvote
Try to render/export that 'effect heavy' part at std UHD 3840x2160 resolution, I suspect that 4GB of video memory is not enough for heavy effects at full C4K+ resolution.
... View more
‎Dec 24, 2020
04:12 PM
I'd check video driver. Try some previous versions, and turn off auto-update feature.
... View more
‎Dec 24, 2020
09:06 AM
Regarding "Set to framesize" vs "Scale to framesize" difference. Here is a simle demo for zoomed UHD clip on a 1920x1080 timeline. Same field of view, but different methods. Hopefully uploaded pics will show the difference in sharpness:
... View more
‎Dec 22, 2020
05:11 PM
worth to try this - NVidia driver version downgrade: https://community.adobe.com/t5/premiere-pro/adobe-premiere-pro-very-slow-playback-on-very-high-end-pc/m-p/11699400?page=1#M318993
... View more
‎Dec 22, 2020
09:55 AM
"16 GB is enough to render 4K. Buying 32GB of RAM will probably yield the same result" - I second that, don't waste your money
... View more
‎Dec 21, 2020
01:12 PM
I'd suggest to use task manager to monitor resources during that slow render. If there is not a single component that has > 50% load you can brush aside any suggestions about "weak" hardware. And so you can start looking for software issues, it can be some Adobe settings, system drivers, bug(s) in Premiere, and of course general lack of code optimization. The latter is not unusual. We all can notice how Adobe just rises minimal system requirements with each major version, plus uses it's subscribers as beta testers, which also says a lot.
... View more
‎Dec 18, 2020
07:45 AM
1 Upvote
... change "di=n" to "di=mp" actually, sorry for confusing
... View more
‎Dec 18, 2020
07:27 AM
1 Upvote
Assuming your DV is NTSC 29.97i try the updated version I uploaded today, pay attention to this in readme: "By default NTSC-DV (SD, 29.97i, 4:1:1) input is deinterlaced in 'normal' mode i.e. not multicore optimized. To switch that edit the file avs\input_config.bat and change "di=mp" to "di=n". But don't forget to revert it after the job is done, or you'll get a major slowdown for all normal (non-DV) sources."
... View more
‎Dec 18, 2020
05:58 AM
I believe 99,9% of videocams produce files with limited color range (16-235), and it seems NVENC by default assumes that the video is 16-235 unless told different. So either you change your input, or find a way to tell encoder that it's 0-255 actually.
... View more
‎Dec 17, 2020
10:01 PM
well, since it's "some" projects, think about what they have in common that others doesn't
... View more
‎Dec 17, 2020
08:23 AM
1 Upvote
for troubleshooting I'd run a copy of the project but downscaled to standard 1920x1080, then selected the trouble part of the timeline and exported it in some intermediate codec, like Prores/Cineform/DNxHD. That way you can check two potentional causes: non-std resolution and h264 codec, and in reasonable time.
... View more
Copyright © 2024 Adobe. All rights reserved.
AdChoices