Lightroom/Camera Raw: Lens Profiles only work on raw/DNG files Distortion Slider functionality limited

This is a very poor support model. As a former IT Support director for a company almost as large as Adobe, I would never approve this type of support. It removes the company and its employees from responsibility for their own work. It makes it difficult for professionals who use the software to run their businesses to get immediate answers to pressing questions that allow them to stay in business. It also creates animosity towards Adobe. They currently have the worst support model that I have ever encountered. 
As to your answer to the issue at hand. I am no longer responding to "answer" to a bug report/feature request (call it what you like). 

The examples I posted are from Mac OS 10.13.4  I am not able to replicate Michael's issue. 

Todd,

Actually I am not the person who marked that as the correct answer,  Someone alas did. I have removed that just now. In fact the Any Crop tool does not function as I need it too. It crops to the size by taking the chunk of the image defined by the AnyCrop tool.  It does not reduce the size of the image and crop out the excess and just reduce the image size. If I select center it crops the section of the image that is 800x533. Does it work? Technically, just not the way I need it to. 

The profile issue is A) a feature request, which is how I listed it in the first place. B) a secondary issue that is not that bloody important yet everyone says they can help me. I will restate it as maybe I didn't say it correctly. 

All lens profiles should be available for all formats, not just raw images with meta data. The "defaults" are insignificant and useless. Additionally; the distortion slider is not working as it used to in previous versions when using existing default profiles. 

The two issues are in conjunction. period. They may or may not be related, and honestly, at this point I really don't care! The cropping issue is more important to me. The cropping/resizing issue is an actual issue and support doesn't want to trouble shoot why an action is getting a bad result because, and I quote, "well there isn't an error message so it isn't broken."

I have a deadline of tomorrow afternoon. I can't even express the issue properly via text as it is pretty much a visual thing. This is why I created a new thread and invited Rikk to it. As it is more a PS thing, it may be outside is area, but it didn't hurt to ask. 
Lastly, could it be related to the lens profiles, Until I can eliminate it, it is possible because the images that create the white edges all have been edited with said lens profile tool. Its not the only commonality, but it is one. 

Victoria,

The frustration is not with this issue alone. The frustration is with a poor support model that does not support my business. I posted this as a feature request. How it became a problem issue, no idea. The slider functionality changed. Support acknowledge that and I mentioned it in the first message. Maybe I wasn't clear enough. The fact is I really don't give a ..... At this point I can change my work flow to use profiles before I do anything else, maybe even on import, we shall see. 

I am more frustrated with getting exact sizes (odd as they may be) out of either LR or PS, neither of which is able to handle these exacting specs. See my reply to Todd above your post. 

Yeah, I understand the frustration with the support model. Unfortunately I can't help with that.

But if the slider functionality changed, that's a bug rather than a feature request (it shouldn't change, because that would affect photos you'd already edited too) so that would be a serious issue.

Other than inviting Rick and this last reply to you, I have been trying to do that. FYI I am on the phone with support and they may have found something. I will post in the other thread when we are done.

Rikk bloodyauto correct...

In spite of my repeated lobbying to Apple and Microsoft they refuse to add "Rikk" to the dictionary.

Regarding the white-space/crop issue you referenced earlier it may be related to this thread: https://feedback.photoshop.com/photoshop_family/topics/i_cant_add_certain_custom_crop_ratios_in_ligh...  
And in no small part accounts for the existence of the Any Crop plugin from John Rellis. 

Probably you should create a separate thread here for further discussion. (I know you have one on the user to user forum but the engineers hang out here.)

I spoke to support extensively yesterday and the issue is that when generating an action (later embedded in a Droplet), the action will generate a crop map based on pixel locations so "Start : 0.00x 0.00 End: 4800 x3600" for example. If you create the action on the largest or an larger image, smaller images will have white gaps in the "excess" areas. 
This is unlike Lightroom which will crop a relative area to a specific size. However LR has the rounding issue so exact sizes are a crap shoot. 

Rather than use AnyCrop I have chosen to use ON1 for the resizing. For me, its a little easier as I already own it, and I already use it for enlargements (it was born from Fractal back in the day). 
As for Microsoft and Apple, Americans. They (we) think they invented English! ;-)

Safe to say you are operational again?

getting there. A lot of catching up to do. 12 hours on the phone with support for something that in my opinion, should even be an issue, but certainly should have been answered faster, cost me a a lot of money. 

THanks