[PD] pix_delay limits

[enrike]

thanks, I just checked and I am not sure how to understand the results

- pix_delay 3000 happily goes up to 83% RAM and stays there once the 
delay is full
- pix_delay 4000 crashes when the RAM reaches 43%

could it be that pix_delay 4000 requires more RAM than the available BUT 
it only crashes after a while when the system or PD realises that there 
is not enough RAM?


og., 2018.eko uztren 19a 12:16(e)an, Max igorleak idatzi zuen:
> AFAIK it's limited to the amount of RAM you have, so maybe adding RAM 
> might help. Have a look at the memory usage to test this assumption.
> 
> On 19.07.2018 12:10, enrike wrote:
>> hi
>>
>> we are trying to have a few minutes long pix_delay but we are getting 
>> errors. it should be somewhere between 3 and 5 mins.
>>
>> In my linux laptop, a pix_delay with an argument around 4000 crashes 
>> PD after 1 min. But a pix_delay with 3000 as argument works fine.
>>
>> some quick tests
>> - pix_delay 3000. works fine
>> - pix_delay 3500. crashes as the object is created ONLY if the GEM 
>> window is open
>> - pix_delay 4000. crashes around one minute after the object creation
>>
>> any suggestions? I attach the patch I am using for testing but it is 
>> simple and I cannot see anything weird in it.
>>
>> thanks
>>
>> enrike
>>
>> _______________________________________________
>> Pd-list at lists.iem.at mailing list
>> UNSUBSCRIBE and account-management -> 
>> https://lists.puredata.info/listinfo/pd-list
> 
> 
> _______________________________________________
> Pd-list at lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> 
> https://lists.puredata.info/listinfo/pd-list