Within the MMALPortConfig class there are properties to allow a user to override the number of buffers and their size but currently this does not work as expected. I believe this is due to connections being enabled prior to the port being started and this in turn appears to reset any custom value set. For reference, the code at fault is here and here - the connection enabling method should come after the port start.
Hmm on closer inspection this could also be due to not recommitting the buffer num/size changes in the port configuration methods. Will fix both as that seems to follow raspistill/vid behaviour more closely.
Within the
MMALPortConfig
class there are properties to allow a user to override the number of buffers and their size but currently this does not work as expected. I believe this is due to connections being enabled prior to the port being started and this in turn appears to reset any custom value set. For reference, the code at fault is here and here - the connection enabling method should come after the port start.