Oh, interesting. Haven't tried myself yet, but good to know that many
patches wouldn't work. I can't get around using [receive~].

Have you seen my last reply (https://lists.puredata.info/pipermail/pd-list/2022-01/130716.html)? It describes how to fix this. (I would not recommend doing this in practice, though.)

---

If more people think that they need to run Pd at a lower scheduler block size, we should think about making it a runtime option. AFAICT, there is no technical reason why it has to be a compile time constant.

Christof


On 1/15/22 2:20 PM, Roman Haefeli wrote:
On Fri, 2022-01-14 at 23:17 +0100, Athos Bacchiocchi wrote:
I was curious so I compiled pd-0.52-1 on linux, with DEFDACBLKSIZE
set to 16.
I set Jack up with buffer size 16, and run pd with jack backend.

Most of the patches in the help browser works, but at least these
objects fail to load:
sigcatch : unexpected vector size
throw~ : vector size mismatch
receive~ : vector size mismatch
sigsend : unexpected vector size
Oh, interesting. Haven't tried myself yet, but good to know that many
patches wouldn't work. I can't get around using [receive~].


In the options for ALSA, the current block size is displayed
correctly as 16 but you cannot select it again once you change it.
That makes sense. The menu dialog code would probably need to be
adapted for that.

Roman

_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list
_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Reply via email to