Cannot record.

[peisong0109]

I'm running ODAS on a Raspberry Pi with Respeaker 4-mic array and running ODAS Web on a remote laptop running odas_web on Windows 10.
Q1:
The odas is running well on Raspberry Pi, but I don't know how to start recording and stop recording. There is nothing shown on the Record window.

Q2:
After running for a while, the ODAS would stop working.

[peisong0109]

config file
respeaker_4_mic_array.cfg.txt

[GodCed]

Q1

Two things.

First you must adjust your configuration file according to the ODAS Studio configuration instructions here. Precisely you must change the interface for the separated and post-filtered modules.

Then you must check the determine if audio is recorded checkbox in the record window as shown here:

Q2

This one will require the ODAS output for debugging. If I recall correctly you can start the odaslive process with the -v argument to enable additional output, but you may want to seek support on the ODAS repo to get more guidance on that.

[peisong0109]

Thank you so much for your answer, it helps me a lot. @GodCed
For the Question 1, I modified my config file and I can record the voice once. But unfortunately, then I cannot record it anymore.
Here is the output:

For the Question 2, here is the output of ODAS and the web terminal:


In the second picture, the Chinese word "段错误" probably means "Segment fault" in English.

[peisong0109]

Thank you so much for your answer, it helps me a lot. @GodCed
For the Question 1, I modified my config file and I can record the voice once. But unfortunately, then I cannot record it anymore.
Here is the output:

For the Question 2, here is the output of ODAS and the web terminal:


In the second picture, the Chinese word "段错误" probably means "Segment fault" in English.

Q2 solved.

[GodCed]

Could you clarify what you mean by being able to record only once? Like what are the steps in your workflow, does tracked sources appear/disappear in the tracking data?

Right now I'm not sure I understand what is happening or what you are attempting to do.

[Bengisu2]

hello, were you able to fix the error? I am getting the same error while recording. @peisong0109

"Recorder 0 was false active"

[ethem4161]

Hello,
I get the following error in npm start.

pi@raspberrypi:~/odas_web $ sudo npm start
[email protected] start
electron .
sh: 1: electron: not found

I also got these errors during installation.
how can i solve these problems.

pi@raspberrypi:~/odas_web $ sudo npm install
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
npm WARN deprecated [email protected]: This library will not receive further updates other than security fixes. We recommend using @grpc/grpc-js instead.
npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: Please update to ini >=1.3.6 to avoid a prototype pollution issue
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: request has been deprecated, see request/request#3142
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)
npm WARN deprecated [email protected]: request has been deprecated, see request/request#3142
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)
npm WARN deprecated [email protected]: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)
npm notice
npm notice New minor version of npm available! 8.3.1 -> 8.4.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.4.0
npm notice Run npm install -g [email protected] to update!
npm notice
npm ERR! code 1
npm ERR! path /home/pi/odas_web/node_modules/grpc
npm ERR! command failed
npm ERR! command sh -c node-pre-gyp install --fallback-to-build --library=static_library
npm ERR! make: Entering directory '/home/pi/odas_web/node_modules/grpc/build'
npm ERR! CXX(target) Release/obj.target/grpc/deps/grpc/src/core/lib/surface/init.o

I wish you good work

[Datian996]

Thank you so much for your answer, it helps me a lot. @GodCed
For the Question 1, I modified my config file and I can record the voice once. But unfortunately, then I cannot record it anymore.
Here is the output:

For the Question 2, here is the output of ODAS and the web terminal:


In the second picture, the Chinese word "段错误" probably means "Segment fault" in English.

Q2 solved.
@peisong0109
hi,
I'm learning to use ODA Studio. Unfortunately I ran into the same problem as you did before (Q2). Very lucky to see that you have solved it. Can you tell me something about the solution?
Any help is greatly appreciated.

[mcasamatsuo]

Recording is now possible by modifying file to socket as shown below.

separated: {
    fS = 16000;
    hopSize = 128;
    nBits = 16;        

    interface: {
        type = "socket";
        ip = "127.0.0.1"
        port = 10000;
    };        
};

postfiltered: {
    fS = 16000;
    hopSize = 128;
    nBits = 16;        
    gain = 10.0;
    interface: {
        type = "socket";
        ip = "127.0.0.1"
        port = 10010;
    };        
};