Originally Posted by
mr_es335
Philip,
You stated, "Juce is an open source library. Meaning it could be patched to fix the issue in SAC/SAW..." ..."True"...but only at the behest or interest of the original developer. Thus, if the original developer has no interest in pursuing the matter, the no further steps would be taken!
The following is typical of that which I have received for those whom i have reached out to...six in all...
"Juce is VERY MUCH an industry standard at this point. My guess is that most plugin developers are using it. SAC, on the other hand, is a product that I***8217;ve only heard of one customer using, that is you. If the SAC developer is insisting that the issue is not his, but is rather a Juce issue, I would ask why Juce plugins successfully run in Pro Tools, Logic, Live, Cubase, FL Studio, Studio One, Bitwig, Reaper, Reason, Garage Band, etc. In general, I would suggest moving on to a modern DAW that is being actively developed. A lot of Windows users that work ***8220;closer to the metal***8221; are very happy with Reaper, which is a $60 investment, and is free to try out."[Emphasis mine]
Of the six, only one had ever heard of SAC...or SAW for that matter. All six said that I should consider Reaper as an alternative! Very disappointing indeed
That would be the most useful approach with the added benefit that it would potentially fix all of the plug-ins utilizing the library.
You then stated, "Perhaps it would be useful to reach out to the Juce development community and see if its possible to find somebody that would be interested in fixing the bug." Good suggestion...thanks for this. I will contact two of the developers whom I have worked closely with and ask them if this might be a possible solution to the "problem". I will keep you posted as to what their response is.
Connect With Us