< Back to IRCAM Forum

MUBU.concat on mubu buffer

MuBu
#1

Dear forum,

I have spend some time on MUBU again. Thanks a lot for all the improvements in the help patches. It helps figuring stuff out although I still hope for a good documentation of pipo methods and mubu.process. Not all the stuff in the help patches is self explanatory and this really deserves a more in depth treatment…

Since I am interested in concatenative syntheses with mubu.concat on self recorded audio I tried to combine the mubu.record help patch with the mubu.concat example. That does not really work or maybe I don’t get it to work. mubu.concat~ seems to expect me to refer to a normal buffer~ object and not to the audio track defined as an audio track within (i)mubu. This is really illogical and confusing for me. I got it to work by recording in a normal buffer which I refer to in an imubu to which I added a marker track with addtrack in which I record the markers that I want to set. That is a pity because I cannot make use of the nice features that mubu.record~ has. Is it not possible to add the possibility in mubu.concat~ to refer to the defined audio-track in a mubu or imubu without having to define a MSP buffer? Or can you explain to me how it is done?

The mubu.concat example is extra confusing since it only occurred later to me that the segmentation is just part of the saved patcher and not part of a process done on the loaded audio.

Thanks for listening, Hans.

#2

Sorry guys, I have found that by using the @audio attribute within mubu.concat I can address the audio buffer within a mubu or imubu as you have done in the pipo.onseg example. It would be good to have that in the help-file of mubu.concat…

#3

Is this clear?:

If a buffer~ with the same name as the mubu container exists, use the audio from that. If you want to refer to an audio track in the mubu container, use the @audio track name attribute.
#4

For me now, yes. It would have been more logical for me if the @audio attribute can be there all the time also when you play a MSP buffer. Something like mubu.concat~ 2 concat-help @audio [audio] and when there is no @audio it will automatically refer to the old situation. The @audio [audio] can then be part of the help patches. The [audio] is what you see as imubu tab so it is logical that if that changes because you record a track within mubu with mubu.record you will have to change the name as well.

My confusion is that when I see mubu.concat~ concat-help patch I think that it refers to the imubu and that it automatically refers to the audio within that imubu which it only does when that audio is an external MSP buffer…

Thanks.