Changeset 88 for pa_proposals

Show
Ignore:
Timestamp:
04/07/06 00:40:29 (3 years ago)
Author:
rossbencina
Message:

cleaned up bad chars

Files:
1 modified

Legend:

Unmodified
Added
Removed

  • pa_proposals/trunk/status.html

    r87 r88  
    3939</P> 
    4040 
    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>  
     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> 
     43 
    4344<P> 
    4445At 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. 
    4546</P> 
    46  <P> 
     47 
     48<P> 
    4749The 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. 
    4850</P> 
    49   
     51 
    5052 
    5153<H2>Implementation Status</H2> 
    … …  
    10861088 
    10871089</BODY> 
    1088 </HTML>K 
     1090</HTML>