public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Karl Swisher <k_swisher@frontier.com>,
	ALSA-DEVEL <alsa-devel@alsa-project.org>
Subject: Re: PreSonus Information For Developers
Date: Sat, 09 May 2015 09:02:03 +0200	[thread overview]
Message-ID: <554DB0EB.9090502@ladisch.de> (raw)
In-Reply-To: <554C1AED.7070503@frontier.com>

Karl Swisher wrote:
> I have what might be useful information to some developers but I do
> not sure who or how to contact the right people.  I recently purchased
> a PreSonus StudioLive AI 32.4.2 mixer.  Have it half way working under
> Linux.  This mixer has a network connection in addition to the
> firewire interface.  I've installed their software under VirtualBox
> and ran tcpflow capturing packet content between the computer and the
> mixer.  I have started creating text files of the packets of which
> below is an example of their software performing functions like the
> mixer booting, backing up, restore, and selecting the digital output
> channels 33 through 48.
>
> 55 43 00 01 06 00 4b 41 65 00 64 00
> 55 43 00 01 1d 00 46 52 65 00 64 00 01 00
> Listpresets/scene 00 00
>
> 55 43 00 01 1b 00 46 52 65 00 64 00 01 00
> Listpresets/channel 00 00
>
> 55 43 00 01 19 00 46 52 65 00 64 00 01 00
> Listpresets/geq 00 00
>
> 55 43 00 01 19 00 46 52 65 00 64 00 01 00
> Listpresets/reverb 00 00
>
> Does anyone here know if there is value in this information or anyone
> that might want it?

This information might be useful for somebody who wants to write a mixer
for this device.

Please add this to a page on the FFADO wiki: http://subversion.ffado.org/


Regards,
Clemens

      reply	other threads:[~2015-05-09  7:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08  2:09 PreSonus Information For Developers Karl Swisher
2015-05-09  7:02 ` Clemens Ladisch [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=554DB0EB.9090502@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=k_swisher@frontier.com \
    /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