Jump to content

jacou

Member
  • Posts

    14
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

jacou's Achievements

  1. Awesome! Both midi velocity compression/expansion and change midi velocities of multiple regions are fixed and that in such a short time! Well done team Logic! I was afraid that I would have to get used to not having these two things anymore for a long time.
  2. Thanks everyone for your knowledge and help! So we'll have to report, wait and see... ☕️
  3. Yes it’s reported. Another issue with midi velocities that I experience in 10.8 is when I select and open multiple midi regions and try to increase or decrease the midi velocities of multiple regions at the same time. Before 10.8 I could select midi notes of multiple regions and use the velocity slider to change them. Now it only changes the velocities of only one region at a time. I guess that’s another bug 🙈
  4. Thank you David for the reply! What a bummer that that feature is gone. It was a part of my everyday workflow 😞 I hope it’s coming back! Thank you for the workaround idea. I actually never used the dynamic parameter in the region inspector. Good to know that it’s there. Is there maybe a key that I can press and hold while dragging midi note velocities that will change the dynamics? Or while moving the velocity slider in the piano roll? It’s hard to believe that the devs remove that feature without any proper alternative.
  5. Hi, since I updated to Logic 10.8 there seems to be no more way to compress/expand the midi notes velocity dynamics. When you go into a midi region via double click, select all midi notes in that region and then try to drag all velocities up or down in the automation/MIDI view (viewing velocity), all midi note velocity values keep the same dynamic relationship. There is no more compression or expansion. All previous Logic versions would compress the midi note velocity values by dragging them down or expand them by dragging them up. I heavily rely on that feature with orchestral composition. Is there any other (simple) way to achieve that midi velocity compression/expansion? Thank you!
  6. Just saw that there is a new stability update for Logic. Is there any info out yet?
  7. Ok I found the problem. I assigned the same foot controller midi CC to something else already. So MS probably blocked them for the Enso plugin. After deleting the other assignment everything worked just fine. Thank you anyway
  8. I’ve been using Audio Damage Enso (audio looper) in AUM on my iPad and never had a Problem with any midi assignment. Using a midi foot controller that sends regular midi CCs. Now that I tried to use Enso in MainStage I couldn’t figure out how to get any midi signal from my foot controller into Enso. Here is the deal. Enso doesn’t let you to midi assign its controls in the DAW. There is a midi assignment within the plugin. So I created a midi track in MainStage, put in Enso as a midi instrument with audio side chain input so that midi can get into the plugin. But the only midi Input I can choose is my midi keyboard but not my foot controller. When I press my foot controller I can see the midi input message in the MS top bar but no way to get it routed into the Enso plugin. Sorry if this is confusing I hope it makes any sense to you. Is there anything I can do that I missed? Would be great to figure this out! (In Logic I got it to work with the same midi side chain audio method)
  9. Oh I can’t really agree with you. I’ve been using my old iPad Air 1 to play electric guitar through AUM with very little latency. Maybe 6ms. I don’t see why Apple wouldn’t be able to release a proper Mainstage version on iPadOS. But it’s probably not their main priority. Let’s first hope for a good enough Logic version on iPadOS.
  10. I guess the easiest is to get thicker strings and tune down the guitar. I have tried to get a lower tuning with plugins but it didn’t work well. You either can slow down the audio but obviously screw with the timing then or you use a pitch shifter that makes the guitar sound unnatural. Metallic weird. Maybe works if you add heavy distortion. I ended up getting a baritone conversion neck. If you find a way to get a decent result let me know. I’m curious ✌️
  11. Are you on Mojave and MainStage 3.4? Then it might be the same issue/bug that we have. See this thread: viewtopic.php?f=17&t=139089
  12. Having the exact same problem here. Mojave + MainStage 3.4 on an iMac that is more than suitable to run MainStage without problems. There wasn't any issue with MainStage 3.3.2 on High Sierra. My feeling is, that something goes wrong with the multithreading. MainStage is probably running only on one of my 4 cpu cores. Also I noticed that in the cpu usage monitor in MainStage the max % value is changing on the Y axis. So if a lot cpu power is needed the max value climbs up to 140% on my computer and if very little cpu is needed the max value goes down to 60%. But as soon as the usage goes anywhere close to the max value, my van starts to turn making a lot of noise. Not sure what exactly is causing the problem (not an expert here) but that behavior seems a little bit odd to me! Let's report back to Apple. Hope they will fix this very soon! Anyone else experiencing similar behavior?
×
×
  • Create New...