I am perfectly fine with that because I don't mind updating all my patches
to adapt them to this change. You will, however, find other users who won't
like this because they will need to update their patches, even though it
may be a matter of running a simple shell script.
Best,
--
Ivica Ico Buk
2017-01-29 17:53 GMT-02:00 Ivica Ico Bukvic :
> I also think unthreaded should be default to maintain determinacy in sync
> with Max,
2017-01-30 17:42 GMT-02:00 Roman Haefeli :
> Sounds like Max' [coll] is threaded
yep, it is threaded, so the idea it shouldn't be the default to be in sync
wit
On Mon, 2017-01-30 at 21:10 +0100, IOhannes m zmölnig wrote:
> On 01/30/2017 08:42 PM, Roman Haefeli wrote:
> >
> > On Mon, 2017-01-30 at 15:20 -0200, Alexandre Torres Porres wrote:
> >
> > >
> > > >
> > > > Doing Uzi with 100k generated entries into coll object in Max
> > > > and I
> > > > ge
On 01/30/2017 08:42 PM, Roman Haefeli wrote:
> On Mon, 2017-01-30 at 15:20 -0200, Alexandre Torres Porres wrote:
>
>>> Doing Uzi with 100k generated entries into coll object in Max and I
>>> get guaranteed crashes from these on both 6 and 7.
>>>
>> well, I tested opening a file with 300k entries
On Mon, 2017-01-30 at 15:20 -0200, Alexandre Torres Porres wrote:
> > Doing Uzi with 100k generated entries into coll object in Max and I
> > get guaranteed crashes from these on both 6 and 7.
> >
> well, I tested opening a file with 300k entries in Max 7 and got no
> audio crash/choke... it loa
one of my messages didnt go to the list, it was too big...
let me adaot and resend it
Tests in Max that stand out:
>
> Reading and writing coll files while sound is running does not cause xruns
> in Max, whereas in Pd it can depending on the size of the coll file and CPU
> utilization.
>
yes, I'
