Check out the list below to learn more about known issues and their solutions. This will ensure that your music creation journey stays as smooth as possible. If you don't find an answer to your questions, contact me.

AUv3 Known Issues

• Your host is unable to locate the plugin

  • Make sure you are looking into the right AUv3 section of your host (effect or instrument)
  • Verify that your host can load AUv3 plugins*
  • Close everything, launch the stand-alone app provided with the AUv3 and try again
  • Reboot your device

  Warning on macOS

  • In Logic Pro, if the plugin is not listed in a mono audio channel, toggle the channel mode to stereo to update the plugin list
  • In Hosting AU, the plugin view may be hidden. This particular problem persists since macOS Catalina (Reported to JUX). In such case, close the plugin and reload it. This occurs only with AUv3 plugins such as FAC and Tonebridge Guitar

  * List of hosts supporting AUv3 plugins on macOS: Logic Pro, Ableton Live, Garage Band, Reaper, Hosting AU, and Wotja

• The plugin does not produce any sound, or the sound is distorted

  Reset the Buffer Size setting on your host to 512, for instance, and try again

  In Logic Pro for macOS, you can also set the Process Buffer Range to 'Small' or 'Medium' (go to general Audio Settings)

• How to load FAC Drumkit Patchstorage kits ?

  Watch this video on how to import Patchstorage kits into FAC Drumkit. The process is the same for both iOS and macOS. Simply download the zip file and access it from FAC Drumkit by long-pressing the preset bar

• The multi-selection of files/folders in FAC Drumkit is not ordered

  The iOS Files dialog (The Document Picker Dialog) does not keep the order of your selection

• Cubasis for iOS: FAC Drumkit "Freeze in place"

  If you use the default option in Cubasis to freeze a track containing FAC Drumkit, you may lose some user samples in the beginning of the rendering. This is not the case when you activate the "compatibility mode" (In Cubasis). The default freeze option renders the track by re-allocating the AUv3, without a pre buffering delay required to initialize the AUv3 properly. Note that you can edit your midi clip and add an offset at the beginning. By doing so, the AUv3 will be initialized properly

• The knobs "duck wet" and "curve" have no effect in FAC Alteza

  The knobs "duck wet" and "curve" are only visible when an additional input bus is provided by the host. Beware that some hosts may provide a muted additional input bus with no support of the sidechain feature, you will see the knobs but the ducking will be ignored. In this case, set the knob "duck wet" to the OFF position

• FAC Envolver for iOS works fine as an audio effect, but there is no MIDI OUT

  In order to output MIDI messages, your host must provide a valid MIDI output block to the AUv3 (AUMIDIOutputEventBlock)

  FAC Envolver is a MIDI/AUDIO fx and can be used in every host, even the ones that still do not provide MIDI out support, in this case the MIDI generator is disabled and the fx can only be used as a standard AUDIO fx

  If you still have issues in a host providing a valid MIDI output block, check the following points:

  • Have you disabled the MIDI out? Both slot buttons (|1/ and |2/) can be toggled (gray muted/yellow activated)
  • Have you properly set the MIDI source in your host? Fac Envolver uses a virtual MIDI cable called "Fred Anton Corvest"
  • Have you mapped the MIDI CC to a parameter? Verify that the MIDI CC# are properly mapped to the parameters you want to control
  • Have you set both envelope DEPTHs to OFF? Increase the depth

• TIP JAR And Store: Error dialog box message "Something went wrong!"

  The network connection may be restricted by the host, touch the "Retry" button to automatically launch the FAC stand-alone app. If you get the error from the stand-alone app, follow the same instructions provided in the next section

• You can't restore the in-app purchases you already bought

  If the "Restore Purchases" button fails to restore your previous purchases:

  • Check your network connection, WIFI must be active
  • Check that you are properly signed in on your device with your Apple ID
  • Touch the "Buy" button, the Apple Store will let you know that you already own the IAP and will restore it for you
  
  

AUBE Known Issues

• The developers' names in the AUBE list differ from those on the App Store

  The manufacturer name on the App Store is a legal name and cannot be chosen by an indie developer. The manufacturer name you get in AUBE is the one provided by the AUv3 itself, so it is the one provided by the developer. The manufacturer name in the AUv3 can also be empty; some developers forget to set one. It's the same thing with the plugin name; a developer can set both names (App Store and AUv3) freely, and sometimes the names are different...

• The AUBE keyboard extension is not visible when my hardware keyboard is attached to my iPad

  • Check that the AUBE keyboard extension is installed properly
  • There is no warning in the General tab in AUBE
  • The AUBE keyboard extension is listed correctly in iOS Settings General > Keyboard
  • Disconnect your hardware keyboard and tap into a text field
  • The AUBE keyboard extension must be shown properly
  • Connect your hardware keyboard and tap into a text field
  • iOS must show a mini action bar on the bottom of the screen
  • Tap the mini keyboard icon on the left of the bar and tap “Show Keyboard”
  • Tap the globe button 🌐 on the screen and select the AUBE keyboard

  The previous information and assistance regarding both hardware and software keyboards on iOS is general and not specific to the AUBE Keyboard extension. It may vary among different hardware keyboard brands. The physical globe button 🌐 (on the hardware keyboard) does not consistently behave properly across various iOS versions, and this issue cannot be fixed or managed by a keyboard extension

• How to delete AUBE data from iCloud ?

  Go to Settings > iCloud > Manage Account Storage > AUBE - Audio Unit Box Explorer and tap 'Delete the data from iCloud.' WARNING: This action will permanently delete your data!

Apple AUv3 Plugins Open Issues on macOS

• Plugin window resize issue in Logic Pro and Garage Band

  There are two problematic scenarios related to how plugins report view configurations (AUAudioUnitViewConfiguration) to the host

  • When you change the zoom factor in the host plugin window, the view starts to grow and shrink erratically. This occurs when the AUv3 reports a valid preferred content size but ignores the view configuration mechanism or doesn’t support any of the view configurations provided by the host
  • The plugin window is squared. This occurs when the AUv3 reports one or more of the requested view configurations to the host. The host provides only square configurations, and it uses one of those view configurations while ignoring the preferred content size

  FAC Punchlab reports the view configurations to the host and sets the view in landscape within the square. This results in the bottom of the plugin appearing black, which is expected

  No Mac Catalyst lifecycle (UI rendered when the plugin is hidden)

  In Mac Catalyst, it's impossible to receive notifications about the show/hide status of a plugin. Consequently, any UI tasks that consume resources will continue to be performed even when the plugin is hidden, resulting in a complete waste of CPU resources

  FAC Punchlab includes a workaround to avoid any waveform rendering when the plugin is hidden

If you do not find an answer to your questions, mail ➞ support••fredantoncorvest•com