P: Publishing a video fails in version 13.2 if a post process action is present & inserted

[camner2]

In LR version 13.2, a video in a Publish Service Collection will fail to publish if the Publish Service has a post-process action installed and inserted. An attempt to publish a video will typically fail with either a This photo was not rendered or This photo is missing error message.

This has been tested with the Hard Drive Publish Service as well as the services SmugMug and jf Collection Publisher.  Post-process actions tested include Lr/Mogrify 2 and jf Metadata Wrangler.

This has also been tested with a new, "virgin" catalog and the issue persists.

It has been tested on MacOS 13.6.4; I have not tested it on Windows.

Workaround: Remove all post-process actions from the Publish Service.

Note: Unlike with the previous Assertion failed error present in 13.1, one can remove the post process action when publishing videos but reinsert the post process action when publishing still images; the mere presence of a video in a published collection no longer causes an error, unless there is a video to publish or republish. But, the workaround it's not really a "solution." If, for example, one makes some change (such as changing metadata) that triggers a need to re-publish both photos and videos, republishing will fail if a post process action is active.

[John R Ellis]

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]

@Rikk Flohr: Photography, please consider moving to Bugs. I see the same issue in my LR 13.2 / Mac OS, using the Metadata Wrangler post-processing action with the Hard Drive publishing service:

[dzeleznik]

Thank you so much for figuring out the exact conditions that were causing this to succeed for me publishing videos on some of my services and fail with "photo missing original" on the exact same videos for other services! I am on 13.2 on Windows and my failures are on a jf Folder Collection publish service with jf Run Any Command injected as a post-process action. As an extra data point, if I remove jf Run Any Command as a post-process action then the service will publish my videos on the service fine. However, if I leave jf Run Any Command inserted as a post-process action, but disable it within the publish service I still get the error:

So it appears that even if the post-process action is disabled and its a no-op, it's mere presence causes video publish failures.

[camner2]

@dzeleznik:

You are certainly correct that merely disabling a post-process action on the right side of the Publishing Manager is not sufficient to make the publish action work. But notice that in my original post I wrote: Workaround: Remove all post-process actions from the Publish Service.  My workaround involves choosing the post-process action on the lower left side of the Publishing Manager and clicking the Remove button. This will remove the action from the right hand panel, but it does not delete it. If you later click the Insert button, the action will reappear on the right hand side with the same settings it had when you removed it.

[dzeleznik]

Just updated to 13.3 and still not fixed... 😞

[camner2]

The bug as originally reported in this thread is still present in version 13.4

[Rikk Flohr: Photography]

Greetings all, 

Updates for the Adobe Photography Products are released.  The August 2024 updates contain an update for this issue. 

If you do not see the update in your Creative Cloud Application, you can refresh it by hitting [Ctrl/Cmd]+[Alt/Opt]+[ R ].

Note: It may take up to 24 hours for your update to be available in your Creative Cloud app.

Thank you for being so patient.

[dzeleznik]

Seems to be fixed for me in the latest v13.5 update. My collections that have jf Run Any Command injected as a post-process action are now publishing videos okay. Thanks for finally getting this resolved!

[camner2]

In my brief test using two publish services, videos exported correctly. So, it appears that this issue has been resolved. Wonderful! 

I did, however, observe a new behavior that I suspect was unintended, but that does not interfere with the publish process. When initiating publishing to an external Publish Service (such as SmugMug), LrC now reports two "operations in progress" rather than one, as before. One of these operations is "Updating Published Collections" (expected), and the other is "Export to 1 folder 'LongHexadecimalName'" (unexpected). Of course, publishing to an external Publish Service requires an export, but the exported file is temporary and is deleted upon completion of the update to the publish service collection. In the past, LrC kept this export behind the scenes and did not expose this temporary export in the interface.

This behavior does not occur when publishing to a Publish Service whose destination is on the local system. That makes sense, because in this case there is no need for a temporary file to be created which is later deleted. 

But, as stated above, this behavior does not impact the image/video publishing process itself.