Steffan Andrews

Also note: If it's a clip, MarkersExtractor will now use the clip name (and not project name) to: - name the output folder - used in filename ID if `timelineNameAndTimecode`...

Ok, timeline parsing is more robust now, and from my initial testing, it should work as expected. Try alpha2: https://github.com/TheAcharya/MarkersExtractor/releases/tag/0.3.7-alpha2

Which timestamp? Is it not using timecode?

Yeah no problem, was probably an oversight originally.

This is done. Will be in 0.3.7.

A TON of work has been put into this thus far. Like literally weeks, full-time. But this remains very much a living and breathing in-progress effort. It's very close to...

After a massive second-pass refactor, I'm getting close to stabilizing the API and getting a robust core feature set done. - The model takes the form of lightweight strongly-typed `XMLElement`...

The re-refactor is basically complete on `fcpxml-refactor` branch. - Unit tests are passing - There are **_substantial_** performance improvements for element extraction There should be a forthcoming merge to main...

Merged PR to main.

Update: Importing the above xml file into Cubase does not import any text or marker events. So the theory is correct that there is no standard MusicXML event type for...