Jump to content

spride

Member
  • Posts

    44
  • Joined

  • Last visited

Personal Information

Recent Profile Visitors

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

spride's Achievements

  1. THANK YOU! That is an area I almost never use or look at and of course (as you imply) ⌥+↓ also transposes by a semitone there. You're right, I am forever mis-hitting Tab to go to the bottom window and not noticing, and I didn't realize that that key combo had an effect in the upper pane too. A thousand thanks, David.
  2. Thank you for taking the time to check this out, David. I attach a sample project using Classical Piano. The issue I am seeing is actually more subtle than I thought. I am pretty sure I first encountered it when using the menus to transpose, because I hadn't learned the keyboard shortcut yet. But when creating the sample project to illustrate the potential bug I find: If the keyboard shortcut is used to make the transposition, the notes are shifted a semitone too far in this case (G# not A) If the Functions menu item is used, then the pattern is transposed as expected. This is replicated using my Intel iMac (Retina 5K, 27-inch, 2017). Logic is 10.7.6 I also attach a screen shot of the pattern as transposed in #1 above showing that the notes are displayed in the correct transposition in the Pattern Editor but (I hope…) play back transposed to a root of G#. 2022-12-31 Pattern Region Transpose Bug.logicx.zip
  3. In "debugging" one of my projects I discovered that the Transpose function in pattern regions does not work correctly. Specifically, a pattern region that is first duplicated, then transposed, will appear to have the correctly transposed pitch values but when played back, the incorrect notes sound and the incorrect note is clearly visible being played on the on-screen keyboard of such plugins as have them. Furthermore, if the transposed pattern region is converted to a MIDI region the incorrect MIDI pitch values are shown. Steps to reproduce Open Logic and create a new blank Project Create an empty track and assign an Instrument whose plugin window has a visible keyboard Create an empty pattern region on the track Populate the pattern region with notes. In this case we will choose a repeated Middle C Play the pattern region and observe correct behavior Duplicate the pattern region Use the pattern region's menu functions (Functions > Transpose -1 Semitone) or keyboard equivalent (Option + down arrow) to transpose the pattern down three semitones, ostensibly to A Observe that the former middle C values are now A below Middle C and monitor as such in the pattern editor (if you click to unset and reset them, A sounds) Play the region. Observe that the note played is G# below Middle C (by ear or reference to another instrument). Open the Plugin window for the instrument and play the pattern. Observe the instrument's G# key being animated Select both pattern regions and choose Convert > Convert to MIDI region Observe that the transposed region's notes have a MIDI pitch value of G# on the MIDI region's piano roll view I have tested this on both of my Logic instances (MBP M1Pro, iMac Retina 5K) and the behavior is the same. I have reported this, inasmuch as one is able, to Apple via their Feedback. I would be very grateful if anyone else has the patience to repeat these tests and tell me what you see? Simon
  4. It's a popular framework in service management and related disciplines for determining root causes of problems when there's no obvious one. It asks questions like: Where is it happening? Where is it not happening? Where could it be happening but isn't? When is it happening? When is it not happening? When could it be happening but isn't? etc The idea is to force you to look at all aspects of the problem rather than yielding to your biases and habits.
  5. Yes. I will continue to observe and see if there is a unique set of circumstances under which it occurs. Luckily I am trained in Kepner-Tregoe problem analysis :-)
  6. Curiouser and curiouser. I'll try to make a video to show the effect.
  7. That's weird. It's very consistent here. I am on a M1Pro running Monterey. Is that in any way similar to your platform?
  8. So I have some more information which may be useful. This seems to occur when you have the plugin window on a different display than Logic. Steps to reproduce: Open the Plugin window Move it to a different display from the one where Logic is running Try to enter text and the keystrokes go to Logic, not the plugin window, despite the fact that the plugin window has the white focus outline Steps to resolve: Move the plugin window back to the same display as Logic Close the plugin window Open the plugin window Text entry behaves as normal Can anyone with two displays or more confirm what I'm seeing?
  9. Thanks, it is possible. If it happens again I will check for the focus line.
  10. Hi Des99 - see my update before I saw your reply, which says that a reboot fixed it (for how long?) but: Cherry Audio MiniMode Arturia SEM-V 2 Arturia Analog Lab 5 Arturia SQ80 V Arturia Jup-8 V 4
  11. Well, I don't know why I didn't try this earlier, given I work in IT - I rebooted and now it works properly. Of course. Gonna leave this here in case anyone else has the same issue.
  12. In Logic 10.7.3 (and maybe below but I've only been using Ableton for the last year or so), if I have a plugin window open and then try to perform keyboard actions within it, for example, searching for a preset using the plugin's search feature, or naming a new preset as I save it, the keystrokes are not sent to the plugin window but to Logic itself, thereby triggering unwanted actions such as play/stop and even deleting regions. I've checked a number of plugins from different mainstream manufacturers (Arturia, Cherry Audio etc) and they all behave similarly. Is anyone else seeing this behavior? MacBook Pro M1Pro / macOS 12.3.1 / 32GB RAM / Logic 10.7.3 / all plugins up to date.
  13. I have not been able to test as my studio machine has a persistent hardware issue that Apple is seemingly unable to diagnose.
×
×
  • Create New...