Hi, I am trying to export a chord partial analysis of up to 20 partials using Partiels to use them in Openmusic. However, when I try to export as sdif file it prompts me to enter the Frame Signature, Matrix Signature and Column name, otherwise, it won’t export, based on previous knowledge I know that 1TRC should be the frame signature for harmonic analysis but I tried and it did not work out, does anyone know what should I put in for those parameters?
Thanks a lot.
Hello,
The SDIF support in Partiels is mainly there for compatibility with some old usages and documents, but it is very limited, particularly for exporting data. I recommend that you use a more open file format, such as CSV or JSON.
Best regards,
Pierre
Hi, Guillot,
Thank you for your rapid response, just saw it. Appreciate it very much! However, the main reason why I want to use SDIF file is because when I do the partial analysis, it exports 20 files and I know how to combine the SDIF files in open music but not sure about the other files. Is there a workaround for the other files too?
1 Like
Here is a thread related to a related issue (regarding CSV) that might be useful: How to import data from Excel. Otherwise, you can find information about the SDIF format here: SDIF Standard Description Types. I think you have to define both the frame and matrix signatures.
Thank you, will check it out and see if it works!
Thank you for the information. I understand the suggestion to use more open formats like CSV or JSON. However, I would like to clarify why this doesn’t fully address the specific need described above.
As michaelxu886 mentioned, the goal is to use the analysis output within OpenMusic and similar environments. In particular, several libraries and tools — including the as->om library from the IRCAM Repmus package — allow converting SDIF files containing partial tracking data into notation-oriented structures such as CHORD-SEQ objects.
To work correctly, these tools require the SDIF files to follow a specific structure, typically using frame and matrix signatures like 1TRC and 1TMI. This workflow was previously supported in AudioSculpt, which exported SDIF files directly in the required format. Since AudioSculpt is no longer maintained, many composers have turned to Spear to generate SDIF files compatible with these tools.
Based on my experience so far, I haven’t been able to export SDIF files from Partiels in a format that allows me to generate a CHORD-SEQ using the Repmus library in OM, even when entering the expected frame and matrix signatures manually. CSV and JSON formats are certainly useful in many contexts, but they don’t appear to be compatible with notation-based import tools such as as->om or others used in environments like OpenMusic, Bach, etc.
I don’t use OM, but it seems that some people use CSV results in OM (in this thread, for example). And using CSV in Max or Pd is very easy (there are example patches in Partiels).
If your goal is to use specific objects that only accept SDIF input, you’d better ask the people concerned to improve support for formats such as JSON or CSV. The SDIF format is in Partiels for minimal support and will never evolve (it may even disappear).
I understand the use of SDIF in the 2000s, but the code base and documentation are not updated or maintained. The format is inconsistent in many ways. Data typing is weak (anything can be done), but implementations expect specific types, which is paradoxical and leads to numerous problems with its integration and data interpretation.
I’m sorry if this means you have to change your workflow, but it is not advisable to rely on SDIF for sustainability and evolvability reasons.