< Back to IRCAM Forum

Pipo.psy crash

MuBu
#1

Hello all,

Macbook Pro, OS 10.6.8

Max 6.0.7

MuBu 1.6.4

I’m getting a crash every time I try to start DSP with pipo~ and pipo.psy, like so:


  
----------begin_max5_patcher----------
  
328.3ocsRsrSCCCD7ryWgkOGpbRgVAmfuCDB4j3ztUI1FamRJUse6Du4Ao7P
  
b.wEaO6Nd1IS7wHBKS2JcL5czGoDxwHBAKEJPFvDVsnMuR3PZLk7Uc1NVbeK
  
ur0ikEE4mGKpa7URu+fQ1KLyAaThJV7zI5SCTgB71cJdU530MBe9VPs4YqL2
  
2qvsIK3wzjzqCaKWGVS4K3SxTpUdknFmG6AKDFVeGUSMn5bCZ9jYzcvaH8jz
  
N0l31acjbZn3onnvR7eKbLfQelZbGn22srnyQkV4Kza3CXQKhS4b9Olggzqr
  
RK7gCea.l76A3pUXzMr8emfKmkf3fXUf5yu1PyFpeYr5zM17wu8gmGzOragz
  
4AkvCZ0LNIWvYKTTHw1i1q.bhrJIFY7uXNgwrWZcCRhFo6u6NsM.WEiPP0CQ
  
EYV4dXj+5nfZmhdGMXnxcB
  
-----------end_max5_patcher-----------

Crash log attached.

One thing I noticed - possibly related - is that setting either of psy.minfreq or psy.maxfreq sets both attributes to the same value (indeed the [pipo~ psy] defaults to both minfreq and maxfreq at 2000 according to the pop-up menu on the inlet). I can’t imagine that helps :slight_smile:

Cheers,

Owen

 

 

 

 

 

 

 

 

 

#2

Hi Owen,

Yes, I can reproduce this behavior.

We just have fundamentally changed the way that attributes of PiPo modules are handled for the next version (that also allows for giving instance names to PiPo modules).

Fortunately, the issue with attributes vanished … and unfortunately the crash remained.

Thank you very much for reporting this. It will be fixed for the next version.

Best

Norbert