rodrigo@anorg.net wrote:
hello again,
I'm trying to set up the CUBEmixer now, but there's a problem with the first-order-ambisonics setting. I cannot set the value to 1 (it seems to be the last argument of the "The_MIXER~" abstraction). There is no abstraction with the name "1_ambi_enc~". Is this a problem? I also cannot find the equivalent to the angles.mtx file. There is a compensation.txt file. This is, I think, the equivalent to the calibrate.mtx file in the abcdefg. I' a right?
yes that is correct.
There is an "sr_list.txt" file, but it is empty.
this is a leftover from times where it was unclear how exactly we should do the dynamic bridge between gui and dsp.
One more problem. There are a number of errors in the DSP patch:
error: Bad arguments for message 'plugin~' to object 'objectmaker' plugin~ $0 COMPANDER $1 $2 ... couldn't create error: Bad arguments for message 'plugin~' to object 'objectmaker' plugin~ $0 DISTANCE $1 $2 ... couldn't create (a lot more of this kind) (I have plugin~ installed)
having plugin~ (as in VST) installed is a bad idea; in the CUBEmixer [plugin~] is an abstraction. i think we will have to rename them, in order to avoid this nameclash.
number_of_zeros_in_decoder:: 44 error: aconnect: Connection failed (Invalid argument) (10 aconnect errors like this) tried but couldn't sync A/D/Aleo
Aconnect has something to do with alsa right? Alsa is doing funny things with the hdsp (distorted signals). It works with oss, though. Is alsa necessary (I'm using debian sid)?
aconnect is about alsa-midi sequences support. [aconnect] is used to store and restore the midi-settings. it is not necessary (unless you need it, of course...); it has nothing to do with sound. (as in "~")
alsa-sound is not really necessary for the CUBEmixer either; however you will have to set this in etc/CUBEmixer/ (copy to the template-file to the same-name without the "template"-part and edit to your needs)
About the abcdefg: Of course I would like to use the CUBEmixer, but for the tests I'm doing now, I can stick to the abcdefg. I need to find out what channel gets assigned to what speaker. About the automatic patch generation of the
there is an output module (something like [main_out~]) where the dac~'s live.
abcdefg: I certainly want to edit the patch. Probably I can save the generated patches, kick all the object creators out, and start them without the script, or make my own.
yes of course that is a possibility. (i am always thinking of an application which needs to fullfill the different needs for a lot of people while staying consistant and without having thousands of copies lying around on your harddisk: don't let yourself encumber by my sorrows...:-))
mfg.asdr. IOhannes