Howdy, Stranger!
We are about to switch to a new forum software. Until then we have removed the registration on this forum.
Categories
- All Categories 25.7K
- Announcements & Guidelines 13
- Common Questions 30
- Using Processing 22.1K
- Programming Questions 12.2K
- Questions about Code 6.4K
- How To... 4.2K
- Hello Processing 72
- GLSL / Shaders 292
- Library Questions 4K
- Hardware, Integration & Other Languages 2.7K
- Kinect 668
- Arduino 1K
- Raspberry PI 188
- Questions about Modes 2K
- Android Mode 1.3K
- JavaScript Mode 413
- Python Mode 205
- Questions about Tools 100
- Espanol 5
- Developing Processing 548
- Create & Announce Libraries 211
- Create & Announce Modes 19
- Create & Announce Tools 29
- Summer of Code 2018 93
- Rails Girls Summer of Code 2017 3
- Summer of Code 2017 49
- Summer of Code 2016 4
- Summer of Code 2015 40
- Summer of Code 2014 22
- p5.js 1.6K
- p5.js Programming Questions 947
- p5.js Library Questions 315
- p5.js Development Questions 31
- General 1.4K
- Events & Opportunities 288
- General Discussion 365
In this Discussion
- clankill3r March 2018
- shiffman March 2018
GSoC idea: overhaul of processing-sound library
Hello,
one of the suggestions on the GSoC project list is bringing the processing-sound library up to date, with a particular eye on improving support across platforms. Having had a look at forum posts and the repository it seems that most of the unresolved issues of the past few years can be traced back to (non-Java) libraries that are dependencies of the Methcla synthesis engine whose maintenance status is unclear (and which is in either case only very sparsely documented).
I was therefore wondering whether it would be more constructive to do a complete overhaul of the library and replacing Methcla with a native Java sound synthesis engine (to maximise platform compatibility)? The processing-sound API is not that massive so it's definitely a manageable task, and it would go hand in hand with improving and extending the existing documentation and tutorials.
Regarding candidate libraries that are mature/stable, well-maintained and tested across many platforms I was wondering about JSyn, which is a very small download yet has all the synthesis and analysis capabilities required by processing-sound, and much more (javadoc). So while it would be possible to expand the sound library API quite a bit, I guess there's a trade-off there with making it a beginner-friendly library that is not too overwhelming? For more complex (and computationally expensive) stuff more experienced people will probably want to move on to minim or even SuperCollider anyway..
I'd be interested to hear people's thoughts on this idea, and also if anyone would be interested in mentoring.
Best! Kevin
Comments
Sounds great. The current sound library is not so good. (Far from good). You can't check if a sound is playing, you can't see how far it is with playing, if play is called on a sound that plays then it stutters etc. I see students fall back to minim all the time, which in my opinion is still way better.
About the complexity / jSyn / whatever I don't know. I just wanted to tell that I think it would be great if the sound department of processing get's some patching.
I'm tagging @reas for his thoughts about the state of the current sound library.