< Back to IRCAM Forum

Imubu: bugs and feature request

MuBu
#1

Dear all,

1/ I just noticed a small bug with iMubu: at least 2 toggle attributes (“region_visible” and “view_showmean”) have a reverse behavior: clicking on “visible” make the corresponding element disappear and vice versa.

2/ Otherwise I have a feature request: would it be possible to implement a “set” message, allowing changing the internal attributes of iMubu without reflecting it at the output? For instance I’d like to be able to do something like “set region 1000 3000”. Currently it’s impossible, implying having a gate at the output to avoid feedback loops, and hoping that the message which is being sent at the output is not defered and sent after the gate closes.

Best,

Alexis

UPDATE:

1/ with region_visible at least it’s actually a little bit trickier than I thought: if I switch it off and on, as I wrote before, the behavior seems to be reversed. However: if I switch it off once, then quit the inspector, lock the patch and click in iMubu with the “region” tool, the region disappears finally

2/ the trick with the gate at the output of iMubu does not work, since the output seems indeed to be defered

… and another minor thing I noticed: clicking in “region” mode on the iMubu first outputs the message “region 0. 0.”, the proper region bounds are first output when the mouse button is released or when the mouse is dragged.

#2

Hi Alexis,
sorry for the delay!

  1. yes you are right (it will be fixed in the next release —> 1.9.6)
  2. we will add a mute-output attribute to imubu (maybe a global one to mute all outputs and another to mute just output after messages)…
    also in the next release.

Best
Riccardo

#3

Hi Riccardo,

great, thanks!

About the “mute-output” idea: why not, but often (and this is my case) outputs are indeed needed parallel to this “set” feature, for instance if you have two different interfaces to control region starts and ends.

As an example I put a small patch below: the goal is to be able to select the regions either with the mouse on imubu, or with the number boxes. I had to add a delay with a pipe to overcome the defer problem, which works more or less but is not really clean. That’s why I was suggesting to add a “set” message for all possible messages to imubu, like most max GUI objects provide.

Since I am at it: I noticed another small bug: when selecting a region with the mouse in imubu, the object first outputs a “region 0. 0.”.

Best

Alexis

  
----------begin_max5_patcher----------  
2060.3ocyZ01iahCD9yY+UvgtOlFgMPHTo6jteGaqhb.mD2RvHiYeoU28a+7  
K.wN7RHYYaWocyl0C3YlGOy3YF6e9vB2czWvktNe14QmEK94CKVnFRNvh5+e  
g6IzKIYnR0i4lPOcBmycWpowwuvUiyvGHzbGbd5mankWchjmg4pWDTOXAhmb  
jjeXKCmv0L12Odk2RmfMfUQgg9QfkN.OnbHXzJOmuV+l6o47RxOvpYaifrdX  
Rph+zce6SabMdzbzI0i59OLBJyPlnU7FgpYNJX3RgRg3BUvRv7kRQXTbqf4I  
GvyPpJ4ulo4iqbf+8gGjerbdPyRNhwuY7LF1ENitC3L5dgy2GL4u9ammOhEf  
BNSnpBU1A4TiSOS3Gc3GwNBooDuzgbpZWkydBqj6HjuhJdoyWZ.UuUhe9h6R  
wrQRN5bDU5voN6vhmOiiY3T4qzv8LRNNgVkqDgfabg.JgUGeOkUDXs5OqMMd  
L.6f2SHMG+rfGcPzLJJ8DtTp+zrZr7VM1fd.kRp9D.U+AB6WGg8qift5X8H5  
Gh+ZAVyLWWmuNep+tp86wr+yojVwRvNeileH60UHx9aECB.ZLvGd1iyOZLj.  
zOR.mNRrWr3IrREZAJ+vrBKEjBrHhgWun.75VBFnf1jePP.B9XYPb.wEZtC3  
V0benZaA+0AsZdXv3Zt2GKMWrAXgXq62VLfv3vV8Odz.A.P7GK8mKV1yb7tW  
E2XgOvabEeS+Jt+zUbRtxuW9q7q2ELHi5iNf6fCkXtyed61+QqUYbHh40BCi  
64Ch9Ms9OyJt1w+VT70evb7QeWmPzcFsOz+bVlgiukGH3ClpKRITmxmLgulz  
BuyP.v3y0HDGOJN3sYNvASIByp09Z0egTuvOgYkxf4mm5EtnhBigWX7JRL6a  
T0DEsrcHRtdH+1gX3mHMueX6nHl.W3BPohoE8WV2rZKmFZJlkWQThhdPwp2C  
MSXCT1TakHuAcTzfMFIKKVkOjQS9NN0HuXA1H12hjaV.mE4T7dTUFeqU0NvU  
8ReOJAO3K2a8OKbOvHozboPXgyxgaX2iNfPUxwglJi5IxQE87xBqDAlL.QQI  
g7pxcHlbYXm1PA1PTlGuMo12KCumWStfjmeAJxoECSjQNbbj2cGUP7zXyshR  
41pbM0sBOS91RzS1nMGkkU6pZO8ufxImDolwI5k.nWKQbNRnnGKSXzrLK8US  
4odnjJrfSvOSR4GULxzXP73jhFiH21U4TxAbI2dLN5Po8HcbbECUsq1CcKGe  
pHSnE1OfU+WLcGMCpYM9XA25lNqIg9BsOTXsP81Xd5JX6jLa2fZgWvotA1F.  
iFKP+hlf80gLleLhKR6KaPPBbEPREkRTpjdGfUgWCj7GFjf2AHs7WHP8Geps  
tna1XRTFXnrAHalJNAmUioyYI+9CS+HyIgdp.wvVoUcuPltAjwQW2+y6Ctok  
RyGDM7lhilNo.+1OGFLVO2AiLH2zdxKeMRdJ9EiLblETSKK2c7IcP73IiaQC  
iadWE2tKf4bBQxNsNvNgJUSRueDS2+t5EqVC.Ga8Tr2Nmj2lf3iFgjkO4jVy  
tc4HbxxQz6pb3OY4PJwf2U4.LI4v6cEOf2Dd79IGdSVNfCJG0C1TQkqLw5zs  
5hH1h3bFYWEW6ZYVh3Mkrqnxqcnr5TYaKEZrLeOmd7Cmk24ovcQcDnjwZaA3  
5crw6bSp0MuZnx0W6MespW+k4rGFLAyvi001q2AGnHsrVnHbLnHL9MCEF4Ub  
i.f5H8Zl2T5IDIWWamnzxssU16clwxC8SeRgVsDvkgxOfYUYhRxLpStgJphS  
2QqxSsN8M8IEkbjRKEuVAsjvs6rhvbeWoEAuwLL2cHglo6rxiN5SNy7iVvGk  
QNj+DA+bWQJohURYa2KP.5ypi8zjZcM2s.iumExoU+oJE0rpaWEFwpx7nPfp  
zWAwlyoobTkS3lBudw663WKGXcS16DqCGsHiv2doxbtcRlL1dorGK.6GXuIF  
4M7z1.3SESuzBtGvsF1aWB64Lia6jXF5U4gVanFl.be1khHHxH4YxNEZYapQ  
eYuV528QEqY6YCxZXIXUvl09vMmscEdRUEo0c7..a6yxEHb4QjN7fXbNmlW5  
Z5R0n8PuQ6YJUri.QDmgQOvvkkDqVK0fjlvvm.shiv0oHCkfORyRwLqoscmt  
5st6AampAh1Fsmk4KsDll8C9zNq1rUur0IPfgWSmXAZQpEguvRta+Eavwo4n  
QYjd5Ha6z2WPTMTz01BtABVEA88CW2N801gCBn15LHz1Pwpwe0X2SnrJbYO1  
51Kv.Pz5Po95Gu1KZi7aQgv3.vXwY5HG1jmZTCkKQOwrF4.BLQiQBxb1IDwZ  
LyeVT4lvapVz6KvRaf34KiF0M2w1c6FuFFlGEylQOM1fnY7jXlXZ2W531Wj3  
6OiYQFlBU4lANefraS12Xr5dGbS2Xrv1i3q.wDwNEJ1Vci3uHknIk83dJ6DR  
IhqGKex6+BvbenUcFNy.Z4e8KX2uUbToK1MlQCqWVnaM31s.WPjYAtCTbqzp  
wwbiiT8AZ1eTkoy60Sg298yavah2xhFO2migpoGXzym2Fq7tJqVOCrRV+20Y  
k73se6rJXRZUv4lUc+rxexr5spUAalhEY7LvI3DXTvbrPotCeWG9fdyBulhs  
95YgUf3eYHHXyjPPvrwK3ulUKEutdPv3YgWQ2R7h4MX+z1noMBxbuK2zhTNK  
VpdalruNnmDIt3xGIYyEW5nKtvQcurQCeQit7RFI37+9v+iG1EBF  
-----------end_max5_patcher-----------
#4

hi Alexis,
finally, now I remember, setting values by message must not output the message, it is not necessary… only setting region do that, but this is a bug (and will be fixed).
The output is needed only when we change values by gui interaction (drag, click etc.), just to know the right value. Reading the code the output seems not delayed after mouse interaction.
Output Region 0. 0. with mouse down is also a bug and should be fixed.

So to resume:

  • setting region by message will not output message
  • setting region by mouse drag will output a message
  • “Region 0. 0.” output at mouse down will disappear

Hope this will fine for you.
Best
Riccardo

#5

Hi again,
if you want to make a test, you can download a mubu with the region changes from there:
http://echanges.ircam.fr/filez/download.php?ad=9022mXWdwR

tell me what you think about
best
Riccardo

#6

Hi Riccardo,

the changes you mention correspond well to what I was meaning. However you provided a new mubu.mxo object, and those changes concern imubu. While I am at it: why is it that the mubu object does not behave exactly like imubu (same output messages etc…), except that it’s graphically imbedded in the window?

Best

Alexis

#7

Hi Alexis, mubu.mxo contains the code for all core mubu objects, imubu.mxo, etc. are only proxies.

#8

hi,
all the basic mubu objects (mubu, imubu, mubu.track/process/play and record) are embedded in the mubu.mxo,
imubu.mxo is just a placeholder (usefull for open help patch and something more). So replacing mubu.mxo you have also the new version of the other basic objects.

Imubu is an extension of mubu, so imubu can understand all the mubu messages, not true for the inverse (for example the region does not exists in mubu), but mubu can redirect all the gui messages to his inner gui (dbl click to open it)

best
Riccardo

#9

Hi Riccardo and Diemo,

Ok I got it. It seems to work perfectly. Thanks!

Best,

Alexis