v2.4.0 release preview feedback

[kevinstadler]

This is the central place for collecting all bugs, issues and general feedback on the preview build of the upcoming Sound library release, which is available for download at the v2.4.0-preview release. The new release of the library will go public at the end of October, until then updates and fixes will be added to the release URL above as they come in.

How to test

Download the latest sound.zip and extract the sound directory into your sketchbook's libraries folder (this is usually in Documents/Processing/libraries/). (On Windows, you will need to close Processing while doing this.)

We are particularly interested to know whether old sketches of yours that use the sound library still work as expected using the new library version. Please feel free to report any and all bugs, crashes or exceptions you get while using the current preview build!

The library reference on the Processing website has not been updated yet, for new functionality please refer to either the library example sketches or the latest library JavaDoc.

Known issues

• need to add documentation/information messages about how to use PortAudio on Linux/Raspberry Pi

[kevinstadler]

Before closing this issue, let's claim that it has something to do with processing/repo-tango#1 (full link address https://github.com/processing/repo-tango/issues/1), and also processing/repo-tango#2 for good measure.

It's possible to link to commits like processing/repo-tango@faa9d2a but permalink code-embeds are apparently not rendered across repositories. This just shows up as a link:

https://github.com/processing/repo-tango/blob/faa9d2ac337dbcf2221ecb06a68942f2b61a711f/README.md?plain=1#L3-L7

[kevinstadler]

This comment is created after the move of the original repo from the organisation to the personal account.

The original issue processing/repo-tango#1 is now really at kevinstadler/repo-tango#1. Currently both render as kevinstadler/repo-tango#1 in the Github frontend, and the tooltip of both shows the personal repository issue.

The same is true for commits, i.e. both processing/repo-tango@faa9d2a and kevinstadler/repo-tango@faa9d2a render as kevinstadler/repo-tango@....

The funny thing is that this forward-resolution also works retroactively, i.e. commit kevinstadler/repo-tango@4b9f757 was only made after the repo had been moved to the personal account, but you can refer to the commit as if it was made to the organisation repository (i.e. processing/repo-tango@4b9f757) and it just renders as a commit to the new repo: processing/repo-tango@4b9f757

[kevinstadler]

The organisation repo and a first issue have now been re-created, so it shouldn't be any problem to refer to the new processing/repo-tango#1