-
Notifications
You must be signed in to change notification settings - Fork 4
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
Overview of modified/deprecated functions from previous p5.sound? #45
Comments
hey @ffd8
let's chat about the deprecated methods in FFT and AudioIn some more |
Btw there's an issue here processing/p5.js-website#636 you can follow for the old methods still showing up on the site! |
|
Hey @ogbabydiesal and thanks for all your hard work! I couldn't help myself turning your spreadsheet into a table—I'm a bit obsessed with spreadsheets 😅—You can find my version here (see screenshot below). Note: I wasn't sure what the greyed out rows meant so I made it a checkbox (unchecked rows get greyed out via conditional formatting). Happy to give you edit access if you'd like to use it! |
@ogbabydiesal Thanks for the kind words 😊 I gave you edit access. Feel free to make changes and fix anything I misunderstood. And let me know if you need help with any of it. |
Congrats @ogbabydiesal and all involved in this revamp of p5.sound! I had last followed the refresh in 2023, but hadn't been following updates until the processing.org announcement today. I have a few small/big questions:
is there an overview of the major deprecated/removed/modified functions from previous p5.sound? I've read the Medium announcement, checked the references, checked editor examples, but can't find a sort of migration explainer for updating. While attempting to implement latest p5.sound into P5LIVE, the technique used for audio-reactivity the past 6 years stopped working, because I think plenty of changes occurred to both
p5.audioIn()
,p5.FFT()
(audioIn complains about missing methods likegetLevel()
and FFT complains aboutsetInput()
andlogAverages()
... would be very helpful if the FES for any broken p5.sound functions pointed to that resource, since it's likely to happen a lot for any sketches older than 2024. Here's my audio-reactive template – any insights for updating it would be appreciated.name is the same to before, however the versioning was reset, currently at 0.10.0 – guessing this will be an issue as it develops or reaches a 1.0 status? The last release of the old p5.sound made it to 1.0.1 (or 1.0.3?). Using 2.0.0+ would make it more clear that functions have been dropped entirely and others work differently than before?
would be helpful if the minified version included a similar timestamp/version header for keeping track of which version one adds to a project:
/** [p5.sound] Version: 1.0.1 - 2021-05-25 */
FYI, finding false references, which is likely known. I was attempting to read up on the difference of how the p5.FFT would work – wished there were more tiny demos for some of the methods that previous version had, then when trying to get the overview, saw that things like polySynth() are still active, yet causes an error as the method doesn't exist (which tells me new p5.sound is used on refs page). Maybe there's plans to reimplement polySynth and others?
an overview of all classes and what they're used for, similar to top of [old references for p5.sound(https://archive.p5js.org/reference/#/libraries/p5.sound) would be super helpful for students and total beginners. Maybe it's an aspect of the new website, or something to add to the lib.
Edit: just realized some functions like
audioIn()
have drastically different behaviors that could cause some big speaker/sound/feedback issues when loading any prior sketches. In the previous version, using the mic didn't sent it to the output, ie with monitoring – it was silent. Just realized new version instantly plays out what comes in from the mic (haha heard weiird scratching sounds when hand brushed passed mic):Thanks for taking aspects into consideration, particularly a guide for migrating to this version.
The text was updated successfully, but these errors were encountered: