Dewdman42

I don’t have the link handy but I’m sure someone else will provide. In the meantime checkout expert sleepers latency fixer free plugin

And track delay moved the notes when you reopened the project? If so that’s a bug please report it

with the new feature of using midifx pre-record, its possible to do all manner of things like that using midifx plugins, including scripter...as you record it. the sky is the limit. You could, for example, use the midifx that can create LFO cycles, etc..and if neccessarily use a scripter script to convert some CC value into current velocity..to end up with some kind of cycling velocity like what you see in your screen shot. That is just one simple example, the sky is really the limit. You could combine with an arp in some way perhaps... you could use the step sequencer that is built into LogicPro and convert some stepped midi message there into velocity values to use, etc... there are all kinds of ways to manipulate velocity besides purely random.

interesting bug. as a work around, use track delay instead of region. Another thing you can do is use the expert sleepers latency fixer plugin to adjust for legato latency.

thanks. Strange that they added that when IAC is already there. Not sure why they would bother with that, but thanks for the heads up about it

I don't understand what you're saying... but anyway I'll look for it next time I am near my mac

Interesting. And then the midi input ignores it?

it can be done. won't be simple.

Yes it could be done. But... Scripter does not have the ability to do lookahead. sort of. it can't move notes earlier in time, only later in time.... However what you can do is delay everything by a certain look ahead amount, and then you move some notes later then others, which gives you a way to basically move notes earlier, relatively speaking. Then the whole track needs a negative offset to make up for the lookahead.

what is the recently added feature you are talking about, I have not heard about that? honestly MidiFXFreeze is the best way and I would not call it "out dated". But yea if you don't care about sample accuracy, ,then IAC loopback works fine, and honestly, most people won't notice as the delay is probably something like within 1ms or less depending on your buffer size.

not entirely sure i understand your question, but the midi time clock is always running in Mainstage and LogicPro, even when the transport is stopped. But you can use the GetTimingInfo function to obtain the transport info and then look at whether the transport is actually still playing or not. Based on that you can have scripter do things (or not).

Channelizer simply uses the articulationID to offset the midi channel. Please read the channelizer wiki page at gitlab

Th output tab only affects key switches, which channel they will be sent on

The main thing is you want to make sure there is NO actual channelizing happening in the switches tab. I can't remember if its even there or not. I think I vaguely recall that LogicPro artset forces midi events to be recorded with the articulation id and the channel assignment as assigned in the middle tab. Which is a flaw IMHO. Also note that generally you don't want cc events to be recorded with articulationID either! And if yo are recording both notes and CC1 events in one recording pass, then both the CC and note events will be encoded with articulation ID. That can be problematic if and when you move notes around or change the articulation of notes, then you have to find all the CC events lining up with that note and change their articulationID also! So that can be very problematic. Work around for that, is to use a script of course, set in pre-record mode, that strips articulationID off of CC events. But in any case, if you just use channelizer instead, then it won't matter if the CC's get encoded with articulationID or not during playback, channelizer only looks at note's to detect articulationID and channelizes those notes accordingly, and any CC's are channelizing along with wherever notes are currently sustaining. It will just work as desired. You only need the artset in order to assign a friendly name to each articulationID and also so that during record you can use some key switches to change articulations on the fly while playing the part in.

There are different ways to look at it. In some ways it can be more complicated to try to use the powers of articulation sets and only massage the results minimally with scripter. As opposed to doing all or most of the heavy lifting with scripter. Articulation sets have some peculiar behavior in some cases that honestly i feel in some cases Apple did it wrong. With scripter you have complete control to make it do exactly what you want, but if you are trying to let artset do some of it and only massage the results then it can sometimes get tricky. so I prefer to keep articulation sets as minimal as possible in fact sometimes doing absolutely nothing other then assign articulation ids to notes during record and having names associated with each articulation id. After that I prefer to use scripter to handle all key switching, channelizing, etc based on the assigned id’s. I have absolute power and control that way. I think the psychology you refer to is about trust and faith in Apple and Logic Pro vs trusting some “script” off the internet to work reliably. But scripter is very reliable if scripted well. But that is the psychology. I predict that when I have a juce version coded in c++ and not free, there will be more trust and confidence in that compared to scripter also. There is no rational reason for that but psychology is not rational. im away from Mac this week so I can’t look at the art set editor to remember if the input tab has something about midi channel?