You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following up on an issue I originally posted here.
[x ] Incorrect Functionality or bug
Description
I’m using a python script to generate a timeline exported to an xml file. I think I’ve encountered a bug: when I add two clips of the same duration on the same track on my timeline, only one of them is added to my xml file. For instance, this timeline is exported correctly, with two distinct <clipitem> generated in the xml:
But this timeline is NOT exported correctly, I get only one <clipitem> in my xml file (the behavior I’m expecting is two clips of the same duration following each other on video track 1. Both clips are made from the same file):
Operating System: Windows
Python version if appropriate: 3.10.14
OpentimelineIO version: opentimelineio-0.17.0 (but I was having the same problem with 0.16)
The text was updated successfully, but these errors were encountered:
Following up on an issue I originally posted here.
[x ] Incorrect Functionality or bug
Description
I’m using a python script to generate a timeline exported to an xml file. I think I’ve encountered a bug: when I add two clips of the same duration on the same track on my timeline, only one of them is added to my xml file. For instance, this timeline is exported correctly, with two distinct
<clipitem>
generated in the xml:(notice both clips have a different duration)
But this timeline is NOT exported correctly, I get only one
<clipitem>
in my xml file (the behavior I’m expecting is two clips of the same duration following each other on video track 1. Both clips are made from the same file):I simply export the timeline with
otio.adapters.write_to_file(timeline, file.xml)
Optional
Environment
Operating System: Windows
Python version if appropriate: 3.10.14
OpentimelineIO version: opentimelineio-0.17.0 (but I was having the same problem with 0.16)
The text was updated successfully, but these errors were encountered: