2023 roadmap and issues cleanup #2684
Replies: 4 comments 22 replies
-
|
it's quite shocking to wake up to 600 emails from wavesurfer project, having no idea what's going on.
isn't this something we should've discussed among everyone first? i'm a bit speechless atm. |
Beta Was this translation helpful? Give feedback.
-
|
True, sorry, I should've put it up for discussion first. |
Beta Was this translation helpful? Give feedback.
-
|
@thijstriemstra btw one of those emails was an invitation to the new org, I hope it wasn’t lost in the crowd. 😅 |
Beta Was this translation helpful? Give feedback.
-
|
@thijstriemstra lol you don't organize your emails in folders @katspaugh it's good you did that clean up most of the issues are very outdated. I like the whole discussions section setup. |
Beta Was this translation helpful? Give feedback.
-
I did? |
Beta Was this translation helpful? Give feedback.
-
|
I guess it's less about the emails themselves and more about someone (me) suddenly doing such a drastic change w/o consulting with the main maintainer and the community. I'll do my best to first propose and discuss things in the future. |
Beta Was this translation helpful? Give feedback.
-
|
@thijstriemstra @entonbiba would you guys be up for a call sometime this week to align on a few things? Namely
|
Beta Was this translation helpful? Give feedback.
-
|
yea notes wise is not a problem, but we should do a call or video |
Beta Was this translation helpful? Give feedback.
-
|
wayyy out of my line but if all of you are okay with it ...can I join? |
Beta Was this translation helpful? Give feedback.
-
|
@prakharpbuf this is primarily for contributors and to see how best we can support it going forward by streamlining the strategy, for sure we will update the roadmap after with our findings. If you have any pull requests you can contribute to the project that would be great and helpful as well! |
Beta Was this translation helpful? Give feedback.
-
|
@thijstriemstra since you suggested Discord, maybe starting a Discord community server would make it easier to organize information and keep up with everything? |
Beta Was this translation helpful? Give feedback.
-
|
I'd love to nerd out about Wavesurfer and Tone.js (and just WebAudio in general) if anyone wants to start one up. |
Beta Was this translation helpful? Give feedback.
-
|
If you're going to be rewriting this to typescript, I suggest you also clean up the audio backend class hierarchy. Right now it is interface AudioBackend {
play(): Promise<void>;
pause(): Promise<void>;
getVolume(): number;
// ...
}
class WebAudio implements AudioBackend {
// ...
}
class MediaElement implements AudioBackend {
// ..
}it's a big task, however :^) |
Beta Was this translation helpful? Give feedback.
-
|
Good point! |
Beta Was this translation helpful? Give feedback.
-
|
I've made a little diagram of how I think it should be:
Apart from making MediaElement and WebAudio equal citizens, I think it would be nice to extract the Decoding and Fetching logic in their own respective modules. |
Beta Was this translation helpful? Give feedback.
-
|
I've started an experimental rewrite here: https://github.com/katspaugh/wavesurfer.ts |
Beta Was this translation helpful? Give feedback.
-
|
Hello, I think it is a great idea to rewrite wavesurfer.js and at the same time, maybe it's a great opportunity for me to give you just a source to improve rendering and zooming performance for the new wavesufer! Maybe you are already aware of this repo, but if not, they've made a great example of how smooth the waveform rendering can be, I haven't seen it anywhere else (sadly its unmaintained for about 8 years but it still performs). Here is the repo: https://github.com/wavesjs/waves-ui Just look at the |
Beta Was this translation helpful? Give feedback.
-
|
Ok I see. I just tried your example and it is indeed performing much better! Chrome: Screen.Recording.2023-03-22.at.14.10.40.movJump back and forth in Safari: Screen.Recording.2023-03-22.at.14.17.16.mov |
Beta Was this translation helpful? Give feedback.
-
|
Thank for taking the time to test and record it! |
Beta Was this translation helpful? Give feedback.
-
|
I tested it again now, and not only it is working better on safari (safari still seems to underperform compared to chrome), the performance on chrome got even better and the micro hiccups are all gone - impressive work and I really appreciate how fast it develops - is there a approx. timeline on when there will be a "stable" release? |
Beta Was this translation helpful? Give feedback.
-
|
I’m still getting occasional bug reports for the alpha, but am planning to release a beta likely this weekend. I’ll keep you all posted. |
Beta Was this translation helpful? Give feedback.
-
|
@katspaugh awesome! :) |
Beta Was this translation helpful? Give feedback.
-
Dear wavesufer.js community 👋 ,
I've decided to do some spring cleaning and closed most of the issued we had open. 🧹
90% of these issues were from more than a year ago, and most of them were questions/dev support requests that were either answered, or never followed up on by their OP.
Instead of creating issues with questions, we encourage the community to use the Q&A section in this forum. I've migrated some recent questions there.
There was also a sizable number of feature ideas which should now be created in the Ideas forum section.
Better documentation
The amount of dev support requests is a sign that we need to make our documentation more accessible.
TypeScript
Another thing I propose to tackle in 2023 is migrating the project to TypeScript.
This will help app developers discover methods/events and their signatures w/o going to the documentation. And it will reduce the possibility of trivial bugs both in wavesurfer.js's code itself and the code that uses it.
Feedback
Your feedback and ideas are very welcome! 🏄
Beta Was this translation helpful? Give feedback.
All reactions