From: Karl Swisher <k_swisher@frontier.com>
To: ALSA-DEVEL <alsa-devel@alsa-project.org>
Subject: PreSonus Information For Developers
Date: Thu, 07 May 2015 22:09:49 -0400 [thread overview]
Message-ID: <554C1AED.7070503@frontier.com> (raw)
Hello all,
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 06 00 4b 41 65 00 64 00
55 43 00 01 06 00 4b 41 65 00 64 00
55 43 00 01 06 00 4b 41 65 00 64 00
55 43 00 01 06 00 4b 41 65 00 64 00
55 43 00 01 06 00 4b 41 65 00 64 00
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
I'm trying to separate out the bin code from the text.
Does anyone here know if there is value in this information or
anyone that might want it? Have a few functions decoded in the format
above.
Thanks
Karl
next reply other threads:[~2015-05-08 2:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 2:09 Karl Swisher [this message]
2015-05-09 7:02 ` PreSonus Information For Developers Clemens Ladisch
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=554C1AED.7070503@frontier.com \
--to=k_swisher@frontier.com \
--cc=alsa-devel@alsa-project.org \
/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