Speaker positions file syntax
3 views
Skip to first unread message
Richard Lee
Apr 26, 2009, 2:13:32 AM4/26/09
to Ambisonics
Some of you will know I've been off-line due to computer problems.
But how did default decodes get into our spec? IMHO, this is completely
unnecessary. "Default decodes" belong in a decoder library like AmbiDecLib.
But if we are looking for Speaker Position File Syntax, I think Fons' format is
as good as any and VERY human friendly.
I'm not sure what you mean by an OSC syntax. Have you any links to an
explanation?
> I know that some of you will gag at this suggestion, but I happen to like
comma separated values (CSV) files for stuff like this.
GAg, gag , ggaaaag ! ... :<O
e deleflie
Apr 25, 2009, 10:02:45 PM4/25/09
to ambis...@googlegroups.com
Hi Richard,
> But how did default decodes get into our spec?
The original spec was just for file formats.
We then compromised that in a big way by attempting to remove any use
of metadata such that the spec would also make sense in software
environments. I believe we have succeeded in doing this.
I've then extended that further/ambitiously to try and make "Universal
Ambisonic" a general 'round trip' standard that eases all aspects of
ambisonic creation/production/delivery.
One of the measuring bars (sitting in the back of my head) is: could
Sony show up and say "we are going to implement ambisonics in our
software/hardware ... where is all the information we need". Universal
Ambisonic is all the information they need.
You'll notice other restrictions aimed at removing decisions. The
software developer does not have to wonder what order he is going to
implement up to. It is defined, he MUST implement 4th order periphony
and 5th order horizontal.
'round trip' I guess the key aspect here.
Etienne
> But how did default decodes get into our spec?
We then compromised that in a big way by attempting to remove any use
of metadata such that the spec would also make sense in software
environments. I believe we have succeeded in doing this.
I've then extended that further/ambitiously to try and make "Universal
Ambisonic" a general 'round trip' standard that eases all aspects of
ambisonic creation/production/delivery.
One of the measuring bars (sitting in the back of my head) is: could
Sony show up and say "we are going to implement ambisonics in our
software/hardware ... where is all the information we need". Universal
Ambisonic is all the information they need.
You'll notice other restrictions aimed at removing decisions. The
software developer does not have to wonder what order he is going to
implement up to. It is defined, he MUST implement 4th order periphony
and 5th order horizontal.
'round trip' I guess the key aspect here.
Etienne
e deleflie
Apr 26, 2009, 1:37:29 AM4/26/09
to ambis...@googlegroups.com
> But if we are looking for Speaker Position File Syntax, I think Fons' format is
> as good as any and VERY human friendly.
>
> I'm not sure what you mean by an OSC syntax. Have you any links to an
> explanation?
> as good as any and VERY human friendly.
>
> I'm not sure what you mean by an OSC syntax. Have you any links to an
> explanation?
OSC is Open Sound Control ....kind of like MIDI but much more powerful/flexible.
its modern and open-source.
http://opensoundcontrol.org/introduction-osc
Etienne
Reply all
Reply to author
Forward
0 new messages