Bug 503692

** Kdenlive 25.04.0 **

SUMMARY
a) When Exporting OpenTimelineIO, Kdenlive does not include file extension in the exported file (missing .otio).

b) When Importing .otio file (exported from Davinci) into Kdenlive, there is no prompt to locate missing assets (video, audio, etc). [Resolve and Kdenlive each being on different PCs]

c) When Importing .otio file (exported from Kdenlive) into Davinci, the order of the tracks is inverted. V1 becomes V2.


STEPS TO REPRODUCE (a)
1. Menu bar, File > OpenTimelinIO Export...
2. Chose destination. name file.
3. Export.

OBSERVED RESULT
OpenTimelineIO file does not have .otio extentio - so file cannot be see by Kdenlive when Importing OpenTimelineIO.

EXPECTED RESULT
Exported file include .otio extension in file name.

+++++++++++++++++

STEPS TO REPRODUCE (b)
1. Export .otio file from Resolve [Resolve being on different PC than Kdenlive].
2. Import .otio file into Kdenlive: File > OpenTimelineIO Import...
3. Select .otio file that is from other PC.

OBSERVED RESULT
[Resolve and Kdenlive each being on different PCs] Kdenlive does not prompt user to locate missing asset files.
Instead returns an error message and stops there. Crashes if user tried to replace files from bin by right clicking.

EXPECTED RESULT
Kdenlive to prompt user to locate missing assets on local system.

+++++++++++++++++

STEPS TO REPRODUCE (c)
1. Export .otio file from Kdenlive: File > OpenTimelineIO Export...
2. Import .otio file into Resolve.

OBSERVED RESULT
The order of the tracks become inverted inside Davinci Resolve, where track V1 goes where V2 is, so above - track V2 goes where track V1 is, so under. This includes A1 and A2.

EXPECTED RESULT
For the order of the tracks to remain the same, V1 being under and V2 being above V1 inside Davinci Resolve


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 6.13.0
Qt Version: 6.8.3

ADDITIONAL INFORMATION
I know that the Davinci Resolve section of the report might be a stretch, but that's how I tested the cross-compatibility.

The real issue, which would happen regardless of what software was used to export the .otio file, is that Kdenlive does not prompt the user to locate the missing assets like it would if the user was opening a .kdenlive project where the assets had been moved to different folders

The OpenTimelineIO export not including the .otio extension in the exported file could cause issues when importing .otio files later on as Kdenlive does not identify OTIO files without the extension - at least on my system, Linux Mint running Flatpak.