- From: Werther Azevedo <midipixel@yahoo.com>
- Date: Tue, 4 Sep 2012 20:20:06 -0700 (PDT)
- To: Audio Working Group <public-audio@w3.org>
Hi Joe and group.=0A=0ANice to see that the use cases document has evolved.= I can only dream of the day when these use cases are possible to implement= on different =0Abrowsers and devices. =0A=0A=0ABut for now, my feedback go= es to the two use cases in my areas of expertise: games and music making.= =0A=0A2.2 3D game with music and convincing sound effects=0AAlthough there = is a nice description about the ways in which sound effects can =0Abe manip= ulated to match player actions, I miss more detail on the =0Amusical side o= f the soundscape. The only time music is mentioned is on the context of cro= ssfading between different soundscapes. I miss a more specific approach to = how music structure would change in =0Aresponse to interactive events. Musi= cal events (such as tempo, time =0Asignature, note properties and envelopes= , to say the least) could react =0Ato :=0A=0A=0A- Player states, such as: l= ow health, imminent defeat, proximity to a certain goal, etc.=0A=0A- Game/e= nvironmental changes, such as: an ending timer, weather/season variation, m= oving between places and worlds=0A=0AI know that this kind of functionality= is covered in use cases 2.3 and =0A2.5, but I think that it should also be= mentioned in the 3D game use =0Acase. I understand that the use case tries= to cover the common ways in =0Awhich modern games manipulate audio. But I'= m concerned exactly with the =0Away they don't! The game industry lost a gr= eat deal of control over =0Amusic when the technology shifted from MIDI/MOD= (which allowed access to note properties) to PCM/Redbook Audio. The Web Au= dio API is a great chance to make music really interactive once again, in a= n =0Aopen way that's accessible to any developer, regardless of middleware.= That's why I'll always make a case for this aspect to be apparent in a wor= king draft or any official documentation.=0A=0AAnother kind of musical vari= ation not necessarily tied to note data is the multitrack aspect of the sou= ndscape, where layers of sound can be added or removed by dynamic control o= f simultaneously playing channels. This is pretty common in modern games an= d could be easily included in the use case. (ie: "As the soundscape changes= , bringing a more somber, scary atmosphere to the scene. The once full orch= estral underscore is slowly reduced, instrument by instrument, to a lonely = and echoing cello.")=0A=0AIn short, it would be imported if the interactive= musical possibilities were highlighted in the use case as well.=0A=0A=0A2.= 5 Music Creation Environment with Sampled Instruments=0A=0AThis scenario se= ems to describe not only notation software (which I assume =0Awas the inten= tion), but the piano roll functionality I'd expect to be in the DAW use cas= e (2.3). Perhaps they could be merged, or 2.3 could reference =0Athe functi= onality of 2.5? Even though notation software doesn't need =0Aaudio clips a= nd audio processing, the contrary isn't true. I can't =0Aimagine a professi= onal DAW without a capable note editor.=0A=0AAnother suggestion would be to= include the tracker interface in this part of =0Athe description: " includ= ing conventional Western notation, tracker and a piano-roll style display".= Trackers are still widely used and some scholars say they're more efficien= t than piano rolls.=A0=0A=0A----=0A=0A=0AThat's it for now. I know most of = my comments come from a MIDI-centric approach, and the document is titled "= Audio Processing use cases". However, I think the overlap is too big to be = missed, specially in the 2.5 use case.=0A=0ASorry for the long message, and= I hope it helps.=0A=0A=0A=0ABest,=0A=0A=0AWerther Azevedo=0A--------------= ------------------------------------------------- Creative Director > Nano Studio Composer > Escape Into Audio teacher > PUC-RIO @midipixel ________________________________ De: Joseph Berkovitz <joe@noteflight.com> Para: Audio Working Group <public-audio@w3.org> Enviadas: Terça-feira, 4 de Setembro de 2012 12:31 Assunto: Use Cases and Requirements review Dear Working Group Members, Olivier Thereaux and I have recently been engaged in redrafting the Use Cases and Requirements document. The document had its origins in the January 2012 face-to-face meeting. At the time, its chief purpose was to capture and rank a set of rough use cases and feature areas to help guide and compare the candidate specs. At this time, though, it feels to us that the group's work is better served by a different document, one which complements the current specification. Our main goals in reworking the document have been as follows: - Paint a broad picture of the audio-enabled web, illustrating its value through plain-language scenarios readable by a non-technical audience - Frame some of the valuable comments and observations made by WG and list members in terms of user stories - Build a portfolio of scenarios which, taken together, generate a comprehensive set of requirements and goals - Develop these goals with reference to user needs, rather than particular APIs and architectures - Connect requirements to real features in the Web Audio API, where they exist - Highlight gaps in the API where requirements rely on features that are not supported At this time we feel that the document is ready for a broader review and welcome your input. If we are able to process feedback in the next several weeks, we could publish this document as a Working Draft. That seems desirable for keeping the our momentum going. Please find the latest version of the document here: https://dvcs.w3.org/hg/audio/raw-file/tip/reqs/Overview.html As a side note, the set of scenarios is not intended to be universal and all-inclusive. Rather, our goal has been to collect a manageable number of scenarios that overlap to cover as wide an area as possible: many application domains and many API requirements. In so doing, we have often chosen to combine a number of smaller use cases into a single larger one. We also sometimes eliminated use cases that, despite their interest, did not add a novel element to the overall picture. Thanks to everyone whose input has made this document possible. Best regards, ... . . . Joe Joe Berkovitz President Noteflight LLCBoston, Mass. phone: +1 978 314 6271www.noteflight.com ---1278015569-290905910-1346815206=:34919 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable <html><body><div style="color:#000; background-color:#fff; font-family:arial, helvetica, sans-serif;font-size:10pt"><div><span>Hi Joe and group.</span></div><div style="color:rgb(0, 0, 0);font-size:13.3333px;font-family:arial, helvetica, sans-serif;background-color:transparent;font-style:normal;"><br><span></span></div><div style="color:rgb(0, 0, 0);font-size:13.3333px;font-family:arial, helvetica, sans-serif;background-color:transparent;font-style:normal;"><span>Nice to see that the use cases document has evolved. I can only dream of the day when these use cases are possible to implement on different browsers and devices. <br></span></div><div style="color:rgb(0, 0, 0);font-size:13.3333px;font-family:arial, helvetica, sans-serif;background-color:transparent;font-style:normal;"><br><span></span></div><div style="color:rgb(0, 0, 0);font-size:13.3333px;font-family:arial, helvetica, sans-serif;background-color:transparent;font-style:normal;"><span>But for now, my feedback goes to the two use cases in my areas of expertise: games and music making.</span></div><div style="color:rgb(0, 0, 0);font-size:13.3333px;font-family:arial, helvetica, sans-serif;background-color:transparent;font-style:normal;"><span style="font-style:italic;"><br><span></span></span></div><div style="color:rgb(0, 0, 0);font-size:13.3333px;font-family:arial, helvetica, sans-serif;background-color:transparent;font-style:normal;"><span style="font-style:italic;"><span><span style="font-weight:bold;">2.2 3D game with music and convincing sound effects</span></span></span></div><div style="color:rgb(0, 0, 0);font-size:13.3333px;font-family:arial, helvetica, sans-serif;background-color:transparent;font-style:normal;"><span>Although there is a nice description about the ways in which sound effects can be manipulated to match player actions, I miss more detail on the musical side of the <span id="yiv1938282982misspell-0" class="yiv1938282982mark">soundscape</span>. The only time music is mentioned is on the context of <span id="yiv1938282982misspell-1" class="yiv1938282982mark">crossfading</span> between different <span id="yiv1938282982misspell-2" class="yiv1938282982mark">soundscapes</span>. I miss a more specific approach to how music structure would change in response to interactive events. Musical events (such as tempo, time signature, note properties and envelopes, to say the least) could react to :<br></span></div><div style="color:rgb(0, 0, 0);font-size:13.3333px;font-family:arial, helvetica, sans-serif;background-color:transparent;font-style:normal;"><span><br></span></div><div style="color:rgb(0, 0, 0);font-size:13.3333px;font-family:arial, helvetica, sans-serif;background-color:transparent;font-style:normal;"><span>- Player states, such as: low health, imminent defeat, proximity to a certain goal, etc.<br></span></div><div style="color:rgb(0, 0, 0);font-size:13.3333px;font-family:arial, helvetica, sans-serif;background-color:transparent;font-style:normal;"><span>- Game/environmental changes, such as: an ending timer, weather/season variation, moving between places and worlds</span></div><div style="color:rgb(0, 0, 0);font-size:13.3333px;font-family:arial, helvetica, sans-serif;background-color:transparent;font-style:normal;"><br><span></span></div><div style="color:rgb(0, 0, 0);font-size:13.3333px;font-family:arial, helvetica, sans-serif;background-color:transparent;font-style:normal;"><span>I know that this kind of functionality is covered in use cases 2.3 and 2.5, but I think that it should also be mentioned in the 3D game use case. I understand that the use case tries to cover the common ways in which modern games manipulate audio. But I'm concerned exactly with the way they don't! The game industry lost a great deal of control over music when the technology shifted from MIDI/MOD (which allowed <span id="yiv1938282982misspell-3" class="yiv1938282982"><span>access</span></span> to note properties) to <span id="yiv1938282982misspell-3" class="yiv1938282982mark">PCM</span>/<span id="yiv1938282982misspell-4" class="yiv1938282982mark">Redbook</span> Audio. The Web Audio <span id="yiv1938282982misspell-5" class="yiv1938282982mark">API</span> is a great chance to make music really interactive once again, in an open way that's accessible to any developer, regardless of <span id="yiv1938282982misspell-6" class="yiv1938282982mark">middleware</span>. That's why I'll always make a case for this aspect to be apparent in a working draft or any official documentation.</span></div><div style="color:rgb(0, 0, 0);font-size:13.3333px;font-family:arial, helvetica, sans-serif;background-color:transparent;font-style:normal;"><br><span></span></div><div class="yiv1938282982yui_3_2_0_28_13468076431371686" style="color:rgb(0, 0, 0);font-size:13.3333px;font-family:arial, helvetica, sans-serif;background-color:transparent;font-style:normal;"><span>Another kind of musical variation not necessarily tied to note data is the <span id="yiv1938282982misspell-7" class="yiv1938282982mark">multitrack</span> aspect of the <span id="yiv1938282982misspell-8" class="yiv1938282982mark">soundscape</span>, where layers of sound can be added or removed by dynamic control of <span id="yiv1938282982misspell-9" class="yiv1938282982"><span>simultaneously</span></span> playing channels. This is pretty common in modern games and could be easily included in the use case. (<span id="yiv1938282982misspell-9" class="yiv1938282982mark">ie</span>: "As the <span id="yiv1938282982misspell-10" class="yiv1938282982mark">soundscape</span> changes, bringing a more somber, scary atmosphere to the scene. <span style="font-weight:bold;"><span style="font-style:italic;"><span>The once full orchestral underscore is slowly reduced, instrument by instrument, to a lonely and echoing cello.</span></span></span>")</span></div><div class="yiv1938282982yui_3_2_0_28_13468076431371686" style="color:rgb(0, 0, 0);font-size:13.3333px;font-family:arial, helvetica, sans-serif;background-color:transparent; font-style:italic;"><br><span></span></div><div class="yiv1938282982yui_3_2_0_28_13468076431373228" style="color:rgb(0, 0, 0);font-size:13.3333px;font-family:arial, helvetica, sans-serif;background-color:transparent;font-style:italic;"><span><span>In short, it would be imported if the interactive musical <span id="yiv1938282982misspell-9" class="yiv1938282982"><span>possibilities</span></span> were highlighted in the use case as well.</span></span><span><span style="font-weight:bold;"><br></span></span></div><div class="yiv1938282982yui_3_2_0_28_13468076431373228" style="color:rgb(0, 0, 0);font-size:13.3333px;font-family:arial, helvetica, sans-serif;background-color:transparent;font-style:italic;"><span><span style="font-weight:bold;"><br></span></span></div><div style="color:rgb(0, 0, 0);font-size:13.3333px;font-family:arial, helvetica, sans-serif;background-color:transparent;font-style:italic;"><span><span style="font-weight:bold;">2.5 Music Creation Environment with Sampled Instruments</span><br></span></div><div style="color:rgb(0, 0, 0);font-size:13.3333px;font-family:arial, helvetica, sans-serif;background-color:transparent;font-style:normal;">This scenario seems to describe not only notation software (which I assume was the intention), but the piano roll functionality I'd expect to be in the <span id="yiv1938282982misspell-11" class="yiv1938282982mark">DAW</span> use case (2.3). Perhaps they could be merged, or 2.3 could reference the functionality of 2.5? Even though notation software doesn't need audio clips and audio processing, the contrary isn't true. I can't imagine a professional <span id="yiv1938282982misspell-12" class="yiv1938282982mark">DAW</span> without a capable note editor.</div><div style="color:rgb(0, 0, 0);font-size:13.3333px;font-family:arial, helvetica, sans-serif;background-color:transparent;font-style:normal;"><br></div><div class="yiv1938282982yui_3_2_0_28_13468076431371782 yiv1938282982yui_3_2_0_28_13468076431373237" style="color:rgb(0, 0, 0); font-size:13.3333px;font-family:arial, helvetica, sans-serif;background-color:transparent;font-style:normal;">Another suggestion would be to include the tracker interface in this part of the description: " including conventional Western notation, <span style="font-style:italic;"><span style="font-weight:bold;">tracker</span> </span>and a piano-roll style display". Trackers are still widely used and <a rel="nofollow" target="_blank" href="http://revisit.info/files/PhD_Thesis_600dpi.pdf">some scholars say</a> they're more efficient than piano rolls. </div><div class="yiv1938282982yui_3_2_0_28_13468076431371782 yiv1938282982yui_3_2_0_28_13468076431373237" style="color:rgb(0, 0, 0);font-size:13.3333px;font-family:arial, helvetica, sans-serif;background-color:transparent;font-style:italic;"><br></div><div class="yiv1938282982yui_3_2_0_28_13468076431371782 yiv1938282982yui_3_2_0_28_13468076431373237" style="color:rgb(0, 0, 0);font-size:13.3333px;font-family:arial, helvetica, sans-serif;background-color:transparent; font-style:italic;">----<br></div><div><br>That's it for now. I know most of my comments come from a MIDI-centric approach, and the document is titled "<span id="yiv1938282982misspell-13" class="yiv1938282982">Audio Processing</span> use cases". However, I think the overlap is too big to be missed, specially in the 2.5 use case..</div><div><br></div><div style="color:rgb(0, 0, 0);font-size:13.3333px;font-family:arial, helvetica, sans-serif;background-color:transparent;font-style:normal;">Sorry for the long message, and I hope it helps.<br></div><div style="color:rgb(0, 0, 0);font-size:13.3333px;font-family:arial, helvetica, sans-serif;background-color:transparent;font-style:normal;"><br></div><div style="color:rgb(0, 0, 0);font-size:13.3333px;font-family:arial, helvetica, sans-serif;background-color:transparent;font-style:normal;"><br></div><div style="color:rgb(0, 0, 0);font-size:13.3333px;font-family:arial, helvetica, sans-serif;background-color:transparent;font-style:normal;">Best,<br></div><div style="color:rgb(0, 0, 0);font-size:13.3333px;font-family:arial, helvetica, sans-serif;background-color:transparent;font-style:normal;"><br><span></span></div><div>Werther Azevedo<br>---------------------------------------------------------------<br>Creative Director > <span id="yiv1938282982misspell-16" class="yiv1938282982mark">Nano</span> Studio<br>Composer > Escape Into<br>Audio teacher > <span id="yiv1938282982misspell-17" class="yiv1938282982mark">PUC</span>-RIO<br>@midipixel</div><div style="color:rgb(0, 0, 0);font-size:13.3333px;font-family:arial, helvetica, sans-serif;background-color:transparent;font-style:normal;"><br></div><div style="font-family: arial, helvetica, sans-serif; font-size: 10pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div dir="ltr"> <font face="Arial" size="2"> <hr size="1"> <b><span style="font-weight:bold;">De:</span></b> Joseph Berkovitz <joe@noteflight.com><br> <b><span style="font-weight: bold;">Para:</span></b> Audio Working Group <public-audio@w3.org> <br> <b><span style="font-weight: bold;">Enviadas:</span></b> Terça-feira, 4 de Setembro de 2012 12:31<br> <b><span style="font-weight: bold;">Assunto:</span></b> Use Cases and Requirements review<br> </font> </div> <br><div id="yiv853476465"><div><div><div><div>Dear Working Group Members,</div><div><br></div><div>Olivier Thereaux and I have recently been engaged in redrafting the Use Cases and Requirements document.</div><div><br></div><div>The document had its origins in the January 2012 face-to-face meeting. At the time, its chief purpose was to capture and rank a set of rough use cases and feature areas to help guide and compare the candidate specs. At this time, though, it feels to us that the group's work is better served by a different document, one which complements the current specification.</div><div><br></div><div>Our main goals in reworking the document have been as follows:</div><div><br></div><div>- Paint a broad picture of the audio-enabled web, illustrating its value through plain-language scenarios readable by a non-technical audience</div><div>- Frame some of the valuable comments and observations made by WG and list members in terms of user stories</div><div>- Build a portfolio of scenarios which, taken together, generate a comprehensive set of requirements and goals</div><div>- Develop these goals with reference to user needs, rather than particular APIs and architectures</div><div>- Connect requirements to real features in the Web Audio API, where they exist</div><div>- Highlight gaps in the API where requirements rely on features that are not supported</div><div><br></div><div>At this time we feel that the document is ready for a broader review and welcome your input. If we are able to process feedback in the next several weeks, we could publish this document as a Working Draft. That seems desirable for keeping the our momentum going.</div><div><br></div><div>Please find the latest version of the document here:</div><div><br></div><div> <a rel="nofollow" target="_blank" href="https://dvcs.w3.org/hg/audio/raw-file/tip/reqs/Overview.html">https://dvcs.w3.org/hg/audio/raw-file/tip/reqs/Overview.html</a></div></div><br><div><div><div>As a side note, the set of scenarios is not intended to be universal and all-inclusive. Rather, our goal has been to collect a manageable number of scenarios that overlap to cover as wide an area as possible: many application domains and many API requirements. In so doing, we have often chosen to combine a number of smaller use cases into a single larger one. We also sometimes eliminated use cases that, despite their interest, did not add a novel element to the overall picture.</div></div></div><div><div><br></div></div><div><div><div>Thanks to everyone whose input has made this document possible.</div><div><br></div><div>Best regards,</div></div><div><br></div><div><span style="font-size:12px;">... . . . Joe</span></div></div></div><div><span class="yiv853476465Apple-style-span" style="border-collapse:separate;border-spacing:0px;"><span class="yiv853476465Apple-style-span" style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;orphans:2;text-indent:0px;text-transform:none;white-space:normal;widows:2;word-spacing:0px;font-size:medium;"><div style="word-wrap:break-word;"><span class="yiv853476465Apple-style-span" style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;orphans:2;text-indent:0px;text-transform:none;white-space:normal;widows:2;word-spacing:0px;font-size:medium;"><div style="word-wrap:break-word;"><span class="yiv853476465Apple-style-span" style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;orphans:2;text-indent:0px;text-transform:none;white-space:normal;widows:2;word-spacing:0px;font-size:medium;"><div style="word-wrap:break-word;"><span class="yiv853476465Apple-style-span" style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;orphans:2;text-indent:0px;text-transform:none;white-space:normal;widows:2;word-spacing:0px;font-size:medium;"><div style="word-wrap:break-word;"><span class="yiv853476465Apple-style-span" style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;orphans:2;text-indent:0px;text-transform:none;white-space:normal;widows:2;word-spacing:0px;font-size:medium;"><div style="word-wrap:break-word;"><span class="yiv853476465Apple-style-span" style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;orphans:2;text-indent:0px;text-transform:none;white-space:normal;widows:2;word-spacing:0px;font-size:medium;"><div style="word-wrap:break-word;"><span class="yiv853476465Apple-style-span" style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;orphans:2;text-indent:0px;text-transform:none;white-space:normal;widows:2;word-spacing:0px;font-size:medium;"><div style="word-wrap:break-word;"><span class="yiv853476465Apple-style-span" style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;orphans:2;text-indent:0px;text-transform:none;white-space:normal;widows:2;word-spacing:0px;font-size:medium;"><div style="word-wrap:break-word;"><span class="yiv853476465Apple-style-span" style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;orphans:2;text-indent:0px;text-transform:none;white-space:normal;widows:2;word-spacing:0px;font-size:medium;"><div style="word-wrap:break-word;"><span class="yiv853476465Apple-style-span" style="border-collapse:separate;font-family:Helvetica;font-size:medium;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;orphans:2;text-indent:0px;text-transform:none;white-space:normal;widows:2;word-spacing:0px;"><div style="word-wrap:break-word;"><span class="yiv853476465Apple-style-span" style="border-collapse:separate;font-family:Helvetica;font-size:medium;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;orphans:2;text-indent:0px;text-transform:none;white-space:normal;widows:2;word-spacing:0px;"><div style="word-wrap:break-word;"><span class="yiv853476465Apple-style-span" style="border-collapse:separate;font-family:Helvetica;font-size:medium;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;orphans:2;text-indent:0px;text-transform:none;white-space:normal;widows:2;word-spacing:0px;"><div style="word-wrap:break-word;"><span class="yiv853476465Apple-style-span" style="border-collapse:separate;font-family:Helvetica;font-size:14px;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;orphans:2;text-indent:0px;text-transform:none;white-space:normal;widows:2;word-spacing:0px;"><div style="word-wrap:break-word;"><span class="yiv853476465Apple-style-span" style="border-collapse:separate;font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;orphans:2;text-indent:0px;text-transform:none;white-space:normal;widows:2;word-spacing:0px;"><div style="word-wrap:break-word;"><div style="color:rgb(0, 0, 0);font-weight:normal;"><br></div><div><span class="yiv853476465Apple-style-span" style="font-size:medium;"><font class="yiv853476465Apple-style-span" size="3"><span class="yiv853476465Apple-style-span" style="font-size:12px;"><div style="color:rgb(0, 0, 0);font-weight:normal;"><b>Joe Berkovitz</b></div><div style="color:rgb(0, 0, 0);font-weight:normal;">President</div><div style="color:rgb(0, 0, 0);font-weight:normal;"><br></div><div style="color:rgb(0, 0, 0);font-weight:normal;"><b><font class="yiv853476465Apple-style-span" color="#ef6c24">Noteflight LLC</font></b></div></span></font></span></div></div></span></div></span></div></span></div></span></div></span></div></span></div></span></div></span></div></span></div></span></div></span></div></span></div></span></div></span><span class="yiv853476465Apple-style-span" style="font-size:12px;">Boston, Mass.</span><div><span class="yiv853476465Apple-style-span" style="font-size:12px;">phone: +1 978 314 6271</span><span class="yiv853476465Apple-style-span" style="border-collapse:separate;color:rgb(0, 0, 0);font-family:Helvetica;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;orphans:2;text-indent:0px;text-transform:none;white-space:normal;widows:2;word-spacing:0px;font-size:medium;"><div style="word-wrap:break-word;"><span class="yiv853476465Apple-style-span" style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;orphans:2;text-indent:0px;text-transform:none;white-space:normal;widows:2;word-spacing:0px;font-size:medium;"><div style="word-wrap:break-word;"><span class="yiv853476465Apple-style-span" style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;orphans:2;text-indent:0px;text-transform:none;white-space:normal;widows:2;word-spacing:0px;font-size:medium;"><div style="word-wrap:break-word;"><span class="yiv853476465Apple-style-span" style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;orphans:2;text-indent:0px;text-transform:none;white-space:normal;widows:2;word-spacing:0px;font-size:medium;"><div style="word-wrap:break-word;"><span class="yiv853476465Apple-style-span" style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;orphans:2;text-indent:0px;text-transform:none;white-space:normal;widows:2;word-spacing:0px;font-size:medium;"><div style="word-wrap:break-word;"><span class="yiv853476465Apple-style-span" style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;orphans:2;text-indent:0px;text-transform:none;white-space:normal;widows:2;word-spacing:0px;font-size:medium;"><div style="word-wrap:break-word;"><span class="yiv853476465Apple-style-span" style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;orphans:2;text-indent:0px;text-transform:none;white-space:normal;widows:2;word-spacing:0px;font-size:medium;"><div style="word-wrap:break-word;"><span class="yiv853476465Apple-style-span" style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;orphans:2;text-indent:0px;text-transform:none;white-space:normal;widows:2;word-spacing:0px;font-size:medium;"><div style="word-wrap:break-word;"><span class="yiv853476465Apple-style-span" style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;orphans:2;text-indent:0px;text-transform:none;white-space:normal;widows:2;word-spacing:0px;font-size:medium;"><div style="word-wrap:break-word;"><span class="yiv853476465Apple-style-span" style="border-collapse:separate;font-family:Helvetica;font-size:medium;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;orphans:2;text-indent:0px;text-transform:none;white-space:normal;widows:2;word-spacing:0px;"><div style="word-wrap:break-word;"><span class="yiv853476465Apple-style-span" style="border-collapse:separate;font-family:Helvetica;font-size:medium;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;orphans:2;text-indent:0px;text-transform:none;white-space:normal;widows:2;word-spacing:0px;"><div style="word-wrap:break-word;"><span class="yiv853476465Apple-style-span" style="border-collapse:separate;font-family:Helvetica;font-size:medium;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;orphans:2;text-indent:0px;text-transform:none;white-space:normal;widows:2;word-spacing:0px;"><div style="word-wrap:break-word;"><span class="yiv853476465Apple-style-span" style="border-collapse:separate;font-family:Helvetica;font-size:14px;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;orphans:2;text-indent:0px;text-transform:none;white-space:normal;widows:2;word-spacing:0px;"><div style="word-wrap:break-word;"><span class="yiv853476465Apple-style-span" style="border-collapse:separate;font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;orphans:2;text-indent:0px;text-transform:none;white-space:normal;widows:2;word-spacing:0px;"><div style="word-wrap:break-word;"><span class="yiv853476465Apple-style-span" style="font-size:medium;"><font class="yiv853476465Apple-style-span" size="3"><span class="yiv853476465Apple-style-span" style="font-size:12px;"><div style="color:rgb(0, 0, 0);font-weight:normal;"><a rel="nofollow" target="_blank" href="http://www.noteflight.com/">www.noteflight.com</a></div></span></font></span></div></span></div></span></div></span></div></span></div></span></div></span></div></span></div></span></div></span></div></span></div></span></div></span></div></span></div></span></div></span> </div> <br></div></div><br><br> </div> </div> </div></body></html> ---1278015569-290905910-1346815206=:34919--
Received on Wednesday, 5 September 2012 17:20:34 UTC