At the moment we use MusyngKite. There is also FatBoy, FluidR3_GM and now Tabla.

Audio.SoundFont.Melody.Maker toMelody has the signature:

   toMelody :: Midi.Recording -> Melody

with a preset phrase length for the Melody of 0.6s.

we should instead use

   toMelody :: Number -> Midi.Recording -> Melody

to allow the user to specify the phrase length. This influences the responsiveness of 'play' buttons in audio players, which can only interrupt the melody after each phrase has played.

And when we do this, resolve the conflict over which version of purescript-typelevel-prelude to use. It seems to me that this conflict is brought in by references to purescript-quickcheck from purescript-test-unit but I don't understand why this causes the problems it does at the moment.

This is what the example uses (it calls it note) but midiNote should really be in the main library.

Hi @newlandsvalley,

I tried deploying chord-editor to jgart.whereis.xn--q9jyb4c for testing but the audio does not work because of the following errors:

Content Security Policy: The page’s settings blocked the loading of a resource at https://gleitz.github.io/midi-js-soundfonts/MusyngKite/acoustic_guitar_steel-ogg.js (“default-src”)

SourceHut Pages is blocking the downloading of external resources like the one specified on this line:

I found an issue regarding publishing midijs as an npm module. It sounds like midijs is abandonware but mscuthbert published a module on the npm registry.

What do you think of using mscuthbert's published module on npm instead of downloading the fonts off the internet?

or else host then locally on your own server.

The README mentions two possibilities for loading the soundfonts but a third possibility would be to be able to load them in the context of a service that does not grant you access to the server. If that service restricts downloading external resources then the user of purescript-soundfonts will not be able to use the library in that deployment environment as demonstrated with jgart.whereis.xn--q9jyb4c. I think that using npm to install the soundfonts would resolve this issue.

What do you think?

You obviously can't play a rest, only a note. However, some clients would benefit by having the option to 'play' a rest as a no-op. This would allow them to emit both notes and rests that are generated from a score and have the final group of notes/rests paced properly.

This is easily achieved by using a MIDI pitch (note id) of less than or equal to zero to represent a rest. In which case, the playNote effect would simply return the duration of the unplayed note (instead of returning zero as an error indication as happens at present). In particular, this would benefit purescript-abc-melody.

and instead rely on the definition now in purescript-midi.

This must wait until purescript-midi is upgraded to Aff 4.0.0

(Currently 9.0.0)

playPhrase will be identical to playNotes except that it also invokes delay for the duration of the phrase. This allows an array of phrases to be paced properly. playMelody will thus simply traverse the array of phrases.

At the moment I use middle C = C5. However this seems to produce melodies an octave higher than I would expect. I think danigb used middle C = C4 - I should change to this to ensure compatibility. This is what danigb's JavaScript player used.