Download the MainStage Sample Library | Fix Missing Sounds Errors | MainStage Tutorial

Поділитися
Вставка
  • Опубліковано 5 вер 2024

КОМЕНТАРІ • 12

  • @jkalel6310
    @jkalel6310 Місяць тому

    can you help me?

  • @mydanbff5483
    @mydanbff5483 7 місяців тому

    Thank you but why is my sound library greyed out after downloading all sounds I can’t access open sound library manager please help

    • @WorshipTeamResources
      @WorshipTeamResources  7 місяців тому

      Is it possible it is still in the process of downloading? If you need help, please send us an email using the form on the support page of our website.

  • @jkalel6310
    @jkalel6310 5 місяців тому

    In mainstage I get an instability error in the audiounit module. Do you think that by installing these downloads that message will stop appearing? greetings

    • @WorshipTeamResources
      @WorshipTeamResources  5 місяців тому +1

      No, Audio Units refer to 3rd party plugin issues.
      You are probably either: Missing a plugin that a sound is using (it wouldn’t be KeyStudio, as we don’t use any third party plugins), have a plugin that is incompatible, or have a plugin that is corrupt.
      If you post the exact error, I can help you diagnose it better.

    • @jkalel6310
      @jkalel6310 5 місяців тому

      @@WorshipTeamResources but in the module manager, everything appears compatible. I followed your advice because some sounds did not appear downloaded in mainstage.

    • @WorshipTeamResources
      @WorshipTeamResources  5 місяців тому

      @@jkalel6310 it doesn’t hurt to download the MainStage sound library, but just know it doesn’t have anything to do with Audio Units.
      What is the exact error message you are getting?

    • @jkalel6310
      @jkalel6310 5 місяців тому

      @@WorshipTeamResources says: an audio units module has detected a problem that could cause system instability. Exit the app and restart mainstage.

    • @WorshipTeamResources
      @WorshipTeamResources  5 місяців тому +1

      @@jkalel6310 it’s either a MainStage bug or perhaps one of the third party plugin developers for a third party plugin you installed is not up to date for what MainStage wants to see.
      If everything looks good in the Plug-in Manager, then I wouldn’t worry about it.