All of lore.kernel.org
 help / color / mirror / Atom feed
From: "m.eik michalke" <alsa@reaktanz.de>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: alsa-devel@alsa-project.org
Subject: Re: presonus StudioLive 24.4.2
Date: Thu, 18 Jun 2020 23:29:58 +0200	[thread overview]
Message-ID: <2657876.DQpN11Lt7Q@meadow> (raw)
In-Reply-To: <20200618140623.GA314288@workstation>

hi,

Am Donnerstag, 18. Juni 2020, 16:06:23 CEST schrieb Takashi Sakamoto:
> The domain specific language in alsa-lib is not so easy to understand
> and control. The result affects to all of ALSA applications like pulseaudio.
> It's better to use alsa_in/alsa_out for the purpose to avoid unexpected
> influences, IMO...

i'll probably try both, and maybe FFADO as well. my goal is a solution that 
reliably works when we (my band) start recording again.

it's a pity alsa currently can't transparently take care of this. it looks 
like basically everything is in place, but you're left with that IKEA feeling, 
a collection of parts and a construction manual in your hand. when you plug in 
a 24-channel sound card and alsa successfully detects all of them, as a user 
you'd expect the single card that is actually offered by alsa to just provide 
all those channels. that the board internally might use mutliple chips is 
something you shouldn't have to worry about/figure out. i'd argue there's 
exactly one configuration that everyone would expect to get from a board like 
this, and that's all channels in one device. it would do no harm to 
automatically configure it like this by default. should someone actually 
prefer to have split devices for whatever use case, IMHO that should be the 
exception to be configured manually.

> > let me know if you need anything else.
> 
> Hm. If you hear sound with periodical noise, please report it. The
> dice-based device is known as one of the devices to require drivers for
> media clock recovery. In detail, please read the other case[1].

i'll check it out. we have just bought the board second-hand to replace a 
phonic helixboard that broke after ~10 years in our studio. i'm just starting 
to get familiar with it and haven't recorded much more than a proof of basic 
functionality yet.


viele grüße :: m.eik




      reply	other threads:[~2020-06-18 21:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-16  8:11 presonus StudioLive 24.4.2 m.eik michalke
2020-06-16 12:18 ` Takashi Sakamoto
2020-06-17 13:00   ` m.eik michalke
2020-06-17 13:37     ` Takashi Sakamoto
2020-06-17 16:12       ` m.eik michalke
2020-06-17 23:32         ` Takashi Sakamoto
2020-06-18 10:14           ` m.eik michalke
2020-06-18 14:06             ` Takashi Sakamoto
2020-06-18 21:29               ` m.eik michalke [this message]

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=2657876.DQpN11Lt7Q@meadow \
    --to=alsa@reaktanz.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=o-takashi@sakamocchi.jp \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.