Hi ShannonM1:
Apple ProRAW files seem to be generated by iPhone photography. Before your post, I had never heard of the ProRAW format. The photos in question are standard RAW files from my Canon R7 mirrorless camera. The photos are imported as JPG and RAW into photos. I have an MacBook Pro M1 laptop which is running Ventura 13.2.1. Both the camera and the laptop were purchased new as of Dec 2022. I bought a SanDisk 4T SSD drive to contain my Photos library, since it surpassed my 2T SSD drive last year.
On a given travel weekend, I might shoot 700 - 2000 photos in RAW format at a conference. I import them into Photos as both JPG and RAW. I do minimal editing (mostly exposure) with the Photos editor (by hitting Return) on a small percentage (5-10%) of the photos. I switch to RAW format only on the ones I edit. The info on the photo switches from 9Mb to around 40Mb once it is edited.
At that point, Photos will NOT load the high-resolution photo when I scroll through the photo album or library. However, it DOES load the high-resolution photo if I hit Return again, going into edit mode. The edited photo also will NOT upload to a shared photo album. The only work-around I have found is to select the edited photos, export them to a folder, then re-import them to the Photos Library. Curiously, they are still 40Mb-ish in size, but they are JPG, not RAW. Then, and only then, can I upload them into a shared album. I use Keywords to separate the edited, RAW-based photos from the other JPG photos before I upload the latter to the shared album.
I have seen others on this forum who seem to have a similar issue, but I have not seen any workarounds other than the one I have uncovered (with help from Apple Support).
Here's another bit of data: If I simply switch the original to be RAW instead of JPG, it still loads and uploads to the shared albums properly. However, if I edit it, it then will not upload to a shared album but gives this error warning:
"The operation couldn’t be completed. (PHResourceLocalAvailabilityRequestErrorDomain error 0.)"
Thank you again,
rcarbaugh