For questions, answers and opinions
https://forum.audacityteam.org/
Actually I sent it to the QA list and only Cc: to devel.Edgar wrote:I find it somewhat depressing that your post to -devel garnered not a single reply.
I got it to compile as noted above but stopped when I could not figure out the -70 vs. -63 thing. We would either need to get one set of figures which worked on all three platforms or figure out how to get the same results (defaults being the same) with pre-compiler #defines. Not having a Mac person to help us is a problem--we need to get someone to compile your code on Mac so Bill can test it.steve wrote: Have you made any progress with compiling/patching on Windows?
In the updated "Release Process/Win" notes, I see that is no longer the case:Edgar wrote:We do not compile GVerb for the Audacity source distro. I could not find the source code nor could I find any non-Audacity based support site. Do you have the source or know someone who does?steve wrote: Unfortunately I'm not a programmer or I would have done so long ago.
We are still keeping some of the LADSPA plug-ins in the Audacity installer, even though we are now offering a separate installer that includes all the LADSPA plug-ins built from version 0.4.15. We include gverb_1216.dll, hard_limiter_1413.dll and sc4_1882.dll. So:
1. Check http://plugin.org.uk/ for updates.
2. If none, just grab the dlls from a previous release.
3. If updated, build these via the audacitywinLADSPA_plugins-win project (see audacitywinLADSPA_plugins-winreadme_LADSPA_plugins-win.txt).
4. Once you have these DLL files, put them in the plug-ins folder, e.g., audacitywinunicode_releaseplug-ins.
