On May 29, 2022, at 11:16 PM, Alexandre Torres Porres <porres@gmail.com> wrote:Em dom., 29 de mai. de 2022 às 11:17, Alexandre Torres Porres <porres@gmail.com> escreveu:I could do that too, of courseI opened a couple of issues that I ran into by revising the codeI now also realize I revised and rewrote a quile old version from 2010, which doesn't allow you to write meta or multi track, while there's a much newer one now that supports this...
I'm too far now to restart again from the new version :) my approach will also be different as I think it makes sense to write midi message as a continuous stream of data rather than lists (like cyclone/seq and else/midi do) so you can just connect vanilla's [midiin] into it and go! Well, I don't know how much I'll recycle from [midifile] for the MIDI writing now...cheersOn Sun, 29 May 2022 at 03:17 Dan Wilcox <danomatika@gmail.com> wrote:Why not help us fix them in midifile?On May 29, 2022, at 8:06 AM, pd-list-request@lists.iem.at wrote:Message: 2
Date: Sat, 28 May 2022 20:35:29 -0300
From: Alexandre Torres Porres <porres@gmail.com>
To: Pd-List <pd-list@lists.iem.at>
Subject: Re: [PD] Question About [Mrpeach/Midifile] Status
Message-ID:
<CAEAsFmgFa64w6Hb8BQr8R2AO5T6SM9FzVAgXkOn7EmsO1HxV7Q@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
by the way, I have my eyes on
https://github.com/pd-externals/mrpeach/issues/1 and will make sure if my
project based on midifile has the same issues or if I can get them fixed.