Oh, one other thing - whilst navigating between videos in loupe view works OK if the first video selected is horizontal. In addition to exiting and re-entering on a vertical video causing a crash, the same thing happens if I simply deselect all files and then select a vertical video whilst staying in loupe view.   So, it seems to be something to do with initially opening the video player in a vertical orientation. There'll be some more crash reports under my email from today. ... View more

If it helps... I did a bunch of troubleshooting further back in this thread and established that it's specifically when entering loupe view with a vertical video selected, if I go into loupe on a horizontal video and then switch to a vertical one it's fine, but if I then come out and go back in on the same vertical video it'll crash.   For me the source of the video makes no difference, only whether it's vertical or horizontal. Could be from phone or camera, mov or mp4, doesn't matter, vertical = crash.   GPU on/off makes no difference, but turning on "Enable HDR in Library" (with GPU on) does stop it happening, so maybe that'll help point to the source of the problem (I don't see any other errors). Although that feature was added in v13.5 and this didn't start until v14 (I've retested with v13.5 since v14 came out and it still didn't happen). ... View more

@Rikk Flohr: Photography I sent both the Apple and Adobe ones earlier, but I don't remember if I filled in the email address. Try again now, I just caused another crash and sent another report, email filled in this time. There should be loads there from the previous versions as well, all with the same email. ... View more

Now that the other issues with v14 seem to have been resolved, I've been update to upgrade to it again and do some more digging into this one. This, for me at least, seems to be related to the "Enable HDR in Library" option under Settings -> Performance. With that disabled I get a crash opening any vertical video in library loupe view, with it enabled they open without a crash. I'm not really sure why that setting should make a difference, given that nothing in my library is HDR and nor are any of my screens (hence why I hadn't enabled it), plus I didn't see this issue in 13.5 which is where that setting was added, but it seems consistent - disabled = crash, enabled = no crash. ... View more

Also confirming 14.1.1 fixes this for me. Synced and edited a bunch of photos and their capture dates haven't changed. Thanks! ... View more

@Admirable_Wizard157F when you unsync a collection it leaves the synced photos in All Synced Photographs, so they're still being synced unless you also go there and remove them manually. ... View more

Same, Lr has no involvement in my editing process, I don't even have it installed. All photos were imported directly into LrC and edited either in LrC or Ps. This issue only appeared once I was done editing and synced the collection they were in to the cloud. ... View more

@Cameron Braun "Original Time" in the "Edit Capture Time" dialog is the current capture time set on the selected item (image, virtual copy, etc), if it's been changed from the actual original time then it shows the changed time. "Corrected Time" is what the dialog will change it to, so without an adjustment specified they both show the same. ... View more

I'm not sure it's GMT offset related, the photos I was syncing were taken during BST, so GMT+1, but it initially changed them by 12 hours, then each time I reverted the capture time it changed them by an hour less. So a photo taken at 10am first changed to 10pm, then 9pm, then 8pm. ... View more

Same issue here. Syncing photos to the cloud changes the capture time. I revert the capture time, it resyncs and changes it again. I should've just stayed on v13. ... View more

Can confirm the 14.1 update has fixed this for me. Thanks! ... View more

I'm seeing this too, crashing when opening video files in Loupe View in v14.01. However, what I have discovered is that it seems to be related to video orientation. If I go into Loupe View on a video which is horizonal then it opens OK, and any other video I click on after that also displays and plays OK, regardless of orientation. However, if I go into Loupe View on a video which is vertical, then LrC crashes. Even if I've previously been into Loupe View starting with a horizontal video, and then played a vertical video whilst still in Loupe View, if I come out and then try to go back in on the same vertical video it'll cause a crash. I hope that makes sense! The crash reports I've been submitting should all have my account email associated with them if needed. ... View more

Thanks for the suggestions @johnrellis, I'll probably just stay on v13 for now. Did want to try out Content Credentials in v14 export but I guess that'll have to wait.   I noticed this shortcut wasn't in the list when I went to see if it had been moved to some other keys and was initially wondering if it had been intentionally removed, didn't know it had never been there. At least it's been acknowledged as a bug, and it does still work on Windows, so hopefully wont be waiting too long for a fix on Mac. ... View more

Any idea what the timeframe is for this being fixed? It's a function I use all the time, so have had to rollback to v13 until I know it works in v14. ... View more

Forgot to mention I was also on macOS 11.5, although I've tried it on Windows 10 21H1 this morning and the behaviour is the same, both using LrC 10.3. You can actually see something isn't right from the Create Preset window as the process version box remains greyed out as though required, ever after unchecking all other items. It only clears when you click Check None.   Interestingly after you've clicked Check None the Tone Curve check box seems to work as expected, over multiple preset creations and application restarts, just so long as you never click Check All again. So the issue specifically seems to be that Check All prevents the Tone Curve checkbox from working, which also includes after a new install or preference reset as Check All is the default. ... View more

Just discovered if I click check none at the bottom of the save preset window then tone curve settings aren't included, if I click check all and untick it in the list then they still are. ... View more

Same issue here. All presets I save include tone curve settings regardless of whether it's ticked or not. The last time I created a preset was in April and it was OK then, so presumably it started with 10.3. Not the end of the world as you can just remove the spurious bits from the preset file with a text editor. As an example, this should contain nothing other than process version: <x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 5.6-c140 79.160451, 2017/05/06-01:08:21 "> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> <rdf:Description rdf:about="" xmlns:crs="http://ns.adobe.com/camera-raw-settings/1.0/" crs:PresetType="Normal" crs:Cluster="" crs:UUID="EE4AECD4BE5E46278AB8503E9F774A46" crs:SupportsAmount="False" crs:SupportsColor="True" crs:SupportsMonochrome="True" crs:SupportsHighDynamicRange="True" crs:SupportsNormalDynamicRange="True" crs:SupportsSceneReferred="True" crs:SupportsOutputReferred="True" crs:CameraModelRestriction="" crs:Copyright="" crs:ContactInfo="" crs:Version="13.3" crs:ProcessVersion="11.0" crs:ParametricShadows="0" crs:ParametricDarks="0" crs:ParametricLights="0" crs:ParametricHighlights="0" crs:ParametricShadowSplit="25" crs:ParametricMidtoneSplit="50" crs:ParametricHighlightSplit="75" crs:ToneCurveName2012="Linear" crs:HasSettings="True"> <crs:Name> <rdf:Alt> <rdf:li xml:lang="x-default">Blank Preset</rdf:li> </rdf:Alt> </crs:Name> <crs:ShortName> <rdf:Alt> <rdf:li xml:lang="x-default"/> </rdf:Alt> </crs:ShortName> <crs:SortName> <rdf:Alt> <rdf:li xml:lang="x-default"/> </rdf:Alt> </crs:SortName> <crs:Group> <rdf:Alt> <rdf:li xml:lang="x-default"/> </rdf:Alt> </crs:Group> <crs:Description> <rdf:Alt> <rdf:li xml:lang="x-default"/> </rdf:Alt> </crs:Description> <crs:ToneCurvePV2012> <rdf:Seq> <rdf:li>0, 0</rdf:li> <rdf:li>255, 255</rdf:li> </rdf:Seq> </crs:ToneCurvePV2012> <crs:ToneCurvePV2012Red> <rdf:Seq> <rdf:li>0, 0</rdf:li> <rdf:li>255, 255</rdf:li> </rdf:Seq> </crs:ToneCurvePV2012Red> <crs:ToneCurvePV2012Green> <rdf:Seq> <rdf:li>0, 0</rdf:li> <rdf:li>255, 255</rdf:li> </rdf:Seq> </crs:ToneCurvePV2012Green> <crs:ToneCurvePV2012Blue> <rdf:Seq> <rdf:li>0, 0</rdf:li> <rdf:li>255, 255</rdf:li> </rdf:Seq> </crs:ToneCurvePV2012Blue> </rdf:Description> </rdf:RDF> </x:xmpmeta> ... View more

So far all I've found is either remove them from all synced collections and add them back in again, or uncheck sync for any collections the photos are in, remove them from All Sync Errors, and then recheck the sync for the collection. If you remove them from All Sync Errors without unsyncing the collections first then they get removed from all the collections as well.   Ridiculously convoluted for something that used to be a simple click on one icon. 🙄 ... View more