Shared eventEmitter

[igorjacauna]

I'm building a multitrack app, and I wish to known if is it possible to have a shared EventEmitter to centralize the time update and other actions for each instance of Peaks.js

Maybe passing in options:

import EventEmitter from 'eventemitter3';

const myEventEmitter = new EventEmitter();

const myPlayer = new MyPlayer(myEventEmitter);


// And for each track in Multitrack that will belongs to a Peaks instance
Peaks.init({
  eventEmitter: myEventEmitter,
  player: myPlayer
});

I had think in make a PR but I thought that was better before to ask if is it possible or have any limitation to implement it

[chrisn]

This sounds interesting... there was a previous discussion in #432. Are you using multiple Peaks instances, for each track? I wonder if it's possible to ensure they're synchronized by using a shared player object. I suggest trying that before considering a shared EventEmitter - it could be that some events still need to be specific to each Peaks instance.

[chrisn]

Thank you, that's really helpful. I'll take a look.

[thom4parisot]

If I understand well, the player provides independant interaction controls to the same audio source. And because Peaks reacts to standard HTML5 audio events, the player acts as a separate interface which is reflected as waveform updates as well.

[chrisn]

Yes, the Player interface is there to decouple the Peaks.js UI objects from the media player. The UI responds to player.* events emitted by the player, but otherwise doesn't know whether it's using a WebAudio AudioContext or an <audio> or <video> element or something else.

[chrisn]

I made this example to show how it might work. This is based on the external player demo page, so uses Tone.js.

[igorjacauna]

Thanks @chrisn, I will try with Tone.js and come back here with results soon

[igorjacauna]

Thats awesome @chrisn , it's working like a charm!

I updated the little project with this example

[chrisn]

Thanks! I'm just trying it out here with some multitrack recordings I found...