Skip to content
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

Ubuntu: getting a string instead of samples in data event. #17

Open
jmbldwn opened this issue Aug 9, 2018 · 4 comments
Open

Ubuntu: getting a string instead of samples in data event. #17

jmbldwn opened this issue Aug 9, 2018 · 4 comments

Comments

@jmbldwn
Copy link

jmbldwn commented Aug 9, 2018

My app works perfectly on my mac. When I run it on my ubuntu machine (my actual target) the 'data' event returns strings instead of samples.

I've tried it with a couple of different USB microphones. Here's an example of a message that is coming through the 'data' callback:

re/alsa/alsa.confommon:CARD=0,DEVICE=3,CTLINDEX=0,AES0=4,AES1=130,AES2=0,AES3=2m

What's causing this? I am able to record on this PC using arecord, so it appears ALSA is working in the system.

@jmbldwn
Copy link
Author

jmbldwn commented Aug 9, 2018

Update: appears to be related to asking for a sample format that the hardware doesn't support. Not sure why this isn't an error instead of passing messages through the data event.

@scriptorian
Copy link

Sorry to hear that this wasn't straightforward. I have had a quick review of the code in this area and I can't see anything obvious that would cause what I guess is an error string to be passed to the data event. If you get any more clues please let us know!

@jmbldwn
Copy link
Author

jmbldwn commented Aug 10, 2018

Maybe more data on the environment might help:
Ubuntu 18.04 64-bit server running on a celeron x86 CPU.
There is no native audio hardware on this device; I'm using USB microphones.
I installed alsa using apt. Appears to be version 1.1.3.

What other info would be helpful?

@scriptorian
Copy link

I have just pushed a big update to naudiodon. It would be good to know if the new implementation still has this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants