?read:.. command starts automatically

[bertankursun2]

Hi,
I am not having a major error but there is an unexpected behavior(for me) with the application. Could anyone tell me what is going on and how can I fix it?

I am testing with gain_live_getting_started.cfg with Fs = 32000 and the output channels are edited.

So I am connected to PHL via wifi and I am sending an mha command to read the file : ?read:/home/mha/phl_test.cfg
Then the openMHA immediately starts the program. It runs correctly, and I can change certain parameters but shouldn't it wait until I set cmd = start ?
The same behavior is observed when I send the command with MATLAB :

Code: Select all

% IP address of mahalia running on PHL when using wireless
mha.host = '10.0.0.1';
% openMHA default TCP port
mha.port= 33337;
mha_query(mha,'','read:/home/mha/phl_test.cfg'); %Selects the .cfg file to read

And the signal processing starts immediately. In addition to that, stop and release commands are not enough to stop it. After a short pause, it is initiated again.

Code: Select all

mha_set(mha,'cmd','stop');
mha_set(mha,'cmd','release');

Only " mha_set(mha,'cmd','quit'); "stops the signal processing completely but then I have to send "?read:" command again and it starts automatically as before...

[hendrikkayser]

Hello,
that behavior could be caused by the Node-Red GUI made for the generic-hearing-aid configuration which might be still running on your system. It periodically sends the start command to mha to activate the processing after finishing the load process of the GUI. Ssh into the system and execute

Code: Select all

sudo systemctl disable --now mahalia-nodered

This will deactivate the system service which runs the GUI an should fix the unexpected behavior on your system.

[bertankursun2]

Thanks a lot!