From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: "m.eik michalke" <alsa@reaktanz.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: presonus StudioLive 24.4.2
Date: Wed, 17 Jun 2020 22:37:04 +0900 [thread overview]
Message-ID: <20200617133704.GB274842@workstation> (raw)
In-Reply-To: <5770610.t4SrzthkjT@yrla>
Hi,
Thanks for the information.
On Wed, Jun 17, 2020 at 03:00:49PM +0200, m.eik michalke wrote:
> > > in case that as of now the studiolive isn't officially supported or the
> > > above behavior is due to the fact that so far only the 16.4.2 is known to
> > > the module, i'm willing to help as far as i can ;) i hope that already
> > > seeing 16 channels is a good point to start and that it's not too hard to
> > > make the remaining 8 show up as well...
> >
> > Would you get output from '/proc/asound/pcm'?
>
> $ cat /proc/asound/pcm
> [...]
> 04-00: DICE : StudioLive : playback 1 : capture 1
> 04-01: DICE : StudioLive : playback 1 : capture 1
>
>
> all looks to me like you were right. IIUC the board provides a total of 32
> output channels and 26 for input. does this mean the device is already fully
> recognized and functional? can alsa be configured to provide all channels as
> one "sound card" so they become available in, say, ardour?
ALSA dice driver is functional expectedly in the case, with the inconvenience
that you noted... The driver adds two pair of PCM playback/capture device so
that each of them handles corresponding single isochronous packet streaming.
I suggest users to use 'alsa_in' and 'alsa_out' in jackd
session. Two pairs of PCM device (hw:x,0 and hw:x,1) need to be handled
for all of PCM channels. I'm sorry but at present total channels are not
available via one pair of PCM device.
Well, this is a request from me. In IEEE 1394 bus, each device has
'configuration ROM' which the other device can read. Linux FireWire
subsystem read it for device detection. I gather the ROM image[1] for
better detection and would I request you to send the ROM image to me
by following below instruction?
After detected, FireWire character device corresponding to your device
is added to Linux system. Typically it's '/dev/fw1'. At the same time,
the ROM image is served via node on sysfs. In the case of '/dev/fw1',
it's '/sys/bus/firewire/devices/fw1/config_rom'. I'd like you to
redirect its content to file and send it to me (or send pull request
by github service).
[1] https://github.com/takaswie/am-config-roms/
Thanks
Takashi Sakamoto
next prev parent reply other threads:[~2020-06-17 13:38 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 [this message]
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
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=20200617133704.GB274842@workstation \
--to=o-takashi@sakamocchi.jp \
--cc=alsa-devel@alsa-project.org \
--cc=alsa@reaktanz.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 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.