<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Hello Gary and Ariel,</div><div><br></div><div>My interest in STK and any audio code is for a commercial embedded IoT product for my use case (hearing impairment, chronic tinnitus therapy/meditation, health etc). </div><div><br></div><div>There's an upside and downside for this,</div><div><br></div><div>From <a href="https://ccrma.stanford.edu/software/stk/information.html">https://ccrma.stanford.edu/software/stk/information.html</a> </div><div><br></div><div>1. "<span style="background-color: rgba(255, 255, 255, 0);">The Synthesis ToolKit is extremely portable (it's mostly platform-independent C and C++ code), and it's completely user-extensible (all source included, no unusual libraries, and no hidden drivers)"</span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">This has always been the primary upside.</span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">2. "The only parts of the Synthesis ToolKit that are platform-dependent concern real-time audio and MIDI"</span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div>It sounds like this comes from the NextStep (NS...) origin and I'm assuming it's independent from the Mach OS kernel, or is this macOS/X or iOS?</div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">3. Then there's the "</span><span style="font-weight: bold; background-color: rgba(255, 255, 255, 0);">Legal and Ethical Notes</span>"</div><div><br></div><div>I can't write potential backers who have interest in health solutions, including my particular situation (hearing impairment, user customizable enhancement) unless I can clarify this language to them in much briefer terms. </div><div><br></div><div>Thanks. </div><div><br></div><div>~ Robert </div><div><br><div>Sent from my iPhone</div></div><div><br>On Aug 5, 2016, at 12:16 PM, Gary Scavone <<a href="mailto:gary@ccrma.stanford.edu">gary@ccrma.Stanford.EDU</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=utf-8">Hi Ariel,<div class=""><br class=""></div><div class="">Thanks for the offer to help. The current release is only about 6 months old, which is fairly “new” from my perspective. And unless I’m missing something, there has only been one merged pull request since then. The two pending pull requests have been replied to but I didn’t get subsequent feedback from the contributors. My feeling is that #58 is not a bug but rather based on the contributor using the class in an incorrect way.</div><div class=""><br class=""></div><div class="">There are several “issues", but I don’t know when I would be able to address them. In general, if someone wants something fixed, they should fix it themselves and then submit a pull request.</div><div class=""><br class=""></div><div class="">There have been a number of updates to the RtMidi and RtAudio classes, but again, I’m not sure they are significant enough to substantiate a new release.</div><div class=""><br class=""></div><div class="">Regards,</div><div class=""><br class=""></div><div class="">—gary</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Aug 3, 2016, at 8:36 AM, Ariel Elkin <<a href="mailto:arielelkin@gmail.com" class="">arielelkin@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><font size="3" class="">Hi all,</font><div class=""><font size="3" class=""><br class=""></font></div><div class=""><font size="3" class="">Several bug fixes and improvements have been accumulating since v4.5.2, it'd be good to draft a new release. </font></div><div class=""><font size="3" class=""><br class=""></font></div><div class=""><font size="3" class="">Also, two pull requests need to be reviewed:</font></div><div class=""><font size="3" class=""><a href="https://github.com/thestk/stk/pulls" class="">https://github.com/thestk/stk/pulls</a><br class=""></font></div><div class=""><font size="3" class=""><br class=""></font></div><div class=""><font size="3" class="">And i</font><span style="font-size: inherit;" class="">ssues have also been accumulating:</span></div><div class=""><span style="font-size: inherit;" class=""><a href="https://github.com/thestk/stk/issues" class="">https://github.com/thestk/stk/issues</a></span></div><div class=""><span style="font-size: inherit;" class=""><br class=""></span></div><div class=""><span style="font-size: inherit;" class="">As far as I'm concerned, I can </span><span style="font-size: inherit;" class="">(as always) </span><span style="font-size: inherit;" class="">provide all the support needed for iOS, but I don't have (at this stage) the required background knowledge for maintaining an STK project on OS X, nor a Linux or Windows machine for development. </span><span style="font-size: inherit;" class=""><br class=""></span></div><div class=""><span style="font-size: inherit;" class=""><br class="">So I think it would be good if </span><span style="font-size: inherit;" class="">we clarify who is responsible for dealing with new issues, pull requests, and overall maintenance. This would make maintenance and development more efficient in the long term.</span></div><div class=""><span style="font-size: inherit;" class=""><br class=""></span></div><div class=""><span style="font-size: inherit;" class="">Ariel</span></div></div>
_______________________________________________<br class="">Stk mailing list<br class=""><a href="mailto:Stk@ccrma.stanford.edu" class="">Stk@ccrma.stanford.edu</a><br class=""><a href="https://cm-mail.stanford.edu/mailman/listinfo/stk">https://cm-mail.stanford.edu/mailman/listinfo/stk</a><br class=""></div></blockquote></div><br class=""></div></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Stk mailing list</span><br><span><a href="mailto:Stk@ccrma.stanford.edu">Stk@ccrma.stanford.edu</a></span><br><span><a href="https://cm-mail.stanford.edu/mailman/listinfo/stk">https://cm-mail.stanford.edu/mailman/listinfo/stk</a></span><br></div></blockquote></body></html>