Group Admins

  • Profile picture of Norbert Schnell

Group Mods

  • Profile picture of Frederic Bevilacqua
  • Profile picture of schwarz
  • Profile picture of borghesi

MuBu for Max

Public Group active 2 hours, 5 minutes ago

MuBu for Max user group.

imubu: bugs and feature request

Author 3 Subscribed Users |
Profile photo of Alexis Baskind
Alexis Baskind

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.

April 1, 2018 at 10:50 #26101
Profile photo of borghesi
borghesi

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

April 11, 2018 at 09:53 #26258
Profile photo of Alexis Baskind
Alexis Baskind

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

— Pasted Max Patch, click to expand. —
April 11, 2018 at 15:37 #26268
Profile photo of borghesi
borghesi

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

April 12, 2018 at 10:32 #26271
Profile photo of borghesi
borghesi

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

April 12, 2018 at 10:59 #26272
Profile photo of Alexis Baskind
Alexis Baskind

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

April 12, 2018 at 17:51 #26278
Profile photo of schwarz
schwarz

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

April 12, 2018 at 18:05 #26279
Profile photo of borghesi
borghesi

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

April 12, 2018 at 18:29 #26280
Profile photo of Alexis Baskind
Alexis Baskind

Hi Riccardo and Diemo,

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

Best,

Alexis

April 14, 2018 at 08:56 #26288

You must be logged in to reply to this topic.

Log in now