1.0.9 pre-release testing

Development and Maintenance
1

Hello

Here is a little summer fun: a candidate release for 1.0.9. it is mostly bug fixes and slight optimisations, and compatibility with SC 3.14 that was just released.

Let me know if anything is unsavoury.

p.a.

release notes:

new features:

[sc] DataSet can read knearest on the server, see DataSet.kr

[all] dataset tobuffer now has an argument to flip the ID and the label.

breaking changes:

[all] bufcompose now takes the source’s samplerate when resizing is needed.

[sc] all .kr triggers are now outputing 1 (or k) only on success

[sc] the signed binaries we provide now needs SC 3.14 - the code can be compiled by end users for any other version of SC they require though.

[pd] fix mouseup bindings on fluid.waveform and fluid.plotter, now optional mouseup message, and remove duplicates of coordinates on mouseup, as well as picky click-drag behaviours.

and many smaller bug fixes, documentation clarifications, and clearer examples, see the repositories for the details!

Download links:

2

List of tests to do before the release:

  • :white_check_mark: unit testing SC MacOS
  • :white_check_mark:unit testing SC windows
  • :white_check_mark:unit testing SC linux
  • advanced code and basic UI test SC macos
  • advanced code and basic UI test SC windows
  • advanced code and basic UI test SC linux
  • sample list test Pd MacOS
  • sample list test Pd Windows
  • sample list test Pd Linux
  • sample list test Max MacOS
  • sample list test Max Windows
  • sample list test CLI MacOS
  • sample list test CLI Windows
  • sample list test CLI Linux
3

Thank you so much!!! Everything is working perfectly!!! SC 3.14 MacBook Pro M2 and MacMini M4 Pro Sequoia 15.5

1 Like
4

Seems to work for me. I’m able to compile and load the extensions with SC 3.14.0 on my old Intel MacBook Air.

1 Like
5

Hello,

flucoma-pd / linux /mac /windows error :

in “fluid.bufnoveltyfeature-help.pd” when clicking the “HTML Documentation” bang,

an error box appears, complaining about not finding “fluid.noveltyfeature.html”.

I guess the “fluid.referencelauncher” argument should be replaced by “fluid.bufnoveltyfeature.html”

1 Like
6

Where do I find the sample list ? I should test “dataset” , “bufcompose” , “fluid.waveform” and “fluid.plotter” right ?

7

Thanks!

indeed, now I need to click on all of the helpfiles to see if I forgot another :cry: I’ll do that next week.

1 Like
8

Built fine on MacOS 15.6 with SC-dev branch :wink: Seems to be working fine! :slight_smile:

1 Like
9

I’ll check the other helpfiles!

1 Like
10

that will help a lot - it is a matter of clicking all of them. If you’re good with a terminal and reg ex, you can probably find the string linked with the file name…

11

Actually @yogi I’ve done the check, there was 19 omissions… thanks to grep and claude it was found in a breeze :slight_smile:

12

Now pd is updated with the corrected helpfile links, same address as above.

13

Thanks for this!

SC:

are the helpfiles autogenerated?

in e.g. FluidBufNoveltyFeature.schelp, there are two appearances of

    SECTION:: Docutils System Messages

  At line 47: syntax error, unexpected ARGUMENT, expecting end of file
[...]
  At line 210: syntax error, unexpected ARGUMENT, expecting end of file

that break .schelp rendering in SC. Simply removing them fixes the error.

14

I’m curious, how did Claude help with grep ?

16

I found no red error message when teting with sample list.

It reminded me of this error I get when plotting an invisible plotter ( when it’s inside a closed subpatch )

plotterBug.pd (2.4 KB)

“uplevel #0 $docmds”(Tcl) COMMANDE INVALIDE : invalid command name “.x55e21d3027d0.c”
while executing
.x55e21d3027d0.c delete 55e21d32e720_frame”
(“uplevel” body line 6)
invoked from within
“uplevel #0 $docmds”

after encoutering this in a patch I have to restart pd so the gui objects behave normally again.

The same apply to fluid.waveform.

17

Hello all

Sorry I was offline… catching up this morning!

Yes they are. There must be a bug in this one. Now I need to check all the helpfiles - I wonder since when this is wrong… :frowning:

No I was good with grep. it was the bash language I cannot be bothered to remember :slight_smile:

I remember your bug report in December - I forgot about it as it wasn’t in github. I will see what I can do.

1 Like
18

Done. I was dumb and made a typo in the source code when I cross-referenced objects. Sorted and compiling on github, should be correct at the link above at 9:15 GMT

19

ok i gave it a spin - it’ll be long to fix, because it seems that the TK object is “destroyed” yet I try to draw it - despite me checking if it is ‘visible’… I’m trying to understand that flag but as you know, Pd’s GUI coding is dark magic meets nightmares…

20

ok a little more prodding, I’m almost fixing that plus zooming at the same time… but man it is a labour of exorcism… maybe tomorrow I’ll be posting a fix

1 Like
21

ok Pd will have to wait because the list is trying its best to help in a very messy place (theirs, not ours)

2 Likes