matter-js VS webaudio-examples

Do you think this worked so cleanly because there is a tutorial similar to this and its in the dataset?

https://github.com/liabru/matter-js/wiki/Tutorials

If you don't want to create your own physics engine, there are also existing ones like matter.js.

A physics engine for the basic stuff (colisions with the terrain, gravity, rigid body mechanics, suspension springs...) would be great and I think Matter.js it's a great option

Another option is to add a third-party physics library such as Matter.js, although setting up and integrating the physics library can be tricky. If you need physics in your game, especially more complex physics effects, Phaser is a better choice.

I have created a demonstration for liquid (or gooey) effect on HTML Canvas using Matter.js and SVG Filters.

I recently came across this library: https://github.com/liabru/matter-js

This was a bold faced lie. Matter.js has no continuous collision detection. You wasted so much of my time I hope you are mildly inconvenienced in the near future! https://github.com/liabru/matter-js/issues/5

https://github.com/liabru/matter-js/issues/243 was a bit confusing. The solutions in this thread don't seem to work for me, and i cant find any information elsewhere.

Over half of the source code is just making the robots exist. If you haven't used matter.js before, you can download it here. You can read the whole documentation here, but the functions we will need are:

In this article, we'll explore three essential terms in the Web Audio API for our project. For more in-depth information, visit MDN Docs.

Exhausted and having tried out various approaches without much success, I decided to give Web Audio API a try. While it appeared slightly harder to work with, I was frankly running out of options. All that said, moving from HTML5 Audio to Web Audio API involved quite a fair bit of changes and experimentation.

MDN Web Audio Doc

I found the wikipedia article [1] on the subject to be helpful to understand a little bit whats going on here.

I wonder if there's more performant wasm implementations that can interface with the WebAudio API [2]? Quick search brings up things like [3]

[1] https://en.wikipedia.org/wiki/Frequency_modulation_synthesis

[2] https://developer.mozilla.org/en-US/docs/Web/API/Web_Audio_A...

[3] https://github.com/a-cordier/wasm-audio

Feel free to refer to the official documentation to learn more about the Web Audio API.

You can see details on how to implement this API in your application, including the interfaces that it extends, the necessary permissions, browser compatibility, and much more on its MDN page.

As part of my effort to remake my old Artsy demo in more modern JavaScript, I decided to start with the music player. The original Amiga demo from 1993 used the SoundTracker MOD format, but my remake from 2013 uses an MP3 file, which was a bit of a cheat. Playing an MP3 is efficient and requires almost zero code, but it's not very interesting. Also, it requires loading several megabytes of data. So I decided to try to make a MOD player from scratch, using only the Web Audio API

After taking a good look through the Web Audio API documentation, I decided that the best way for my synthesizer to output sound to the speakers was through the use of the AudioWorkletNode combined with an AudioWorkletProcessor. This combination of two nodes would allow me to generate audio in a background thread which could then be played through the speakers.

Let us take a look at various concepts behind Web Audio API.