#MPIXELS XNCONVERT SOFTWARE#

I'm confused as to what you consider your 'bottleneck' to be. Then, I Export images that I want to share or use externally, like you said, smaller jpegs for viewing, I actually keep those jpegs on the external library drive for either future reference or archiving or whatever. And, they are backed up to an external backup drive. I move these to an external library drive. My 'archive' is the Lightroom Library/folders with my Raw files. Hmm, first, when you say you are converting the Raw to max size/quality jpegs for 'archival', well, that's not what I do. i tried using a ssd (840 Pro) as the source drive, and with a decent processor + 16gb ram, there's no way a resizing task could max out the rig.

#MPIXELS XNCONVERT SOFTWARE#

I'd see the software as the bottleneck here.

for example, there wouldn't be a significant visual difference between a 6Mb and 500kb JPEG (2000px) even when viewed on a good screen like the ipad air. quality wouldn't be so much of a concern here. This leads me to want to create small (2000px on long side) and manageable files to be stored locally on the tablet. but even with a fast connection, there's a slight pause for every photo i browse through. one alternative I'm using now is browse these photos on the cloud from my tablet. I've accumulated over 100,000 photos these years and have backed them up to the cloud. Max quality JPEGs downsized and reduced quality to maximize space/optimize viewing on tablets RAW files processed in LR, converted to Max quality JPEGs for archivalĢ. Are you processing jpegs, or converting from Raw and then resizing the resulting jpeg?ġ.

Mpixels xnconvert