PortAudio is an open source project powered by Assembla

Assembla offers free public and private SVN/Git repositories and project hosting with bug/issue tracking and collaboration tools.

portaudio

Commit 88

User picture
  • Author: rossbencina
  • 2006-04-07 12:40 (about 8 years ago)

cleaned up bad chars

Files Affected

 
8788
38
For some years PortAudio development proceeded incrementally - bugs were fixed, new implementations were created and a few features were added. Around the time
of the original V18 release in 2001 a big list of requested features existed, and there were many separate implementations of the PortAudio API, some with more
cut-and-paste commonality than code sharing. Due to a combination of forces, most notably the desire to support multiple Host APIs in a single PortAudio build,
it was decided to develop a new unified common infrastructure (support library) with which to implement V19. At that time the feature requests were developed
into a set of <a href="index.html">enhancement proposals</a> which describe the new (Version 2.0) PortAudio API now documented in
V19's <a href="http://www.portaudio.com/docs/v19-doxydocs/portaudio_8h.html">portaudio.h</a>. The proposals have been stable since
2003. The common infrastructure is implemented in the <a href="http://www.portaudio.com/usingcvs.html">v19-devel CVS branch</a>, and the
version 2.0 API is well documented, and available as part of the <a href="http://www.portaudio.com/docs/v19-doxydocs/">doxygen generated
documentation</a>.
38
For some years PortAudio development proceeded incrementally - bugs were fixed, new implementations were created and a few features were added. Around the time
of the original V18 release in 2001 a big list of requested features existed, and there were many separate implementations of the PortAudio API, some with more
cut-and-paste commonality than code sharing. Due to a combination of forces, most notably the desire to support multiple Host APIs in a single PortAudio build,
it was decided to develop a new unified common infrastructure (support library) with which to implement V19. At that time the feature requests were developed
into a set of <a href="index.html">enhancement proposals</a> which describe the new (Version 2.0) PortAudio API now documented in
V19's <a href="http://www.portaudio.com/docs/v19-doxydocs/portaudio_8h.html">portaudio.h</a>. The proposals have been stable since
2003. The common infrastructure is implemented in the <a href="http://www.portaudio.com/usingcvs.html">v19-devel CVS branch</a>, and the
version 2.0 API is well documented, and available as part of the <a href="http://www.portaudio.com/docs/v19-doxydocs/">doxygen generated
documentation</a>.
39
</P>
39
</P>
40
 
40
 
41
<P>Although each proposal is relatively small when taken in isolation, the overall scale of required changes from V18 to V19 is substantial. The new common infrastructure imposes a new interface for implementations. This new interface increases reliability and consistency and reduces development effort, but calls for considerable refactoring (some would say redevelopment) of existing PortAudio implementations relative to the V18 code base. 
41
<P>Although each proposal is relatively small when taken in isolation, the overall scale of required changes from V18 to V19 is substantial. The new
common infrastructure imposes a new interface for implementations. This new interface increases reliability and consistency and reduces development effort, but
calls for considerable refactoring (some would say redevelopment) of existing PortAudio implementations relative to the V18 code base. 
42
</P>
42
</P>
 
 
43
 
43
<P>
44
<P>
44
At the time of writing, a substantial portion of V19 functionality has been implemented for Windows (MME, DirectSound, and ASIO) for Linux (ALSA, OSS, and
JACK), and for Mac OSX Core Audio. Platforms which were well supported with V18 which are not currently supported by V19 are SGI AL and pre-OSX Macintosh (Sound
Manager). The V19 ASIO implementation has not been back-ported to the Macintosh, however it would require little effort to do so if the need arose.
45
At the time of writing, a substantial portion of V19 functionality has been implemented for Windows (MME, DirectSound, and ASIO) for Linux (ALSA, OSS, and
JACK), and for Mac OSX Core Audio. Platforms which were well supported with V18 which are not currently supported by V19 are SGI AL and pre-OSX Macintosh (Sound
Manager). The V19 ASIO implementation has not been back-ported to the Macintosh, however it would require little effort to do so if the need arose.
45
</P>
46
</P>
46
<P>
47
 
 
 
48
<P>
47
The amount of development required to move from V18 release to V19 release has proven to be a significant obstacle to completing the V19 release. In hindsight
it may have been preferable to plan an incremental change schedule for migrating implementations from V18 to the new version 2.0 API. However hindsight is of
little benefit to us now, and we need a plan to finalise the V19 release, the remainder of this document is part of that plan.
49
The amount of development required to move from V18 release to V19 release has proven to be a significant obstacle to completing the V19 release. In hindsight
it may have been preferable to plan an incremental change schedule for migrating implementations from V18 to the new version 2.0 API. However hindsight is of
little benefit to us now, and we need a plan to finalise the V19 release, the remainder of this document is part of that plan.
48
</P>
50
</P>
49

 
 
50
 
51
 
 
 
52
 
51
<H2>Implementation Status</H2>
53
<H2>Implementation Status</H2>
52
 
54
 
53
<P>
55
<P>
...
 
...
 
1085
 
1087
 
1086
 
1088
 
1087
</BODY>
1089
</BODY>
1088
</HTML>K
1090
</HTML>