exdeejjjaaaa

no SSD is capable of 32 GB (as in thirty two gigabytes)/sec ... Samsung itself claims 10+ times less in seq. read/write throughput in ideal lab test conditions... am I missing something ?

sell, sell, sell

the ultimate one is = http://www.jenoptik-inc.com/coastalopt-standard-lenses/uv-vis-nir-60mm-slr-lens-mainmenu-155/80-uv-vis-ir-60-mm-apo-macro.html nothing else touches it

yes

https://www.lensrentals.com/blog/2016/04/a-look-at-electromagnetic-focusing/

what is worth considering here is that resizing with mouse behaves differently on computers... more so - resizing with mouse shall be identical to resizing with keys ... sure - but you simply miss ...

the mere fact that you can't see that behavior in your setup does not mean that it is a user error... so why there you don't see the that jump then... apparently the provision was there, just Adobe ...

I am using a regular USB mouse with standard driver in Win10... not touchpad or anything like this.

OK - what is your computer configuration in terms of iGPU and/or dGPU ?

OK, so I guess I need to find somebody on a PC/Win10 notebook with intel GPU and discrete mobile nVidia GPU to see if this combo makes ACR to go astray ... thank you.

OK, may be NVidia (GTX870M) and/or embedded Intel (HD4600) vs discrete AMD (AMD R9 280x is a desktop discrete card and your monitor/s/ connected to it directly, right ?) then...

And what are your GPUs (in CPU and/or discrete) ?

nobody was/is insisting... if you don't want then don't by all means :-)... move on

sure, video shall be enough if you ping smb in Adobe Win10 Pro x64, M$ reports version = 1511 and OS build = 10586.218 iGPU from i7-4810MQ = HD4600, M$ reports driver version = 20.19.15.4331, from ...

ACR can do square-brackets, yes - but the point specifically was about resizing with the mouse...

it is pretty much possible that it is even specific to Window 10 related issue, yes.. but it is not something that I invented, I can reproduce it now just as when video was shot... it is ...

not exactly, it happens on PC/Windows, ___BUT__ you miss the point that ACR/LR code can in fact control where to put the mouse pointer inside ACR/LR window... ACR/LR code can detect when resizing ...

may be because you are, I bet, on mac/osx and this mess is probably pc/windows related (Win10x64 and latest public ACR version for CC in my case) - you open raw in ACR/LR and start using "Spot ...

while you are in a pinging mood - plz ask when Adobe will finally fix this mess = https://youtu.be/ZQu7FbSkFFU when users change the size of the spot with the mouse they are not logically expecting ...

are you sure that Adobe does not add dithering when it converts from internal "> 8bit" representation of the data (when working with the raw file) in its internal working space to output to ...