Vlad Spears

I've developed a suite of plugins and am testing before release. I'm 

experiencing crashes when choosing AU presets in Live 5.2.1. At 

first I thought it was a problem with my own plugins, but I tested 

another from a third party and a few from Cycling and all exhibit the 

same crash. I've searched the list archives but found nothing on 

this. There are, however, a few similar sounding reports from 

Opening the AU preset browser in Live 5.2.1, then double-clicking 

certain presets in some Pluggos will crash the app. The crash occurs 

with the same preset every time. Sometimes double-clicking on the 

preset will not provoke a crash, but the preset values will not 

load. A second attempt to load the preset will then crash the app.

I've just tested LongStereoDelay and crashed several times in a row 

by choosing the "All .74!" preset. Others which I've crashed 

reliably are Fragulator's "2400 Baud" and Monstercrunch's "a kind of 

These same Cycling Pluggos load and function fine as VSTs in Live 

5.2.1 and as AUs in Digital Performer 4.6. So do my own and the 

I can post the Live crash log from LongStereoDelay's bailout if that 

I've developed a suite of plugins and am testing before release.  I'm  
experiencing crashes when choosing AU presets in Live 5.2.1.  At  
first I thought it was a problem with my own plugins, but I tested  
another from a third party and a few from Cycling and all exhibit the  
same crash.  I've searched the list archives but found nothing on  
this.  There are, however, a few similar sounding reports from  
earlier this year in the Ableton forums.

OS X 10.4.7, PowerBook G4 1.33GHz, 1GB
Ableton Live 5.2.1, Pluggo 3.5.4
Max/MSP 4.5.7 + Jitter 1.5.2

Opening the AU preset browser in Live 5.2.1, then double-clicking  
certain presets in some Pluggos will crash the app.  The crash occurs  
with the same preset every time.  Sometimes double-clicking on the  
preset will not provoke a crash, but the preset values will not  
load.  A second attempt to load the preset will then crash the app.

I've just tested LongStereoDelay and crashed several times in a row  
by choosing the "All .74!" preset.  Others which I've crashed  
reliably are Fragulator's "2400 Baud" and Monstercrunch's "a kind of  
swing."

These same Cycling Pluggos load and function fine as VSTs in Live  
5.2.1 and as AUs in Digital Performer 4.6.  So do my own and the  
other crashing third party Pluggo.

I can post the Live crash log from LongStereoDelay's bailout if that  
will help.

Vlad Spears
A kind of sky we've never seen
http://www.2secondfuse.com

os-x-pluggo-3-5-4-au-live-5-2-1-crash

on my PB Live 5.2.1 crashes too, when loading the "All .74!" preset 

OS X 10.4.7, PowerBook G4 1.67GHz, 2GB RAM

>Opening the AU preset browser in Live 5.2.1, then double-clicking 

certain presets in some Pluggos will crash the app. The crash 

>occurs with the same preset every time. Sometimes double-clicking 

on the preset will not provoke a crash, but the preset values >will 

not load. A second attempt to load the preset will then crash the app.

on my PB Live 5.2.1 crashes too, when loading the "All .74!" preset  
in the pluggo LongStereoDelay.

Setup:
OS X 10.4.7, PowerBook G4 1.67GHz, 2GB RAM
Ableton Live 5.2.1, Pluggo 3.5.4
Max/MSP 4.5.7 + Jitter 1.5.2

 >Opening the AU preset browser in Live 5.2.1, then double-clicking  
certain presets in some Pluggos will crash the app.  The crash  
 >occurs with the same preset every time.  Sometimes double-clicking  
on the preset will not provoke a crash, but the preset values >will  
not load.  A second attempt to load the preset will then crash the app.


Thanks for the confirmation, Reinhold. I was pretty sure it wasn't 

On Aug 16, 2006, at 11:23 PM, halbander wrote:

> on my PB Live 5.2.1 crashes too, when loading the "All .74!" preset 

> OS X 10.4.7, PowerBook G4 1.67GHz, 2GB RAM

> >Opening the AU preset browser in Live 5.2.1, then double-clicking 

> certain presets in some Pluggos will crash the app. The crash 

> >occurs with the same preset every time. Sometimes double-clicking 

> on the preset will not provoke a crash, but the preset values >will 

> not load. A second attempt to load the preset will then crash the 

Thanks for the confirmation, Reinhold.  I was pretty sure it wasn't  
just my machine.

> Hi Vade,
>
> on my PB Live 5.2.1 crashes too, when loading the "All .74!" preset  
> in the pluggo LongStereoDelay.
>
> Setup:
> OS X 10.4.7, PowerBook G4 1.67GHz, 2GB RAM
> Ableton Live 5.2.1, Pluggo 3.5.4
> Max/MSP 4.5.7 + Jitter 1.5.2
>
> regrads
>
> reinhold
>
> >Opening the AU preset browser in Live 5.2.1, then double-clicking  
> certain presets in some Pluggos will crash the app.  The crash  
> >occurs with the same preset every time.  Sometimes double-clicking  
> on the preset will not provoke a crash, but the preset values >will  
> not load.  A second attempt to load the preset will then crash the  
> app.


This bug has been fixed in our upcoming Pluggo 3.6 release.

On Aug 17, 2006, at 1:23 AM, halbander wrote:

This bug has been fixed in our upcoming Pluggo 3.6 release.
    -Tim

Excellent! Thanks Tim (and all the other hard-working elves)!

On Aug 17, 2006, at 9:47 AM, Tim Place wrote:

> This bug has been fixed in our upcoming Pluggo 3.6 release.

> On Aug 17, 2006, at 1:23 AM, halbander wrote:

>> on my PB Live 5.2.1 crashes too, when loading the "All .74!" 

>> OS X 10.4.7, PowerBook G4 1.67GHz, 2GB RAM

>> >Opening the AU preset browser in Live 5.2.1, then double-clicking 

>> certain presets in some Pluggos will crash the app. The crash 

>> >occurs with the same preset every time. Sometimes double- 

>> clicking on the preset will not provoke a crash, but the preset 

>> values >will not load. A second attempt to load the preset will 

Excellent!  Thanks Tim (and all the other hard-working elves)!

> This bug has been fixed in our upcoming Pluggo 3.6 release.
>    -Tim
>
> On Aug 17, 2006, at 1:23 AM, halbander wrote:
>
>> Hi Vade,
>>
>> on my PB Live 5.2.1 crashes too, when loading the "All .74!"  
>> preset in the pluggo LongStereoDelay.
>>
>> Setup:
>> OS X 10.4.7, PowerBook G4 1.67GHz, 2GB RAM
>> Ableton Live 5.2.1, Pluggo 3.5.4
>> Max/MSP 4.5.7 + Jitter 1.5.2
>>
>> regrads
>>
>> reinhold
>>
>> >Opening the AU preset browser in Live 5.2.1, then double-clicking  
>> certain presets in some Pluggos will crash the app.  The crash  
>> >occurs with the same preset every time.  Sometimes double- 
>> clicking on the preset will not provoke a crash, but the preset  
>> values >will not load.  A second attempt to load the preset will  
>> then crash the app.
>


Just a note to say that I am experiencing a similar problem however with all the latest versions of Pluggo(3.6) and Live(6.10) and in both AU and VST (very frustrating!)

The crash seem to happen in particular with instrument plugins and presets that have a lot of predetermined midi / cc controls I think (I could be barking up the wrong tree entirely though...)

Attached is a log of the crash that I get without fail when opening the mod wheel squeegy preset in lo - fi drums....

Ignore my previous message. The problem seems to be related solely to presets in this one particular plugin.

I keep having a crash too, especially if there is a umenu in the patch.

> I keep having a crash too, especially if there is a umenu in the patch.

The vst specs don't allow umenus (they are programmed as a window) you 

Jabbo schrieb:
> I keep having a crash too, especially if there is a umenu in the patch.

The vst specs don't allow umenus (they are programmed as a window) you 
have to replace them with an ubumenu...

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com

On 2 nov. 07, at 09:41, Stefan Tiedje wrote:

>> I keep having a crash too, especially if there is a umenu in the 

> The vst specs don't allow umenus (they are programmed as a window) 

> you have to replace them with an ubumenu...

Stefan, you mean the inverse, right? Ubumenu is unsupported in vst 

because it uses another window. You have to replace them by umenu.

> Jabbo schrieb:
>> I keep having a crash too, especially if there is a umenu in the  
>> patch.
>
> The vst specs don't allow umenus (they are programmed as a window)  
> you have to replace them with an ubumenu...

Stefan, you mean the inverse, right? Ubumenu is unsupported in vst  
because it uses another window. You have to replace them by umenu.

Is it better to have one pluggo sending beat information to the rest of the plugos, or is it better to have a clock for everypatch, i.e.:

shall I use one ddg.beatsync as a master, or shall I put a ddg.beatsync in every instance of the plugin?

I am sorry, but something in the search option of the forum is not working, and via google I don

another question.
Is it better to have one pluggo sending beat information to the rest of the plugos, or is it better to have a clock for everypatch, i.e.:
shall I use one ddg.beatsync as a master, or shall I put a ddg.beatsync in every instance of the plugin?

I am sorry, but something in the search option of the forum is not working, and via google I don


OS X Pluggo 3.5.4 AU + Live 5.2.1 = crash?