3.14.0-rc1 announcement

Development
1

We are publishing SuperCollider 3.14.0-rc1, a release candidate for the next minor version of SC. As this is a release candidate, it is meant for testing and evaluation, and it is not an official release. If no major issues are found in the release candidate, a proper release will be made in about a week. You can download it here: Release 3.14.0-rc1 · supercollider/supercollider · GitHub

This version has a number of changes since SC 3.13. Highlights include:

  • Sclang functions now support collecting arbitrary keyword arguments via { |...args, kwargs| kwargs }
  • The initialization sample of multiple UGens was fixed
  • Documentation can now also be themed like the IDE
  • Due to updated bundled boost libraries on macOS and Windows, FluCoMa UGens which were working under SuperCollider 3.13 are not compatible anymore with 3.14! Go to GitHub - flucoma/flucoma-sc: Fluid Corpus Manipulation plugins for Supercollider to check for compatible version.
  • Even though these are not as much of user-facing changes, there were countless structural upgrades: we migrated to qt6, added and improved tests, updated 3rd-party libraries, updated the build system for most recent build tools, and adapted a new organizational structure for development

A big thank you to all developers for your contributions!

Full Changelog: https://github.com/supercollider/supercollider/blob/3.14/CHANGELOG.md

Marcin, Dennis, Gianluca, and Josh

12 Likes
2

PS Please test these builds! We need as many people as possible to test these to find any possible issues before the final release. Thanks!

1 Like
3

hey, thats very cool :slight_smile:

I have to admit that i dont understand what this means exactly.

4

If you don’t use FluCoMa plugins, then it doesn’t mean anything :slight_smile:

I you do use FluCoMa, then you’ll need a new version of their plugins for them to work with SC, once they release it. This is only for macOS and Windows though.

5

Does this mean when i update to SC 3.14. and want to use FluCoMa, then i have to wait until they have published a new update, otherwise FluCoMa wont work?

6

Yes, unfortunately (macOS and Windows only).

7

So on macOS and Windows there are no Problems with updating and FluCoMa or the other way around?

8

Congrats everyone, and thanks for all your hard work.
Josh

/*
Josh Parmenter
www.realizedsound.net/josh
*/

3 Likes
9

The currently available downloads of the FluCoMa plugins are only working with SuperCollider 3.13.
Once 3.14 has been released officially (aka it has been merged to the main branch), FluCoMa will distribute a new version which is compatible w/ 3.14 (but not with 3.13 anymore).

You can also build the FluCoMa plugins yourself to obtain a 3.14 compatible version.

For more information see Upcoming Boost upgrade in SuperCollider · Issue #149 · flucoma/flucoma-sc · GitHub

2 Likes
10

Thanks!

Wow, this is amazing:

WARNING: Input sample rate is 44100, but output is 48000. Attempting to set input sample rate to match the output.

We don’t see this anymore!

ERROR: ERROR: Input sample rate is 48000, but output is 44100. Mismatched sample rates are not supported. To disable input, set the number of input channels to 0.

could not initialize audio.

Server ‘localhost’ exited with exit code 0.

11

This is huge! I can’t wait to try it out. Thanks to all

12

Just realised I never did any documentation for the kwargs stuff. Usually I’d do this immediately, but I’m away from home until next week. Do we have a planned date for the actual release? Would be good to squeeze that it!

13

If this suggestion is helpful, I think the example you have here would be great for the writing classes helpfile:

1 Like
14

@Eric_Sluyter thanks yes it should talk about

  1. The syntax and what is returned
  2. Object prototyping - the original use case
  3. And how it impacts instance members
  4. Going the other way, with performargs

I will try and do a pr on Monday, but won’t be able to do so an earlier unfortunately!

1 Like
15

Hey Jordan, I’ll see if I can do some of it on the weekend. Since we’ve steered this together, I think I know where to add documentation.

16

Sure whatever works!

17

Those:

If anything is missing, let me know!
(object prototyping is still not extensively covered, but that might be a separate issue?)