Re: Some questions for Csound users and developers about the future of the Csound Windows installer
| Date | 2017-06-13 22:02 | ||
| From | Andrea Strappa | ||
| Subject | Re: Some questions for Csound users and developers about the future of the Csound Windows installer | ||
|
Hi,
I use 2), 6), 8). But I'm interested to
all.
I think that the features have an easy
installation to integrate with Csound it could be indipendent, but the
features that have an elaborated installation could be enclosed in the
installer.
Greetings
Andrea S.
----- Original Message -----
|
| Date | 2017-06-19 23:59 | ||
| From | andy fillebrown | ||
| Subject | Re: Some questions for Csound users and developers about the future of the Csound Windows installer | ||
(1) The FluidSynth opcodes? YES (2) The Java interfaces? NO (3) The LuaJIT opcodes? NO (4) The CsoundAC algorithmic composition system? NO (5) The STK (C++) opcodes? NO (6) The CsoundQt "front end" for running Csound? YES (7) The linear algebra opcodes? NO (8) The FLTK widgets? NO! On Tue, Jun 13, 2017 at 5:02 PM, Andrea Strappa <a_strappa@tin.it> wrote:
|
| Date | 2017-06-25 20:16 | ||
| From | Michael Gogins | ||
| Subject | Re: [Csnd-dev] [Csnd] Some questions for Csound users and developers about the future of the Csound Windows installer | ||
Thanks to everyone who responded to this. After reading all the responses and thinking about I have come to the following conclusions: (1) I will drop LuaJIT, the Lua opcodes, and the Lua interfaces from the Windows installer. They are not widely used and their function has mostly been replaced by JavaScript and HTML5. (2) I will keep the remaining features for the time being: (2.a.) The FluidSynth opcodes. (2.b.) The Java interfaces. (2.c.) The CsoundAC system and interfaces. Ultimately I will move these features out of the Csound repository but not now. There are no longer any external dependencies so it should be easy to get this to build. (2.d.) The STK opcodes. (2.e.) I will continue to include CsoundQt in the Windows installer and I will merge and maintain the HTML5 support in CsoundQt. (2.f.) The linear algebra opcodes. I will replace the use of GMM with the use of Eigen3 for which there is already a port for the Visual Studio build system. (2.g) The FLTK opcodes. Regards, Mike ----------------------------------------------------- Michael GoginsIrreducible Productions http://michaelgogins.tumblr.com Michael dot Gogins at gmail dot com On Mon, Jun 19, 2017 at 6:59 PM, andy fillebrown <andy.fillebrown@gmail.com> wrote:
|
| Date | 2017-06-25 20:16 | ||
| From | Michael Gogins | ||
| Subject | Re: Some questions for Csound users and developers about the future of the Csound Windows installer | ||
Thanks to everyone who responded to this. After reading all the responses and thinking about I have come to the following conclusions: (1) I will drop LuaJIT, the Lua opcodes, and the Lua interfaces from the Windows installer. They are not widely used and their function has mostly been replaced by JavaScript and HTML5. (2) I will keep the remaining features for the time being: (2.a.) The FluidSynth opcodes. (2.b.) The Java interfaces. (2.c.) The CsoundAC system and interfaces. Ultimately I will move these features out of the Csound repository but not now. There are no longer any external dependencies so it should be easy to get this to build. (2.d.) The STK opcodes. (2.e.) I will continue to include CsoundQt in the Windows installer and I will merge and maintain the HTML5 support in CsoundQt. (2.f.) The linear algebra opcodes. I will replace the use of GMM with the use of Eigen3 for which there is already a port for the Visual Studio build system. (2.g) The FLTK opcodes. Regards, Mike ----------------------------------------------------- Michael GoginsIrreducible Productions http://michaelgogins.tumblr.com Michael dot Gogins at gmail dot com On Mon, Jun 19, 2017 at 6:59 PM, andy fillebrown <andy.fillebrown@gmail.com> wrote:
|
| Date | 2017-06-25 20:57 | ||
| From | Steven Yi | ||
| Subject | Re: Some questions for Csound users and developers about the future of the Csound Windows installer | ||
Sounds good and thanks very much Michael for all your work on this! On Sun, Jun 25, 2017 at 3:16 PM, Michael Gogins <michael.gogins@gmail.com> wrote:
|
| Date | 2017-06-27 15:08 | ||
| From | Felipe Sateler | ||
| Subject | Re: [Csnd-dev] [Csnd] Some questions for Csound users and developers about the future of the Csound Windows installer | ||
Hi, I have a few comments and questions as downstream debian packager of csound, prompted by this discussion. I have seen my available time being considerably reduced so if reducing some workload is possible I'd like to do that. 1. Should I drop the lua bindings and opcodes too? Are lua bindings being shipped in any other installer? 2. Should I still build the java bindings for debian? The main consumer of the java API is blue, but AFAIK nobody has tried to use blue with the debian-provided java interface. 3. If CsoundAC is removed from the main repository, it is unlikely I will maintain it downstream in debian. (But I'm available for questions and eventually uploading to debian if someone else wants to do the work of tracking upstream releases, bugfixing, etc). Saludos On Sun, Jun 25, 2017 at 3:16 PM, Michael Gogins <michael.gogins@gmail.com> wrote:
Saludos, Felipe Sateler |
| Date | 2017-06-27 15:12 | ||
| From | Michael Gogins | ||
| Subject | Re: [Csnd-dev] [Csnd] Some questions for Csound users and developers about the future of the Csound Windows installer | ||
I am not currently planning to remove CsoundAC, I am considering doing that in the future but at least for now, it stays in the repository, so I would appreciate your continued support for CsoundAC. Unless somebody else needs them, you can drop the Lua features, that's OK with me. I think you should continue to support the Java bindings. Thanks, Mike ----------------------------------------------------- Michael GoginsIrreducible Productions http://michaelgogins.tumblr.com Michael dot Gogins at gmail dot com On Tue, Jun 27, 2017 at 10:08 AM, Felipe Sateler <fsateler@gmail.com> wrote:
|
| Date | 2017-06-27 16:19 | ||
| From | Felipe Sateler | ||
| Subject | Re: [Csnd-dev] [Csnd] Some questions for Csound users and developers about the future of the Csound Windows installer | ||
I know it is not to be done right now. But I thought I should mention this fact before that decision is made, in case it is relevant. On Tue, Jun 27, 2017 at 10:12 AM, Michael Gogins <michael.gogins@gmail.com> wrote:
Saludos, Felipe Sateler |
| Date | 2017-06-27 16:36 | ||
| From | Steven Yi | ||
| Subject | Re: [Csnd-dev] [Csnd] Some questions for Csound users and developers about the future of the Csound Windows installer | ||
| Hi Felipe, I suspect there are Blue users that use the Csound java package in Debian, due to the occasional mailing list reports and version of Csound matching up with Debian package. It would simplify things for me if that was maintained. Moving forward, I could look into using JFFI and creating separate binding system that would dynamically load libcsound rather current bindings using libcsnd6, but I don't have a sense of performance impact or viability on that at the moment. Thanks! Steven On Tue, Jun 27, 2017 at 11:20 AM Felipe Sateler <fsateler@gmail.com> wrote:
|