Overview	DATA	PROCESS			OPTIONS, SETTINGS, & ABOUT
		FEATURE + VISUALIZATION	PATTERN	CONVERT

The CONVERT tab

In the CONVERT tab, you can define the parameters for converting melodies to different file formats

• MCSV1 format (mcsv)

• MCSV2 format (mcsv2, new since v1.2)

• MIDI format (midi)

• Lilypond format (ly, new since v1.2)

• Notes (simple onset/pitch format as used by Temperley, notes)

• SQLITE/WJAZZD format (database)

The set of melodies to convert is defined by the DATA tab. You can start melconv using the Start Processing button in the bottom and open the result folder using the Open Result Folder button. Note: You can define the output directory via the OPTIONS, SETTINGS, & ABOUT tab.

Note

A more detailed description of melconv functionality can be found here here.

Note

Since version 1.2. of the MeloSpyGUI, converted files will be written to the subfolder data/converted of your installation. Setting the output path in the options tab will not affect this behavior.

Here is a screenshot of the midi output format in the program:

Each output format has a different set of optional parameters, common to all is the transpose parameter which let you specify a global transposition (in semitones) for the melodies, e.g., transposition by an octave.

Output format parameters

Output format	Parameter	Description
midi	Tempo	Here you can specify the tempo of the MIDI file by specifying either a BPM value or using auto (default), which will reproduse the tempo of the source file.
midi	Quantize	If set to True the MIDI onsets will be quantized.
midi	Quantize Duration	If set to True also the MIDI duration will be quantized.
midi	Ticks per Beat	By default, the converter module uses an optimal ticks per beat value, which in some exceptional cases might be too large for the MIDI format. In this case, the melody will be re-quantized using the value as specified here. If the field is left empty, a value of 64*9*5*7 = 20160 will be used. (NB: The problem is that commercial notation programs such as Finale and Sibelius always use their own (sub-optimal) quantization procedure even for perfectly quantized MIDI files, which occasionally results in undesired effects. For these cases, forcing a specific ticks per beat value here might be a remedy.
mcsv	–	–
mcsv2	Transpose	Transposes output the specified number of semitones
mcsv2	Annotations	Annotations to be included in the output as a comma-separate list. Options are: phrase, chorus, chord, form, idea, which will result in the addition of corresponding row-wise labels
mcsv2	Loudness	True or False. If set to True also loudness values are included, only available for solos transcription fromt he Weimar Jazz Database
mcsv2	Separator	Semicolon, Comma or Tab. The field separator to be used in the output CSV files.
mcsv2	Decimal	Dot or Comma or Tab. The decimal separator to be used in the output CSV files (do not combine decimal point comma with a field separator comma).
mcsv2	Beat Track	True, False or Only. If set to True, actually two files will be generated. The melodic content and a file containing a CSV representation of an annotated beat track (only available for Weimar Jazz Database=. If set to only, only the beat track will be exported, but no melody files.
notes	Annotate Phrases	Adds a column with binary markers for phrase beginnings (1=start of phrase, 0=in phrase).
notes	Include durations	Adds a column with duration values.
notes	Include note offets	Adds a column with note offsets.
notes	Pitch first	Writes pitches insted of onsets in the first column
database	Path to SQLITE3 file	Full qualified path of target database (mandatory).
database	Metadata file	Absolute path to an Excel file with meta data (only for SV → WJazzD, optional).
database	Directory with loudness annotations	Absolute path to a directory with loudness data (only for SV → WJazzD, optional).
lilypond	Transpose	Transposes output the specified number of semitones.

Next part: OPTIONS, SETTINGS, & ABOUT tab