Hello. I suggested quite recently and twice (did my previous mails got lost?) the following system: There would be an opcode/instrument pool which has initiated opcodes/instruments. When an opcode/instrument is needed it is taken from the pool. When an opcode/instrument is not used anymore it is returned to the engine servant who cleans the buffers etc. and returns the opcode/instrument to the pool for reuse. The pool content may change during the composition if we know the upcoming schedule, i.e., no need to compute max number of opcodes of a composition in advance, or such. This should be fast -- at least there would not be any mallocs or buffer cleanings when the opcode or the instrument is really instantiated. Comments? Juhana
- Re: [linux-audio-dev] Real time plug ins Benno Senoner
- [linux-audio-dev] 0.5.6: change in behav... Fernando Pablo Lopez-Lezcano
- Re: [linux-audio-dev] Real time plug ins James McCartney
- Re: [linux-audio-dev] Real time plug ins Paul Barton-Davis
- Re: [linux-audio-dev] Real time plug... James McCartney
- Re: [linux-audio-dev] Real time ... Juhana Sadeharju
- Re: [linux-audio-dev] Real time ... Paul Barton-Davis
- Re: [linux-audio-dev] Real t... James McCartney
- Re: [linux-audio-dev] Real time plug... David Olofson
- Re: [linux-audio-dev] Real time plug ins David Olofson
- Re: [linux-audio-dev] Real time plug... Paul Barton-Davis
- Re: [linux-audio-dev] Real time ... David Olofson
- RE: [linux-audio-dev] Real time plug ins Richard W.E. Furse
- Re: [linux-audio-dev] Real time plug ins James McCartney
- Re: [linux-audio-dev] Real time plug ins James McCartney