|
@icallaci: Ah, yes that makes sense. The problem is caused by a performance optimization, where when replacing a format the original is not deleted first, but just directly replaced. This causes the orphan problem when the filename for the new format is different from the filename for the old format, as in the case of the changed path length calculation. Fix will be in the next release.
You can just ignore the orphans or remove then via Library Maintenance.
|