hey tom,

i think we are going to need some help from either the community or
MOTU on this one.

i know of no other coremidi api calls i could make that would affect
this situation. i even tracked down doug wyatt at namm last year to
ask him, and he didn't have any ideas i could follow up on.

i did ask a question here before to find out whether anyone else had
non-working interfaces, but didn't get any responses. i conclude that
either the timepiece is the only non-working one, or that upon
finding out that their interface didn't work, people just deleted the
program and went about their business!

tom could you perhaps ask a question at MOTU about this? maybe if you
include enough technical jargon you might get past a support-bot to
someone who knows what's up.

thanks man
j




>I think I've mentioned this before, but I'll re-iterate since time may be
>available for someone to look into it now...
>
>I use an MOTU Miditimepiece AV.
>
>Turn it on, fire up mrp, a see lights blink like I expect while coremidi
>comes to life. After that, nothing.
>
>Now the fun part. If I fire up another working Midi app such as Clockworks
>which is MOTU's midi patch manager for the timepiece, mrp will magically
>start working.
>
>A while back you sent me a couple test programs which just init'd midi and
>sent some data, just dug one out and it doesnt work. I even updated the
>MOTU drivers to the latest and greatest version.
>
>Figured I'd mention...