On 08/22/2016 08:34 PM, Norman nolte wrote:
> On 08/22/2016 08:49 AM, Daniel Mack wrote:
>> On 07/19/2016 10:08 PM, Norman nolte wrote:
>>> Currently the patch is only activated for UD-H01 and other models
>>> sharing the same usb product id but it is possible that this patch might
>>> be useful
Hi Daniel,
On 08/22/2016 08:49 AM, Daniel Mack wrote:
Hi Norman,
On 07/19/2016 10:08 PM, Norman nolte wrote:
I own a TEAC UD-H01 DAC. I'm aware that the UD-H01 has a strange/faulty
feedback frequency behaviour which is fortunately already handled by a
quirk in ALSA snd-usb-audio kernel module
Hi Norman,
On 07/19/2016 10:08 PM, Norman nolte wrote:
> I own a TEAC UD-H01 DAC. I'm aware that the UD-H01 has a strange/faulty
> feedback frequency behaviour which is fortunately already handled by a
> quirk in ALSA snd-usb-audio kernel module (git commit
> 7040b6d1febfdbd9c1595efb751d492cd25
On 05/14/2014 02:04 PM, Masaru Nomiya wrote:
> [...]
> 014-05-14T09:39:34.554436+09:00 linux-uw5l kernel: [ 255.186576] XXX
> snd_usb_add_endpoint():478
Ok, so the quirk is set, but doesn't work for your card. Someone needs
to figure out what sort of workaround must be used in order to fix it.
Hello,
In the Message;
Subject: Re: [Alsa-user] Problem with TEAC USB UD-H01 and ALSA
Message-ID : <5373192a.5040...@zonque.org>
Date & Time: Wed, 14 May 2014 09:20:10 +0200
Daniel Mack has written:
> And now search for the XXX marker instead:
> # cat messages | g
On 05/14/2014 03:03 AM, Masaru Nomiya wrote:
> Daniel Mack has written:
>> if ((chip->usb_id == USB_ID(0x0644, 0x8038) || /* TEAC UD-H01 */
>> chip->usb_id == USB_ID(0x0644, 0x8043)) && /* TEAC UD-501 */
>> ep->syncmaxsize == 4) {
>> printk(KERN_ERR "XXX %s():%d\n", __
Hello,
In the Message;
Subject: Re: [Alsa-user] Problem with TEAC USB UD-H01 and ALSA
Message-ID : <5371f686.2010...@zonque.org>
Date & Time: Tue, 13 May 2014 12:40:06 +0200
Daniel Mack has written:
[...]
> Nope. What I meant is this:
> if ((chip->usb_id == US
Hello,
In the Message;
Subject: Re: [Alsa-user] Problem with TEAC USB UD-H01 and ALSA
Message-ID :
Date & Time: Tue, 13 May 2014 14:06:19 +0200
Takashi Iwai has written:
> At Tue, 13 May 2014 19:52:54 +0900,
> Masaru Nomiya wrote:
>>
[...]
>> What is &quo
At Tue, 13 May 2014 19:52:54 +0900,
Masaru Nomiya wrote:
>
> Hello,
>
> In the Message;
>
> Subject : Re: [Alsa-user] Problem with TEAC USB UD-H01 and ALSA
> Message-ID : <5371f686.2010...@zonque.org>
> Date & Time: Tue, 13 May 2014 12:40:06 +
Hello,
In the Message;
Subject: Re: [Alsa-user] Problem with TEAC USB UD-H01 and ALSA
Message-ID : <5371f686.2010...@zonque.org>
Date & Time: Tue, 13 May 2014 12:40:06 +0200
Daniel Mack has written:
> On 05/13/2014 12:19 PM, Masaru Nomiya wrote:
> > Maybe, I&#x
On 05/13/2014 12:19 PM, Masaru Nomiya wrote:
> Maybe, I've got mistaken. That is, I added your advice as follows;
>
> if ((chip->usb_id == USB_ID(0x0644, 0x8038) || /* TEAC UD-H01
> */
>chip->usb_id == USB_ID(0x0644, 0x8043)) && /* TEAC UD-501
> */
>
Hello,
In the Message;
Subject: Re: [Alsa-user] Problem with TEAC USB UD-H01 and ALSA
Message-ID : <5371edc0.7050...@zonque.org>
Date & Time: Tue, 13 May 2014 12:02:40 +0200
Daniel Mack has written:
> On 05/13/2014 11:55 AM, Masaru Nomiya wrote:
> > Danie
On 05/13/2014 11:55 AM, Masaru Nomiya wrote:
> Daniel Mack has written:
>
>> It is related, but the code relies on the boolean variable
>> sender->udh01_fb_quirk which should be set for you device by the patch I
>> sent you. You could add this line inside this if-condition:
>
>> printk(KERN_ER
Hello,
In the Message;
Subject: Re: [Alsa-user] Problem with TEAC USB UD-H01 and ALSA
Message-ID : <537084ad.6010...@zonque.org>
Date & Time: Mon, 12 May 2014 10:22:05 +0200
Daniel Mack has written:
> On 05/12/2014 10:15 AM, Masaru Nomiya wrote:
> > Danie
On 05/12/2014 10:15 AM, Masaru Nomiya wrote:
> Daniel Mack has written:
>> Yes. If the quirk doesn't work for you, the device needs some other
>> workaround than the UD-H01.
>
> Is this not related?
>
> [...]
> if (unlikely(sender->udh01_fb_quirk)) {
It is related, but the code relies on
Hello,
In the Message;
Subject: Re: [Alsa-user] Problem with TEAC USB UD-H01 and ALSA
Message-ID : <536f41ad.9020...@zonque.org>
Date & Time: Sun, 11 May 2014 11:23:57 +0200
Daniel Mack has written:
> On 05/11/2014 06:57 AM, Masaru Nomiya wrote:
>> In the Message
On 05/11/2014 06:57 AM, Masaru Nomiya wrote:
> In the Message;
>
> Subject : Re: [Alsa-user] Problem with TEAC USB UD-H01 and ALSA
> Message-ID : <536e5f58.4020...@zonque.org>
> Date & Time: Sat, 10 May 2014 19:18:16 +0200
>
> Daniel Mack has written:
I saw it is in 3.15.rc5, and it works fine for me (TEAC UD-H01).
Splendid, thanks!
Rutger.
On ven., 2014-05-09 at 09:00 +0200, Clemens Ladisch wrote:
> Rutger Noot wrote:
> > I heard that there is a patch solving the problem with the TEAC USB
> > UD-H01. Did that already make it to a stable ke
Hello,
In the Message;
Subject: Re: [Alsa-user] Problem with TEAC USB UD-H01 and ALSA
Message-ID : <536e5f58.4020...@zonque.org>
Date & Time: Sat, 10 May 2014 19:18:16 +0200
Daniel Mack has written:
> Please test the attached patch, on top of Linus' master git
On 05/10/2014 06:53 AM, 野宮 賢 / NOMIYA Masaru wrote:
> In the Message;
>
> Subject : Re: [Alsa-user] Problem with TEAC USB UD-H01 and ALSA
> Message-ID : <536d9c74.9020...@benoist.name>
> Date & Time: Fri, 09 May 2014 20:26:44 -0700
>
> Julien Benoist h
Hello,
In the Message;
Subject: Re: [Alsa-user] Problem with TEAC USB UD-H01 and ALSA
Message-ID : <87d2fm1bgv.wl%nom...@galaxy.dti.ne.jp>
Date & Time: Sat, 10 May 2014 13:53:04 +0900
野宮 賢 / NOMIYA Masaru has written:
> In the Message;
> Subject: Re: [Al
In the Message;
Subject: Re: [Alsa-user] Problem with TEAC USB UD-H01 and ALSA
Message-ID : <536d9c74.9020...@benoist.name>
Date & Time: Fri, 09 May 2014 20:26:44 -0700
Julien Benoist has written:
> On 05/09/2014 12:00 AM, Clemens Ladisch wrote:
>> Rutger Noot
On 05/09/2014 12:00 AM, Clemens Ladisch wrote:
> Rutger Noot wrote:
>> I heard that there is a patch solving the problem with the TEAC USB
>> UD-H01. Did that already make it to a stable kernel?
>
> Linus merged the patch yesterday; it should show up in the next
> stable kernel.
FYI, your patch al
Rutger Noot wrote:
> I heard that there is a patch solving the problem with the TEAC USB
> UD-H01. Did that already make it to a stable kernel?
Linus merged the patch yesterday; it should show up in the next
stable kernel.
Regards,
Clemens
---
Dear all,
I heard that there is a patch solving the problem with the TEAC USB
UD-H01. Did that already make it to a stable kernel?
For what it is worth, I am now running a stable fedora kernel:
3.14.2-200.fc20.x86_64 and the behaviour has changed. No more clicks,
but now there is another artefa
On 04/04/2014 02:02 AM, Daniel Mack wrote:
>> Yesterday I got my hands on more diverse 24/192 content to make more
>> experiments. I've come to the conclusion that the crackles that were
>> very noticeable with the patch mentioned upper in the thread are not
>> 100% absent without the patch, they a
On 04/04/2014 11:41 AM, Clemens Ladisch wrote:
> jul...@benoist.name wrote:
>> On 04/02/2014 04:01 AM, Clemens Ladisch wrote:
>>> What are the contents of /proc/asound/card/*/stream0 before and after
>>> this patch, for aplay and xbmc?
>>
>> Status: Running
>> Interface = 3
>> Altset = 2
jul...@benoist.name wrote:
> On 04/02/2014 04:01 AM, Clemens Ladisch wrote:
>> What are the contents of /proc/asound/card/*/stream0 before and after
>> this patch, for aplay and xbmc?
>
> Status: Running
> Interface = 3
> Altset = 2
> Packet Size = 156
> Momentary freq = 183992 Hz
On 04/04/2014 08:54 AM, jul...@benoist.name wrote:
> On 04/03/2014 11:16 AM, Daniel Mack wrote:
>> ... 16bit, so things don't work for you in 192k/16bit, right?
>
> Well, it's not like I had experienced a lot with it, but the few times I
> tried 16/192, I didn't hear the crackles that are very n
On 04/03/2014 11:16 AM, Daniel Mack wrote:
>> TEAC TEAC USB AUDIO DEVICE at usb-:00:1d.0-1.4, high speed : USB Audio
>
> That's a device with IDs 0644:8038, correct?
That's right, here's how the USB stack announces it:
[67129.718571] hid-generic 0003:0644:8038.0006: input,hidraw2: USB HID
v
On 04/03/2014 04:11 AM, jul...@benoist.name wrote:
> On 04/02/2014 04:01 AM, Clemens Ladisch wrote:
>> What are the contents of /proc/asound/card/*/stream0 before and after
>> this patch, for aplay and xbmc?
>
> It's essentially unchanged, before and after the patch, with aplay(*)
> and xbmc, exc
Daniel Mack zonque.org> writes:
..
>
> Please post the output of 'lsusb -v'.
>
Dear Daniel
thank you for considering this.
Though my knowledge of Linux is not so deep,
I would be glade to help you as a tester,
for what I would be able to do to solve this issue.
The only thing I've got to
Daniel Mack zonque.org> writes:
>
> Hi,
>
> On 03/28/2014 06:49 PM, Andrea M wrote:
> > I bought an USB DAC from TEAC (device UD-H01 with chip TENOR 8802) and this,
> > with its own drivers, works perfectly under Windows7 and OSX ( I tried both
> > with 16 and 24 bit from 44.1 to 192Khz).
>
>
Daniel Mack zonque.org> writes:
>
> Hi,
>
> On 03/28/2014 06:49 PM, Andrea M wrote:
> > I bought an USB DAC from TEAC (device UD-H01 with chip TENOR 8802) and this,
> > with its own drivers, works perfectly under Windows7 and OSX ( I tried both
> > with 16 and 24 bit from 44.1 to 192Khz).
>
>
Daniel Mack zonque.org> writes:
>
> Hi,
>
> On 03/28/2014 06:49 PM, Andrea M wrote:
> > I bought an USB DAC from TEAC (device UD-H01 with chip TENOR 8802) and this,
> > with its own drivers, works perfectly under Windows7 and OSX ( I tried both
> > with 16 and 24 bit from 44.1 to 192Khz).
>
>
On 04/02/2014 04:01 AM, Clemens Ladisch wrote:
> What are the contents of /proc/asound/card/*/stream0 before and after
> this patch, for aplay and xbmc?
It's essentially unchanged, before and after the patch, with aplay(*)
and xbmc, except for 'momentary freq' which varies of course, but stays
i
Daniel Mack wrote:
> On 04/02/2014 10:12 AM, jul...@benoist.name wrote:
>> On 03/31/2014 12:02 PM, Daniel Mack wrote:
>>> If you're really certain about this, and if you can rule out all other
>>> components than the kernel, please do a git bisect to find which commit
>>> causes this regression. De
Hi Julien,
On 04/02/2014 10:12 AM, jul...@benoist.name wrote:
> On 03/31/2014 12:02 PM, Daniel Mack wrote:
>> If you're really certain about this, and if you can rule out all other
>> components than the kernel, please do a git bisect to find which commit
>> causes this regression. Depending on ho
On 03/31/2014 12:02 PM, Daniel Mack wrote:
> If you're really certain about this, and if you can rule out all other
> components than the kernel, please do a git bisect to find which commit
> causes this regression. Depending on how long it takes you to tell
> whether a kernel version is affected,
Hi,
On 03/28/2014 06:49 PM, Andrea M wrote:
> I bought an USB DAC from TEAC (device UD-H01 with chip TENOR 8802) and this,
> with its own drivers, works perfectly under Windows7 and OSX ( I tried both
> with 16 and 24 bit from 44.1 to 192Khz).
If you need a custom driver on OSX, this is a sign th
On 03/28/2014 07:33 PM, Julien Benoist wrote:
> I made the following observations:
> - whatever the kernel - with sox/aplay sending raw content to the ALSA
> device - 24/192 content is subject to very high jitter/cracks.
> - interestingly, I've noticed that xbmc (7a6cb7f) plays 24/192 content
> c
Dear Andrea and list,
I had, and still have, the same problem: see the thread "teac UD-H01,
bad 24 bit playback" for a discussion. There were other reports (Teac
DAC, I've read someone can make it work fine via USB 16/2/44100, but NOT
ME...) of similar problems, with the jitter even at 16bit. Thi
On 03/28/2014 10:49 AM, Andrea M wrote:
> I bought an USB DAC from TEAC (device UD-H01 with chip TENOR 8802) and this,
> with its own drivers, works perfectly under Windows7 and OSX ( I tried both
> with 16 and 24 bit from 44.1 to 192Khz).
> On my netbook which has Linux Mint last version and drive
43 matches
Mail list logo
