41–49 of 49 posts
Creator here - thanks for the feedback! For anyone interested on the stack, the visual part is React / Redux SPA. I use Firebase's Firestore as a DB (I wanted to try it and so far it's really cool) and Google Cloud Functions for the APIs. The repo is hosted on Gitlab and is a Lerna monorepo, which is amazing.
Very cool! Is there a link to the repo? I didn't see one...
Earlier quoted context omitted.
That's really cool and I'll surely consider it for future releases. I'm trying to sort out the priorities for this project and the feedback on HN is amazing. Thanks.
No problem. Your app is really cool! I really have to compliment you on the design/ux too. Clean, easy to look at, and minimal futuristic. I look forward to seeing more! Do you have a github or a blog I can follow? I didn't see anything in the info on your site.
The blog is a WIP, I would like to blog about Audio DSP with maybe code examples hosted on the worklet editor. I just need to find the time.
My GitHub repo is cristiano.belloni, but I don't really use it - I normally use GitLab these days, and most of my repos are private for one reason or another. I'll probably open some of them, but only if I know there is interest and I can maintain them properly.
Earlier quoted context omitted.
As soon as browser support the standard, the message will be shown less and less. Chrome was an early adopter, but Audio Worklets are part of a W3C working draft, which is the de facto standard for web audio: https://www.w3.org/TR/webaudio/
Calling it a standard might be jumping the gun. from your very link > Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
Earlier quoted context omitted.
For now, yes. But, since the app is based on a standard spec, other browser will hopefully support Web Audio Worklets soon. > — Please note that the app runs only on Chrome > v66, for > now, because Chrome is the only browser implementing the > Audio Worklet[1] spec. Other browser will follow suit > (hopefully) soon [1] https://developers.google.com/web/updates/2017/12/audio-work...
Just to be clear, Audio Worklet is not "a standard spec". It's an earlyish-stage spec proposal which might well change as it goes through the standardization process.
This is cool and looks promising! If you want some DSP functions in JS, I had made some[0] in the past. They're all MIT licensed and sometimes you would need to adapt the code a bit because of the imports and globals that are implicit as these were domain specific. [0]: https://github.com/opendsp
This is cool and looks promising! If you want some DSP functions in JS, I had made some[0] in the past. They're all MIT licensed and sometimes you would need to adapt the code a bit because of the imports and globals that are implicit as these were domain specific. [0]: https://github.com/opendsp
That is a goldmine, thanks!!
Earlier quoted context omitted.
Have you considered using Open Sound Control[0]? There is a nice JS package for it. I've put together a couple demo web apps using OSC as both client and server. Bonuses include that you get midi with it, it creates RESTful 2 way interfaces for your endpoints, can be shared over the internet (WebRTC), and it's universally easy to hook to other stuff! Also there is a FANTASTIC customizable interface app for iOS and An…
shameless self-promotion: I work on a free software OSC sequencer: https://ossia.io