Steffan Andrews

Writing back to FCPXML is non-trivial and not something we can reliably do yet.

I'm not sure how I'm not being clear. Once we ingest FCPXML, that's it. We can't go back to it at this time. We have to use the parsed data...

Definitely possible on the MarkersExtractor side. 1. I can split its operation into two stages as mentioned before. 1. PARSE: One operation parses FCPXML and flattens it down to a...

> does it make sense to include the Line Number from FCPXML No. Line numbers are brittle and naive. There are better ways to reference markers. We already have a...

Ok, makes sense. This seems doable.

Same issue on MacBook Pro M1 Max (64GM RAM), macOS 14.6.1 and affects all FLUX.1 models - dev and schnell.

The example project is not optimized so that's certainly possible. SwiftUI is not an efficient UI backend but it was used because of its simplicity.

With the Swift Concurrency refactors underway, this issue should be resolved.

Without diving back into the codebase, I have a couple theories why that may be the case. I'm busy this week but will try to have a look at this...

Apologies for the delay - I have been dealing with some family emergencies. Most properties on `MIDIDevice`, `MIDIEntity` and `MIDIEndpoint` are pulled, not pushed. So when you use `device.isOffline` it...