bgribble/mfp

Samplerate is not communicated through Python-side app

Closed this issue · 1 comments

The idiom MFPApp().samplerate is used in patches all over the place. Unfortunately it's set to 44100 by default and never updated! This shows up in (for example) the biquad designer demo patch, #191.

The mfp_context object on the C side has the samplerate, so it just needs to get published. I would say mfp_context_init is the proper place for this. I think maybe this was lost in the refactoring that got rid of the multiprocessing-based RPC system.

Commit above is adequate for this. There's still a global samplerate but it gets updated whenever a new context is created. Closing this ticket.