Displaying 14 results from an estimated 14 matches for "050985c2".
2008 Feb 13
2
OggPCM: support for little-endianness only?
...ULD respectively for IETF and W3C stuff.
Then why not make the common endianness MUST and the rest of it SHOULD?
That was my sentiment, after all...
--
Sampo Syreeni, aka decoy - mailto:decoy@iki.fi, tel:+358-50-5756111
student/math+cs/helsinki university, http://www.iki.fi/~decoy/front
openpgp: 050985C2/025E D175 ABE5 027C 9494 EEB0 E090 8BA9 0509 85C2
2008 Feb 13
3
OggPCM: support for little-endianness only?
...to be passed within a single architecture, allowing both formats
> is always worse.
...some people *are* able to guarantee that. Why hinder them?
--
Sampo Syreeni, aka decoy - mailto:decoy@iki.fi, tel:+358-50-5756111
student/math+cs/helsinki university, http://www.iki.fi/~decoy/front
openpgp: 050985C2/025E D175 ABE5 027C 9494 EEB0 E090 8BA9 0509 85C2
2007 Dec 30
6
OggPCM: support for little-endianness only?
List,
A recent discussion over on XiphWiki is trying to decide if OggPCM
should support only little-endianness or the usual combo of big and
little.
It started with the following statement by an user (Qqq):
"Portable players are usually ARM, which is usually little-endian. The
Macintosh is now little-endian. Obviously the PC is little-endian.
Clearly there is a winner. It's long past
2007 Oct 19
0
OggPCM family
...it the last time around and
nobody objected, and 4) cover as many of the special cases, nits,
canonicalization issues, and so on, as I can think of.
--
Sampo Syreeni, aka decoy - mailto:decoy@iki.fi, tel:+358-50-5756111
student/math+cs/helsinki university, http://www.iki.fi/~decoy/front
openpgp: 050985C2/025E D175 ABE5 027C 9494 EEB0 E090 8BA9 0509 85C2
2008 Jan 02
1
OggPCM: support for little-endianness only?
...ts exactly.
On a related note, comments on the reworked channel mapping headers
would be appreciated. I think they're finally in workable shape.
--
Sampo Syreeni, aka decoy - mailto:decoy@iki.fi, tel:+358-50-5756111
student/math+cs/helsinki university, http://www.iki.fi/~decoy/front
openpgp: 050985C2/025E D175 ABE5 027C 9494 EEB0 E090 8BA9 0509 85C2
2008 Feb 13
2
OggPCM: support for little-endianness only?
Ian Malone wrote:
> This is all well and good but OggPCM is in an Ogg transport
> stream, so that needs to be unpacked anyway.
Fair enough. Since the ogg pages (which I beleive are 4k) need
to be unpacked anyway, there is little harm in having to
(possibly) do endswapping as well.
Erik
--
-----------------------------------------------------------------
Erik de Castro Lopo
2005 Nov 19
0
OggPCM2: channel map
...el formats.
>
> I think a default mapping would be needed just to help for the
> conversion header.
I'm not sure I understand this part.
--
Sampo Syreeni, aka decoy - mailto:decoy@iki.fi, tel:+358-50-5756111
student/math+cs/helsinki university, http://www.iki.fi/~decoy/front
openpgp: 050985C2/025E D175 ABE5 027C 9494 EEB0 E090 8BA9 0509 85C2
2007 Oct 19
2
OggPCM family
Hi,
The Xiph Wiki contains the four pages:
OggPCM
OggPCM Draft1 (with Talk page)
OggPCM Draft2
OggPCM Draft3
Can I suggest that this be reduced to just one
(or maybe two) pages. I suggest this because
somebody has started making changes to
OggPCM Draft2. My guess is that this is not
desirable.
Regards,
Martin
--
Martin J Leese
E-mail: martin.leese@stanfordalumni.org
Web:
2007 Oct 02
0
finalizing oggpcm channel maps
...ment, dig up a representative
list of channel types for the enumerations, put in some context about
the different choices we've made, and so on.
--
Sampo Syreeni, aka decoy - mailto:decoy@iki.fi, tel:+358-50-5756111
student/math+cs/helsinki university, http://www.iki.fi/~decoy/front
openpgp: 050985C2/025E D175 ABE5 027C 9494 EEB0 E090 8BA9 0509 85C2
2005 Nov 17
0
OggPCM2: channel map
...I'm not quite sure what the overall
spatial distribution of the surround field is supposed to be. Hopefully
I can find something concrete on it.
--
Sampo Syreeni, aka decoy - mailto:decoy@iki.fi, tel:+358-50-5756111
student/math+cs/helsinki university, http://www.iki.fi/~decoy/front
openpgp: 050985C2/025E D175 ABE5 027C 9494 EEB0 E090 8BA9 0509 85C2
2005 Nov 15
0
OggPCM2 : chunked vs interleaved data
...ce implementation background.
I joined the list after OggPCM was mentioned on sursound, so it's also
safe to assume I'm an ambisonic bigot.)
--
Sampo Syreeni, aka decoy - mailto:decoy@iki.fi, tel:+358-50-5756111
student/math+cs/helsinki university, http://www.iki.fi/~decoy/front
openpgp: 050985C2/025E D175 ABE5 027C 9494 EEB0 E090 8BA9 0509 85C2
2005 Nov 18
2
OggPCM2: channel map
> I that this is handled pretty nicely by the "simple map" that Sampo
> suggested. This is basically the same thing as the "channel map"
> described on the wiki, but with the (physical,logical) channel pair
> swapped. So, using the syntax from the wiki:
> channel_type = OGG_CHANNEL_MAP_STEREO
> channel_map [OGG_CHANNEL_FRONT_LEFT] = 1
> channel_map
2005 Nov 17
2
OggPCM2 : chunked vs interleaved data
Sampo Syreeni wrote:
> Secondly, I'd like to see the channel map fleshed out in more detail.
Sampo,
I did flesh out the wiki a **little** more. Is the intent clearer now?
> (Beware of the pet peeve...)
What is that pet peeve?
> IMO the mapping should cover at least the
> channel assignments possible in WAVE files, the most common Ambisonic
> ones, and perhaps some added
2005 Nov 15
7
OggPCM2 : chunked vs interleaved data
I made a few updates to OggPCM2 http://wiki.xiph.org/index.php/OggPCM2
reflecting the latest discussions. Could everyone have a look at it and
see if they agree. Otherwise, what do you feel should be changed? Anyone
wants to speak in support of chunked PCM?
For all those that are just tired of this mess like me, please express
yourself in the new spec I created: OggPCM3