WARNING!
With the new Ircam Forum website coming, the user groups will be migrated towards a new platform.
Please plan user groups downtime between Monday, March 25th and Tuesday, March 26th.

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 days, 16 hours ago

MuBu for Max user group.

mubu.usual.onseg

Author 2 Subscribed Users |
Profile photo of EP
EP

mubu.usual.onseg doesn’t seem to draw all markers in imubu properly until you click in graphic display of imubu
see for example helpfile of mubu.usual.onseg
see also attached image

Attachments:
  1. Skärmavbild-2018-04-24-kl.-10.44.22

    Skärmavbild-2018-04-24-kl.-10.44.22.png

April 24, 2018 at 09:50 #26382
Profile photo of ktatar
ktatar

I am having a similar issue with segmentation with pipo. I automatically read a .wav file to a mubu container. Then, using the read output of the mubu object, I initiate a mubu.process for segmentation, which creates markers of segment locations. However, when I automatically initiate mubu.process, the segmentation algorithm does not parse the whole audio, and stops somewhere in the middle, and outputs alldone message. If I initiate the mubu.process segmentation twice, then mubu.process parses the whole file.

I think the issue comes from reading a .wav file. I think mubu.process starts processing before mubu container is done with reading. I found a workaround by initiating the mubu.process twice, but I think there is a bug in the reading process. I attached the max patch.

August 4, 2018 at 03:25 #27380
Profile photo of EP
EP

I don’t know if this applies to your problem, but in my case the problem was entirely related to redrawing of the views in imubu (perhaps you are using imubu elsewhere in your patch for visualization of the mubu buffer).
My solution was to send the message forceredraw on done (or doneall) from mubu.usual.onseg (in your case mubu.process).
However, I noticed that this will not always redraw the all the views (audio, seg, etc.), but only the foremost one. So to make sure that all the views in imubu redraw correctly everytime I read and process an audio file, I send the message foremost 2, forceredraw, foremost 1, forceredraw.
I hope this is of some help.

August 4, 2018 at 10:22 #27383
Profile photo of ktatar
ktatar

Thanks EP for the workaround, I will give it a try. Though, in my case, I am not using any visualization of the buffers, and the patcher doesn’t have any imubu objects.

August 6, 2018 at 12:55 #27397

You must be logged in to reply to this topic.

Log in now