Jump to content

minilq

Member
  • Posts

    24
  • Joined

  • Last visited

minilq's Achievements

Newbie

Newbie (1/14)

0

Reputation

1

Community Answers

  1. You do have to be careful to create a track per CC or you risk erasing previously recorded data on other CCs
  2. Yep, the new track with same instruments is a workaround.
  3. The crucial part of my question was how to record “automation” (in this case CC info) independently of the notes. Apparently, track parameters like volume, pan, etc are special cased, and treating CC like track automation is not possible.
  4. Yes, I'm aware that I could manually enter information, but it seems like a no-brainer that Logic should be able to transmit information it already knows.
  5. MIDI Clock lets you know how many 16th notes into a sequence you are, but that's not enough information for a receiving device to (for example) calculate bar numbers for display. That's why the System Realtime Notation Information messages exist.
  6. I’m not sure I understand your answer. You seem to be saying that since there is a way to enter sysex manually, there is no way for Logic to generate them on playback. Do I have that right?
  7. Well, yes, you could, I suppose, manually enter them, but I think the purpose of these messages is that a sequencer automatically transmits them to allow other devices to follow, much like MTC and timing clock (0xF8).
  8. The MIDI Spec specifies a set of System Realtime messages that can be used to transmit the current time signature and bar number. (See https://www.midi.org/specifications-old/item/table-4-universal-system-exclusive-messages, look for "Notation Information") I cannot for the life of me figure out how to cajole Logic into transmitting these messages. Can anyone help?
  9. Also, after a half hour or so of use, the interface often starts to drop samples (sounds like glitching). Unplugging it then plugging it back in fixes it. For awhile.
  10. Avoid Zoom interfaces if you make use of MIDI automation. See my post at: /viewtopic.php?f=10&t=132136&p=691777#p691777.
  11. No, whether or not MicEfx is running, the Zoom interfaces always send out sysex info, which makes working with MIDI automation impossible.
  12. Avoid Zoom interfaces if make use of MIDI automation. See my post at: /viewtopic.php?f=10&t=132136&p=691777#p691777.
  13. I would avoid any Zoom audio interface if you're using Logic Pro X. The way Zoom's interfaces communicates with their bundled MixEfx software makes working with MIDI automation or step input via MIDI impossible, whether you make use of MicEfx or not. Zoom's "workaround" is to unplug their interface. This has been a problem for years and Zoom seems not to care. Details are here:
  14. First things first. Please run Disk Utility and see whether your boot disk or your external disk are formatted to be case-sensitive.
  15. Historically on the Mac, file systems are case-insensitive, so “foo.aif” and “Foo.aif” would in fact refer to the same file. It is possible to format a drive to be case-sensitive, but it’s generally a bad idea. You can use Disk Utility to see if your disks are case-sensitive (you’ll see “case-sensitive” if they are)
×
×
  • Create New...