-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No output from realtime analysis objects on macOS CI build on older Mac #315
Comments
Thanks for this, I will try and test this on an i5 at home (I think my partner's air is one) and have a poke. Appreciate the detailed report :) |
Dear @leoauri can you try the new release and tell us if it is still the case? Thanks |
Hi Pierre, I did get output from fluid.mfcc~ now, but only one set of values exactly every 11.366 seconds. Here is the patcher I tested with:
|
With a hop size of 512 samples at 44.1khz sampling rate that is exactly what you would expect. I think that means the issue is solved :) |
@leoauri do you mean always the same set of values every (signal vector size) or a new value every hop size (hence me using zl change after the descriptors) ? |
Somebody is confused here, maybe me. 44.1k sampling / 512 FFT window, we would expect many analyses per second, not one every eleven seconds? |
I get one list of values at regular ~11 second intervals |
@leoauri here is a slightly more precise measuring patch. with overdrive on, and your signal vector size to something below 512, then I get 11.6ms
|
That somebody is me. I assumed ms without reading carefully ;) I'll leave you two to it. |
@tremblap A sequence of timings from your patch:
|
What's that? |
The fftsettings do not influence the timings. Those above were the default 1024 window, these 512:
|
what do the -1s refer to in |
svs is your max settings - what are your i/o vector size and your signal vector size in the Audio Status window? |
-1 = default. for 1024 -1 -1 it means 1024 512 1024. -1 for hop means half the window, and -1 for fft means the nearest exponent of 2 on or above the window |
i/o vector size 4096 |
👌 |
ok just for the test here, can you try 512 for i/o and keep 64 for s/v and od on. Try this patch instead - much cheaper processing of melbands:
|
Ah. 512 for i/o gives expected ~11ms results. Thing is, apparently I cannot change this setting when Max is using Ableton as the audio host. |
Now that is interesting. Let me do some tests here. |
Also, in max4live, I am now again getting "no output" in both the last patches 😆 |
I don't have Ableton here, but you run it at 4096? Here the results in Max at 2048 are almost as expected - @weefuzzy is on holidays this week and I will have to ask him a few questions about expected values in such context. More soon |
When started with Ableton as the Audio host, i/o is set to 4096 and there are no other values to choose from in the dropdown |
Realtime components (fluid.mfcc~, fluid.spectralshape~, ...) give no output in the CI compiled versions from tag/1.0.0, but built on a mac, they do.
This is on
Max version
Here is a patch which reproduces
The text was updated successfully, but these errors were encountered: