yes, mine is a extension of this issue or maybe a symptom of that core issue.
For me this causes these additonal plates to get shuffled/erroring on batch load on remote systems.
So 1) clips not connected to segement openclips
and 2) these “ unconnected “ clips somehow reference the source machine in whatever way and are causing havok and confusion.
If you ever need a publish improvement focus group i will give you all the time I have and then some!
Count me in if that ever happens.
november probably
There is no plan to have a discussion about Shot Publishing in the near future. We have a backlog of reported issues that we will go though but no ETA yet.
As far as the Wiretap Gateway reference in the Clip node setups of the published Batch Group, this is no more the case with Flame Family 2026: as stated earlier, the concept of Remote Wiretap Gateway is gone and thus the Batch setups and Open Clips reference the actual media files and not Wiretap Gateway server, which removes the spiderwebs of media references man of you reported in the past.