alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: nick83ola <nick83ola@gmail.com>
To: Jens Verwiebe <info@jensverwiebe.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] Line 6 Helix quirks
Date: Sun, 24 Nov 2019 23:07:24 +0000	[thread overview]
Message-ID: <CABPh3UPYhJZu85XMRPfJqs_-yuTpxvfCogiaNTaHnJhTFaUwYQ@mail.gmail.com> (raw)
In-Reply-To: <30bf6f19-e97b-c4fe-e428-7cade1df7751@jensverwiebe.de>

Hi Jens,
in my hx stomp with 2.82 firmware the USB id is the same and I'm not
experiencing any glitch.
Also some people on line6 confirm that the patch is working for hx stomp.
If on helix the situation is different you should submit a patch.

Best Regards
Nicola Lunghi

On Sun, 24 Nov 2019 at 13:41, Jens Verwiebe <info@jensverwiebe.de> wrote:

> Back to the Helix once more .....
>
> I already informed Nicola about latest Line6 firmware 2.8 ff changes.
>
> All Helix devices seem to get a new product id due to the new core changes.
>
> Additionally we have now an endpoint 5 for HID support ( applied dump ).
> Not sure what we can make out of this
>
> cause a lack of investigation time. The audio endpoint descriptors are
> unchanged.
>
>
> The problem with not working implicite feedback stays, so i still use my
> arbitrary 48005 Hz hack.
>
> Without slight pop would ocure in audio, but still with this hack every
> 20 minutes i get a slight distortion which
>
> is no surprise.
>
> Can someone shed light here if an implicite feedback device should show
> the exact momentäry fequency ?
>
> Should i see also the 16.16 feedback format ?
>
> I looked through all code and 'am still stunned where the sync
>
> fails.
>
> Btw: i have also attached ioreg information from macOS if this helps
> someone to dig deeper. I dumped driverless
>
> "usb compliant" mode here with integer outcome for a quick overlook.
>
>
> This so far ... Jens
>
> --
>
> Jens Verwiebe
> Allerskehre 44 - 22309 Hamburg
>
> Tel.: +49 40 68 78 50
> mailto: info@jensverwiebe.de
> web: https://www.jensverwiebe.de
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2019-11-24 23:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGnrtESNwneRXqKOnp-_gfkPDu11g+-M4s5dOs+pOMD30Wp8uw@mail.gmail.com>
2019-10-20 13:50 ` [alsa-devel] Line 6 Helix quirks nick83ola
2019-11-24 13:39   ` Jens Verwiebe
2019-11-24 23:07     ` nick83ola [this message]
2019-11-24 23:13       ` nick83ola
2019-11-24 23:23         ` nick83ola
2019-11-25 18:14           ` Jens Verwiebe
2020-01-23 23:07   ` Carlo Calica
2020-01-25 10:10     ` Takashi Iwai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABPh3UPYhJZu85XMRPfJqs_-yuTpxvfCogiaNTaHnJhTFaUwYQ@mail.gmail.com \
    --to=nick83ola@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=info@jensverwiebe.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).