processing / processing/p5.js-compatibility

p5.sound.js migration guide

Open
#33 2 comments 0 reactions 1 assignee View on GitHub

@ksen0 is already working on this.

Since Dec 16, 2025.

Dominant language
JavaScript
Stars
18
Forks
9
PR merge metrics
No merged PRs in 30d

Description

This 1.x/2.x compatibility/changelist repository doesn't mention the major changes to p5.sound.js that were part of the 2.x change. A migration guide, or even a list of changes would be very helpful.

I tried to migrate a 1.11.1 sketch I wrote awhile ago to 2.0.5, and have encountered nothing but confusion. I went to the Library Management popup and chose version 2.0.5. It turned off the p5.sound.js Add-on Library. I turned it back on, and it added a line to index.html for version 0.2.0 of p5.sound. The version seems to be going backwards! And it didn't work, giving an error "TypeError: p5.MonoSynth is not a constructor". There is a link on the Library Management "View the reference for p5.sound compatible with p5.js 2.0.5", which I clicked. The reference doesn't include p5.MonoSynth, so is that deprecated? What do I use instead? (For this issue, that question is rhetorical; I share my experience to illustrate the need for a migration guide. Though if someone has an answer, I might try the migration again.)

If a p5.sound migration guide isn't coming anytime soon, at least mention that it has changed significantly in the list of 2.x changes.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.