Apple Feedback Assistant ID: 102886575900
DESCRIBE THE BUG:
When copying media between two different events within the same Library using the Option-drag method, Final Cut Pro fails to create a new physical copy of the media within the Library bundle.
Even though the UI displays the "plus" (+) icon suggesting a copy is being made, the clip in the destination event remains linked to the original media file located in the source event's folder. If the source event is subsequently deleted, the physical media is destroyed, causing permanent data loss for the destination event despite the user's intention to "copy" and isolate that media.
TO REPRODUCE:
1. Create a Library with two events: Event A and Event B.
2. Import a media file into Event A (Internal/Managed media).
3. Hold the Option key and drag the clip from Event A into Event B.
4. Select the clip in Event B, right-click, and choose "Show in Finder."
5. Observation: Note that the file path points to the "Event A" folder inside the Library bundle.
6. Delete Event A from the Library.
7. Result: The media in Event B goes offline or is permanently deleted from the disk because no physical copy was ever generated in Event B's storage path.
EXPECTED BEHAVIOUR:
When Option-dragging (copying) between events, Final Cut Pro should duplicate the physical media file into the destination event's folder within the Library bundle. This ensures that events are self-contained and prevents accidental data loss when cleaning up or deleting older events.
SCREENSHOTS:
https://adilo.bigcommand.com/watch/i9JDkafi
SPECS:
SPECS:
• Model: Mac Studio (Mac13,2)
• Chip: Apple M1 Ultra (20-core)
• Memory: 128 GB RAM
• FCP Version: 12.2
• System Firmware: 18000.101.7
ADDITIONAL COMMENTS:
This bug has been present for approximately two years, appearing to coincide with the transition to Apple Silicon. It is a critical data integrity issue. I have previously reported this via Feedback Assistant a year ago, but the behavior persists in FCP 12.2.0. This has resulted in actual loss of project data when deleting "old" events that were assumed to no longer be linked to active ones.
Apple Feedback Assistant ID: 102886575900
DESCRIBE THE BUG:
When copying media between two different events within the same Library using the Option-drag method, Final Cut Pro fails to create a new physical copy of the media within the Library bundle.
Even though the UI displays the "plus" (+) icon suggesting a copy is being made, the clip in the destination event remains linked to the original media file located in the source event's folder. If the source event is subsequently deleted, the physical media is destroyed, causing permanent data loss for the destination event despite the user's intention to "copy" and isolate that media.
TO REPRODUCE:
1. Create a Library with two events: Event A and Event B.
2. Import a media file into Event A (Internal/Managed media).
3. Hold the Option key and drag the clip from Event A into Event B.
4. Select the clip in Event B, right-click, and choose "Show in Finder."
5. Observation: Note that the file path points to the "Event A" folder inside the Library bundle.
6. Delete Event A from the Library.
7. Result: The media in Event B goes offline or is permanently deleted from the disk because no physical copy was ever generated in Event B's storage path.
EXPECTED BEHAVIOUR:
When Option-dragging (copying) between events, Final Cut Pro should duplicate the physical media file into the destination event's folder within the Library bundle. This ensures that events are self-contained and prevents accidental data loss when cleaning up or deleting older events.
SCREENSHOTS:
https://adilo.bigcommand.com/watch/i9JDkafi
SPECS:
SPECS:
• Model: Mac Studio (Mac13,2)
• Chip: Apple M1 Ultra (20-core)
• Memory: 128 GB RAM
• FCP Version: 12.2
• System Firmware: 18000.101.7
ADDITIONAL COMMENTS:
This bug has been present for approximately two years, appearing to coincide with the transition to Apple Silicon. It is a critical data integrity issue. I have previously reported this via Feedback Assistant a year ago, but the behavior persists in FCP 12.2.0. This has resulted in actual loss of project data when deleting "old" events that were assumed to no longer be linked to active ones.