Bug: pd-external - input message queue is full

[dromer]

Probably need to set bigger default. inQueueKb.

Happened on a basic example patch with both send and print objects.

plugdata: pdext/HeavyContext.cpp:131: virtual bool HeavyContext::sendMessageToReceiver(uint32_t, double, HvMessage*): Assertion `false && "::sendMessageToReceiver - The input message queue is full and cannot accept more messages until they " "have been processed. Try increasing the inQueueKb size in the new_with_options() constructor."' failed.
Aborted

[unclewayback]

Hello, came here to report same thing with my own test example in plugdata. When moving a slider that sends a ctl message into the patch I get a crash with the "que is full" message in my terminal. I suppose for now I will throttle the ctl message update speed on the way in. What is the current default?

[dromer]

Default what? Control messages update at the beginning of every audio cycle.

[unclewayback]

The default as it stands, that you are thinking of making bigger? inQueuekb?

So there is only a certain amount of RAM alloted to control messages or something?

But yes: I was wondering what sort of speed to throttle messages at - how many message per block does the current default permit, do you think?

Anyway I'm not having crashes since only sending updates from the slider once a delay of 50ms has passed.

[dromer]

It is calculated here: https://github.com/Wasted-Audio/hvcc/blob/develop/hvcc/compiler.py#L183-L187

[unclewayback]

Thanks! I'm not at the level of really being able to understand that unfortunately. I read it as 10kb, but then a maximum queue length of 2 (so for instance, one note + velocity pack per block?). At any rate I am mostly hoping to use Heavy for signal rate stuff (got one of the new Bela's on the way!) so I'll probably get by via trial and error until I find time to learn to write externals.