New MIDI file for midi opcode examples (and replace FLTK examples)

[AsterixMusic]

most of the examples that use FLTK are midi opcodes. I suggest to have 1 standard midi-file with "all" kind of message, with related list. Ex: channel 1: 4 notes with different velocity channel 2: 1 note with control change channel 3: 2 control change channel 4: 2 notes - 1 program change - 2 notes channel 5: ..... ........ ........

This file could be useful to test also all the MIDI opcodes. midi_Csound.mid.zip

[csounder]

excellent idea.

• can you share a .csd file that works currently with this proposed standard MIDI file.

- dB

Dr. Richard Boulanger

Professor

Electronic Production and Design

Berklee College of Music

Professional Writing & Technology Division

On Sun, Jul 11, 2021 at 4:27 AM Stefano Cucchi @.***> wrote:

most of the examples that use FLTK are midi opcodes. I suggest to have 1 standard midi-file with "all" kind of message, with related list. Ex: channel 1: 4 notes with different velocity channel 2: 1 note with control change channel 3: 2 control change channel 4: 2 notes - 1 program change - 2 notes channel 5: ..... ........ ........

This file could be useful to test also all the MIDI opcodes. midi_Csound.mid.zip https://us-west-2.protection.sophos.com?d=github.com&u=aHR0cHM6Ly9naXRodWIuY29tL2Nzb3VuZC9tYW51YWwvZmlsZXMvNjc5NjU2Ni9taWRpX0Nzb3VuZC5taWQuemlw&i=NWYxNzBkMDNiNTVmZGEwZmIyNjczYmRm&t=WVdjcWNPaUw0TVdKK0lwSlZVb2lONmxqZmR3b1RhYThleHF0TzhZcTV6Zz0=&h=5381524643fe45138141e0bcf3d05554

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://us-west-2.protection.sophos.com?d=github.com&u=aHR0cHM6Ly9naXRodWIuY29tL2Nzb3VuZC9tYW51YWwvaXNzdWVzLzU2MA==&i=NWYxNzBkMDNiNTVmZGEwZmIyNjczYmRm&t=ZnJONEVPRlVGdFgxNVVHMHVPWmFWajJpL1pOai9pa3pQSENSQ2o4cGpTND0=&h=5381524643fe45138141e0bcf3d05554, or unsubscribe https://us-west-2.protection.sophos.com?d=github.com&u=aHR0cHM6Ly9naXRodWIuY29tL25vdGlmaWNhdGlvbnMvdW5zdWJzY3JpYmUtYXV0aC9BQUxXWUZTRUtNQVZMRFNWTFBCNE5JVFRYRklZREFOQ05GU001QUZDQVlCUQ==&i=NWYxNzBkMDNiNTVmZGEwZmIyNjczYmRm&t=K3BpZzJZTzdvUUJ4M3g1bFcvNllJYkJPUTlxVHgydnk5N1laempSTG1KST0=&h=5381524643fe45138141e0bcf3d05554 .

[AsterixMusic]

Not yet, me and Menno are still looking for all the data we need to put on this MIDI file:

Polyphonic aftertouch sustain pitch bend … ... I’m thinking about 1 big example with many instruments, one instruments every message.

Ex:

Instr 1: fey notes Instr 2: control change Instr 3: polyphonic aftertouch Instr 4: Program change Instr 5: … Instr 6: …

Do you think it’s a good idea, or it’s better to think about many examples

---

Stefano Cucchi I.T.B. Project Studio Viale Europa 15, 20088 Rosate (Mi) Tel: 3402601621 www.itbprojectstudio.com Mail: @.***

On 12 Jul 2021, at 02:25, csounder @.***> wrote:

excellent idea.

• can you share a .csd file that works currently with this proposed standard MIDI file.

- dB

Dr. Richard Boulanger

Professor

Electronic Production and Design

Berklee College of Music

Professional Writing & Technology Division

On Sun, Jul 11, 2021 at 4:27 AM Stefano Cucchi @.***> wrote:

most of the examples that use FLTK are midi opcodes. I suggest to have 1 standard midi-file with "all" kind of message, with related list. Ex: channel 1: 4 notes with different velocity channel 2: 1 note with control change channel 3: 2 control change channel 4: 2 notes - 1 program change - 2 notes channel 5: ..... ........ ........

This file could be useful to test also all the MIDI opcodes. midi_Csound.mid.zip https://us-west-2.protection.sophos.com?d=github.com&u=aHR0cHM6Ly9naXRodWIuY29tL2Nzb3VuZC9tYW51YWwvZmlsZXMvNjc5NjU2Ni9taWRpX0Nzb3VuZC5taWQuemlw&i=NWYxNzBkMDNiNTVmZGEwZmIyNjczYmRm&t=WVdjcWNPaUw0TVdKK0lwSlZVb2lONmxqZmR3b1RhYThleHF0TzhZcTV6Zz0=&h=5381524643fe45138141e0bcf3d05554

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://us-west-2.protection.sophos.com?d=github.com&u=aHR0cHM6Ly9naXRodWIuY29tL2Nzb3VuZC9tYW51YWwvaXNzdWVzLzU2MA==&i=NWYxNzBkMDNiNTVmZGEwZmIyNjczYmRm&t=ZnJONEVPRlVGdFgxNVVHMHVPWmFWajJpL1pOai9pa3pQSENSQ2o4cGpTND0=&h=5381524643fe45138141e0bcf3d05554, or unsubscribe https://us-west-2.protection.sophos.com?d=github.com&u=aHR0cHM6Ly9naXRodWIuY29tL25vdGlmaWNhdGlvbnMvdW5zdWJzY3JpYmUtYXV0aC9BQUxXWUZTRUtNQVZMRFNWTFBCNE5JVFRYRklZREFOQ05GU001QUZDQVlCUQ==&i=NWYxNzBkMDNiNTVmZGEwZmIyNjczYmRm&t=K3BpZzJZTzdvUUJ4M3g1bFcvNllJYkJPUTlxVHgydnk5N1laempSTG1KST0=&h=5381524643fe45138141e0bcf3d05554 .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/csound/manual/issues/560#issuecomment-877888053, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQLYSASUUPWYXA5GHGCMXVLTXIZATANCNFSM5AFCAYBQ.

[csounder]

Yes, this is an excellent plan, with one larger .csd file that shows how (in individual instruments) each of these MIDI messages might be interpreted, mapped, used. This would make a great "supermodel" for students especially.

- dB

Dr. Richard Boulanger

Professor

Electronic Production and Design

Berklee College of Music

Professional Writing & Technology Division

On Mon, Jul 12, 2021 at 4:34 PM Stefano Cucchi @.***> wrote:

Not yet, me and Menno are still looking for all the data we need to put on this MIDI file:

Polyphonic aftertouch sustain pitch bend … ... I’m thinking about 1 big example with many instruments, one instruments every message.

Ex:

Instr 1: fey notes Instr 2: control change Instr 3: polyphonic aftertouch Instr 4: Program change Instr 5: … Instr 6: …

Do you think it’s a good idea, or it’s better to think about many examples

---

Stefano Cucchi I.T.B. Project Studio Viale Europa 15, 20088 Rosate (Mi) Tel: 3402601621 www.itbprojectstudio.com Mail: @.***

On 12 Jul 2021, at 02:25, csounder @.***> wrote:

excellent idea.

• can you share a .csd file that works currently with this proposed standard MIDI file.

- dB

Dr. Richard Boulanger

Professor

Electronic Production and Design

Berklee College of Music

Professional Writing & Technology Division

On Sun, Jul 11, 2021 at 4:27 AM Stefano Cucchi @.***> wrote:

most of the examples that use FLTK are midi opcodes. I suggest to have 1 standard midi-file with "all" kind of message, with related list. Ex: channel 1: 4 notes with different velocity channel 2: 1 note with control change channel 3: 2 control change channel 4: 2 notes - 1 program change - 2 notes channel 5: ..... ........ ........

This file could be useful to test also all the MIDI opcodes. midi_Csound.mid.zip < https://us-west-2.protection.sophos.com?d=github.com&u=aHR0cHM6Ly9naXRodWIuY29tL2Nzb3VuZC9tYW51YWwvZmlsZXMvNjc5NjU2Ni9taWRpX0Nzb3VuZC5taWQuemlw&i=NWYxNzBkMDNiNTVmZGEwZmIyNjczYmRm&t=WVdjcWNPaUw0TVdKK0lwSlZVb2lONmxqZmR3b1RhYThleHF0TzhZcTV6Zz0=&h=5381524643fe45138141e0bcf3d05554

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub < https://us-west-2.protection.sophos.com?d=github.com&u=aHR0cHM6Ly9naXRodWIuY29tL2Nzb3VuZC9tYW51YWwvaXNzdWVzLzU2MA==&i=NWYxNzBkMDNiNTVmZGEwZmIyNjczYmRm&t=ZnJONEVPRlVGdFgxNVVHMHVPWmFWajJpL1pOai9pa3pQSENSQ2o4cGpTND0=&h=5381524643fe45138141e0bcf3d05554 , or unsubscribe < https://us-west-2.protection.sophos.com?d=github.com&u=aHR0cHM6Ly9naXRodWIuY29tL25vdGlmaWNhdGlvbnMvdW5zdWJzY3JpYmUtYXV0aC9BQUxXWUZTRUtNQVZMRFNWTFBCNE5JVFRYRklZREFOQ05GU001QUZDQVlCUQ==&i=NWYxNzBkMDNiNTVmZGEwZmIyNjczYmRm&t=K3BpZzJZTzdvUUJ4M3g1bFcvNllJYkJPUTlxVHgydnk5N1laempSTG1KST0=&h=5381524643fe45138141e0bcf3d05554

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/csound/manual/issues/560#issuecomment-877888053>, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AQLYSASUUPWYXA5GHGCMXVLTXIZATANCNFSM5AFCAYBQ .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://us-west-2.protection.sophos.com?d=github.com&u=aHR0cHM6Ly9naXRodWIuY29tL2Nzb3VuZC9tYW51YWwvaXNzdWVzLzU2MCNpc3N1ZWNvbW1lbnQtODc4NTc2NTg5&i=NWYxNzBkMDNiNTVmZGEwZmIyNjczYmRm&t=Z25hMEtxMnJkeHhXV3grVEtCcmxXK0psVGlFbTBweUFXVFNodnhuSVFmND0=&h=37737cf208054a42bda7c024923e4f07, or unsubscribe https://us-west-2.protection.sophos.com?d=github.com&u=aHR0cHM6Ly9naXRodWIuY29tL25vdGlmaWNhdGlvbnMvdW5zdWJzY3JpYmUtYXV0aC9BQUxXWUZXNFNMTFFSVUtQNkdSWlZDRFRYTkdWVkFOQ05GU001QUZDQVlCUQ==&i=NWYxNzBkMDNiNTVmZGEwZmIyNjczYmRm&t=MS9zZmZnYTdMVjVJajdBRHI1VWJwR2FGTE1pK3JXNEoxckdhbjFZSnI5dz0=&h=37737cf208054a42bda7c024923e4f07 .

[tjingboem]

the idea of having 1 'big' Midi file that should cover the replacement of all FLTK Midi instruments has yet another advantage; if we find, along the way, that a new CC or sysex should be added because an example requires this due to the particular Midi opcode, we can simply make this addition to an existing Midi channel or create a new Midi channel for it. And then save it under the same name, so older new Midi examples continue to work. If we re-use one and the same Midi file name for such changes, we do not need to get back to already existing Midi FLTK replaced examples.

Each new Midi example should be able to extract its useful information from a certain channel. I believe Midi Out can have 64 channels, Midi In has 16? Not sure...

Ex: channel 1: 4 notes with different velocity channel 2: a few chords with different velocity channel 3: 1 note with control change channel 4: 1 chord with control change channel 5: 2 notes - 1 program change - 2 notes channel 6: a known melody channel 7: lots of CCs and sysex ........ ........ lots CCs and sysex could be added to channel 7 for example, so it can play the notes from midi channel 1 or 2, and get its CCs from midi channel 7? Or use the 'preset' from channel 1 or 2 or 6...