dawproject

The implementation is quite simple actually because you can start with the basics and add more features later. For example you could just implement trackname, notes, CC and channel, and the importer in Studio One and Bitwig would use that info and nothing else. You don’t need to implement all the xml. Using a decent AI makes this quite easy as it can write the script and it’s easy to debug.

Managed a build a decent .dawproject converter based on .mid files exported from Synfire. It sets all the vst3 plugins for each track as Vienna Ensemble Pro Event. 

However, what’s stumped me is how to export the .vstpreset data from Synfire.

EDIT: If I can get this working with track channels and vstpresets, then I’ll upload the whole code to Github for anyone to use.

Yes, getting midi over to Studio One is simply a case of drag and dropping the .mid file LOL!

It's when implementing the VST3 plugins that it starts to become helpful. But I can't seem to set track midi channel in Studio One, and there seems absolutely no way to programmatically get plugin data out of Synfire without using drones.

EDIT: Here is the github repository for the code: (https://github.com/ruchirlives/dawproject)

Here is the structure of the code in case it helps:

Here's an annotated outline of the code, with personal folder locations removed:

I. Import necessary libraries
  A. lxml for XML processing
  B. midifunctions for MIDI file processing
  C. zipfile for creating ZIP archives
  D. os for file and directory operations
  E. vstanalyser for modifying VST3 preset files

II. Define global variables
  A. deviceID for the Vienna Ensemble Pro Event VST3 plugin

III. Function: process_musicxml(musicxml_file)
  A. Parse the MusicXML file
  B. Create a list of devices for parts in the MusicXML
     1. Extract part ID, part name, device, and channel information
  C. Create a list of tracks for parts in the MusicXML
     1. Extract part name, device, and channel information
  D. Return the list of tracks

IV. Function: create_project_file(miditracks)
  A. Create the root element for the new XML
  B. Create the Application element
  C. Create the Structure element
     1. Iterate over the MIDI tracks
        a. Extract metadata (track name, channel, instrument name)
        b. Create Track, Channel, Devices, and Vst3Plugin elements
        c. Create the State element for the VST3 plugin
  D. Create the Arrangement element
     1. Create Lanes elements for each MIDI track
        a. Create Clips elements
        b. Create Notes elements and populate with note information
        c. Extract and create Points elements for CC messages
  E. Return the project XML

V. Function: extract_cc_messages_lists(messages)
  A. Extract CC messages from the MIDI messages
  B. Group CC messages by controller number
  C. Return a list of CC message lists

VI. Function: validate(projectxmlfile)
  A. Create an XML schema validator using the XSD schema
  B. Validate the project XML against the XSD schema
  C. Print validation results

VII. Function: create_dawproject_archive(project, name)
  A. Save the project XML file
  B. Create the plugin folder
  C. Create a ZIP archive (.dawproject file)
     1. Add the project XML file to the archive
     2. Add the plugin folder and its contents to the archive
  D. Return the paths of the XML file and .dawproject file

VIII. Function: create_plugin_folder(midi_file)
  A. Create a folder for the VST3 plugin
  B. Iterate over tracks in the MIDI file
     1. Create a VST3 preset file for each track
     2. Save the preset file in the plugin folder
  C. Return the plugin folder path

IX. Function: convert(midi_file)
  A. Load the MIDI file
  B. Extract the name from the file path
  C. Create the project XML using create_project_file()
  D. Create the .dawproject archive using create_dawproject_archive()
  E. Validate the project XML using validate()

Also cockos reaper users, as they already have a dawproject converter implemented. So for now, studio one, bitwig and reaper.