Re: Developer Fund
Posted: Fri Nov 24, 2017 11:42 pm
How can we proceed to transfer 200$ ?
so exciting !
so exciting !
Here’s a fun idea - what if everyone gets to vote on order of (say top 3 or 5) goals.John Bowen wrote: Fri Nov 24, 2017 8:41 pm It’s important to know how much more owners would be willing to pay. This would affect the schedule significantly in terms of being able to get things up and running quickly. Please everyone let me know.
No, this would be a new software developer for the DSP part of the Solaris. That concerns new features that are in the ‘synth voice’ portion of the code, such as new oscs or filters, or other things that are handled on a per voice basis, as well as the Master FX section, which currently is the Chorus, Flanger, Delay, and EQ. The v1.3.1 OS update by Jim Hewes had to do with fixing the bugs and adding features to the Blackfin part of the code, which generally manages the system - the displays, the I/O functions, the MIDI code, voice handling, etc.. Jim has done a huge amount of work for the Solaris OS code, fixing all the bugs he could, and adding a lot of new features that have been requested, but he’s not working with the audio-related DSP code.
Are you also looking for someone to polish and finish the Mac and PC utilities for preset naming (and perhaps sample loading?), and perhaps build a VST librarian.John Bowen wrote: Sun Nov 26, 2017 5:16 pmNo, this would be a new software developer for the DSP part of the Solaris. That concerns new features that are in the ‘synth voice’ portion of the code, such as new oscs or filters, or other things that are handled on a per voice basis, as well as the Master FX section, which currently is the Chorus, Flanger, Delay, and EQ. The v1.3.1 OS update by Jim Hewes had to do with fixing the bugs and adding features to the Blackfin part of the code, which generally manages the system - the displays, the I/O functions, the MIDI code, voice handling, etc.. Jim has done a huge amount of work for the Solaris OS code, fixing all the bugs he could, and adding a lot of new features that have been requested, but he’s not working with the audio-related DSP code.
Yes. I’d actually prefer spending first on useability (library utility) and workflow (like multi and sample handling) to adding more effects and oscillator algos. But id be happy if you could do both.John Bowen wrote: Sun Nov 26, 2017 5:55 pm Yes, but all of those utilities are separate from the development being discussed here. I think you are suggesting a general Developer Fund, not one solely dedicated to DSP enhancements?
There are few online here that have worked on editors for the PC/Windows platform - minorguy, gundorf, and qtuner. Perhaps they can respond here regarding open sourcing of their code.Hook wrote: Mon Nov 27, 2017 8:13 am Are there bits of utilities that could be open sourced to see if others would be willing to work on them?