• Welcome to the Lightroom Queen Forums! We're a friendly bunch, so please feel free to register and join in the conversation. If you're not familiar with forums, you'll find step by step instructions on how to post your first thread under Help at the bottom of the page. You're also welcome to download our free Lightroom Quick Start eBooks and explore our other FAQ resources.
  • Stop struggling with Lightroom! There's no need to spend hours hunting for the answers to your Lightroom Classic questions. All the information you need is in Adobe Lightroom Classic - The Missing FAQ!

    To help you get started, there's a series of easy tutorials to guide you through a simple workflow. As you grow in confidence, the book switches to a conversational FAQ format, so you can quickly find answers to advanced questions. And better still, the eBooks are updated for every release, so it's always up to date.
  • 12 December 2024 It's Lightroom update time again! See What’s New in Lightroom Classic 14.1, Mobile & Desktop (December 2024)? for Feature updates, new cameras and lenses, and bug fixes.

Can't publish videos with LR 13.1

Status
Not open for further replies.
C

camner

Active Member
Premium Classic Member
Joined
Sep 28, 2008
Messages
808
Location
Tacoma, WA
Lightroom Experience
Intermediate
Lightroom Version
Classic
Lightroom Version Number
13.1
Operating System
  1. macOS 13 Ventura
After I click "Publish" when trying to publish a video in LR 13.1, I get the following error message (publishing still images works just fine).
SCR-20231224-sLR error.jpeg

This occurs consistently with any of several publish services I have tried, including the built-in Hard Drive service (the other two I have tried are SmugMugs publish plugin and Friedl's Collection Publisher).

I have tried the following troubleshooting steps:
  1. Rebooted the computer and restarted LR
  2. Created a fresh catalog and imported a single video into the catalog
  3. Tried videos from several different cameras (including a video from 2007, just for grins!)
FWIW, I'm running Ventura 13.6.3 on a 2020 27" iMac.
 
Sort by date Sort by votes
I had that on one of my SmugMug publish collections, but it worked on others. My solution was to force a Lightroom backup on exit with the integrity check selected. After that the error went away. I know it's actually not called integrity check but it's whatever it does to verify your catalog. I'm just not on my computer right now so and I don't remember the exact wording.
 
Upvote 0 Downvote
According to someone else who has reported this and a similar problem, Adobe has acknowledged this issue.
Click to expand...
Adobe customer support isn't to be trusted with this -- they'll say anything to close out a call, and who knows whether they'll file an actionable bug report.

There is an "official" bug report here:
https://community.adobe.com/t5/ligh...r-when-trying-to-publish-a-video/m-p/14320909

and I've asked that the other thread in that forum be merged with it. I've also called it out to Adobe employee Rikk Flohr. Not sure if anything will happen with it until the New Year -- I think most Adobe employees are on company-wide vacation.
 
Upvote 0 Downvote
Woodbutcher said:
I had that on one of my SmugMug publish collections, but it worked on others. My solution was to force a Lightroom backup on exit with the integrity check selected. After that the error went away. I know it's actually not called integrity check but it's whatever it does to verify your catalog. I'm just not on my computer right now so and I don't remember the exact wording.
Click to expand...
Tried that (actually that happens automatically each time I quit LR unless I specifically choose not to backup or test integrity). Alas, that didn't fix things for me.
 
Upvote 0 Downvote
johnrellis said:
Adobe customer support isn't to be trusted with this -- they'll say anything to close out a call, and who knows whether they'll file an actionable bug report.

There is an "official" bug report here:
https://community.adobe.com/t5/ligh...r-when-trying-to-publish-a-video/m-p/14320909

and I've asked that the other thread in that forum be merged with it. I've also called it out to Adobe employee Rikk Flohr. Not sure if anything will happen with it until the New Year -- I think most Adobe employees are on company-wide vacation.
Click to expand...
What distinguishes an "official" bug report from a discussion post talking about an issue?
 
Upvote 0 Downvote
camner said:
What distinguishes an "official" bug report from a discussion post talking about an issue?
Click to expand...
Generally, reported "bugs" remain in the "Discussions" area until either Adobe themselves can reproduce the problem using the provided steps or a number of "me too" messages are posted by senior members of the community. As you see from that "official" bug report it is still in the "Discussions" area but @johnrellis has requested that Rikk Flohr moves the report to the "Bugs" area. However, Adobe are still on their winter break until 2nd January, so it may not happen until then.
 
Upvote 0 Downvote
Jim Wilde said:
Generally, reported "bugs" remain in the "Discussions" area until either Adobe themselves can reproduce the problem using the provided steps or a number of "me too" messages are posted by senior members of the community. As you see from that "official" bug report it is still in the "Discussions" area but @johnrellis has requested that Rikk Flohr moves the report to the "Bugs" area. However, Adobe are still on their winter break until 2nd January, so it may not happen until then.
Click to expand...
Thanks, Jim. So, if I understand correctly, as an Adobe forum contributor, a user doesn't file an "official" bug report, but a community post describing an issue becomes an "official" bug report when an Adobe employee so designates an issue. Yes?
 
Upvote 0 Downvote
camner said:
Thanks, Jim. So, if I understand correctly, as an Adobe forum contributor, a user doesn't file an "official" bug report, but a community post describing an issue becomes an "official" bug report when an Adobe employee so designates an issue. Yes?
Click to expand...
Not quite.....a user CAN file a report in the "Bugs" section of the community forum, but that may then get re-assigned by Adobe into "Discussions" pending confirmation that it is indeed a bug. Often, what we think is a bug turns out to be not the case.
 
Upvote 0 Downvote
In practice all reports filed in the ‘bugs’ section are moved to ‘discussions’ and will stay there until it is officially a bug and entered in Adobe’s bug tracking system. For this reason I am puzzled why ordinary human beings are able to post in ‘bugs’ at all. I assume that is really only so people can add their experience to an existing bug report.
 
Upvote 0 Downvote
Jim Wilde said:
Not quite.....a user CAN file a report in the "Bugs" section of the community forum, but that may then get re-assigned by Adobe into "Discussions" pending confirmation that it is indeed a bug. Often, what we think is a bug turns out to be not the case.
Click to expand...
 
Upvote 0 Downvote
I would think then that a reasonable approach to take when a user notices behavior that seems to be a bug is that they post the observation in the Discussions folder, but once more people say something such as, “Me too!” then it’s appropriate for someone to post in the Bugs location.
 
Upvote 0 Downvote
camner said:
I would think then that a reasonable approach to take when a user notices behavior that seems to be a bug is that they post the observation in the Discussions folder, but once more people say something such as, “Me too!” then it’s appropriate for someone to post in the Bugs location.
Click to expand...
Nope. It’s appropriate to notify Rikk Flohr about it, so he can decide to make it official. Like I said, if you post something in ‘Bugs’, the post will be moved to Discussions, so you would only create a duplicate post this way (either that, or the post will be merged with the original discussion).
 
Upvote 0 Downvote
Status
Not open for further replies.
Back
Top