-
Notifications
You must be signed in to change notification settings - Fork 19
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
Internal MIDI Interface? #3
Comments
I have now downloaded this project, and am going to see if I can isolate the SoundFont synth myself. |
I'll be watching any updates and will post findings if I make progress when I get to work on it. As noted in the issue I raised, it would be of value to know if the synth can be used without https. The app source posted by Ryoya on that issue may perhaps be useful for that purpose |
Sorry for late reply. I can not have confident that I am answering your question correctly, but I think this would be the isolated style. |
I'm afraid the links don't help much. The coding level is too high! :-) I've been digging about in your smfplayer code, and see that you are using logue's code from I want to create a GitHub repository whose purpose is to define an interface for software SoundFont synthesizers, and I want to use the logue synth code in the first implementation of that interface. Using a concrete example should help me develop the interface, and at the same time provide a working synth that can easily be included on any website. I'm hoping that:
|
Sorry that I did not explain in detail. <wm-webmidilink targetsynth="[URL]" width="[width]" height="[height]" linklevel="[0 or 1]"></wm-webmidilink>
So what the developer must do to use virtual Web Audio Synth with
And what those who wants to develop virtual Web Audio Synth need to do is simply to support Web Midi Link. For example: <wm-webmidilink targetsynth="http://logue.github.io/smfplayer.js/wml.html"></wm-webmidilink> Web Components(Polymer) is a part of the "Extensible Web", so it would be the standard way to extend Web API in near future. And if these steps are still difficult for the developer, I guess Web Audio/MIDI API is also difficult for that developer. |
The problem there is that I really need to get rid of the synth's GUI. Parameters like width and height are referring to something inessential, that has to be removed. I'm currently writing a minimal host (GUI) for the (GUI-less) logue synth. Maybe I'm going to fail with egg all over my face, but I currently don't think that's going to happen. Lets wait and see... |
I am looking forward to see your GUI-less synth. But.... my understanding is right, are you saying that Web Audio virtual synth without GUI is much easier to write for developer? Yes, I agree that. However, how can users, who are using web site that has Web Audio virtual synth, know what is happening with Web Audio virtual synth during playing? And how can users change the parameters of Web Audio virtual synth? And By the way, I added |
The synth is loaded into a host app that provides the GUI.
Using the host application's GUI. The host interacts with the synth via the internal interface. Its up to the host to decide what users can and cannot do. Its really very simple. :-) |
OK, now I may understand what you are trying to do. You are trying to define only interface between host app and the web audio synth. It sounds something new. So the point of your proposal is to separate GUI and sound algorithm, and let host app developer to implement their original GUI with that sound algorithm. So the between yours and |
Yes, that's right. |
Thanks Ryoya! In #2, you said:
That's exactly what I'm going to do. Your recommendation comes at exactly the right moment. Sorry I'm running a couple of days later than announced. Will definitely publish something during the coming week. |
Hi Ryoya, |
Would it be possible to separate this project's GUI (Graphic User Interface) from its synth code, using an interface like the one I describe at [1]?
I have my own GUI, and would just like to use the synth. :-)
My proposed interface is, of course, just a sketch. Maybe you have other ideas about how to do this?
Very best wishes,
James
[1] WebAudio/web-midi-api#154
The text was updated successfully, but these errors were encountered: