-
Notifications
You must be signed in to change notification settings - Fork 7
/
faq.html
450 lines (361 loc) · 22.4 KB
/
faq.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
<!doctype html>
<head>
<title>Destroy FX : FAQ</title>
<link rel="Stylesheet" type="text/css" href="dfx.css" />
<meta name="author" content="Tom 7 and Sophia" />
<style>
body {
background-color: #750927;
}
.maincolumn {
background-color: #98022C;
}
div.infobox {
width: 575px;
}
div.q h3 {
font-size: 20px;
font-weight: bold;
margin-top: 0;
}
div.q h4 {
font-size: 16px;
font-weight: bold;
}
div.toc li {
font-size: 14px;
list-style-type: none;
margin-bottom: 4px;
}
</style>
</head>
<div class="maincolumn">
<a href="index.html"><img class="title" src="faq-title.png" width="385" height="70" alt="Destroy FX: FAQ" /></a>
<!-- toc -->
<div class="infobox toc">
<li><a href="#incompatibility">Why won't your plugins show up on my system?</a></li>
<li><a href="#us">Who are you?</a></li>
<li><a href="#needlessquestion">How do I do <i>X</i>? Or can your software do <i>X</i>?</a></li>
<li><a href="#bugreporting">I think I found a bug.</a></li>
<li><a href="#filedownloads">What do I do with the files that I downloaded?</a></li>
<li><a href="#installation">How do I install your plugins?</a></li>
<li><a href="#noshow">Your plugins won't show up. What can I do?</a></li>
<li><a href="#auval">Do your Audio Unit versions pass AUValidation in Logic?</a></li>
<li><a href="#how2makeplugins">How can I make plugins?</a></li>
<li><a href="#bundling">Can we put your software on a CD/DVD that we will include with our magazine?</a></li>
<li><a href="#otherformats">Will there be AAX / LADSPA / DirectX / MAS / etc. versions?</a></li>
<li><a href="#banner">Do you have a banner that I can put on my web site?</a></li>
<li><a href="#vstmidi">Why won't VST MIDI or VST GUI Tester run on my computer? I use Windows.</a></li>
<li><a href="#biz">Are you available for paid consulting work?</a></li>
<li><a href="#retirement">Are you still going to make new software?</a></li>
</div>
<div class="infobox q" id="incompatibility">
<h3>Why won't your plugins show up on my system?</h3>
These are a few possible sources of incompatibility:
<ul>
<li>Our plugins only run in 64-bit host software. Some old software is 32-bit.</li>
<li>If you are using VST for Mac, we have discontinued development of those long ago and the
last versions only run on ancient PowerPC-based Macs. We have heard positive reports about
<a href="https://www.bluecataudio.com/Products/Product_PatchWork/">Blue Cat Audio's PatchWork</a>
as a wrapper to use AUs in VST-only hosts.</li>
<li>Confirm that your computer and host software meet our
<a href="sysreq.html">system requirements</a>.</li>
</ul>
Transverb 1.5.2 for Mac also will likely produce the ominous message that it "can't be
opened because Apple cannot check it for malicious software." This is because oops we
forgot to "notarize" the download package. The easiest solution is to convince macOS
that it was not downloaded from the wilds of the internet via the following command in Terminal:
<br />
<code>xattr -d com.apple.quarantine ~/Downloads/transverb-1.5.2-mac.dmg</code>
<br />
(which assumes the default downloaded path to the disk image file, though adjust the end of that
command accordingly if you relocated the file). You may need to unmount and remount the
Transverb disk image as well.
</div>
<div class="infobox q" id="us">
<h3>Who are you?</h3>
<p>We are Sophia Poirier and Tom Murphy 7. We are buddies from back since grade school. We like
to make music and, sometime around December 1999, making music software became a part of that
process. You can contact us <a href="index.html#contact">here</a>.</p>
<p>For more information about Tom, try <a href="http:https://tom7.org/">visiting</a>
<a href="http:https://spacebar.org/">one</a> <a href="http:https://carnage-melon.tom7.org/">of</a>
<a href="http:https://radar.spacebar.org/">his</a> <a href="http:https://www.tom7.com/">numerous</a>
<a href="http:https://members.spacebar.org/imightbetm/">web</a> <a href="http:https://snoot.org/">sites</a>.
Sophia, on the other hand, is allergic to internet presence.
</p>
</div>
<div class="infobox q" id="needlessquestion">
<h3>How do I do <i>X</i>? Or can your software do <i>X</i>?</h3>
Please read the <a href="docs.html">documentation</a> included with the plugin before you write to us.
Most of the questions that we get are answered in the documentation.
</div>
<div class="infobox q" id="bugreporting">
<h3>I think I found a bug.</h3>
Before writing to us about a problem, please check our web page to see if there might be a
newer version of the software (we may have already fixed the bug). If you still need to write
to us about a bug or some problem, please include the following information:
<ul>
<li>the exact steps of what you were doing (or trying to do) with our software, what you were
expecting to happen, and what actually happened</li>
<li>the name and version of the operating system that you're using</li>
<li>the type of computer that you're using (manufacturer, CPU type, etc.)</li>
<li>the name and version of the host software in which you are using our plugins (if it is a
plugin that you're writing to us about)</li>
<li>the version of our software that you're using (in macOS, do Get Info on the file in
Finder to see the version; in Windows, uhhh, I guess you could write a simple VST host app
that loads the DLL and uses the effGetVendorVersion opcode to query the plugin's version
number)</li>
<li>the format of our software that you are using, if it is a plugin (AU, VST, etc.)</li>
</ul>
<p> Also, if you are using macOS and experienced a crash with our software, crash logs can
often be very helpful, so it is great if you can send the crash log to us. You should be able
to find the crash log in <code>~/Library/Logs/DiagnosticReports</code> (that's in your user
home Library).
</div>
<div class="infobox q" id="filedownloads">
<h3>What do I do with the files that I downloaded?</h3>
<p>The files at this web page are compressed archives. This means that there are several files
wrapped up into one single file (archive) which is shrunk down in size (compressed) so that it
doesn't take as long to download. You need to decompress the archives before you do anything
else. If the files don't automatically decompress (or "expand") when you download them, and if
double-clicking on them after downloading doesn't work either, then that probably means that
you need to install software that can decompress these archives. We use (or have used) several
archive formats: 7z archives (files ending in .7z), Apple disk images (files ending in .dmg),
ZIP (files ending in .zip), and StuffIt X (files ending in .sitx). macOS has software built-in
for mounting its disk image files and expanding most compressed file formats. Tom likes
<a href="https://www.7-zip.org/">7-Zip</a> on Windows.
<a href="https://www.stuffit.com">StuffIt Expander</a> may be needed for our earliest
(up through 2003) Mac and source file distributions.</p>
<p>If you have successfully decompressed the archives, read our <a href="#installation">installation
instructions</a> to learn how to install our software.</p>
</div>
<div class="infobox p" id="installation">
<h3>How do I install your plugins?</h3>
<h4>Audio Units:</h4>
<p>To install one of our Audio Units on macOS, simply run its installer.</p>
<p>To use Audio Unit plugins, you will need software (which we call the "host application")
that can load them. We try to maintain a <a href="hostapps.html">list of host applications</a>.</p>
<p>If the plugins don't show up in your Audio Unit host, try logging out and then logging
back in. If that doesn't help, then you might even need to reboot your computer,
or if you are handy with Terminal:
<br />
<code>sudo killall -9 AudioComponentRegistrar</code></p>
<h4>VST plugins:</h4>
<p>To use VST plugins, you will need software (which we call the "host application") that can
load them. We try to maintain a <a href="hostapps.html">list of host applications</a>.</p>
<p>Most of the time, you install VST plugins by placing the plugin files into a folder called
VstPlugIns. The VstPlugIns folder usually needs to be located in the same folder as the host
application.</p>
<img class="centered" src="vstplugins-folder.png" width="306" height="198" alt="VstPlugIns folder" />
<p>There is variation between some of the different hosts, so check your host's documentation
for more specific instruction. On <b>macOS</b>, there is a standard location for VST plugins:
<code>Library/Audio/Plug-Ins/VST/</code> (As with Audio Units, that can be Library in the
user or local domain.) Decent hosts automatically know to look for VST plugins there.
On <b>Windows</b> a common location is <code>c:\Program Files\Steinberg\VstPlugins</code>, but
you might need to check your host's documentation or settings.
</p>
<p><b>Special note for Windows users:</b>
The plugin files for Windows have names with .dll extensions. If you use Windows and are not
able to see the plugin files, then you probably have the "Do not show hidden or system files"
preference selected under "Folder Options" in Windows. To change this, open any folder on your
computer, open the View menu, and select Folder Options. Next, click on the View tab. You should
now see the "Hidden files" option. Change it to "Do not show hidden files," or "Show all files" if
you prefer. Now you should be able to see the .dll files.</p>
</div>
<div class="infobox q" id="noshow">
<h3>Your plugins won't show up. What can I do?</h3>
<p> First, make sure that you have installed them correctly. Please refer to our
<a href="#installation">installation instructions</a>.</p>
<p>Make sure that your system supports the plugin(s) by checking our <a href="sysreq.html">system
requirements</a>.</p>
<p>Also, make sure that the host application that you are using supports the particular
plugin(s) that you are trying to use. You can find details about many host applications and
the sorts of plugins that they support in our <a href="hostapps.html">list of host applications</a>.</p>
<p>Logic and Digital Performer also have some additional things to be aware of when
troubleshooting plugins not showing up...
</p>
<h4>Logic:</h4>
<p>Logic (version 7.0 and higher) utilizes AUValidation to determine which AUs will
be enabled for use. AUValidation is Apple's official validator of conformance to the AU
specification. Any AU that fails or crashes AUValidation will be disabled in Logic.
When you first launch Logic, it will run each of your installed AUs through
AUValidation. The results are remembered, and after that, new AUs will only be run through
AUValidation when you install additional AUs or when you update your existing AUs to newer
versions.</p>
<p>All of our AUs currently pass AUValidation to the best of our knowledge. However,
sometimes Apple updates AUValidation in ways that can catch more problems that we previously
didn't realize an AU had, and also on occasion some system-specific problems can affect
them passing, so it's good to know how to troubleshoot this.</p>
<p>First, you can try launching the Plug-In Manager and rescanning a failed AU. You launch
it by going to the Logic application menu → Preferences → Plug-in Manager. The
Plug-In Manager presents you with a list of all of your installed AUs and the results of
their last AUValidation scan. You can push the Reset & Rescan button for an AU to rescan it.
You can, if all else fails, override a disabled AU here by clicking on its Use checkbox.</p>
<p>In more extreme cases of problems, you can force Logic to redo its AUValidation scanning
from scratch by trashing Logic's AUValidation results cache file. This file is located at
<code>~/Library/Caches/AudioUnitCache/com.apple.audiounits.cache</code> (that's in your user
home Library). You should trash or move that file when Logic is not running, and also run
the following command in Terminal:
<br />
<code>defaults delete com.apple.audio.InfoHelper</code>
<br />
Then relaunch Logic to begin a full rescan of all installed AUs.</p>
<p>In cases where you are not able to get an AU of ours to pass AUValidation, and you are
sure that you have the latest version of the AU installed, please go into Plug-In Manager,
do a Rescan of the AU, select and copy all of the text in the validation results window that
pops open, and please <a href="index.html#contact">send that to us</a>. If the AU is crashing
AUValidation, please send us the crash log as well, which you should be able to find at:
<code>~/Library/Logs/DiagnosticReports/auval.crash</code>
</p>
<h4>Digital Performer:</h4>
<p>Digital Performer also performs tests on all AUs before enabling them for use, but does so
using its own torture test tool rather than Apple's AUValidation, so note that results can
vary between the two. The way in which DP tests AUs, remembers the results, tests again only
for new additions or updated versions, etc. is all similar to what is described above for
Logic and AUValidation. All of our AUs currently pass DP's AU test to the best of our
knowledge.</p>
<p>If you do encounter problems, you can force DP to redo its AU testing from scratch by
trashing DP's AU test results cache file. This file is located at
<code>~/Library/Preferences/Digital Performer™/Audio Unit Info Cache</code>
(that's in your user home Library). You should trash or move that file when DP is not
running, and then relaunch DP to begin a full rescan of all installed AUs.</p>
<p> In cases where you are not able to get an AU of ours to pass DP's AU test, and you are
sure that you have the latest version installed, please see if you have the file
<code>~/Documents/MOTU AU Test Results.txt</code> and <a href="index.html#contact">send
that to us</a>. Also if the AU is crashing DP's AU test, please send us the crash log as well,
which you should be able to find at <code>~/Library/Logs/DiagnosticReports/MOTU_AU_Examiner.crash</code>
</p>
</div>
<div class="infobox q" id="auval">
<h3>Do your Audio Unit versions pass AUValidation in Logic?</h3>
<p>Yes, they all pass. If you are experiencing troubles, make sure to download the latest
versions from our site.
</p>
</div>
<div class="infobox q" id="how2makeplugins">
<h3>How can I make plugins?</h3>
<p>If you want to make plugins, the first thing you want to do is learn how to program a
little. You probably want to learn C and C++ since that's what the AU and VST SDKs are written
in. Most other languages unfortunately are not suitable for realtime audio applications.</p>
<p>If you want to make Audio Unit plugins, first pick up the CoreAudio SDK from the
<a href="https://developer.apple.com/audio/">Apple Developer</a> site. The Audio Unit SDK
is a part of the CoreAudio SDK. There is also a
<a href="https://lists.apple.com/mailman/listinfo/coreaudio-api">CoreAudio API email list</a> to
which you may want to subscribe, it's very useful (as are the list's archives).</a>.
</p>
<p>If you want to make VST plugins, go to <a href="http:https://www.steinberg.net/">Steinberg's web site</a>
and get the VST SDK. This has the source code that you need to make VST plugins, source code for a few
example plugins, and some "documentation". You also might want to subscribe to the VST
developers email list that Steinberg manages. That way, you have access to the list archives
(there's a lot of information in there) and you can post your own questions to the list when you
encounter problems.</p>
<p>For general audio/DSP/music programming, we also recommend the
<a href="https://www.musicdsp.org">music-dsp</a> source code archive and email list for information
about audio DSP (digital signal processing) in general.
</p>
</div>
<div class="infobox q" id="bundling">
<h3>Can we put your software on a CD/DVD that we will include with our magazine?</h3>
<p>The answer to that question is usually yes, with the following stipulations:</p>
<ul>
<li>send us two complementary copies of that issue of your magazine (one to Tom and one to Sophia)</li>
<li>include versions for all supported platforms (if it makes sense to do that; if your
magazine focuses on a specific platform, then it might not make sense)</li>
<li>make sure that you go to our web page at the last minute and get the most recent versions of our stuff</li>
<li>follow the redistribution terms of the software's license</li>
<li>if possible, include some piece about us in your magazine (review, news, interview)</li>
<li><a href="index.html#contact">contact us</a> first (we will probably say "yes" if you agree to these
stipulations, but please still contact us first)</li>
</ul>
</div>
<div class="infobox q" id="otherformats">
<h3>Will there be AAX / LADSPA / DirectX / MAS / etc. versions?</h3>
<p>It's very unlikely.</p>
<p>Especially all of Digidesign's formats (AAX, RTAS, AudioSuite, and TDM) because they are
completely closed, proprietary formats. You need Digidesign's permission to make plugins in
those formats and then you must keep the details secret, which doesn't work for us since we
release our source code.</p>
<p>And we definitely won't do MAS since Digital Performer now supports Audio Units (as of
version 4.1), so MAS is basically an irrelevant format.</p>
<p>LADSPA currently lacks a lot of features that our plugins rely on (tempo and other musical
time information, MIDI, custom GUIs, etc.), so it would be difficult to support that format
and it would require removing a lot of functionality from our plugins.</p>
</div>
<div class="infobox q" id="banner">
<h3>Do you have a banner that I can put on my web site?</h3>
<p>Yes we do, check it out:</p>
<a href="banner.gif"><img class="centered" src="banner.gif" width="468" height="60" alt="Destroy FX banner"
title="visit the Destroy FX web site" /></a>
<p>You can add it to your web site by including the following HTML:</p>
<code>
<a href="http:https://destroyfx.org">
<br />
<img src="http:https://destroyfx.org/banner.gif" width="468" height="60" alt="visit the Destroy FX web site">
<br />
</a>
</code>
</div>
<div class="infobox q" id="vstmidi">
<h3>Why won't VST MIDI or VST GUI Tester run on my computer? I use Windows and/or macOS.</h3>
<p>Because there are no Windows or macOS versions of those apps. They only run under "classic"
Mac OS (8 or 9, not X or later) currently. At the time when we made these, Max was not yet
available for Mac OS X or Windows. Now it is, however, we've discontinued development of these
applications (because we don't think that they're very worthwhile). The source patches are
still available, though, if anyone wants to try to create stand-alone applications from them
for those other platforms.</p>
</div>
<div class="infobox q" id="biz">
<h3>Are you available for paid consulting work?</h3>
<p>The Destroy FX team is not currently available for hire, but here are projects that we have done:</p>
<div class="twocolumn gig">
<div><a href="http:https://sfxmachine.com/"><img src="sfx-small.png" alt="SFX Machine RT"></a></div>
<div>
<a href="http:https://sfxmachine.com/">SFX Machine RT</a> - A cool multi-effects audio suite
capable of very unique, bizarre, and wonderful sound mangling. Sophia did the real-time
update of this plugin for Audio Unit and VST formats. Sophia also developed the
Backwards Machine plugin.
</div>
</div>
<div class="twocolumn gig">
<div><a href="http:https://cycling74.com/"><img src="pluggo-small.jpg" alt="Pluggo"></a></div>
<div>
<a href="http:https://cycling74.com/">Pluggo</a> - The never ending plugin. Pluggo was a
collection of 100+ unusual and great effects and instruments. Plus, it also let you
turn your Max/MSP creations into plugins that you can use in other apps. Sophia did the
Audio Unit update for Pluggo (plus a bit of work on Max/MSP).
</div>
</div>
<div class="twocolumn gig">
<div><a href="http:https://ursplugins.com/"><img src="urs-logo-small.jpg" alt="URS"></a></div>
<div>
<a href="http:https://ursplugins.com/">URS Classic Console Plug-Ins</a> - These are faithful,
high-end models of classic hardware equalizers and compressors. Sophia did the Audio
Unit and VST versions of all of their plugins as well as the RTAS/AudioSuite versions
of a some of them.
</div>
</div>
<div class="twocolumn gig">
<div><a href="http:https://abbeyroadplugins.com/"><img src="abbeyroad.png" alt="Abbey Road"></a></div>
<div>
<a href="http:https://abbeyroadplugins.com/">Abbey Road Plug-Ins</a> - These were authentic
recreations of Abbey Road Studios equipment. Sophia did the Audio Unit and VST versions
of most of their plugins.
</div>
</div>
<div class="twocolumn gig">
<div><a href="http:https://refusesoftware.com/"><img src="refuse-logo.png" alt="reFuse Software"></a></div>
<div>
<a href="http:https://refusesoftware.com/">reFuse Software</a> - Sophia did the native Audio
Unit, VST, and RTAS versions of their Lowender subharmonic bass synthesizer plugin.
</div>
</div>
</div>
<div class="infobox q" id="retirement">
<h3>Are you still going to make new software?</h3>
<p>Perhaps! As of 2020, Sophia and Tom have been doing other full-time software development work for
many years, and it makes us tired. However, we've mostly managed to get the plugins and our
libraries into a state where they are feasible to work on again. Both of us have ideas and unfinished
plugins still in our hearts.</p>
</div>
</div>
</body>