Jump to content

1offby

Member
  • Posts

    15
  • Joined

  • Last visited

1offby's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. It's a bug and still in 10.2.1. Not great and hard to work around.
  2. Yes! I did Eric; thank you for that suggestion. I also got results when setting the Mixer to "track" view. As in all workarounds, I can get Smart Controls to stick inside a Track Stack in limited cases using a workaround, including yours, but not consistently. I *think* that an External Controller assigned to a Smart Control "Selected Track" Parameter should be persistent even when that track is in a Track Stack. While various workarounds may work in specific cases, the workaround functioning does not "fix" the bug. What I am hoping is that the Logic dev team will address the issue.
  3. First of all, thanks to Jordi and others on this thread. Second, note that the solutions posted are workarounds to what is a bug in Logic X that persists in 10.2. Finally, after testing several options I conclude that Smart Controls will lose external assignments in track stacks, even when workarounds are applied, in unpredictable ways. To clarify: 1) Jordi, in your workaround .gif are the Smart Controls for each Software Instrument Track assigned to different CC numbers? This does seem to work. 2) If Jordi's example has different CC numbers assigned to Smart Controls that is a use case different from the one I'm trying to implement 3) In my use case Software Instruments in Track Stacks aren't only running stock Logic plugins--They have custom Smart Controls assigned to MIDI Scripter parameters 4) I want a bunch of these tracks, each with a single Smart control, all to respond to the same CC number/external controller when that track is selected. This is what seems to fail pretty consistently when the track is in a Track Stack. 5) I think that makes the Controller Assignments>Expert View>Channel Strip>Software Instrument workaround ineffective, since that binds a particular Software Instrument parameter to the controller. TL;DR This is a bug worth fixing, even if there is a workaround. I also think the workaround is only somewhat effective.
  4. Hello all, Thanks for the proof-of-concept .gif Jordi. As I mess with this I am now able to add instruments with smart controls to a track stack no problem, no workaround needed. On my personal laptop, Late 2011 MacBook Pro OS X 10.10.5 I'll try this on one of the 2013 Mac Pro rigs at work ASAP. It was there that I had trouble with this, and made my post August 30. Strange. (I did trash the .cs file as I tried to troubleshoot on the Mac Pro FYI. Didn't help)
  5. This continues on Logic 10.2. It's worth fixing. I tried the fix proposed by Jordi, but that did not work. I can reproduce on two systems and see other forums posting this issue Late 2013 Mac Pro or Late 2011 MacBook Pro OS X 10.10.4 Logic 10.2 Steps: 1) New Logic Project 2) Create a few Software Instrument Tracks 3) Assign an external MIDI controller to one of the Smart Controls for one of the Instrument Tracks 4) Make sure the external MIDI controller is controlling the Smart Control as expected 5) add all Software Instrument Tracks to a Track Stack 6) external MIDI controller stops working as expected for the track with an external MIDI controller assigned to a Smart Control Just building a big template to take advantage of MIDI FX+Smart Controls. Lack of ability to use track stacks is a drag. MacBook Pro (15-inch Late 2011), OS X Yosemite (10.10.4)
  6. I put this precis on new MIDI fixes in 10.2 here: http://www.logicprohelp.com/forum/viewtopic.php?f=1&t=119073 Is that better than down deep in this thread for future reference?
  7. Following up on the Logic X 10.2 release notes, here are some specific improvements regarding MIDI: MIDI Click Environment Object: More accurate output, especially across tempo changes Software Instrument Track and External MIDI Track: Delay settings function as expected (Previous Logic versions had issues with negative delay settings and miscellaneous other issues) Project Settings>Synchronization>MIDI: New UI. MIDI Clock (also known as MIDI Realtime) messages are much more accurate across tempo changes Project Settings>Synchronization>MIDI: Sending MIDI Clock does not affect track delay settings (Previous Logic versions would sometimes ignore negative track Delay settings when sending MIDI Clock) Physical Input Environment Object: MIDI Port name includes Manufacturer ID Fixed Issue where Logic could send corrupt MIDI data through External MIDI Tracks when editing controllers in the Piano Roll
  8. Ski: OK To clarify, I am reporting the opposite result. Per my initial post: Ski: I may incorrectly understand community forums as an egalitarian location for sharing software issues etc rather than a spot where experts dispense their "time and benefit of experience" to a grateful public. I have found that solutions can come from any source, not just the experts. My main goal in making this posting was to report the behavior I can reproduce on two systems, see if anyone can replicate, and create an archive for future users should this behavior truly be an issue within Logic X. Ski: I understand that is your experience. One method for reporting such behavior involves finding a reproducible error and trying to understand its source. There are several things that can contribute to MIDI message timing issues and I simply have not been able to find a scenario where the IAC bus is the cause, or any less/more problematic than any MIDI bus. As I said: I really mean that! But anecdotal reports don't help me as a software user. I am still curious whether anyone has experienced a similar issue to the thread topic.
  9. Here's the test script for anyone interested: //Logic X Scripter plugin //Test Timing of Scripter Automation Lane //Try this with Logic X Preferences>Audio>General>Sample Accurate Automation set to "off" and "Volume, Pan, Sends, Plug-In Parameters" var TEST = [ [0, "One"], [64, "Two"], [127, "Three"], ]; //midi channel for ccOut var midiChannel = 1; //cc number for ccOut var ccNum = 21; //instrument name var instrument = "TEST"; //make string for menu var menuList = []; var i; for (i = 0; i < TEST.length; i += 1) { menuList[menuList.length] = TEST[i][1]; } //create the Logic X Scripter Control var PluginParameters = [ {name: instrument, type: "menu", valueStrings: menuList, numberOfSteps: TEST.length, defaultValue: 0 } ]; //send a cc number on parameter change just BEFORE a note event. Use an external application, such as MIDI Monitor, to trace event timing out of Logic function ParameterChanged(param, value) { 'use strict'; if (value >= 0) { var articChange = new ControlChange; articChange.number = ccNum; articChange.value = TEST[value][0]; articChange.channel = midiChannel; articChange.send(); } }
  10. Thanks Ski. True, Logic does often send a clump of MIDI messages at transport start/stop, but that is usually due to events within Logic not a Core MIDI issue. Based on my own experience, stories of inaccuracy due to any particular MIDI bus/Core MIDI are not true. As a matter of fact I have wasted a lot of time creating and maintaining alternatives to the IAC bus by relying on such reports. If ski or someone can create a MIDI event timing issue that is reproducible and due to a MIDI port or bus I'd like to see it. Sometimes a machine that has been on for several days needs a restart to flush out the MIDI system, but that's the only Core MIDI weirdness I have found. Particular to this post, MIDI events in general are being sent across the IAC bus with total accuracy. In this case it is only the events being triggered by a Smart Control controlling a MIDI FX Scripter plugin that are sent at unexpected times. The bus does not "know" what within Logic Pro X.app is sending a MIDI message; another reason it likely is not the IAC bus. I do mention the MIDI monitor application in my original post: I have been using that, as well as other resources, to check the order of MIDI events into/out from Logic. I posted here after testing the issue as carefully as I could, including trying alternate MIDI ports/busses. I was able to "fix" the issue by changing the Sample Accurate Automation setting; this makes me suspect it's something about the way MIDI events are prioritized on Software Instrument Tracks. I'd be very interested if there are issues with the JavaScript I used; but again, since changing the Sample Accurate Automation settings resolves the issue not sure how JavaScript could be the culprit. Ski,did you read my post or look at the Logic X Project I linked to help explain the issue? I'd be curious to hear from any Logic Pro X users who are interested in reproducing the behavior, have experienced something similar, or have further suggestions.
  11. Also posted at: https://discussions.apple.com/message/28703249#28703249 OS X 10.10.4 Logic 10.1.1 Late 2013 Mac Pro and Late 2011 Macbook Pro Issue: MIDI Scripter plugins on tracks set to the "External Instrument" plugin send MIDI data at the wrong time unless Preferences>Audio>General>Sample Accurate Automation "Volume, Pan, Sends & Plug-In Parameters" is selected. Question: Should MIDI Scripter events output using the External Instrument plugin require "Sample Accurate" Automation to have the same timing accuracy as other MIDI output? Steps: 1)Download and unzip the Logic X Project here: https://goo.gl/r1GG2g The Project has: MIDI CC data written for CC 1 Region Automation for a Smart Control assigned to a basic MIDI Script sending CC 21 Two note events Preceding each note event there are events written for CC 1 and the Smart Control 2) Using an external MIDI event detector such as MIDI Monitor notice the order of MIDI events, track the output of MIDI events from Logic (I used IAC Bus 1, Channel 1) 3) When Preferences>Audio>General>Sample Accurate Automation "Volume, Pan, Sends & Plug-In Parameters" is selected, events are output in the proper order 4) When Preferences>Audio>General>Sample Accurate Automation "Volume, Pan, Off is selected, MIDI events from the Smart Control Automation Lane (CC 21) are sent early Expected result: MIDI event timing is accurate without needing to enable Sample Accurate Automation Actual Result: MIDI event timing is inaccurate unless Sample Accurate Automation is enabled In my case this means enabling an audio related preference that uses more CPU to ensure MIDI event timing, which seems illogical My main goal in this case is to use the MIDI Scripter. I'd prefer to use an External MIDI Track, but External MIDI Tracks do not support the Scripter Plugin. As I try to use Software Instrument Tracks using the External Instrument Plugin I notice how MIDI event output seems to be tangled in the audio thread/stack/whatever. TL;DR Anyone else?
  12. After further investigation, referring to the numbers at the top of the post: 1) Yes. Make sure the automation setting for the track is set to "region" (as of Logic 10.1.1) https://ask.audio/articles/logic-pro-x-track-or-region-based-automation 2) Yes. The way I did this was to: a) make a MIDI FX Scripter for a software instrument track b) assign a smart control to the parameter I want to edit in the piano roll c) assign an external controller to control that smart control (not the MIDI FX Scripter parameter--the smart control) d) write some automation to the region using the external controller e) open the Piano Roll, open the MIDI draw pane. In the Controller menu select "autodefine" or use the shortcut (D for me) f) In my case, I see the MIDI FX parameters in the MIDI Draw area 3) Yes, see my post Jun 30
  13. I can reproduce this behavior under Logic 10.10.1 I posted it to the Apple discussion thread: https://discussions.apple.com/thread/7158403 cello, when you write: What main bus do you mean?
  14. Thanks ski, hello forum, Since posting this I have figured out how to connect Smart Controls to MIDI FX parameters (Logic Pro X Manual page 1,351). I think the answer to (2) is no.....
  15. Hello, I am curious whether these are features in Logic Pro X 10.1.1 for MIDI FX Plugins (especially Scripter plugins): 1) is it possible for parameters in MIDI FX Plugins to apply to MIDI Regions rather than as Track Automation? 2) Can MIDI FX Plugin Parameters be edited in the Piano Roll rather than in the Track Automation area? 3) Can Smart Controls be created/edited/assigned to MIDI FX parameters? Maybe this is all possible, I can't find how to set it up...thank you for any guidance!
×
×
  • Create New...