MIDI Error

[Morrish]

Hey all,
I have been trying for hours to run Griid on my new Ipad. I followed the set up-guide to the letter.When I launch griid on my Ipad and click auto connect I get the following error message.

"MIDI Error

Communication between Griid and Ableton Live could not be established.

Check the MIDI settings in Ableton Live and Griid Connector"

I'm running windows 7 64-bit.


Thanks in advance for the help.

[nick_liine]

Hey all,
I have been trying for hours to run Griid on my new Ipad. I followed the set up-guide to the letter.When I launch griid on my Ipad and click auto connect I get the following error message.

"MIDI Error

Communication between Griid and Ableton Live could not be established.

Check the MIDI settings in Ableton Live and Griid Connector"

I'm running windows 7 64-bit.

Thanks in advance for the help.

Which version of Ableton Live are you running?

Please make sure you have the following selecting in Ableton / Preferences / MIDI Sync:
Control Surface: Griid
Input: 2- Griid
Output: Griid

If you're still having trouble, please get in touch at support@griid.net

Thanks,
Nick

[alansax]

I have the same problem.

[marino_liine]

Hi alansax,

Please get in touch with us at support@liine.net

Cheers,
Marino.

[sasha_b]

Same problem here..

[sawatzki]

Hi there,

I seem to have the same problem - Griid Pro on my phone connects to the network, finds Griid Connector but won't talk to live, resulting in the infamous "MIDI Error".
At the same time, Kapture Pad connects with no problems to Kapture Pad Connector and Live.

I'm on a Macbook Pro 3.06 GHz Core 2 Duo, running OS X 10.6.5. Live is at 8.2.6, Griid Connector 1.13.3
My phone is an iPhone 4 with iOS 5.0.1 [jb with redsn0w].

I had sent an email to Griid support, but they were of NO HELP, because my phone is jailbroken... [many power-user iphones are!]

So I had to do some research on my own.

These are my findings:

1.) In live preferences -> midi ->, when I set "Griid" as a control surface, it does not automatically set the in/out ports to "Griid". I had to choose them manually from the corresponding drop-down menus.
This made me wonder, because with Kapture Pad, the control surface in/out ports are set to "Kapture Pad" AUTOMATICALLY when I set Kapture Pad as control surface.

2.) I started "MIDI Monitor", a free app to monitor all MIDI that's happening on your computer.
Griid Connect sends out a sysex string "F0 00 00 07" three times, and gets no answer from live.

Code: Select all

From Griid: F0 00 00 F7
From Griid: F0 00 00 F7
From Griid: F0 00 00 F7

When I connect Kapture Pad on my phone to Kapture Pad Connector and Live, the sysex communication is the following:

Code: Select all

From Kapture Pad: F0 00 00 F7
To Kapture Pad: F0 00 00 00 00 05 00 02  00 00 00 F7
[...more sysex communication]

...then, other data is beeing transfered by sysex.

So I tried to trick Griid Pro to think it's connected to Live by sending out the sysex message from Kapture Pad Connector - and: voila, Griid Pro thinks it has talked to Live and builds its User Interface.
Of course, it stays at "Buffering 0%", because live is not actually talking to it - it keeps sending out sysex requests for the live set info.

So what do these findings show?
The problem clearly has nothing to do with the iPhone being jailbroken - it's the communication between Live and Grid Connector that doesn't seem to work!

Maybe some conflicting midi drivers? I have a lot of controllers - virtual and physical. I'm also running Automap Pro - a hell of a messy system... :-/

Any help / hints are gladly appreciated!!w


P.S.:
When in Griid Connector or Kapture Pad Connector, I had a look at the Max window [cmd+m]
This has probably nothing to do with the problem itself - but anyway:
Both apps state the following errors & warnings:

Code: Select all

No midi driver folder or default driver // <-- ERROR - red background!
[...]
method bringtofront called on invalid object // <-- WARNING - yellow background

[alyssaly]

I am also in bad luck!Mine has the same problem~****!