Jump to content

ro-ja

Member
  • Posts

    18
  • Joined

  • Last visited

ro-ja's Achievements

Newbie

Newbie (1/14)

  • Reacting Well Rare
  • First Post Rare
  • Collaborator Rare
  • Week One Done
  • One Month Later Rare

Recent Badges

2

Reputation

  1. Not in front of Logic to test it, but if I remember correctly: To see your patches the little blue triangle has to be on the left of the Settings pop-up menu (like in your first screenshot). To accomplish this click on the left side of the menu. When a plugin is highlighted (as in the second screenshot) the library displays the presets of this plugin.
  2. In analogika's example you would have several patches. Controller 1 would trigger the piano in all of these patches and controller 2 would trigger another sound (strings, sax, etc.). Is this what you want to achieve? From your original post I was thinking you want to be able to change timbres individually on both controllers which can't be done in Mainstage AFAIK.
  3. You could do it if you use just one virtual instrument with each controller and if these virtual instruments can somehow respond to patch changes. Instead of changing MainStage patches you would configure your buttons to recall the different timbres on each instrument.
  4. I'm using this script to automate things in Mainstage and it works quite well. In your case you would replace the note ons and control changes in the event list with program changes. Insert the Scripter plugin in an external instrument channel strip. Set the Midi Out of the channel strip to the IAC driver (if the IAC driver isn't available activate it in the Audio-Midi-Setup app). In the concert settings choose the IAC driver as a source for program changes. Now when you start the Mainstage clock the patches should change at the beat positions you defined in the script. Since applications send and receive on the IAC bus it can come to a Midi loop that freezes Mainstage. If I remember correctly I circumvented that by creating a Midi activity screen control in layout mode that I set to receive data on the IAC bus. On the concert level I created an external instrument channel strip, set this Midi activity control as input device, and set the Midi output of the channel strip to No output.
  5. If you need the loopback(s) globally you can use it on the concert level. If you need specific loopbacks for different songs I would organize the songs in sets. This way you can have things that should be available for the whole song on the set level and things that you need only for certain parts on the patch level. I find it useful also that you can set the loopback to be cleared automatically when you switch to another set. So nothing gets carried over to another song accidentally.
  6. Between Concert Level and Patch Level there's also the Set Level. Put the Loopback plugin in a set. Fill the set with patches. Now you can change patches and the Loopback keeps playing / recording.
  7. In Layout View create a Parameter Text object. In Edit View create a new Instrument Channel and insert a Playback plugin. Click the Parameter Text object and map it in the Screen Control Inspector as shown in the screen shot.
  8. Don't know if this helps, but if you use the Playback plugin for your backing tracks, you could create a text object and assign the plugin's parameter "Time To End" (as bars and beats or as hh:mm:ss) to it.
  9. This bug has been fixed in 3.5.2. Recordings are in stereo again and I've experienced no drop outs so far.
  10. I've just seen that 3.5.1 is out. Upgraded and tested again. No more glitches but now the recording is only mono
  11. I experience the same behaviour. Seems not to be related to Catalina but to be a bug in 3.5. A test with 3.4.2 and 3.4.4 under Catalina went without issues.
  12. Can you explain which bugs you are experiencing in Mix Control? I've updated to Mojave recently and except for one minor issue everything works fine so far. The Saffire Pro 40 doesn't connect to the Mix software when it is switched on before my Mac mini boots. But this seems to be something related specifically to this system because when connected to my MacBook Pro the problem doesn't occur.
  13. What happens if you try to open a concert after the program has loaded? Does this work? Maybe you just changed Mainstage´s start up behaviour. Below are the several options which can be found in the general preferences. Startup Startup Action pop-up menu: Choose the startup action when you open MainStage. The choices are: •Do Nothing: Does nothing. You can open the Choose Template dialog by choosing File > New. •Create New Concert from Template: Opens the Choose Template dialog. •Open Most Recent Concert: Opens the last open concert in the same mode it was in when you closed it. •Open Most Recent Concert in Perform Mode: Opens the last open concert in Perform mode.
  14. If you define the desired number of bars in the loopback plug-in while it is still empty (nothing recorded yet) the length should be preserved after the recorded audio is cleared.
×
×
  • Create New...