<
danielphegarty@googlemail.com> wrote:
> Hey Per,
> Just wanted to give you an update on the issue and see if you had any
> insight.
> We ran the set a couple of times until one of the errors showed up, then
> reviewed the issue using MidiMonitor. On the whole i always use the SUS
> commands for the EDP, as it allows us be to be really precise with loop
> lengths. The error occurred when sending 4 'D3's (D3 being a 'general
> reset') out simultaneously to the 4 EDPS. I have these programmed as just 1
> frame long, and ordinarily it works fine. In this case I could see that only
> the note-offs had fired, and the note-ons had been missed. I looped the
> track 20 or 30 times but could not repeat the error. But at our next
> rehearsal the same issue recurred!
> I can't imagine why this would be happening intermittently. It's not only
> D3's, once in a while a mute or a record will miss. It just seems that Logic
> is slightly unstable. What is interesting is this tends to only happen when
> we are actually playing, at which point we are playing soft-synths
> simultaneously to the midi tracks controlling the EDPs. I'm using a decent
> spec Macbook Pro, but perhaps it's just too much for the system to handle?
> Very frustrating! Thanks again for your help.
> Daniel
>
> 2009/5/15 Daniel Hegarty <
danielphegarty@googlemail.com>
>>
>> I have. I ran MidiMonitor last night for the full length of the 30 minute
>> track, and it all looked very healthy, no glitches.
>> However, we also run 6 or 7 softsynths in the logic file which we play
>> live. We have two midi keyboards inputting and playing these instruments, at
>> different points, but also occasionally simultaneously. On the most part it
>> works fine, the trouble is we're normally playing when the glitches happen
>> so it's difficult to keep an eye on the MidiMonitor. Though, now I think
>> about it, we could run MidiMonitor while we're playing and then review the
>> log afterwards. Good idea!
>> I'll let you know the results.
>> Thanks
>> Daniel
>>
>> 2009/5/15 Per Boysen <
perboysen@gmail.com>
>>>
>>> On Fri, May 15, 2009 at 1:01 PM, Daniel Hegarty
>>> <
danielphegarty@googlemail.com> wrote:
>>> > It just seems like once in a while, logic decides not to bother sending
>>> > the
>>> > signals. Could that be CPU related do you think? I am running quite a
>>> > lot
>>> > off just a macbook pro.
>>>
>>> Well, that's indeed odd. But there has to be an explanation that we
>>> yet don't know about. Definitely not CPU related, because Logic would
>>> pop up a warning message before that happens. Are you sure it simply
>>> stops sending out the MIDI that is spinning in the sequencer? Have you
>>> monitored the MIDI Out port? That would be a good way to start
>>> trouble-shooting.
>>>
>>> Per
>>>
>>
>
>