Changeset 11
- Timestamp:
- 07/30/02 22:03:51 (6 years ago)
- Files:
-
- 1 modified
Legend:
- Unmodified
- Added
- Removed
-
pa_proposals/trunk/004-CallbackVariableFramesPerBuffer.html
r4 r11 18 18 <P><A href="index.html">Enhancement Proposals Index</A>, 19 19 <A href="http://www.portaudio.com/">PortAudio Home Page</A></P> 20 <P>Updated: July 23, 2002 </P> 21 22 <H2><A NAME="AllowCallbackVariableFramesPerBuffer">Allow Callbacks to Accept Variable framesPerBuffer</A></H2> 20 <P>Updated: July 31, 2002 </P> 23 21 24 22 <H4>Status</H4> 25 23 26 24 <P> 27 This proposal sufficiently defined to be implemented. The current v19-devel branch implements passing 0 for the framesPerCallback (framesPerBuffer) parameter to indicate "don't care", however the paFramesPerBufferUnspecified constant has not been defined. We need to decide whether the paFramesPerBufferUnspecified constant will be provided at all, and if provided whether it should retain its name or have different one, such as paVariableFramesPerBuffer. There is still some discussion about whether the Pa_OpenStream() parameter should be called framesPerBuffer, framesPerCallback, granularityFrames, framesPerBlock or something else (see this thread for details: <A HREF="http://techweb.rfa.org/pipermail/portaudio/2002-July/000889.html">http://techweb.rfa.org/pipermail/portaudio/2002-July/000889.html</A> ) The name of this parameter 28 needs to reflect the fact that it is also used as a preferred granularity specifier for blocking read/write streams. 25 This proposal sufficiently defined to be implemented. The current v19-devel branch implements passing 0 for Pa_OpenStream's framesPerBuffer parameter to indicate "don't care", however the paFramesPerBufferUnspecified constant has not been defined. 29 26 </P> 30 27 … … 56 53 57 54 <P> 58 To make the code more obvious, a special constant couldbe defined:<BR>55 To make the code more obvious, a special constant will be defined:<BR> 59 56 </P> 60 57 61 58 <PRE> 62 #define paFramesPerBufferUnspecified (0) <BR>59 #define paFramesPerBufferUnspecified (0) 63 60 </PRE> 64 61 … … 78 75 </P> 79 76 77 <P> 78 The name paVariableFramesPerBuffer was considered as an alternative to 79 paFramesPerBufferUnspecified, however it was deemed to make it unclear whether PortAudio or the client determined the buffer size variation. 80 </P> 81 82 80 83 <H4>Impact Analysis</H4> 81 84
