Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should WAM Controller speak directly to Web Midi Port? #4

Open
olilarkin opened this issue Oct 2, 2018 · 2 comments
Open

Should WAM Controller speak directly to Web Midi Port? #4

olilarkin opened this issue Oct 2, 2018 · 2 comments

Comments

@olilarkin
Copy link
Member

Seems odd to me that the WAM controller should know about the port.

set midiIn (port) {

@jariseon
Copy link
Member

jariseon commented Oct 2, 2018

wams are different from desktop plugins in the sense that there might not be a host at all: a wam may be integrated into a web app directly, and therefore it "plugs in" with Web Midi API (as well as Web Audio API).

@olilarkin
Copy link
Member Author

Could a WAM not be a MIDI processor, like you can have say a VST arpeggiator? I think this would be nice, especially if we sort out timestamped MIDI messages. I don't think WAMs should talk directly to the WebMIDI ports. VirtualCZ.io needs to output MIDI (sysex) so i will add WAMController.midiOutPort for now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants