[alsa-devel] Behringer Uphoria UMC204 usb audio capture only pops and clicks
Should I be posting somewhere else. If so can someone let me know where?
On 04/21/2014 05:12 AM, Andrew Reyes wrote:
Should I be posting somewhere else. If so can someone let me know where?
Please don't start a new thread every time you post but reply to an existing thread. Given the traffic on this list, the conversation is not easy to follow otherwise.
Regarding your issue - the descriptors look sane AFAICS. Please have a look at /proc/asound/card/xxx/stream* (where xxx is the index of your USB soundcard), and report the actual streaming frequency when playing at rates higher than 44.1khz.
You can also monitor the values automatically, like so:
(while sleep 0.123; do grep 'Momentary freq' /proc/asound/xxx/stream0; done) | uniq
Also, how to you play the audio? Try with aplay, and try to tweak the values in the --buffer-size parameters.
Daniel
How do I reply to an existing thread? I'm not clear on that. Sorry about that. I was under the impression I had to reply by using the same subject description.
On Mon, Apr 21, 2014 at 8:25 AM, Daniel Mack daniel@zonque.org wrote:
On 04/21/2014 05:12 AM, Andrew Reyes wrote:
Should I be posting somewhere else. If so can someone let me know where?
Please don't start a new thread every time you post but reply to an existing thread. Given the traffic on this list, the conversation is not easy to follow otherwise.
Regarding your issue - the descriptors look sane AFAICS. Please have a look at /proc/asound/card/xxx/stream* (where xxx is the index of your USB soundcard), and report the actual streaming frequency when playing at rates higher than 44.1khz.
You can also monitor the values automatically, like so:
(while sleep 0.123; do grep 'Momentary freq' /proc/asound/xxx/stream0; done) | uniq
Also, how to you play the audio? Try with aplay, and try to tweak the values in the --buffer-size parameters.
Daniel
And this is the pastebin link for the stream info set at 48khz: http://pastebin.com/ysw6j5uA
On Mon, Apr 21, 2014 at 9:10 AM, Andrew Reyes dsreyes1014@gmail.com wrote:
How do I reply to an existing thread? I'm not clear on that. Sorry about that. I was under the impression I had to reply by using the same subject description.
On Mon, Apr 21, 2014 at 8:25 AM, Daniel Mack daniel@zonque.org wrote:
On 04/21/2014 05:12 AM, Andrew Reyes wrote:
Should I be posting somewhere else. If so can someone let me know where?
Please don't start a new thread every time you post but reply to an existing thread. Given the traffic on this list, the conversation is not easy to follow otherwise.
Regarding your issue - the descriptors look sane AFAICS. Please have a look at /proc/asound/card/xxx/stream* (where xxx is the index of your USB soundcard), and report the actual streaming frequency when playing at rates higher than 44.1khz.
You can also monitor the values automatically, like so:
(while sleep 0.123; do grep 'Momentary freq' /proc/asound/xxx/stream0; done) | uniq
Also, how to you play the audio? Try with aplay, and try to tweak the values in the --buffer-size parameters.
Daniel
(please do not top-post)
On 04/21/2014 04:17 PM, Andrew Reyes wrote:
And this is the pastebin link for the stream info set at 48khz: http://pastebin.com/ysw6j5uA
Ok, so the actual frequency is close enough to the nominal one. Please also do the tests wit aplay to see whether your issue can be recovered by chosing larger buffer sizes. Do you see any messages in dmesg when these 'clicks and pop' occur?
Also, please try this one:
(while sleep 0.123; do grep 'Momentary freq' /proc/asound/xxx/stream0; done) | uniq
Thanks, Daniel
The while shell command shows consistent 96k when set at 96khz and dmesg shows nothing where it pops and clicks. How do I use aplay to adjust buffer-size?
On Mon, Apr 21, 2014 at 11:11 AM, Daniel Mack daniel@zonque.org wrote:
(please do not top-post)
On 04/21/2014 04:17 PM, Andrew Reyes wrote:
And this is the pastebin link for the stream info set at 48khz: http://pastebin.com/ysw6j5uA
Ok, so the actual frequency is close enough to the nominal one. Please also do the tests wit aplay to see whether your issue can be recovered by chosing larger buffer sizes. Do you see any messages in dmesg when these 'clicks and pop' occur?
Also, please try this one:
(while sleep 0.123; do grep 'Momentary freq' /proc/asound/xxx/stream0; done) | uniq
Thanks, Daniel
(Please, do not top-post but quote properly!)
On 04/21/2014 06:51 PM, Andrew Reyes wrote:
The while shell command shows consistent 96k when set at 96khz and dmesg shows nothing where it pops and clicks. How do I use aplay to adjust buffer-size?
aplay -Dhw:xxx --buffer-size 2048 file.wav
(again, xxx is the index or short name of your audio card).
Which application do you normally use to play audio?
Daniel
aplay -Dhw:xxx --buffer-size 2048 file.wav
(again, xxx is the index or short name of your audio card).
Which application do you normally use to play audio?
I'm using JACK right now for recording and gigging live and pulseaudio for Youtube and movies. Here is the pastebin link for the aplay command: http://pastebin.com/3nquKW12
On Mon, Apr 21, 2014 at 12:49 PM, Daniel Mack daniel@zonque.org wrote:
(Please, do not top-post but quote properly!)
On 04/21/2014 06:51 PM, Andrew Reyes wrote:
The while shell command shows consistent 96k when set at 96khz and dmesg shows nothing where it pops and clicks. How do I use aplay to adjust buffer-size?
aplay -Dhw:xxx --buffer-size 2048 file.wav
(again, xxx is the index or short name of your audio card).
Which application do you normally use to play audio?
Daniel
On 04/21/2014 08:33 PM, Andrew Reyes wrote:
aplay -Dhw:xxx --buffer-size 2048 file.wav
(again, xxx is the index or short name of your audio card).
Which application do you normally use to play audio?
I'm using JACK right now for recording and gigging live and pulseaudio for Youtube and movies.
Bot should of course work, but as they're built on top of ALSA, it's best to debug directly on the lower level. IOW: with aplay.
Here is the pastebin link for the aplay command: http://pastebin.com/3nquKW12
Playing WAVE 'Open The Eyes Of My Heart.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo aplay: set_params:1233: Sample format non available Available formats:
- S32_LE
Ok, in this case, please use "plughw" instead of "hw".
Daniel
Ok, in this case, please use "plughw" instead of "hw".
Ok that worked. It plays fine at 44100 but when I try to set `--period-size=48000` it still defaults to 44100.
On Mon, Apr 21, 2014 at 1:37 PM, Daniel Mack daniel@zonque.org wrote:
On 04/21/2014 08:33 PM, Andrew Reyes wrote:
aplay -Dhw:xxx --buffer-size 2048 file.wav
(again, xxx is the index or short name of your audio card).
Which application do you normally use to play audio?
I'm using JACK right now for recording and gigging live and pulseaudio
for
Youtube and movies.
Bot should of course work, but as they're built on top of ALSA, it's best to debug directly on the lower level. IOW: with aplay.
Here is the pastebin link for the aplay command: http://pastebin.com/3nquKW12
Playing WAVE 'Open The Eyes Of My Heart.wav' : Signed 16 bit Little
Endian, Rate 44100 Hz, Stereo
aplay: set_params:1233: Sample format non available Available formats:
- S32_LE
Ok, in this case, please use "plughw" instead of "hw".
Daniel
Ok, in this case, please use "plughw" instead of "hw".
Ok that worked. It plays fine at 44100 but when I try to set
`--period-size=48000` it still defaults to 44100.
I'm sorry I meant to `--rate=48000`.
On Mon, Apr 21, 2014 at 1:44 PM, Andrew Reyes dsreyes1014@gmail.com wrote:
Ok, in this case, please use "plughw" instead of "hw".
Ok that worked. It plays fine at 44100 but when I try to set `--period-size=48000` it still defaults to 44100.
On Mon, Apr 21, 2014 at 1:37 PM, Daniel Mack daniel@zonque.org wrote:
On 04/21/2014 08:33 PM, Andrew Reyes wrote:
aplay -Dhw:xxx --buffer-size 2048 file.wav
(again, xxx is the index or short name of your audio card).
Which application do you normally use to play audio?
I'm using JACK right now for recording and gigging live and pulseaudio
for
Youtube and movies.
Bot should of course work, but as they're built on top of ALSA, it's best to debug directly on the lower level. IOW: with aplay.
Here is the pastebin link for the aplay command: http://pastebin.com/3nquKW12
Playing WAVE 'Open The Eyes Of My Heart.wav' : Signed 16 bit Little
Endian, Rate 44100 Hz, Stereo
aplay: set_params:1233: Sample format non available Available formats:
- S32_LE
Ok, in this case, please use "plughw" instead of "hw".
Daniel
On 04/21/2014 08:49 PM, Andrew Reyes wrote:
Ok, in this case, please use "plughw" instead of "hw".
Ok that worked. It plays fine at 44100 but when I try to set
`--period-size=48000` it still defaults to 44100.
I'm sorry I meant to `--rate=48000`.
Generate some sine wav files in various rates with something like audacity and play them. FWIW, a 192k file can be found here:
http://zonque.org/sine-192khz.wav (~22 MB)
Daniel
Generate some sine wav files in various rates with something like audacity and play them. FWIW, a 192k file can be found here:
http://zonque.org/sine-192khz.wav (~22 MB)
Ok I will try that now. I should let you know that I just tried the arecord command for that same device at 48000 and it pops and clicks just as in JACK.
On Mon, Apr 21, 2014 at 1:54 PM, Daniel Mack daniel@zonque.org wrote:
On 04/21/2014 08:49 PM, Andrew Reyes wrote:
Ok, in this case, please use "plughw" instead of "hw".
Ok that worked. It plays fine at 44100 but when I try to set
`--period-size=48000` it still defaults to 44100.
I'm sorry I meant to `--rate=48000`.
Generate some sine wav files in various rates with something like audacity and play them. FWIW, a 192k file can be found here:
http://zonque.org/sine-192khz.wav (~22 MB)
Daniel
Ok I did playback on a 48khz song and no pops and clicks. So it's just on the capture side only. What could cause that on the capture side of things?
On Mon, Apr 21, 2014 at 1:56 PM, Andrew Reyes dsreyes1014@gmail.com wrote:
Generate some sine wav files in various rates with something like audacity and play them. FWIW, a 192k file can be found here:
http://zonque.org/sine-192khz.wav (~22 MB)
Ok I will try that now. I should let you know that I just tried the arecord command for that same device at 48000 and it pops and clicks just as in JACK.
On Mon, Apr 21, 2014 at 1:54 PM, Daniel Mack daniel@zonque.org wrote:
On 04/21/2014 08:49 PM, Andrew Reyes wrote:
Ok, in this case, please use "plughw" instead of "hw".
Ok that worked. It plays fine at 44100 but when I try to set
`--period-size=48000` it still defaults to 44100.
I'm sorry I meant to `--rate=48000`.
Generate some sine wav files in various rates with something like audacity and play them. FWIW, a 192k file can be found here:
http://zonque.org/sine-192khz.wav (~22 MB)
Daniel
Is there something else I could do to get to the problem?
On Mon, Apr 21, 2014 at 3:33 PM, Andrew Reyes dsreyes1014@gmail.com wrote:
Ok I did playback on a 48khz song and no pops and clicks. So it's just on the capture side only. What could cause that on the capture side of things?
On Mon, Apr 21, 2014 at 1:56 PM, Andrew Reyes dsreyes1014@gmail.comwrote:
Generate some sine wav files in various rates with something like audacity and play them. FWIW, a 192k file can be found here:
http://zonque.org/sine-192khz.wav (~22 MB)
Ok I will try that now. I should let you know that I just tried the arecord command for that same device at 48000 and it pops and clicks just as in JACK.
On Mon, Apr 21, 2014 at 1:54 PM, Daniel Mack daniel@zonque.org wrote:
On 04/21/2014 08:49 PM, Andrew Reyes wrote:
Ok, in this case, please use "plughw" instead of "hw".
Ok that worked. It plays fine at 44100 but when I try to set
`--period-size=48000` it still defaults to 44100.
I'm sorry I meant to `--rate=48000`.
Generate some sine wav files in various rates with something like audacity and play them. FWIW, a 192k file can be found here:
http://zonque.org/sine-192khz.wav (~22 MB)
Daniel
On April 23, 2014 4:40:07 PM CEST, Andrew Reyes dsreyes1014@gmail.com wrote:
Is there something else I could do to get to the problem?
I can just give you a few more ideas to debug this, but that includes more action from your side.
* First of all, try the same device on a different computer, and/or a different USB port, especially if you're using an XHCI (USB3) port.
* Try the device on Mac OS X, without installing a driver and see if you have the same problem here.
* Use usbmon and analyze the data stream when a pop occurs. Compare that with settings that don't produce pops. There's good documentation on usbmon in Documentation/usb/ in the Linux kernel.
Best regards, Daniel
I can just give you a few more ideas to debug this, but that includes
more action from your side.
- First of all, try the same device on a different computer, and/or a
different USB port, especially if you're using an XHCI (USB3) port.
- Try the device on Mac OS X, without installing a driver and see if you
have the same problem here.
- Use usbmon and analyze the data stream when a pop occurs. Compare that
with settings that don't produce pops. There's good documentation on usbmon in Documentation/usb/ in the Linux kernel.
Ok cool. I'll get right on that. I did try the first suggestion on four different computers and different ports and it's the same issue but just to be thorough I'll check again.
On Wed, Apr 23, 2014 at 9:59 AM, Daniel Mack daniel@zonque.org wrote:
On April 23, 2014 4:40:07 PM CEST, Andrew Reyes dsreyes1014@gmail.com wrote:
Is there something else I could do to get to the problem?
I can just give you a few more ideas to debug this, but that includes more action from your side.
- First of all, try the same device on a different computer, and/or a
different USB port, especially if you're using an XHCI (USB3) port.
- Try the device on Mac OS X, without installing a driver and see if you
have the same problem here.
- Use usbmon and analyze the data stream when a pop occurs. Compare that
with settings that don't produce pops. There's good documentation on usbmon in Documentation/usb/ in the Linux kernel.
Best regards, Daniel
-- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Ok I got the two different logs and I don't what I'm looking for lol. It's just raw data. My last option is to try using it on Windows or Mac just to make sure it's not the interface.
On Wed, Apr 23, 2014 at 10:40 AM, Andrew Reyes dsreyes1014@gmail.comwrote:
I can just give you a few more ideas to debug this, but that includes
more action from your side.
- First of all, try the same device on a different computer, and/or a
different USB port, especially if you're using an XHCI (USB3) port.
- Try the device on Mac OS X, without installing a driver and see if you
have the same problem here.
- Use usbmon and analyze the data stream when a pop occurs. Compare that
with settings that don't produce pops. There's good documentation on usbmon in Documentation/usb/ in the Linux kernel.
Ok cool. I'll get right on that. I did try the first suggestion on four different computers and different ports and it's the same issue but just to be thorough I'll check again.
On Wed, Apr 23, 2014 at 9:59 AM, Daniel Mack daniel@zonque.org wrote:
On April 23, 2014 4:40:07 PM CEST, Andrew Reyes dsreyes1014@gmail.com wrote:
Is there something else I could do to get to the problem?
I can just give you a few more ideas to debug this, but that includes more action from your side.
- First of all, try the same device on a different computer, and/or a
different USB port, especially if you're using an XHCI (USB3) port.
- Try the device on Mac OS X, without installing a driver and see if you
have the same problem here.
- Use usbmon and analyze the data stream when a pop occurs. Compare that
with settings that don't produce pops. There's good documentation on usbmon in Documentation/usb/ in the Linux kernel.
Best regards, Daniel
-- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Daniel I got my hands on Windows 7 PC and installed the drivers from the website and it does the samething. So now I'm leaning toward a defective soundcard. I'm sending it back for a new one.
On Wed, Apr 23, 2014 at 11:18 AM, Andrew Reyes dsreyes1014@gmail.comwrote:
Ok I got the two different logs and I don't what I'm looking for lol. It's just raw data. My last option is to try using it on Windows or Mac just to make sure it's not the interface.
On Wed, Apr 23, 2014 at 10:40 AM, Andrew Reyes dsreyes1014@gmail.comwrote:
I can just give you a few more ideas to debug this, but that includes
more action from your side.
- First of all, try the same device on a different computer, and/or a
different USB port, especially if you're using an XHCI (USB3) port.
- Try the device on Mac OS X, without installing a driver and see if
you have the same problem here.
- Use usbmon and analyze the data stream when a pop occurs. Compare
that with settings that don't produce pops. There's good documentation on usbmon in Documentation/usb/ in the Linux kernel.
Ok cool. I'll get right on that. I did try the first suggestion on four different computers and different ports and it's the same issue but just to be thorough I'll check again.
On Wed, Apr 23, 2014 at 9:59 AM, Daniel Mack daniel@zonque.org wrote:
On April 23, 2014 4:40:07 PM CEST, Andrew Reyes dsreyes1014@gmail.com wrote:
Is there something else I could do to get to the problem?
I can just give you a few more ideas to debug this, but that includes more action from your side.
- First of all, try the same device on a different computer, and/or a
different USB port, especially if you're using an XHCI (USB3) port.
- Try the device on Mac OS X, without installing a driver and see if you
have the same problem here.
- Use usbmon and analyze the data stream when a pop occurs. Compare that
with settings that don't produce pops. There's good documentation on usbmon in Documentation/usb/ in the Linux kernel.
Best regards, Daniel
-- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Daniel it turns out with a brand new UMC204 it still does it on my linux box. I'm at a loss.
On Thu, Apr 24, 2014 at 9:14 AM, Andrew Reyes dsreyes1014@gmail.com wrote:
Daniel I got my hands on Windows 7 PC and installed the drivers from the website and it does the samething. So now I'm leaning toward a defective soundcard. I'm sending it back for a new one.
On Wed, Apr 23, 2014 at 11:18 AM, Andrew Reyes dsreyes1014@gmail.comwrote:
Ok I got the two different logs and I don't what I'm looking for lol. It's just raw data. My last option is to try using it on Windows or Mac just to make sure it's not the interface.
On Wed, Apr 23, 2014 at 10:40 AM, Andrew Reyes dsreyes1014@gmail.comwrote:
I can just give you a few more ideas to debug this, but that includes
more action from your side.
- First of all, try the same device on a different computer, and/or a
different USB port, especially if you're using an XHCI (USB3) port.
- Try the device on Mac OS X, without installing a driver and see if
you have the same problem here.
- Use usbmon and analyze the data stream when a pop occurs. Compare
that with settings that don't produce pops. There's good documentation on usbmon in Documentation/usb/ in the Linux kernel.
Ok cool. I'll get right on that. I did try the first suggestion on four different computers and different ports and it's the same issue but just to be thorough I'll check again.
On Wed, Apr 23, 2014 at 9:59 AM, Daniel Mack daniel@zonque.org wrote:
On April 23, 2014 4:40:07 PM CEST, Andrew Reyes dsreyes1014@gmail.com wrote:
Is there something else I could do to get to the problem?
I can just give you a few more ideas to debug this, but that includes more action from your side.
- First of all, try the same device on a different computer, and/or a
different USB port, especially if you're using an XHCI (USB3) port.
- Try the device on Mac OS X, without installing a driver and see if
you have the same problem here.
- Use usbmon and analyze the data stream when a pop occurs. Compare
that with settings that don't produce pops. There's good documentation on usbmon in Documentation/usb/ in the Linux kernel.
Best regards, Daniel
-- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
(please, do not top post!)
On April 29, 2014 6:53:36 PM WAT, Andrew Reyes dsreyes1014@gmail.com wrote:
Daniel it turns out with a brand new UMC204 it still does it on my linux box. I'm at a loss.
Try that one on Windows as well. Uf it doesn't work there either, send tge hardqare back and get a different model. If the hardware has such severe bugs, there nothing the Linux driver can do to fix it up.
Daniel
On Thu, Apr 24, 2014 at 9:14 AM, Andrew Reyes dsreyes1014@gmail.com wrote:
Daniel I got my hands on Windows 7 PC and installed the drivers from
the
website and it does the samething. So now I'm leaning toward a
defective
soundcard. I'm sending it back for a new one.
On Wed, Apr 23, 2014 at 11:18 AM, Andrew Reyes
dsreyes1014@gmail.comwrote:
Ok I got the two different logs and I don't what I'm looking for
lol.
It's just raw data. My last option is to try using it on Windows or
Mac
just to make sure it's not the interface.
On Wed, Apr 23, 2014 at 10:40 AM, Andrew Reyes
dsreyes1014@gmail.comwrote:
I can just give you a few more ideas to debug this, but that
includes
more action from your side.
- First of all, try the same device on a different computer,
and/or a
different USB port, especially if you're using an XHCI (USB3) port.
- Try the device on Mac OS X, without installing a driver and see
if
you have the same problem here.
- Use usbmon and analyze the data stream when a pop occurs.
Compare
that with settings that don't produce pops. There's good
documentation on
usbmon in Documentation/usb/ in the Linux kernel.
Ok cool. I'll get right on that. I did try the first suggestion on
four
different computers and different ports and it's the same issue but
just to
be thorough I'll check again.
On Wed, Apr 23, 2014 at 9:59 AM, Daniel Mack daniel@zonque.org
wrote:
On April 23, 2014 4:40:07 PM CEST, Andrew Reyes
wrote:
Is there something else I could do to get to the problem?
I can just give you a few more ideas to debug this, but that
includes
more action from your side.
- First of all, try the same device on a different computer,
and/or a
different USB port, especially if you're using an XHCI (USB3)
port.
- Try the device on Mac OS X, without installing a driver and see
if
you have the same problem here.
- Use usbmon and analyze the data stream when a pop occurs.
Compare
that with settings that don't produce pops. There's good
documentation on
usbmon in Documentation/usb/ in the Linux kernel.
Best regards, Daniel
-- Sent from my Android phone with K-9 Mail. Please excuse my
brevity.
participants (2)
-
Andrew Reyes -
Daniel Mack