Hello all
1.0.8 is upon us. As usual, all of this needs doing. I will tick as I go but if you fancy helping, I’m happy to share
p
===
Hello all
1.0.8 is upon us. As usual, all of this needs doing. I will tick as I go but if you fancy helping, I’m happy to share
p
===
2 posts were merged into an existing topic: Max/Ableton Users - easy help needed
I’d be happy to help with pd Linux test, what is “sample list test” about ?
oh it is here: opening each helpfile in this file, and pressing all buttons. If no red and all behave, it is a pass!
rel-cli-test-list.txt (160 Bytes)
rel-max-tester.maxpat (6.2 KB)
rel-pd-tester.pd (671 Bytes)
On PD / LINUX:
fluid.bufnoveltyfeature-help.pd:
fluid.noveltyfeature~: no method for ‘metric’
this happens when opening “pd parameters” abstraction, and click on the vertical radio called “metric”.
fix: replace message “metric 0” by “algorithm $1”
( same happens in “fluid.bufnoveltyfeature” & “fluid.bufnoveltyslice” )
fluid.ampgate~-help.pd:
fluid.ampgate~: no method for ‘maxsize’
this happens when opening “pd parameters” abstraction, and click on “maxsize 88200”
appart from that, no RED error message.
oh we did that change ages ago, and it slipped my reviews! I’ll correct now, thanks!
Hello,
in Pure data there is something that I didn’t notice, when I click on “online reference”
the web page is not found in the browser. I guess the Flucoma website changed a bit.
On which OS? here on MacOS and Pd55-2 it works…
btw there are delays in me testing because I’m on ARM so my Win and Lin machines are not dealing with the binaries we compile…
… and the MacOS SC unit testers are misbehaving for a corrected algo that I need to thoroughly check… and the Linux SC unit testers are timing out… so it is much much slower than I hoped!
sorry I forgot to mention, I’m on Linux.
“online reference” button I clicked is in “fluid.bufmfcc’s help file”
it leads to : https://learn.flucoma.org/reference/bufmfcc/
which gives an error 404
indeed you caught an error - the non-real-time objects that have a real-time equivalent should point to the latter. Thanks!
you’ve actually caught a pattern of errors, now all corrected in Pd but Max/SC/CLI need checking, nice one!
Potentially massive bug/issue here.
read
-ing a .json
into a dataset doesn’t work the first time. You have to read
twice for it to register. Meaning the first read of any dataset fails, and every subsequent read
is “one behind”.
Steps to reproduce:
load attached .json
(or any)
print
results (empty)
read
again
print
results (now the values are correct)
----------begin_max5_patcher----------
359.3ocuT9sSCCBEF+Z3ongqqKE1R04qhwXXsGmrzAM.cVyx7YW3vpap6Olo
Y2Py4qG3iezO5ZJgMyzCNV18YOjQHqoDBJEEHaqIrkx9pFoCaisDbN4bfkmd
mG58n9Jv5TF8fdqzW8hRO+IKT4SqOub5nh7rz3jaiiBwnhrG2NEc2RSmuA7n
Q7cpJ8fnXqXpO+asPZoYrOWEUMtcLyVbifEk1Powg7+HesVk1eJ53hczMVbE
nST7exmEj0m.ux61itwWA53SuD5zvqgY+C3dtoSUOpV5kNv+dVibt6rrx4E3
ihxyPq3PzxOJs4Gk3x8IFag0nze+5Itgi5e8XvY5rUCljR+4Y61x0fyqzRe7
J5d8D7D65fG0+ZmBeqtZdER8WlWoCTYa6vephFEsIjfVXrwxo4XoRmJKvRKr
RMz+DTQZCIFeHtzYwsFqubBKMUSMX0cJLAPi.FrDSmZY3hWqLwBFhoaneb1H
FoM
-----------end_max5_patcher-----------
data:
deriv means.json.zip (810 Bytes)
On version:
1.0.8+sha.8fb178f.core.sha.f89e3e4d
OSX 15.2
edit:
Hmm, seems to work ok now again, though it did persist through restarting Max a couple times.
which max version? Looks like 9…
trying to reproduce here on 8 and pd and sc and cannot. Will try harder but might be a cycling issue?
So I did a little radical test: 100 automated reboot, reload, and check size in SC:
(
y = 0;
z = Condition.new;
Routine{
100.do{|x|
x.postln;
s.quit;
s.waitForBoot{c = FluidDataSet(s).read("/Users/pa/Downloads/deriv means.json", {c.size{|x|if(x == 9, y = y+1);z.unhang}});};
z.hang;
};
"% loads on 100 attempts successful\n".postf(y);
}.play;
)
and I’m running it on all 3 OSes. Trying Max8 and Max9 in MacOS and Windows11 too. So far all working.
It’s definitely Max 9.
Trying it again and it’s working fine, but it did happen several more times again yesterday.
Did some quick testing in Max 8 and couldn’t reproduce, but I don’t do my daily patching in there anymore so if it’s inconsistent I wouldn’t be able to tell.
I’ll keep my eyes peeled to see if I can narrow things down more.
on my side, I found a release-blocking problem on Transient - I am assessing if it is new, and how new, then I’ll see if we release with a warning (it was always broken so keep on trucking with different random values) or if I try to solve it once and for all (famous last words). More soon.
I’ve not been able to reproduce the issue here again.