Mattebass

I'm experiencing a strange ( to me) behavior of the button object: I'm working with Jitter and Audio,

performing a FFT and placing the data of one frame in a matrix;

The matrix is then read to generate an audio signal and a visualization of the spectral content.

The problem is due to the fact that when I trigger the matrix clicking on the button, I could properly hear and visualize the content;

Otherwise, when triggering the button by an hardware controller, I can hear the audio properly but I've no visualization of the spectral data.

I'm supposing that the message sent by the button when clicking or triggering is slightly different, but It seems strange.

P.s this is the pfft file I you need to test the main patch 

Hello to everyone,
I'm experiencing a strange ( to me) behavior of the button object: I'm working with Jitter and Audio,
performing a FFT and placing the data of one frame in a matrix;
The matrix is then read to generate an audio signal and a visualization of the spectral content.
The problem is due to the fact that when I trigger the matrix clicking on the button, I could properly hear and visualize the content;
Otherwise, when triggering the button by an hardware controller, I can hear the audio properly but I've no visualization of the spectral data.
I can't understand why.
I'm supposing that the message sent by the button  when clicking or triggering is slightly different, but It seems strange.

different-behavior-of-bang

Inserting [deferlow] after controller input will probably solve it.

See this article for detailed explanations.

https://cycling74.com/articles/event-priority-in-max-scheduler-vs-queue/

thanks, You solved my problem and gave me interesting material to read

thanks, You  solved my problem and gave  me interesting material to read

different behavior of bang