Sound can not be measured even when odas studio starts with npm start.

[suekiti0327]

The usage of npm start that I had taught before went well, and when I tried to measure the sound, I had the problem of not measuring the sound.I'm also setting up odas control, but it doesn't work at all.Please tell me what kind of countermeasure there is.

I will raise the current situation in the photo.

[GodCed]

You need to follow these instructions and replace <ip> and <sample rate> by actual values. I see those placeholders numerous times in your photos. I also see some place where you redirect the sound to files, which won't work with ODAS Studio.

You also seem to run ODAS Studio directly on a Raspberry PI, which won't work properly because of the processor load. I advise you run ODAS Studio on a desktop or laptop and provide the IP adress of the computer running ODAS Studio in your ODAS config file (<ip> placeholders).

[suekiti0327]

Thank you for your opinion. I'm sorry many times, but I have something I would like to know. I want to teach about IP address setting (For example,Connect raspberry pi to PC ).

There is one concern. Is the content of the picture below also affected? The contents of the red frame are not displayed now.

[GodCed]

Hi, no, the content of the picture below is not affected by IP settings.

The red frame shows the output of the $ arecord -L command, which lists the audio recording devices avaible on the machine. It is not related to the network configuration.

[suekiti0327]

I'm sorry, the photos that I described were the ones that were described on the Internet, and were used to show the parts that I could not display. The picture below is shown when I run it with my python. Even in this case, is it possible to pick up the sound?

Another thing that I had already mentioned was that I needed to use another PC to start odas, but when I try to run it on a PC it doesn't work well, but in this case Do you need to reinstall npm again? Please tell me the procedure etc. in that case.

[GodCed]

1. Your $ arecord -L output seems to indicate that your Pi is not recognizing your microphone array. My guess is that you will not be able to run ODAS in that situation. However, this is dependent of your setup and I can't help you with that. I suggest you seek help on the Seeed side.

2. I don't think you need to reinstall npm, only the Node.js packages. In the odas_web folder:

$ rm -rf node_modules
$ npm install
$ npm start

Also make sure you are running the proper Node.js version. It is v8 for ODAS Studio 0.2 or v12 for ODAS Studio 0.3. You can check your Node.js version with $ node -v. The ODAS Studio version is in the package.json file and is printed when you run $ npm start.

[suekiti0327]

Thank you for your opinion. I tried the method you taught me. Then if I do npm start I get an error and I can not proceed. What steps can I solve? I apologize for the inconvenience, but thank you.

[GodCed]

The warning you see just before the error means electron (the framework used to create ODAS Studio) cannot open the display. Make sure you have a display connected and that you are not logged in using SSH on the Pi.

If that doesn't work try searching the web for "electron can't open display" or related queries to fix your setup.

[suekiti0327]

Thank you for your many opinion. I used to connect via SSH.So I changed to GUI connection and executed npm strat again.Then I got a lag and I couldn't do it well, and the problem that odas dropped on the way came out.In addition, the following error has come out, do you know this solution?If you know, could you tell me? Thank you.

[GodCed]

Then I got a lag and I couldn't do it well, and the problem that odas dropped on the way came out.

Sorry, I'm not sure I understand what you are trying to say. If you mean ODAS Studio lagged and ODAS stopped this is because you are running ODAS Studio on a Raspberry Pi which is not powerful enough. You need to run ODAS Studio on a desktop or on a laptop. ODAS can run on a Pi.

In addition, the following error has come out

The error means the port used by ODAS Studio are already in use Error: listen EADDRINUSE: adress already in use :::10000. I see the output of a previous log before, if it crashed it is likely that some process didn't finish properly. Try running $ killall electron to end all ODAS Studio processes and retry $ npm start.

[suekiti0327]

Thank you for your opinion. I tried to do your solution but I didn't use killall electron well. The following picture is the situation at that time.

In addition, the contents in package.json are also raised temporarily.

What kind of countermeasure will it work?

[GodCed]

I don't understand what you were trying to do in your screen photos. You seemed to have typed $ killall electron in the Node.js output which won't work. You need to type it in the terminal when the Node.js main process is closed.

Furthermore you only need $ killall electron if the main process is dead and if you get the Error: listen EADDRINUSE: adress already in use :::10000 output when you try to restart it.

Also, you don't need to type the $ before a command. As you can see it is already present in your terminal before each command.