From: Daniel Mack <zonque@gmail.com>
To: Andreas Koch <andreas@akdesigninc.com>
Cc: Jussi Laako <jussi@sonarnerd.net>,
tiwai@suse.de, clemens@ladisch.de, alsa-devel@alsa-project.org,
demian@auraliti.com, ray@auraliti.com
Subject: Re: [PATCH 2/2] alsa-lib: bring pcm.h and pcm.c in sync with the kernel list
Date: Fri, 05 Apr 2013 09:45:09 +0200 [thread overview]
Message-ID: <515E8105.9070607@gmail.com> (raw)
In-Reply-To: <7.0.0.16.2.20130327213632.13b07718@akdesigninc.com>
Hi Andreas,
On 28.03.2013 05:58, Andreas Koch wrote:
>> Am I right to assume that in your case it's the same as for DoP,
>> IOW, oldest in MSB?
>
> Good point - thanks for bringing it up - another can of worms.
> With Windows having a little endian philosophy we started early on
> with the first DSD workstation by putting the oldest sample in the
> LSB position. ASIO came along and adopted the same thing, but then
> extended support for the opposite as well. Rigisystems (offering OEM
> modules for USB audio) came along about a year ago and insisted that
> there is only their way, i.e. putting the oldest bit in the MSB
> position. I tried to explain to them that there are already hundreds
> of products out in the market that do it differently, but that didn't
> matter to them. The result is that now we have implementations with
> both. Up until now that was not a huge issue, because there is no
> generic Windows driver and every hardware manufacturer had to have a
> custom driver.
> Now of course, with your heroic effort in creating a generic driver
> that would help everyone, we have a mess. Some DACs expect little
> endian (mine and others as well) and others (all that are based on
> Rigisystems modules) big endian positions.
>
> Since the time I had the discussions with Rigisystems I didn't have
> any further communication with them. Maybe it is a good idea to touch
> base with them again and find out what the latest is. I will try my
> contact there and let you know.
Did you hear back from them yet? Do you think we should allocate types
for Big Endian DOP formats?
Thanks,
Daniel
next prev parent reply other threads:[~2013-04-05 7:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 23:32 [PATCH 1/2] alsa-lib: pcm.c: fix indentation Daniel Mack
2013-03-27 23:32 ` [PATCH 2/2] alsa-lib: bring pcm.h and pcm.c in sync with the kernel list Daniel Mack
2013-03-27 23:45 ` Jussi Laako
[not found] ` <7.0.0.16.2.20130327213632.13b07718@akdesigninc.com>
2013-03-28 7:36 ` Jussi Laako
2013-03-28 7:49 ` Jussi Laako
2013-03-28 9:54 ` Daniel Mack
2013-03-28 9:52 ` Daniel Mack
2013-04-05 7:45 ` Daniel Mack [this message]
[not found] ` <7.0.0.16.2.20130405092937.144d10d0@akdesigninc.com>
2013-04-05 20:48 ` Jussi Laako
2013-04-05 20:53 ` Jussi Laako
2013-04-06 11:29 ` Daniel Mack
2013-04-06 17:52 ` Jussi Laako
2013-04-06 17:58 ` Daniel Mack
2013-04-06 21:48 ` Jussi Laako
-- strict thread matches above, loose matches on Subject: below --
2013-04-18 8:37 [PATCH 1/2] alsa-lib: pcm.c: fix indentation Daniel Mack
2013-04-18 8:37 ` [PATCH 2/2] alsa-lib: bring pcm.h and pcm.c in sync with the kernel list Daniel Mack
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=515E8105.9070607@gmail.com \
--to=zonque@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=andreas@akdesigninc.com \
--cc=clemens@ladisch.de \
--cc=demian@auraliti.com \
--cc=jussi@sonarnerd.net \
--cc=ray@auraliti.com \
--cc=tiwai@suse.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.