Asynchronous after chordseq export

[siebenhirter]

Hello,
If an SMF is used that was converted from the ChordSequencer's (CS) internal memory to an SMF 0 using <EXPORT>, it will be corrupted.
It is non-reusable bcause running asynchronously with every loop.

In the internal memory the CS works with a track's timestamp, metadata, and start/stop commands. As long as memories data is used, or only saved in styles/songbook entries, the CS will function satisfactory. Only exporting creates an SMF with an error.

I select the style 6/8 PopRock with its CS-Progression and startet <Export> to convert CS-memory to an SMF 0 named 01-1.mid.
Note events can be seen on attachment "PianoRoll01-1.jpg" .

Note events will beginn at measure one, track one. But the track end in that SMF is entered after the note events of the penultimate chord with hex "FF 2F 00" and the note events of the last chord are written after this (see attachment HexEdit01-1a.jpg).

This does not appear to be a common MIDI standard. The Pa1000 thus creates faulty parameters in the note events of the last chord (see attachment Sequ01-1a.jpg). This faulty parameter – lengths D:000.00.000 – cannot be corrected using the sequencer's Event Edit.

Reusing this SMF after import (with conversion to metadata) has the fatal effect that the note events of the last chord are missing and that a loop is shortened by the original length of the note events of the last chord, thus no longer running synchronously with the style. The length of the last chord cannot be a whole bar, but it can also be any non-quantized length – and thus with every loop the CS runs asynchronously !

PS: About end of track, metaevents, delta time, track event --> https://people.carleton.edu/~jellinge/m ... Files.html