-
Notifications
You must be signed in to change notification settings - Fork 294
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to start Seeed Voicecard service. #243
Comments
If you have recently upgrade / install new kernel, you might need the v5.5 branch https://github.com/HinTak/seeed-voicecard |
This is the same as #239 , btw. |
I just used the method of reducing the kernel,The sound card is displayed in the aply -l command. |
#238 (comment) see comment regarding downgrading |
@HinTak I tried your fork v5.5 for the 4-mic array on the Pi4 with the the 5.4.51-v7l+ kernel. The soundcard is displayed in arecord-L but not found by pyaudio. Any idea what I can do? |
@TimWolz you have a bug in your python code: why |
You need to use amixer to adjust the volume... And make sure the playback volume is large enough. This is the same issue as #240 |
Also the default seeed studio setup (the one that downgrade the kernel) direct the playback to the on-board phone jack. Everything else is silent for playback, I imagine. Anyway, playback problem does not belong here. Try recording, and transfer the file to your desktop for listen if you cannot find out which phone jack to use for listening. There are more than one, and I am sure you got it wrong. Not a driver problem. There are 3 sound outlets - two phone jacks, one on the pi board and another on the respeaker board, and also hdmi. The downgraded kernel allows you to use only one. More recent kernels they are separately usable, apparently. |
@HinTak Thanks for your reply. The point why I chose 5 is because there aren't more devices. The same code worked well with the old kernel and the master version. Regarding arecord. I can start it with the default device, which is supposed to be the seeed voicecard but it doesn't terminate, although I specify -d 3. And one cannot replay the (faulty) file. Now, if I also want to specify the device -D seeed4micvoicec, the following error occours ALSA lib pcm.c:2565:(snd_pcm_open_noupdate) Unknown PCM seeed4micvoicec |
Use the read me - |
Thanks! Sorry thought I have to specify the device name displayed by arecord. But the command from the readme throws the following error: |
@TimWolz I don't know - I only have the 6-mic device and it works okay with either the old kernel with seeed studio upstream, or current 64-bit ubuntu with my fork... Note also there are two 4-mics devices - one works like a 4-mics, the other works like an 8-mics device with the last few channela empty (i.e. like the 6-mics, but more empty channels). Did you read the wrong section/use the wrong parameters? |
The if-endif block below around the amixer call fixes respeaker#239 respeaker#240 respeaker#243
The if-endif block below around the amixer call fixes respeaker#239 respeaker#240 respeaker#243
● seeed-voicecard.service - Seeed Voicecard service
Loaded: loaded (/lib/systemd/system/seeed-voicecard.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2020-08-23 08:37:00 CST; 4h 5min ago
Main PID: 362 (code=exited, status=1/FAILURE)
8月 23 08:36:46 raspberrypi systemd[1]: Starting Seeed Voicecard service...
8月 23 08:36:47 raspberrypi seeed-voicecard[362]: + exec
8月 23 08:36:47 raspberrypi seeed-voicecard[362]: ++ basename /usr/bin/seeed-voicecard
8月 23 08:37:00 raspberrypi systemd[1]: seeed-voicecard.service: Main process exited, code=exited, status=1/FAILURE
8月 23 08:37:00 raspberrypi systemd[1]: seeed-voicecard.service: Failed with result 'exit-code'.
8月 23 08:37:00 raspberrypi systemd[1]: Failed to start Seeed Voicecard service.
The text was updated successfully, but these errors were encountered: