Jump to content

Jordi Torres

Moderator
  • Posts

    17,441
  • Joined

  • Last visited

  • Days Won

    37

Jordi Torres last won the day on March 25

Jordi Torres had the most liked content!

About Jordi Torres

Recent Profile Visitors

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

Jordi Torres's Achievements

  1. You're welcome Bobby! 🙂 Normally unchecking that box will simply disable the automatic configuration that is facilitated behind the scenes by the MIDI Device Script I mentioned, and this simply means that your keyboard will send MIDI data to Logic that's not mapped to anything (so, plain MIDI notes, Control Change events, Pitch Bend, etc.) Yes, by doing this you'll be able to freely assign any of the MIDI messages your keyboard sends to parameters of your choice in Logic. Good. Sure, post back if you run into other issues. J.
  2. Hi @Bobby Knusprig, I think there's a MIDI Device Script built into Logic for you Roland A-49 (actually valid for all Roland A Series keyboards). This basically auto maps some of the keyboards controls to Logic's Smart controls and other functions. As you don't necessarily have to use your keyboard this way, you could try bypassing (disabling) this auto configuration and use the keyboard as a regular, "dumb" MIDI controller. To do so, please go to Settings > Control Surfaces > MIDI Controllers. You should the a table there with a like for your keyboard, and a checkbox in the "Auto" column. See if unchecking that box makes the keyboard behave as expected. If that doesn't help, next I'd check that you have the latest driver available for your keyboard and your version of macOS (which version of macOS and Logic do you have?) https://www.roland.com/global/support/by_product/a-49/updates_drivers/ J.
  3. For some time now it's possible to call Transform Window user presets by key command. So that would be the way to achieve that. You'll just have to create a user preset for "flattening" the velocity to a value of your choice, then save that project as a template and start all your projects from it so that your Transform preset is always available and applicable via key command. BTW, the commands are Apply Transform User Preset x to selected Events (where "x" is the user preset number). J.
  4. @trstack, Here's a couple more ideas: 1 - Quit Logic and delete Logic's control surfaces preferences file: /Users/your username/Library/Preferences/com.apple.logic.pro.cs Please remember that your user Library folder may be hidden. You can access it from the Finder's Go menu and holding down the Option (Alt) key. Once this is done, launch Logic and test again. Note: You'll have to set up the Montage as a control surface again after doing this. 2- Upload your current Audio MIDI Setup MIDI Devices configuration file (I'm assuming you have just one) to be absolutely sure there's nothing weird there: /Users/your username/Library/Audio/MIDI Configurations/Default.mcfg J.
  5. I’m not in front of my Macs right now, but from memory I don’t think there is a MIDI Device Script for that keyboard for it to be automatically configured for Logic (hence no entry for it in that window) Now it sounds more like it’s simply sending unwanted MIDI data to Logic. You could easily check this with a tool such as the free Snoize MIDI Monitor. J.
  6. Hi Deborah, Smart Controls doesn't do that. A MIDI controller or Control Surface might, though. If your MIDI Controller appears in this window, uncheck the Auto checkbox and see whether the behavior stops? https://support.apple.com/en-gb/guide/logicpro/lgcp14702db2/10.8/mac/13.5 What MIDI Controller do you have? J.
  7. Hi globet, No, that precise feature doesn't exist in Logic. You can always send a feature request to the Logic team: https://www.apple.com/feedback/logic-pro/ J.
  8. We're flattered, but sounds like they're lacking in he tech support department 😅 Give this one a try: Give this a try: https://www.logicprohelp.com/forums/topic/149781-autotune-pro-successfully-validated-during-scan-but-not-showing-in-plug-in-menu/?do=findComment&comment=870937 J.
  9. Right, but as far as Logic is concerned, a Software Instrument track + External Instrument plugin is an external MIDI track. But you could still do a multi-timbral setup this way if necessary, you could even route MIDI Channel-specific data to a single Software Instrument track and apply your MIDI effect to all data simultaneously, or process each MIDI Channel-specific data with separate instances of your MIDI effect. One thing to keep in mind when using Software Instrument track + External Instrument plugin: No SysEx will pass through those. You necessarily need a "classic" External MIDI track for that. J.
  10. Hi @Orourkekings, I did not watch the video, but If you want to use any Audio Units MIDI Effect with a hardware synth, you will have to do so by creating a Software Instrument track + External Instrument plugin. J.
  11. Hi Bahadir, Here it works in Logic 10.8.1 if you omit this step with the Aux: J.
  12. Ok, glad to hear you managed to lock the region down. Yeah, the SMPTE Lock options under the Piano Roll's functions menu is for SMPTE-locking MIDI events within the region, not the region itself 😉 J.
  13. Hi @mediacity, Thanks for the additional info. Well, if you also hear these crossfade clicks with PCM bounces, then we can exclude any MP3-specific issues. If it sounds OK in more than one place besides your iPad, then at least you can rest assured there isn't something wrong with those files. Unfortunately I can't really help you troubleshoot your OneDrive/iPad-specific issue. Just out of curiosity, which version of Logic and macOS are you running there? J.
  14. Ok, this is more specific then. Sounds like the issue is only present when listening to the resulting MP3 on OneDrive via your iPad? Then that narrows the issue down to that specific context. You have not to shown your MP3 settings when bouncing to MP3 from Logic (you need to select the MP3 line in "Destinations" for those to be visible when you take the screenshot). I still wonder if a PCM bounce (Wave format) gives you the same results when listening in the destination environment (OneDrive/your iPad)? J.
  15. Thank for the screenshot, Well, in your case the main difference is that by doing the above (instead of bouncing) won't even give you the option to choose MP3 as the resulting format: When bouncing, I'd suggest you set the Normalize setting to "Off" (or "Overload Protection Only"). Besides this, the main difference between bouncing and exporting is that when you bounce, the audio that ends up in your file is taken from the main stereo output channel, whereas with exporting the audio is taken from the output of a track (or tracks) channel strip output. J.
×
×
  • Create New...