I make an audio post production tool that translates XML exported from video editing software (Final Cut Pro X, Adobe Premiere, Davinci Resolve & EditShare Lightworks) into formats that can be opened in various DAWs.
A Studio One Professional user recently requested that I add support for Studio One, so I just did in the latest release - Vordio 5.3.2. For use with Studio One you should convert an NLE XML to OpenTL format. There is no need for OMFs or AAFs. Vordio workflow is entirely XML based.
Studio One can import OpenTL files, but has some minor limitations as Studio One ignores some information in the file. It would be great if Presonus added support for importing these extra small bits of information.
However, even with these minor limitations, all the material is there & in sync ready for post production mixing. So still really useful.
More info here..
Very nice tool. Thanks for sharing.
If you're interested, from a developer POV, you can write the Studio One song format from scratch, the literal song format. It's all xml. The only somewhat tricky part is managing the cross references for the media UID's for the media pool. I did that in Visual Basic, converted a few text based song formats (Reaper, Ardour, etc) directly to Studio One song format, and it worked although my initial coding approach was somewhat clunky, not being a highly skilled developer.
I'll have a go at it again later and do it better. The best approach, once you study the layout of the xml files in a Studio One song package, is to create a Studio One song class that has all of the objects and properties for all of the data and parts represented that a song requires, then fill those objects in the class up with any data from anywhere, write the xml files to disk and zip them up into a song package. Doing that will translate - way - more song settings than OpenTL.
Example class: Needs work. https://github.com/ExpressMix/Read-Song ... g_Class.vb
Users browsing this forum: No registered users and 4 guests