-
Notifications
You must be signed in to change notification settings - Fork 4
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
Default microphone seems not to record #32
Comments
@beckend Thanks, I'll look into why this might be happening. |
I can observe the same issue on a fresh install of Ubuntu 22.10. I tested the mic and speaker in other applications and they work without a hitch. I tried the "play" example and that doesn't seem to work either using the default speakers. I already wrote a bunch of code using wavy on my primary system so I hope I can fix this so I won't have to rewrite that to run it on my second system. I can provide any details necessary to debug this. Thanks. @AldaronLau EDIT:
It seems that the code isn't going past the |
Thanks, @AnkushMalaker! I haven't had as much time as I would like to work on Wavy recently, but I will use some of my holiday time off to look at this, and updating Wavy. I think this might be related to the case where Wavy is not able to get the requested format of F32LE from ALSA, and doesn't properly handle fallbacks. Can you provide a list of the supported I16/F32/etc., interleaved/non-interleaved, and number of channels settings for the default speakers and microphones of both systems? |
Sure! Where/how can I get this info? @AldaronLau |
@AnkushMalaker you can get it by running: arecord --dump-hw-params default Which on my machine, produces
Then, aplay --dump-hw-params default Which on my machine, produces:
|
Thanks. Here it is. @AldaronLau
On the system where it is working:
Do note that the audio recording and playing using above command worked on both systems, ie, I could hear the playback in second command of what I recorded in first command. |
@AldaronLau Hope you had great holidays. |
@AnkushMalaker I wasn't able to put aside as much time as I would like to look at this. But, it looks like the issue is not what I thought it was. I now suspect it has to do with the something in the |
It logs "recording" once, but never reaches to the limit of the buffers to write.
The text was updated successfully, but these errors were encountered: