[Chris Wright]

quadro has 10 bit float point 3d rendering but less cuda cores so slower for more money.
k620 faster than m2000. 1060 much faster than either.
you could get a cheaper gtx1050ti than k620 with double the cores and speed for $139.
1060 20% more expensive than 1050ti for 20% better performance. 1050ti best small budget, 1060 best medium build, 1070 best bang for buck, 1080 often cpu bottlenecked

cuda only accelerates this stuff so if you don’t use it then save money.
https://blogs.adobe.com/creativecloud/cuda-mercury-playback-engine-and-adobe-premiere-pro/?segment=dva
https://blogs.adobe.com/creativecloud/adobe-premiere-pro-cs5-5-improvements-in-cuda-processing-and-the-mercury-playback-engine/?segment=dva

[Chris Wright]

the first two things that pop into my head are change video renderer to software from cuda and disable intel h.264 acceleration in preferences. if those don’t work, then deselect import seq natively and delete media cache.

[Chris Wright]

both around 12.5 dynamic range
c100 Built in ND and on board XLR, slightly better lowlight, gh5 3.5mm mic
c100 internal AVCHD recording 4:2:0 signal, ninja external recorder $600 STILL 8 bit 4:2:2! , gh5 10 bit internal 4:2:2
max recording resolution: c100 HD, gh5 4k @60fps.

[Chris Wright]

is this thread still unresolved? I would elevate it to adobe video queue support if so. Please let us know either way so it may benefit others.

[Chris Wright]

just copy and paste all your interlaced video into a new progressive sequence. it will deinterlace for you automatically.

[Chris Wright]

did you set nvidia control panel to premiere.exe always use? what does gpusniffer say?
go into the bios setup. From there, disable the “iGPU” feature
installed geforce experience?
deleted preferences and restart?

[Chris Wright]

light the greenscreen and see if your vectorscope target is dead in line 60% to green box. There should be no deviation along this line. If there is, you don’t have even lighting. Also, your green ire should be lower than you think, exposing green at its native luminance, 49 ire luma, 55 ire chroma.

soft, even light within 0.2 f-stops across screen with lightmeter
keylight is ok, primatte is better
film with 444 10 bit, if not, then 422 10bit, then 4:2:0(hard to key), don’t key with transcoded footage. always key from RAW
light actor separately from screen 8-10 ft away, skin at native iso sensor ire white level/60 ire or 1.5- 2 stops more than screen.
https://www.xdcam-user.com/2013/12/cine-ei-mode-when-recording-s-log23-and-raw-on-the-f5-and-f55/
if slog3 doesn’t have 10 bit, or you don’t have RAW, shoot prolost settings instead.
https://prolost.com/blog/2012/4/10/prolost-flat.html

lighting greenscreen video with a vectorscope and waveform monitor
https://www.youtube.com/watch?v=Z07lKQg00Bg

what clothes to not wear
https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0ahUKEwj0_JzxmbPRAhVE1GMKHa-UARMQtwIIHDAA&url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D28epRF6Cy4A&usg=AFQjCNEIWCsvkJV24HNKrwg2ZvwBT-ZKXA

setting up greenscreen
https://tubularinsights.com/7-tips-set-up-professional-green-screen/
https://www.videomaker.com/videonews/2013/11/5-green-screen-tips-to-make-your-project-stand-out
https://www.pinnaclestudiopro.com/green-screen-tips/

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

[Chris Wright]

i got an example buried in this template:

under the comp “final output” in layer called “sharpen” with its alpha matte if you’re curious.
https://f1.creativecow.net/9780/ae-technicolor-cc-2015

[Chris Wright]

“My conclusions are:
1) There does not seem to be any hard coded limit on CPU threads for H.264 output workflow for Premiere Pro (ie 4k to 4k utilizes 100% CPU on 24 threads — dual Xeon 6-core w/ HT’s)
2) However, there is a definite limit as to how may CPU threads will get utilized for a HD to HD H.264 output workflow; I was seeing 90+ % CPU utilization, but only when I had dropped available cores to around 12 threads. With 24 threads available, I was only seeing about 50% CPU utilization (think about that as closer to 100% utilization on 12 cores and the rest are just sitting around).
3) Both Premiere Pro and Media Encoder can run at the same time and utilize more cores than either will by itself (for HD workflows and lots of available CPU cores) When I ran both simultaneously, total CPU utilization was hitting just above 90% (w/ 24 threads available).”

https://forums.adobe.com/thread/2244842?start=40&tstart=0

[Chris Wright]

premiere’s lumetri can load luts. some mac users with p3 monitors say it helps.