Clicking the label of All Instruments or Piano doesn't tick the checkbox

Most of the code was written as a prototype. Check it for readability and refactor where helpful.

thejazzpage.de has some good ones

This has been something I've wanted to do from the beginning, so I'm surprised I don't see an issue for it.

cycle-midi right now will send any notes it receives to the first instrument. It should also listen to notes from that instrument, and return a stream of them. This will allow a Cycle application to both write notes to an instrument and read notes from them.

Cycle's isolate

https://www.html5rocks.com/en/tutorials/security/sandboxed-iframes/

Right now, MIDIConvert has the same permissions as the rest of the background page. Since the background page doesn't have many permissions, this is probably OK. Still, it would be safer if the MIDI parsing happened in a sandboxed IFRAME, so we knew a malformed MIDI couldn't takeover the background page.

My PR has landed in MIDIConvert, so now it's time to use it in midicast.

e.g. percussion (channel 10)

The PLAY SONG button in the ENTER URL tab doesn't work if you paste into the field.

MIDI commands:

0xB0 0x07 0x00-7F: volume
0xB0 0x40 0x00-7F: sustain pedal
0xB0 0x43 0x00-7F: soft pedal
0xB0 0x42 0x00-7F: sostenuto pedal
0xB0 0x7B 0x00: all notes off
0xB0 0x78 0x00: all sounds off

Hi,

I'm working on an extension and would like to use/contribute to the cycle-extensions package, but it seems like it would make more sense if it had a repo to itself.

Any chance of that happening?

There are improvements that have been made to pundle since this was started (like automatically setting the debug flag). Upgrade and make the appropriate changes.

For instance:

• Checkbox
• TabbedPane
• Button
• ListItem

It can depend on snab-style.

manifest.json has some security settings disabled to make HMR work. We need a production-quality version.

What are the minimum necessary permissions? Can we defer asking for permission to
fetch until after a user does something?

midicast should be a browser_action rather than a page_action, to ensure the controls can be opened even when there are no MIDIs on the current page. Still, it would be a nice user experience for the icon to change when there are MIDIs available.

chrome.declarativeContent.SetIcon ought to be able to handle this, but it doesn't work with browser actions right now. Poke Devlin about this, and see when it's fixed. Then, use it.

i used to be able to use direct download links on the extention but now i cant i use midi cast to play songs in blob opera also when i click the play button after pasting the link it does not work also error in```
/> *// error in this line
<style>
@import url('/third_party/material-components-web/material-components-web.css');
@import url('https://fonts.googleapis.com/css?family=Roboto|Material+Icons');

If background.js and popup.js were individual bundles, we could do

"background": {
    "scripts": [
      "./dist/background.js"
    ]
}

instead of using the index.html background page. However, since Pundle only works on one entry (which is served from localhost), this would be hard to do without breaking the dev workflow.

(This was also advice from Devlin.)

e.g. channel, default instruments

https://developer.mozilla.org/en-US/docs/Web/API/Web_Storage_API/Using_the_Web_Storage_API

The timing sounds like it might be a bit off. Maybe the pulse is throwing it off?

Both background.html and popup.html are just empty containers for Cycle to render to. Can we consolidate them?

Right now, Cycle determines which components to render based on location.href. We'd need a different sigil to determine which to render.

Presently, the popup is empty on the new tab page because hostPageDriver fails on chrome: schemes. This should be fixed.

Right now, midicast defaults to channel 1. We should detect which channel a user's instrument uses.

A flow for detecting an instrument's channel:

• Play a different note on each channel.
• User repeats note, app deduces channel
• App plays a different note on only that channel.
• User repeats note to confirm correct channel.

Right now, we just scan for .mid files. For popular sites, we could support other URL formats:

e.g. midiworld.com and www.midis101.com

I think this is set up, but thejazzpage.de doesn't show songs in the popup.

After one song finishes, play the next one.

If the background page has an error, display it in the popup.

midiDriver could accept a stream of notes to send to an instrument and return a stream of notes from the instrument. This would make it useful independent of this particular extension.

It ought to be fairly simple to build a demo page that shows off the extension without users having to install it. You'd basically just need to link the message buses to one another and seed hostPage$ with links.

Pasting this track: http://thejazzpage.de/sounds/minorsw.mid doesn't work until you've selected a song from song scanner (e.g. from http://www.midiworld.com/liszt.htm) first.

Each has a specific signature for Sinks and Sources. Make specific type aliases for each one.

https://github.com/material-components/material-components-web/blob/master/packages/mdc-ripple/foundation.js

Related: #36

For instance, the tabbed pane could have its contents slide from left/right with an implied transition, while the indicator springs between tabs:

https://material.io/guidelines/components/tabs.html#tabs-specs

If a MIDI instrument isn't found, show Audio MIDI Setup directions in the popover.

The user ought to be able to bookmark songs into a library. Perhaps that library could persist across devices.

Can we use the enums to be more specific with our types?