search

respeaker / seeed-voicecard

2 Mic Hat, 4 Mic Array, 6-Mic Circular Array Kit, and 4-Mic Linear Array Kit for Raspberry Pi
GNU General Public License v3.0
489 stars 294 forks source link

Respeaker 2mic driver does not work on PI 3 B #26

Closed dm1010111 closed 6 years ago

dm1010111 commented 6 years ago

I have Raspberry Pi 3 B and hooked with respeaker 2-Mics Pi HAT. I use Linux Rasberrypi OS 4.9.59-v7+ built on 10/29/2017. When the system up, "speaker-test -t wav" is OK. I did following to install the 2-mics driver: $git clone https://github.com/respeaker/seeed-voicecard.git $cd seeed-voicecard $sudo ./install.sh 2mic $reboot after system reboot, the "speaker-test -t wav" is broken. The test $ arecord -f cd -Dhw:1 | aplay -Dhw:1 Is broken. No record no playback. Please help rootcause the issue. It looks like "sudo ./install 2mic" 2mic driver has some issue.

dm1010111 commented 6 years ago

Add some observations: If I use "sudo ./uninstall 2mic", then the speaker-test will work again. fro some reason, after installing 2mic driver, the on Pi 3 board speaker is disabled.

Pillar1989 commented 6 years ago 
pi@raspberrypi:~/seeed-voicecard $ arecord -l
**** List of CAPTURE Hardware Devices ****
card 1: seeed2micvoicec [seeed-2mic-voicecard], device 0: bcm2835-i2s-wm8960-hifi wm8960-hifi-0 []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
pi@raspberrypi:~/seeed-voicecard $

seeed2micvoicec is card 1 ?

dm1010111 commented 6 years ago

Hi Baozhu, on my Pi 3 and respeaker 2mic system, I can pass pass " arecord -f cd -Dhw:1 | aplay -Dhw:1"echo test.

I got google-assistant-demo stuck. Following is the message: $google-assistant-demo --device_model_id 2micberry device_model_id: 2micberry device_id: ACDCBE4E571C34433D72A4DB1AFC502C

ON_MUTED_CHANGED: {'is_muted': False} ON_START_FINISHED [2360:2386:ERROR:mic_failure_detector.cc(140)] [assistant] Channel 1 has failed. Powers -inf and -inf

$aplay -l List of PLAYBACK Hardware Devices card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: seeed2micvoicec [seeed-2mic-voicecard], device 0: bcm2835-i2s-wm8960-hifi wm8960-hifi-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0

$arecord -l List of CAPTURE Hardware Devices card 1: seeed2micvoicec [seeed-2mic-voicecard], device 0: bcm2835-i2s-wm8960-hifi wm8960-hifi-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0

I just no clue how to debug this issue. Please let me know what is the solution.

Pillar1989 commented 6 years ago

https://github.com/respeaker/seeed-voicecard/blob/master/asound_2mic.conf#L22 https://github.com/respeaker/seeed-voicecard/blob/master/asound_2mic.conf#L29 should be "hw:1,0"

dm1010111 commented 6 years ago

I made the change. This time I got following errors: N_MUTED_CHANGED: {'is_muted': False} ON_START_FINISHED [1808:1824:ERROR:socket_bio_adapter.cc(109)] BIORead failed with net error code=-100 [1808:1824:ERROR:tls_stream_socket.cc(329)] TlsStreamSocket hit error. rv=-107 message=-107 [1808:1824:ERROR:tls_stream_socket.cc(330)] BoringSsl error queue: [1808:1824:ERROR:fcm_tls_socket.cc(41)] FcmTlsSocket encountered error. code=ReadFailed message=FCM TLS socket read failed. rv=-107 [1808:1824:ERROR:connection_handler_impl.cc(288)] OnRefresh: FCM TLS socket read failed. rv=-107 [1808:1824:ERROR:connection_handler_impl.cc(72)] ConnectionHandlerError: code=ReadFailed, message=FCM TLS socket read failed. rv=-107 [1808:1834:ERROR:mic_failure_detector.cc(140)] [assistant] Channel 1 has failed. Powers -inf and -inf

Please let me know any thiong wrong with my setup.

dm1010111 commented 6 years ago

My .asoundrc is listed in below:

The IPC key of dmix or dsnoop plugin must be unique

If 555555 or 666666 is used by other processes, use another one

pcm.!default { type asym playback.pcm "playback" capture.pcm "capture" }

pcm.playback { type plug slave.pcm "dmixed" }

pcm.capture { type plug slave.pcm "array" }

pcm.dmixed { type dmix slave.pcm "hw:1,0" ipc_key 555555 }

pcm.array { type dsnoop slave { pcm "hw:1,0" channels 2 } ipc_key 666666 }

dm1010111 commented 6 years ago

Finally I resolve the issue with following .asoundrc file:

The IPC key of dmix or dsnoop plugin must be unique

If 555555 or 666666 is used by other processes, use another one

pcm.!default { type asym playback.pcm "playback" capture.pcm "capture" }

pcm.playback { type plug slave.pcm "dmixed" }

pcm.capture { type plug slave.pcm "array" }

pcm.dmixed { type dmix slave.pcm "hw:1,0" ipc_key 555555 }

pcm.array { type dsnoop slave { pcm "hw:1,0" channels 2 } ipc_key 666666 } Thank you for all your helps, Baozhu.

calinichta commented 6 years ago

I just updated and upgraded my Raspbian Linux Kernel to the mentioned kernel (Linux Rasberrypi OS 4.9.59-v7+) but I'm still not able to install the drivers.

"journalctl -xe" lists the following:

-- Unit systemd-modules-load.service has begun starting up. Jan 20 00:49:30 raspberrypi systemd-modules-load[1036]: Failed to find module 'snd-soc-ac108' Jan 20 00:49:30 raspberrypi systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE Jan 20 00:49:30 raspberrypi systemd[1]: Failed to start Load Kernel Modules. -- Subject: Unit systemd-modules-load.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-modules-load.service has failed. -- -- The result is failed. Jan 20 00:49:30 raspberrypi systemd[1]: systemd-modules-load.service: Unit entered failed state. Jan 20 00:49:30 raspberrypi systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. Jan 20 00:49:30 raspberrypi sudo[1030]: pam_unix(sudo:session): session closed for user root

Seems that snd-soc-ac108 is not generated, so I'm not able to see the seed2mic-device in alsamixer or somewhere else. I'm stuck since 4 hours.

Does anyone now what's wrong?

dkmerona commented 6 years ago

have a similar problem; did sudo ./install.sh 2mic; reboot and aplay -l dont list the card

Pillar1989 commented 6 years ago

@calinichta I think you need reflash the sd card. then reinstall the seeed-voicecard.

dkmerona commented 6 years ago

i just boot on sd card, all my system file is on an usb without problem till now;

Pillar1989 commented 6 years ago

Your u disk must be linux file system.

calinichta commented 6 years ago

I reinstalled the image about 4 times - but on berryboot with an external USB drive.

Setting up the latest raspbian with kernel 4.9.57 on the SD card only woks fine.

Taking a berryboot image with kernel 4.9.57 also works fine, but not on my time intensive and carefully installed image based on kernel 4.9.26v7-aufs.

There, the systemd complains about not finding the right drivers snd-soc-ac108.ko and snd-soc-wm9860.ko

When I start "sudo ./install.sh" it tells me that there is no build folder in the given kernel what is right indeed.

Does anyone got successfully build drivers for kernel 4.9.26v7-aufs in folder "/lib/modules/4.9.26v7-aufs/kernel/sound/soc/codecs"?

Thank you very much in advance.

Am 22.01.2018 3:33 vorm. schrieb "Baozhu Zuo" notifications@github.com:

@calinichta https://github.com/calinichta I think you need reflash the sd card. then reinstall the seeed-voicecard.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/respeaker/seeed-voicecard/issues/26#issuecomment-359309088, or mute the thread https://github.com/notifications/unsubscribe-auth/Ah9npFp3BMXBSQ8HTTTrRW-sDTE0YHtTks5tM_N7gaJpZM4RgrdH .

Pillar1989 commented 6 years ago

4.9.26v7-aufs？ we only tested seeed-voicecard on raspbian.

calinichta commented 6 years ago

This is the raspbian image 2017-09 for berryboot with kernel 4.9.26v7-aufs - might this cause the problem? As I already mentioned, running an image with kernel 4.9.57 is fine.

Am 22.01.2018 1:06 nachm. schrieb "Baozhu Zuo" notifications@github.com:

4.9.26v7-aufs？ we only tested seeed-voicecard on raspbian.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/respeaker/seeed-voicecard/issues/26#issuecomment-359404988, or mute the thread https://github.com/notifications/unsubscribe-auth/Ah9npFIdVu8lEbaBbckg6s9onGXTOa6Zks5tNHnEgaJpZM4RgrdH .

dkmerona commented 6 years ago

for the comment on linux file, for sure its linux file because my linux system is running well for a lot of applications. typing yname -a give 4.9.59-v7

Pillar1989 commented 6 years ago

@calinichta Have you solved your issue ?

calinichta commented 6 years ago

@Baozhu Zuo Unfortunately I didn't have time to fix it, maybe next week...but I try hard

Am 26.01.2018 7:48 vorm. schrieb "Baozhu Zuo" notifications@github.com:

@calinichta https://github.com/calinichta Have you solved your issue ?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/respeaker/seeed-voicecard/issues/26#issuecomment-360698248, or mute the thread https://github.com/notifications/unsubscribe-auth/Ah9npHq5vHkCN2ZMsbzHT_wgxtJbln8kks5tOXVRgaJpZM4RgrdH .

dkmerona commented 6 years ago

i have kernel 4.9.59-v7 and it's not working. Any help?

calinichta commented 6 years ago

I had updated to that kernel from 4.9.27 and it also didn't work, because typing "uname -r" it still says "kernel 4.9.27...after setting up a complete new image based on kernel 4.9.59-v7 it worked, because" uname -r" says 4.9.59-v7.

I know that this is no help for you, but maybe you experience the same.

Am 26.01.2018 8:47 nachm. schrieb "dkmerona" notifications@github.com:

i have kernel 4.9.59-v7 and it's not working. Any help?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/respeaker/seeed-voicecard/issues/26#issuecomment-360886225, or mute the thread https://github.com/notifications/unsubscribe-auth/Ah9npAL5DJlKSpvLCbt_EN6xqsmWv0ZJks5tOivsgaJpZM4RgrdH .

darles commented 6 years ago

Same here - not working with 4.9.26v7-aufs

Pillar1989 commented 6 years ago

@darles @dkmerona Where can I download berryboot image ?

calinichta commented 6 years ago

You'll find berryboot images on https://berryboot.alexgoldcheidt.com/images/

Am 29.01.2018 2:33 vorm. schrieb "Baozhu Zuo" notifications@github.com:

@darles https://github.com/darles @dkmerona https://github.com/dkmerona Where can I download berryboot image ?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/respeaker/seeed-voicecard/issues/26#issuecomment-361117159, or mute the thread https://github.com/notifications/unsubscribe-auth/Ah9npAZflO_4pz3oB-VWpeGnAbdIpBBPks5tPR_ugaJpZM4RgrdH .

dkmerona commented 6 years ago

anyway can we hope have a patch of driver if needed for 4.9.59-v7 or anybody from seeed confirming that actual drivers are ok for this kernel?

calinichta commented 6 years ago

As I already wrote, drivers work fine on an image with kernel 4.9.57-v7...but not if it was updated from 4.9.26v7-aufs.

Am 29.01.2018 8:41 nachm. schrieb "dkmerona" notifications@github.com:

anyway can we hope have a patch of driver if needed for 4.9.59-v7 or anybody from seeed confirming that actual drivers are ok for this kernel?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/respeaker/seeed-voicecard/issues/26#issuecomment-361362307, or mute the thread https://github.com/notifications/unsubscribe-auth/Ah9npJDNKaN1Et_xf18ri0yU5pwU3EMvks5tPh7zgaJpZM4RgrdH .

dkmerona commented 6 years ago

arg^^; so what to do when you are using a 4.9.57-v7; what are the steps to follow because i updated the kernel and after that i download the driver and tried to install these drivers. May be i uninstall drivers and try to install drivers once more time?

calinichta commented 6 years ago

That didn't work for me. I had to get an image that comes with kernel 4.9.57-v7

Am 29.01.2018 8:53 nachm. schrieb "dkmerona" notifications@github.com:

arg^^; so what to do when you are using a 4.9.57-v7; what are the steps to follow because i updated the kernel and after that i download the driver and tried to install these drivers. May be i uninstall drivers and try to install drivers once more time?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/respeaker/seeed-voicecard/issues/26#issuecomment-361365751, or mute the thread https://github.com/notifications/unsubscribe-auth/Ah9npJ9JQQe7JhajYVyyWn9k1ZoVrd1Pks5tPiGtgaJpZM4RgrdH .

dkmerona commented 6 years ago

well i cannot install a new image as i have other application running ; i need a runnable driver

Pillar1989 commented 6 years ago

@dkmerona If you have raspberrypi-kernel-headers for 4.9.57-v7 version, you can ignore the new image.

ukayzm commented 6 years ago

I'm having the same issue with the initial issue of dm1010111, but 4 mic in my case. I have Raspberry Pi 3 B, respeaker 4-Mics Pi HAT, using Raspbian stretch lite, 4.9.59-v7+ built on 10/29/2017.

Before installing 4mic driver, speaker-test -t wav works fine. After installing 4mic driver by sudo ./install.sh 4mic and reboot, speaker-test -t wav stops forever with this output on console:

$ speaker-test -t wav
speaker-test 1.1.3

Playback device is default
Stream parameters are 48000Hz, S16_LE, 1 channels
WAV file(s)
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 12000 to 18000
Period size range from 6000 to 6000
Using max buffer size 18000
Periods = 4
was set period_size = 6000
was set buffer_size = 18000
 0 - Front Left

After the above output, it does not go any more, but stops forever. I have to press ^C to get out of the stopped speaker-test. It gives this output like this when pressing ^C.

^CWrite error: -4,Interrupted system call
xrun_recovery failed: -4,Interrupted system call
Transfer failed: Interrupted system call

When I uninstall the driver by sudo ./uninstall.sh 4mic; sudo ./uninstall.sh 2mic, and reboot, speaker-test -t wav works fine. I have tried this from re-installing OS several times, but the result is always same.

The strange thing is that the recording works well, even when the playback fails. So I don't think that my 4 mic hat is physically damaged.

Another strange thing is this log on booting up:

[    3.460557]  i2c_id number :0
[    3.460567]  ac108  codec_index :0
[    3.460571]  ac108  I2S data protocol type :1
[    3.461115] ac108_write error->[REG-0x00,val-0x12]
ukayzm commented 6 years ago

FYI, This is the output of arecord and aplay, which is different from the one in http://wiki.seeed.cc/ReSpeaker_4_Mic_Array_for_Raspberry_Pi/ 

$ arecord -L
null
    Discard all samples (playback) or generate zero samples (capture)
default
playback
dmixed
ac108
sysdefault:CARD=seeed4micvoicec
    seeed-4mic-voicecard,
    Default Audio Device
dmix:CARD=seeed4micvoicec,DEV=0
    seeed-4mic-voicecard,
    Direct sample mixing device
dsnoop:CARD=seeed4micvoicec,DEV=0
    seeed-4mic-voicecard,
    Direct sample snooping device
hw:CARD=seeed4micvoicec,DEV=0
    seeed-4mic-voicecard,
    Direct hardware device without any conversions
plughw:CARD=seeed4micvoicec,DEV=0
    seeed-4mic-voicecard,
    Hardware device with all software conversions
$ aplay -L
null
    Discard all samples (playback) or generate zero samples (capture)
default
playback
dmixed
ac108
sysdefault:CARD=ALSA
    bcm2835 ALSA, bcm2835 ALSA
    Default Audio Device
dmix:CARD=ALSA,DEV=0
    bcm2835 ALSA, bcm2835 ALSA
    Direct sample mixing device
dmix:CARD=ALSA,DEV=1
    bcm2835 ALSA, bcm2835 IEC958/HDMI
    Direct sample mixing device
dsnoop:CARD=ALSA,DEV=0
    bcm2835 ALSA, bcm2835 ALSA
    Direct sample snooping device
dsnoop:CARD=ALSA,DEV=1
    bcm2835 ALSA, bcm2835 IEC958/HDMI
    Direct sample snooping device
hw:CARD=ALSA,DEV=0
    bcm2835 ALSA, bcm2835 ALSA
    Direct hardware device without any conversions
hw:CARD=ALSA,DEV=1
    bcm2835 ALSA, bcm2835 IEC958/HDMI
    Direct hardware device without any conversions
plughw:CARD=ALSA,DEV=0
    bcm2835 ALSA, bcm2835 ALSA
    Hardware device with all software conversions
plughw:CARD=ALSA,DEV=1
    bcm2835 ALSA, bcm2835 IEC958/HDMI
    Hardware device with all software conversions
$

Could you please review my issue? Thank you in advance.

Pillar1989 commented 6 years ago

@ukayzm we are so sorry for your encounter. We have been optimized seeed-voicecard installation scheme. Please use the new image to install it. git clone https://github.com/respeaker/seeed-voicecard -b install

ukayzm commented 6 years ago

@Pillar1989, I re-installed driver and now it works fine. Thank you very much.

pbmccabe commented 6 years ago

I've found that no matter what is attempted, sound, for this application only, will always go out the HDMI port if it is available. Leaving it unplugged and accessing via VNC, for example, makes it use the output jack. Then it works. My question is how to control the volume level? The system volume control does nothing with this application. Speaker-test works fine and the volume control works. Modifying mixer values also does nothing for this application. The volume is fixed at quite a high level as it is. Thank you...

jabulonboaz commented 6 years ago

@Pilar1989 and all you have a new image for 2mic too? Or a way to fix this issue please? I am on a Pi3 and running AlexaPi but i can't get the the record to work. Even if i replace the input_device with the error log suggestions bellow then i get different errors: Error log follows:

pi@raspberrypi:~ $ sudo systemctl status AlexaPi.service ? AlexaPi.service - Alexa client for all your devices Loaded: loaded (/usr/lib/systemd/system/AlexaPi.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2018-02-07 01:35:46 UTC; 3min 56s ago Docs: https://github.com/alexa-pi/AlexaPi/wiki Process: 590 ExecStart=/usr/bin/python /opt/AlexaPi/src/main.py --daemon (code=exited, status=1/FAILURE) Main PID: 590 (code=exited, status=1/FAILURE)

Feb 07 01:35:45 raspberrypi python[590]: ALSA lib pcm_dsnoop.c:556:(snd_pcm_dsnoop_open) The dsnoop plugin supports only capture stream Feb 07 01:35:46 raspberrypi python[590]: CRITICAL: Your input_device 'seeed-2mic-voicecard' is invalid. Use one of the following: Feb 07 01:35:46 raspberrypi python[590]: seeed-2mic-voicecard: - (plughw:0,0) Feb 07 01:35:46 raspberrypi python[590]: sysdefault Feb 07 01:35:46 raspberrypi python[590]: capture Feb 07 01:35:46 raspberrypi python[590]: array Feb 07 01:35:46 raspberrypi python[590]: default Feb 07 01:35:46 raspberrypi systemd[1]: AlexaPi.service: Main process exited, code=exited, status=1/FAILURE Feb 07 01:35:46 raspberrypi systemd[1]: AlexaPi.service: Unit entered failed state. Feb 07 01:35:46 raspberrypi systemd[1]: AlexaPi.service: Failed with result 'exit-code'.

Pillar1989 commented 6 years ago

@jabulonboaz Please use a new raspbian image install git clone https://github.com/respeaker/seeed-voicecard -b install . Then setup AlexaPi to your system. install will be merge to master branch quickly.

jabulonboaz commented 6 years ago

@Pillar1989 is this link o for the 2mic drivers yes? what install command do i use ? the above just cloned the git I also tried: git clone https://github.com/respeaker/seeed-voicecard -b install cd seeed-voicecard sudo ./install.sh 2mic sudo reboot But the Respeaker does not get installed i cheeked with "aplay -l" i cant see it pi@raspberrypi:~ $ aplay -l List of PLAYBACK Hardware Devices card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI] Subdevices: 1/1 Subdevice #0: subdevice #0 pi@raspberrypi:~ $

SimonGurney commented 6 years ago

I had this on a Pi Zero.

Did the following

sudo ./uninstall.sh 2mic reboot sudo ./uninstall.sh 4mic reboot sudo ./install.sh 2mic

jabulonboaz commented 6 years ago

I tried that @SimonGurney i saw it on your other post then figured out the ".sh" missing bit from your other post. No luck the above git link does not install it but the old .git url cloned does but i was advised to clone with this new -b install way. Do i have to uninstall with the hat off? I saw u just wrote that somewhere. Btw my final goal is what u have to move the build on a Pi0w from the Pi3. Any pointers are welcomed here as i been "fighting" with this thing for ages.

SimonGurney commented 6 years ago

I did the uninstalls and installs with the hat off as it would kill my pi when I connected it.

Not sure what the new method is but I cloned with the link off the wiki which pulled the git repo.

Do you get anything? I almost gave up hope but when I checked the button on it was working and I could see it’s state changing in python.

Get Outlook for iOShttps://aka.ms/o0ukef

From: jabulonboaz notifications@github.com Sent: Wednesday, February 7, 2018 6:17:05 PM To: respeaker/seeed-voicecard Cc: SimonGurney; Mention Subject: Re: [respeaker/seeed-voicecard] Respeaker 2mic driver does not work on PI 3 B (#26)

I tried that @SimonGurneyhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsimongurney&data=02%7C01%7C%7Cc6cb9aa634e54ae8975e08d56e57026f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636536242330569018&sdata=sm0aQq3wRXMCnIQyM5wrs37MM6pxxTf6Tnl4ycCraFU%3D&reserved=0 i saw it on your other post then figured out the ".sh" missing bit from your other post. No luck the above git link does not install it but the old .git url cloned does but i was advised to clone with this new -b install way. Do i have to uninstall with the hat off? I saw u just wrote that somewhere. Btw my final goal is what u have to move the build on a Pi0w from the Pi3. Any pointers are welcomed here as i been "fighting" with this thing for ages.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Frespeaker%2Fseeed-voicecard%2Fissues%2F26%23issuecomment-363860738&data=02%7C01%7C%7Cc6cb9aa634e54ae8975e08d56e57026f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636536242330569018&sdata=K%2FnI0x%2B5JJuB8KahMOhy2y6p5B1reh2Tr3CT4fvUooY%3D&reserved=0, or mute the threadhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAV5cvUJvNpgrIwctMNlrphjL61mx-C_Rks5tSeihgaJpZM4RgrdH&data=02%7C01%7C%7Cc6cb9aa634e54ae8975e08d56e57026f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636536242330725258&sdata=ja87OJtqN10vZIT65ovn7n22xA9R%2Fk%2Ffpud04JTYkMo%3D&reserved=0.

jabulonboaz commented 6 years ago

I am using AlexaPi and going headless no button Simon. Are you building Alexa with AlexaPi or AVS? I will try your method with the normal git.

SimonGurney commented 6 years ago

There is a button on the 2mic hat that you can read the state from via the gpio.

I’m actually just using it for audio out in a different project, also headless. Might try the alexapi project if it gets a bit better. Would really want drop in support before I went with it.

Get Outlook for iOShttps://aka.ms/o0ukef

From: jabulonboaz notifications@github.com Sent: Wednesday, February 7, 2018 6:40:26 PM To: respeaker/seeed-voicecard Cc: SimonGurney; Mention Subject: Re: [respeaker/seeed-voicecard] Respeaker 2mic driver does not work on PI 3 B (#26)

I am using AlexaPi and going headless no button Simon. Are you building Alexa with AlexaPi or AVS? I will try your method with the normal git.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Frespeaker%2Fseeed-voicecard%2Fissues%2F26%23issuecomment-363867703&data=02%7C01%7C%7C20e1797930204f97ed1708d56e5a4289%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636536256292206014&sdata=C1hgLbdLFmfXHebBSPfAEnTLMbK7LX00KgEykbkNn2Y%3D&reserved=0, or mute the threadhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAV5cvR4LOz482FU7rd346Mr4vXLTHVMCks5tSe4agaJpZM4RgrdH&data=02%7C01%7C%7C20e1797930204f97ed1708d56e5a4289%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636536256292206014&sdata=qlO28vcXE9ZVodRgvokO%2BVLhfSe2CCRKKZ07JyaXreM%3D&reserved=0.

jabulonboaz commented 6 years ago

@Pillar1989 your kind support please how do i install with just this command ? git clone https://github.com/respeaker/seeed-voicecard -b install

jabulonboaz commented 6 years ago

@SimonGurney so what did you use for your build?

SimonGurney commented 6 years ago

This guide http://wiki.seeed.cc/Respeaker_2_Mics_Pi_HAT/

Get Outlook for iOShttps://aka.ms/o0ukef

From: jabulonboaz notifications@github.com Sent: Wednesday, February 7, 2018 7:45:24 PM To: respeaker/seeed-voicecard Cc: SimonGurney; Mention Subject: Re: [respeaker/seeed-voicecard] Respeaker 2mic driver does not work on PI 3 B (#26)

@SimonGurneyhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsimongurney&data=02%7C01%7C%7Cfde4b7f758224ac7d15a08d56e6355d1%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636536295269053593&sdata=xFlwBf1OAsJqkGpmy4Vu84W%2BpsZ5oImrjEXSlExRPEU%3D&reserved=0 so what did you use for your build?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Frespeaker%2Fseeed-voicecard%2Fissues%2F26%23issuecomment-363887792&data=02%7C01%7C%7Cfde4b7f758224ac7d15a08d56e6355d1%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636536295269053593&sdata=75l0I5qY0bvnWLBnjpmiG1d4gWRe4zF5sl4bfUeWGYU%3D&reserved=0, or mute the threadhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAV5cvdd5y9oNUZizb1p9hRCRXAdE1YlOks5tSf1UgaJpZM4RgrdH&data=02%7C01%7C%7Cfde4b7f758224ac7d15a08d56e6355d1%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636536295269053593&sdata=zU%2FrNIoS78pbC5ViRy6aI2efFrMbEqcWSCqmvbSyV2Q%3D&reserved=0.

jabulonboaz commented 6 years ago

@Pillar1989

● AlexaPi.service - Alexa client for all your devices Loaded: loaded (/usr/lib/systemd/system/AlexaPi.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2018-02-07 22:05:22 UTC; 1min 30s ago Docs: https://github.com/alexa-pi/AlexaPi/wiki Process: 562 ExecStart=/usr/bin/python /opt/AlexaPi/src/main.py --daemon (code=exited, status=1/FAILURE) Main PID: 562 (code=exited, status=1/FAILURE)

Feb 07 22:05:22 raspberrypi python[562]: self.fetch_more_tokens() Feb 07 22:05:22 raspberrypi python[562]: File "/usr/local/lib/python2.7/dist-packages/yaml/scanner.py", line 220, in fetch_more_tokens Feb 07 22:05:22 raspberrypi python[562]: return self.fetch_value() Feb 07 22:05:22 raspberrypi python[562]: File "/usr/local/lib/python2.7/dist-packages/yaml/scanner.py", line 576, in fetch_value Feb 07 22:05:22 raspberrypi python[562]: self.get_mark()) Feb 07 22:05:22 raspberrypi python[562]: yaml.scanner.ScannerError: mapping values are not allowed here Feb 07 22:05:22 raspberrypi python[562]: in "/etc/opt/AlexaPi/config.yaml", line 12, column 37 Feb 07 22:05:22 raspberrypi systemd[1]: AlexaPi.service: Main process exited, code=exited, status=1/FAILURE Feb 07 22:05:22 raspberrypi systemd[1]: AlexaPi.service: Unit entered failed state. Feb 07 22:05:22 raspberrypi systemd[1]: AlexaPi.service: Failed with result 'exit-code'.

jabulonboaz commented 6 years ago

i can hear the test sound and i can verify that recording works but alexa does not star up due to audio errors. this happens only with the Respeaker, when i do the same build with a USB mic and the audio jack of the RPi3 Alexa Pi works prefect;y. @yexiaobo-seeedstudio @Pillar1989 we need some support with details please.

Pillar1989 commented 6 years ago

@jabulonboaz We didnt test with Alexa PI. Do you read this document https://github.com/alexa-pi/AlexaPi/wiki/Audio-setup-&-debugging ? Alexa PI have answered the issue.

Feb 07 22:05:22 raspberrypi python[562]: in "/etc/opt/AlexaPi/config.yaml", line 12, column 37
jabulonboaz commented 6 years ago

@Pillar1989 Yes i read it over and over and yes i have already explained that i tried all the combinations and replaced line 12 that is referring to he input device with all the combinations of names for Respeaker 2mic. What is your suggestion please ? And u still did not answer my original question on how to install your you drivers as the git URL u provided does not do anything. Your support would be highly appreciated. Please try AlexaPi and provide a solution to this problem, i have bought 3 respeakers. I have tried all the word combinations described bellow describing the respeaker: pi@raspberrypi:~ $ sudo systemctl status AlexaPi.service ? AlexaPi.service - Alexa client for all your devices Loaded: loaded (/usr/lib/systemd/system/AlexaPi.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2018-02-07 01:35:46 UTC; 3min 56s ago Docs: https://github.com/alexa-pi/AlexaPi/wiki Process: 590 ExecStart=/usr/bin/python /opt/AlexaPi/src/main.py --daemon (code=exited, status=1/FAILURE) Main PID: 590 (code=exited, status=1/FAILURE)

Feb 07 01:35:45 raspberrypi python[590]: ALSA lib pcm_dsnoop.c:556:(snd_pcm_dsnoop_open) The dsnoop plugin supports only capture stream Feb 07 01:35:46 raspberrypi python[590]: CRITICAL: Your input_device 'seeed-2mic-voicecard' is invalid. Use one of the following: Feb 07 01:35:46 raspberrypi python[590]: seeed-2mic-voicecard: - (plughw:0,0) Feb 07 01:35:46 raspberrypi python[590]: sysdefault Feb 07 01:35:46 raspberrypi python[590]: capture Feb 07 01:35:46 raspberrypi python[590]: array Feb 07 01:35:46 raspberrypi python[590]: default Feb 07 01:35:46 raspberrypi systemd[1]: AlexaPi.service: Main process exited, code=exited, status=1/FAILURE Feb 07 01:35:46 raspberrypi systemd[1]: AlexaPi.service: Unit entered failed state. Feb 07 01:35:46 raspberrypi systemd[1]: AlexaPi.service: Failed with result 'exit-code'.

SimonGurney commented 6 years ago

Might not work but I reference the speaker card as “hw:1,0”

Get Outlook for iOShttps://aka.ms/o0ukef

From: jabulonboaz notifications@github.com Sent: Thursday, February 8, 2018 1:19:32 PM To: respeaker/seeed-voicecard Cc: SimonGurney; Mention Subject: Re: [respeaker/seeed-voicecard] Respeaker 2mic driver does not work on PI 3 B (#26)

@Pillar1989https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpillar1989&data=02%7C01%7C%7C2bb47d28b1914422109208d56ef69828%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636536927743750113&sdata=0H5vJeH1X9J9n9I8BinftlN5oYVX8t7lMullX4b3JFY%3D&reserved=0 Yes i read it over and over and yes i have already explained that i tried all the combinations and replaced line 12 that is referring to he input device with all the combinations of names for Respeaker 2mic. What is your suggestion please ? And u still did not answer my original question on how to install your you drivers as the git URL u provided does not do anything. Your support would be highly appreciated.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Frespeaker%2Fseeed-voicecard%2Fissues%2F26%23issuecomment-364109009&data=02%7C01%7C%7C2bb47d28b1914422109208d56ef69828%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636536927743750113&sdata=cbnQm96EMQUPz8Ryc6eYKnJkn3ydIDpD6y8bS%2F%2FUADo%3D&reserved=0, or mute the threadhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAV5cveCVsjz8biXxGRzP_Cyw-_-oPI8fks5tSvRkgaJpZM4RgrdH&data=02%7C01%7C%7C2bb47d28b1914422109208d56ef69828%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636536927743750113&sdata=dg%2FhwCyQNRf0hZM3%2BS4Tyywv8fwiHpmr6mrbObu%2Bg60%3D&reserved=0.