I would like to add a thought to this Raw+JPG discussion. I shoot a D2H, which has only a tiny 375x570 preview image out of camera. Once I update the NEF in Capture, I have a full size preview in the NEF but an out of date JPG. I would like to streamline this workflow, avoiding the need to selectively delete the preview JPGs after the edit. I find it confusing to see the original unedited image in raw+jpg mode.
One solution, which is what Nikon employed in View V4. is to have the ingest program embed the JPG preview into the raw. PM extracts this preview so it is already reading all these raw files and knows the layout. Is that possible? Nikon deprecated this feature with it's new ViewNX (saying take a hike to it's D2H users), so that becomes a long term problem as this older Transfer program gets even older and new camera models are announced. I think this would be a good feature for PM. Even with cameras that have full size embedded JPGs in the NEF, such as the D200, that embedded JPG is only about 800K, verses a 3M+ (and therefore presumably higher quality) JPG PReview produced in camera. Embedding the camera's JPG into the raw would result in more consistent quality. After selective editing in Capture, I end with a mix of 800K and 3M embedded previews. I know that I can do a batch save on all my NEFs to force a full size preview but Capture does this at the rate of about 5 a minute on my machine. With sometimes thousands of images, that can easily be an overnight process.
Another solution would be to use the newest image and/or add some smart selection based on size. If my raw's embedded preview is only 375x570 (approximately the size of the D2H preview) and my associated JPG file is around 1600x2400, PM should use the larger image. After the file is updated, both files will be the same dimensions so then the date sort could take effect, or the NEF could win when the dimensions are the same or reasonably close.
One way or the other, it would solve a serious workflow problem that anyone with a D2H should be having, and without any solution (AFAIK) currently in PM...
Regards,
Neil