Jump to content

thomaskyhn

Member
  • Posts

    20
  • Joined

  • Last visited

thomaskyhn's Achievements

Newbie

Newbie (1/14)

0

Reputation

1

Community Answers

  1. Yes, the developer seems to have disappeared. I've used it a lot earlier without any problems; I'm not sure what has happened. Perhaps it's become incompatible with Logic; or Logic has a bug.
  2. That would be a great help. Here's an example – a project with two tracks, each with an instance of the MIDI FX Freeze plugin and an instance of EXS24. When I attempt to capture the region in the two tracks simultaneously, the problem occurs. (This setup is only meant to reproduce the problem; in other scenarios there would, of course, be no point in capturing MIDI data similar to what you already have.) I've included the MIDI FX Freeze plugin in the zip file. Steps to reproduce: * open both MIDI FX Freeze plugins * click the big circular button, so that (part of) it turns red (in order to prepare it for capturing MIDI data) * play back the regions in the project from bar 1 to 20 * drag the captured MIDI files from MIDI FX Freeze onto any track to see the result https://www.dropbox.com/s/z2qn0dukblillyv/Test.logicx.zip?dl=0
  3. Thanks for the suggestion. Unfortunately that didn't solve the problem.
  4. Addition: There are no other MIDI effect plugins in this project, and there's only this one track.
  5. Thanks for your reply. Do you know why this happens? As a test, I've captured this MIDI region using MIDI FX Freeze: Here's the result: As you can see, the notes stop before the end of the recording.
  6. Has anyone else had problems when capturing MIDI data (using the MIDI FX Freeze plugin or the IAC Driver/external instrument method)? I get errors – excessively long notes – almost every time, and I can't figure out what's causing the problem. It happens even in projects that contain no automation and no other MIDI effect plugins than MIDI FX Freeze. I've tried deleting Logic's plist file, audio units cache, and starting from scratch with an empty project, but the problem persists. I've looked for other ways of capturing MIDI data, but haven't been able to find any. If anyone knows of one, I'd be happy to know about it. (Logic Pro X 10.4.4 on macOS 10.14.4.)
  7. Got the right answer in the Apple Discussions pages: Only the Modifier and Modulator plugins will do this.
  8. In the release notes for Logic Pro X 10.3, it says "MIDI plug-ins can now remote control any automatable plug-in parameter on the same channel strip". I've looked through the manuals (latest updates – User Guide, Effects and Instruments) but I can't find any info on how to do this. I'm aware that the Modulator plugin has a target setting that you can use for this purpose, but in the release notes it sounds like it's all MIDI plugins you can use for automating the parameters of other plugins. Can anyone here point me in the right direction?
  9. Is there a simple way to modify this script in order to get a random note length effect?
  10. I tried this, but it doesn't work as intended: function HandleMIDI(event) { event.trace(); if (event instanceof NoteOn) { event.sendAfterMilliseconds(randomDelay(0, delayTime)); } else if (event instanceof NoteOff ) { event.sendAfterMilliseconds(randomDelay(0, delayTime)); } } I assume that rather than apply the same random delay to both events, it randomizes them individually.
×
×
  • Create New...