The CICM is pleased to share the first release of HoaLibrary for Pure Data.

HoaLibrary is a collection of C++ classes, FAUST functions and objects for Pure Data, Max and VST destined to high order Ambisonics sound reproduction.

HoaLibrary allows musicians and composers to synthesize, transform and render sound fields in a creative and artistic way. This library facilitates the understanding and the appropriation of key concepts of Ambisonics. Thanks to original graphical interfaces a lot of new signal processings are allowed like diffuse sound field synthesis, perspective distortion or spatial filtering.

HoaLibrary is free, open-source and made available by CICM, the centre of research on musical composition and computer science of the Paris 8 University.

Objects:

hoa.decoder~ : An ambisonic decoder (ambisonic, binaural, irregular configurations).
hoa.encoder~ : An ambisonic encoder.
hoa.map~ : An ambisonic sources spatializer.
hoa.delay~ : An ambisonic sound field delay.
hoa.freeverb~ : An implementation of the freeverb algorithm for Ambisonics.
hoa.grain~ : An ambisonic granular synthesizer.
hoa.map : A GUI to spatialize sources on a map.
hoa.meter~ : A circular meter with sound field descriptor.
hoa.optim~ : An ambisonic sound field optimization.
hoa.pi : A good pi number.
hoa.projector~ : A plane wave decomposer.
hoa.recomposer~ : A plane wave recomposer to harmonics domain.
hoa.ringmod~ : An ambisonic sound field ring modulation.
hoa.rotate~ : An ambisonic sound field rotation external.
hoa.scope~ : An ambisonic harmonic scope.
hoa.space : A GUI to design ambisonic space.
hoa.space~ : A plane wave spatial filter.
hoa.wider~ : An ambisonic fractional orders simulator.

Release

Sources

Feedbacks are welcome.
Thanks.

Pierre

Hi Pierre,

Thanks for the reply, I added the issue to Github.

Take care,
Gilberto

Hi Pierre. This is excellent. I have downloaded it for both Max and PD. Thank you!

I am currently working with only 4 speakers in my apartment, 2 in front of me to my right and left and two behind me, right and left.

I am trying to set it up as so as to position the speakers and visualize only four. I can't figure out how to do it from the tutorials. For instance, if I change from 16 to 8 channels it still visualizes 16 channels:

Edit: Here is the setup which I think will work for my my 4 channel speaker array. For the moment I cannot seem to visualise it... other than using the 4x Vu meters:

@Martinukai Thanks !

If you use the order 2, in 2d you should have at least 5 loudspeakers (2*2+1). If you have only 4 loudspeakers, you should use the order 1 or use the decoder in irregular mode instead of regular. In the tutorials, there is a part that explains the relation between the order of decomposition, the number of harmonics and the number of loudspeakers.

If you want to use [hoa.2d.meter~] for 4 loudspeakers, you can right click on the object (in edit mode) and change the number of channels in the properties window (you can also change the angles). You can also use the messages [channels $1( and [angles $1 $2 $3 etc.( You should have a look at the help file of the object.

Thanks for the reply, Pierre. I went back over the tutorial and what you say now makes sense about configuring for 4 channels only. Apolgies. I guess I was pretty tired last night.

The issue I am having with visualizing remains. The "[hoa.2d.meter~]" will not allow me to right click on it when in edit mode. No box appears allowing me to edit it's properties.

Thanks!

It seems that you use extended, can you tell me your OS and the pd version ? I'll try to figure out what happens but I'm not sure to maintain the extended version in the future... Anyway, have you try with the messages like explained in the help file ?

Cheers

@Pierre-Guillot said:

hoa.2d.meter~

Yes, the messages seem to work for the visualizer so that I can now only see four channels. I guess there's no real need to be able to access the properties afterall?

PD version: 0.43.4-extended
Operating System is: OSX El Capitan 10.11.6

Many thanks again, Pierre!

Yes, all attributes of the GUIs are settable with messages. You can send the message [attrprint( to an object to display in the console all the attributes (their names, the messages they are associated to, the types of the arguments and the number of arguments expected).

Thanks once more, Pierre!

is there a version that works on linux 64 i cannot get it to load or build