noise suppression with librespeaker in RespeakerCorev2

Products & Technology ReSpeaker
#5

Hi Cinettoa,



Thanks for your post, which helps us to find a bug in HybridNode. We have already fixed it and feel free to update the lib: </s>sudo dpkg -i librespeaker_2.0.1-build181017_armhf.deb <e>

We will also merge the fix into our dev branch and release ASAP.
librespeaker_2.0.1-build181017_armhf.deb.zip (1.03 MB)

#6

Hi Jerry,

I’ve removed the old librespeaker using “dpkg -r librespeaker” and then install the package you provided with “dpkg -i”.

the package is correctly installed according to dpkg -l librespeaker.

I’ve a new issue.

The file /usr/local/include/librespeaker.so is not present anymore I couldn’t compile my cc script using g++.

So, I’ve copied the file librespeaker.so.2.0.1 to librespeaker.so and I was eventually able to compile.

However after compiling the same cc script I’ve sent you yesterday, it returns an error right after launching it:



terminate called after throwing an instance of ‘std::bad_array_new_length’

what(): std::bad_array_new_length.



Any support about this?



Thanks for your help

#7

I attach a little output for troubleshooting.



(393ms)DEBUG – record stream state: 1 [pulse_collector_node.cc:244]

(404ms)DEBUG – record stream state: 1 [pulse_collector_node.cc:244]

(414ms)DEBUG – record stream state: 1 [pulse_collector_node.cc:244]

(424ms)DEBUG – record stream state: 1 [pulse_collector_node.cc:244]

(434ms)DEBUG – record stream state: 2 [pulse_collector_node.cc:244]

(434ms)INFO – Connected to PulseAudio server. [pulse_collector_node.cc:255]

(435ms)DEBUG – PulseCollectorNode input: channels 8 rate 48000, output: channels 8 rate 16000 [pulse_collector_node.cc:274]

(435ms)INFO – PulseCollectorNode thread started. [pulse_collector_node.cc:276]

(437ms)INFO – HybridNode is accepting interleaved data. [hybrid_node.cc:171]

terminate called after throwing an instance of ‘std::bad_array_new_length’

what(): std::bad_array_new_length

Aborted

#8

Have you added parameter “–std=c++11”? Please try this:
</s>g++ main_vep_nr_test.cc -o main_vep_nr_test -L/usr/local/lib -I/usr/local/include/respeaker -lrespeaker -lsndfile -fPIC -std=c++11 -fpermissive<e>

#9

Hi,

just tried but still the same error.

Just to double check, I’ve also tried to reinstall the librespeaker v2.0.0 and re-compile the same cc file. In this way it is working.



Any other suggestion or any additional info I can provide?

#10

Could you check the md5sum of the deb package? It should be </s>b98d4bc263215f28162ff2c9a2df182b<e> .

#11

Is it possible to run out of memory? It seems like the most probable cause bad_array_new_length.

<LINK_TEXT text=“http://en.cppreference.com/w/cpp/memory … new_length”>http://en.cppreference.com/w/cpp/memory/new/bad_array_new_length</LINK_TEXT>

#12

Hi,

I confirm the checksum



md5sum librespeaker_2.0.1-build181017_armhf.deb

b98d4bc263215f28162ff2c9a2df182b librespeaker_2.0.1-build181017_armhf.deb



It seems to me strange that this is a memory problem.

This same examples war running properly with the previous bugged version.

I will double check also this by the way.

Is it working in your respeakerCore?

#13

Yes, it is working on my core v2.

You can try the following main_vep_nr_test built on my Respeaker Core V2.

</s>respeaker@v2:~/test_nr/src$ uname -a Linux v2 4.4.138-respeaker-r0 #2 SMP Wed Jul 25 11:29:18 CST 2018 armv7l GNU/Linux<e>
main_vep_nr_test.zip (8.75 KB)

#14

uname -a returns the same output of yours.



the file you attached is returning the same error.



I’ve tried to reflash the SD card, reinstall only librespeaker and its dependencies and then run again but I still get the same error.



Any other idea?

#15

Hi Cinettoa,



I have also tried to reflash the SD card. I installed librespeaker-2.0.0 and pulseaudio, copy common.res and alexa.umdl and “main_vep_nr_test” I built before, then reboot. After reboot, of course main_vep_nr_test was able to run, but it just could not wake up because I were using librespeaker-2.0.0. Then I installed librespeaker-2.0.1 and made a symbolic link to “librespeaker.so.2”. After this, my “main_vep_nr_test” worked well.

If these steps don’t help, I suggest you use another faster SD card(eg. class10).

#16

Hi,

I’ve tried step by step you procedura but I still get the same error.

I will buy a faster SD and try again.

It is possible that my feedback will be a little delayed this time.



I have another question related to this library. If you prefer I can open a new issue.



Do you have any guidance or example on how to return the output of the librespeaker audio processing pipeline to a linux device instead of a file?



Thanks for your help!

#17

HI Cinettoa,



Any feedback is welcome!



And please open a new issue of your question;). Can you explain more about your question? Do you mean that you need to process audio stream on ReSpeaker and then send that stream to another Linux device?

#18

Thanks!

I’m going to open a new issue so you can reply me there!

#19

The same problem with “out of the box” example. I’m using new librespeaker_2.0.1 library version

#20

You mean the “bad_array_new_length” problem when using librespeaker_2.0.1 ? Or the “Noise Suppression doesn’t work” problem? Can you provide more information? Thanks!

#21

Noise Suppression doesn’t work

#22



Hi!
I've tried again using a fast sd card (sundisk 128Gb V30 U1 A2) but still the same error.
What about if I create an image of my respeaker core v2 and I send to you for testing?
how can I send you such a big image?

Thanks!
#23

Hi Cinettoa,



You can upload your image to Google Drive. But one more thing need to confirm before that, check if you are using the latest image downloaded from here: <LINK_TEXT text=“https://v2.fangcloud.com/share/7395fd13 … 14&lang=en”>https://v2.fangcloud.com/share/7395fd138a1cab496fd4792fe5?folder_id=188000311814&lang=en</LINK_TEXT>



Thanks.

#24

Hi,

I confirm that I am using the respeaker-debian-9-lxqt-sd-20180801-4gb.img which should be the last.

Tomorrow I upload the image of my sd card and send you the link of my google drive.