>>> Can you convince me to use the ACN scheme?
>
> it is very well documented on michael chapman's site.
does the channel order have support elsewhere?
Etienne
> http://ambisonics.ch/standards/channels/
>
> very big plus :)
>
>
> --
> Jörn Nettingsmeier
> Lortzingstr. 11, 45128 Essen, Tel. +49 1
>> I think the most confusing thing is for the channel names to have an
>> implied order. FuMa implies the order of the alphabet, but this order
>> is wrong. And ANC implies its numerical order. It would be strange to
>> have ACN channel 3 in position 2.
>
> It is confusing if the implied order is
On 11/26/2010 12:59 AM, f...@kokkinizita.net wrote:
>> Can you convince me to use the ACN scheme?
it is very well documented on michael chapman's site.
http://ambisonics.ch/standards/channels/
very big plus :)
--
Jörn Nettingsmeier
Lortzingstr. 11, 45128 Essen, Tel. +49 177 7937487
Meister f
On Fri, Nov 26, 2010 at 11:39:01AM +1100, e deleflie wrote:
> > OTOH, the main consideration for choosing ACN was that these things
> > will in most cases be handled by tools and code rather than by humans.
>
> I have found that the *most* error prone step is hooking up the Jack
> channels from m
> and list the required 'g' values for the signal sets you support.
that's what I've done, but I havn't made a distinction between peri and hori
> OTOH, the main consideration for choosing ACN was that these things
> will in most cases be handled by tools and code rather than by humans.
I have f
On Fri, Nov 26, 2010 at 09:23:06AM +1100, e deleflie wrote:
> > You can include an extra gain factor to ensure all signals remain
> > in the +/- 1 range, but that would depend on the order (it would
> > be the inverse of the highest Zmm conversion factor).
>
> yes, that's what I'm after ... I thi
>> > Hmmm. The column heading says 'conversion to B-format/FMH',
>> > and the values are prefixed by an 'x'. This suggests that
>> > to get FMH you have to multiply the N3D component by the
>> > value listed.
>>
>> thanks for picking that up... I think it is more likely, in the
>> future, that B-fo
On Thu, Nov 25, 2010 at 12:03:55PM +1100, e deleflie wrote:
> > Hmmm. The column heading says 'conversion to B-format/FMH',
> > and the values are prefixed by an 'x'. This suggests that
> > to get FMH you have to multiply the N3D component by the
> > value listed.
>
> thanks for picking that up..
> Hmmm. The column heading says 'conversion to B-format/FMH',
> and the values are prefixed by an 'x'. This suggests that
> to get FMH you have to multiply the N3D component by the
> value listed.
thanks for picking that up... I think it is more likely, in the
future, that B-format will be convert
