Re: [fluid-dev] Chrome Native Client

[Matt Giuca]

I've actually been thinking about doing the same thing (although I haven't started or done any kind of feasibility study).

However, I know my way around NaCl/Pepper pretty well (I have been working with the Pepper team to add new APIs). I can't think of a reason why this would be a problem (other than perhaps different latency conditions under NaCl).

On Tue, Nov 12, 2013 at 4:32 PM, David Henningsson <address@hidden> wrote:

As for the technical details, I'm not an expert on browsers and browser

technology, but I see no reason why it wouldn't work if someone can
figure out how to get the MIDI data from the SDK to fluidsynth.

Getting the MIDI data to FluidSynth shouldn't be a problem. The obvious way would be to send the MIDI bytes from _javascript_ into FluidSynth, and then use the method I added to FS awhile back to load MIDI data from memory. The hard part would be wiring up FluidSynth's audio output to Pepper audio. (Doable, but requiring work and maintenance.)

I would also be interested in exposing the FluidSynth MIDI player API to _javascript_ via a Pepper messaging interface, so that the _javascript_ app can send raw MIDI events (not just whole files). I'd say the "wiring up to Pepper audio" part would be in scope for adding directly into the FluidSynth code base. But the latter part (building APIs to talk to _javascript_ via Pepper) would not be in the scope of FluidSynth; I think there should be a separate project that wraps FluidSynth and provides Pepper bindings.

Anyway, I'm not actively working on this now. If someone does work on this, I'd like to hear back on this channel. Also, please ask me if you have any NaCl/Pepper enquiries since I should be able to help.

Matt