[Stk] New release and maintenance

[Gary Scavone]

Hi Robert,

Are you referring to the license or the possibility that some concepts implemented in STK may be covered by patents?  Since the digital waveguide patent has expired, I would guess there are no longer any problems.

Regards,

—gary

> On Aug 5, 2016, at 1:30 PM, Robert Thompson <rdthompson2013 at icloud.com> wrote:
> 
> Hello Gary and Ariel,
> 
> 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). 
> 
> There's an upside and downside for this,
> 
> From https://ccrma.stanford.edu/software/stk/information.html <https://ccrma.stanford.edu/software/stk/information.html> 
> 
> 1. "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)"
> 
> This has always been the primary upside.
> 
> 2. "The only parts of the Synthesis ToolKit that are platform-dependent concern real-time audio and MIDI"
> 
> 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?
> 
> 3. Then there's the "Legal and Ethical Notes"
> 
> 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. 
> 
> Thanks. 
> 
> ~ Robert 
> 
> Sent from my iPhone
> 
> On Aug 5, 2016, at 12:16 PM, Gary Scavone <gary at ccrma.Stanford.EDU <mailto:gary at ccrma.stanford.edu>> wrote:
> 
>> Hi Ariel,
>> 
>> 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.
>> 
>> 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.
>> 
>> 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.
>> 
>> Regards,
>> 
>> —gary
>> 
>>> On Aug 3, 2016, at 8:36 AM, Ariel Elkin <arielelkin at gmail.com <mailto:arielelkin at gmail.com>> wrote:
>>> 
>>> Hi all,
>>> 
>>> Several bug fixes and improvements have been accumulating since v4.5.2, it'd be good to draft a new release. 
>>> 
>>> Also, two pull requests need to be reviewed:
>>> https://github.com/thestk/stk/pulls <https://github.com/thestk/stk/pulls>
>>> 
>>> And issues have also been accumulating:
>>> https://github.com/thestk/stk/issues <https://github.com/thestk/stk/issues>
>>> 
>>> As far as I'm concerned, I can (as always) 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. 
>>> 
>>> So I think it would be good if 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.
>>> 
>>> Ariel
>>> _______________________________________________
>>> Stk mailing list
>>> Stk at ccrma.stanford.edu <mailto:Stk at ccrma.stanford.edu>
>>> https://cm-mail.stanford.edu/mailman/listinfo/stk <https://cm-mail.stanford.edu/mailman/listinfo/stk>
>> 
>> _______________________________________________
>> Stk mailing list
>> Stk at ccrma.stanford.edu <mailto:Stk at ccrma.stanford.edu>
>> https://cm-mail.stanford.edu/mailman/listinfo/stk <https://cm-mail.stanford.edu/mailman/listinfo/stk>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://cm-mail.stanford.edu/pipermail/stk/attachments/20160805/e66a8985/attachment-0001.html>