jaromy / ableton-live-command8

Remote MIDI Script for using Command|8 control surface in Ableton Live
0 stars 0 forks source link

Command 8 and Ableton aren't talking to each other #2

Open jaromy opened 4 years ago

jaromy commented 4 years ago

Hey Jaromy,

Hope you're good!

I'm having a bit of trouble getting this working - wondering if you could help me out?

I have saved the Command8 file in the Ableton folder:

Screen Shot 2020-04-29 at 4 31 32 PM

And I believe I've managed to load the SysEx file into the Command 8 (I used SysEx Librarian as I couldn't figure out how to do it any other way).

It is displaying "Ableton Live" as a setting on the Command 8 and when selected, it moves the faders to these levels:

IMG_2447

IMG_2448

In Ableton, I have selected the following presets but I'm not getting any response either way - the Command 8 and Ableton aren't talking to eachother:

Screen Shot 2020-04-29 at 4 35 06 PM

I appreciate this was a long time ago for you, but I'm just reaching out on the off chance you can see something glaringly obvious that I've done wrong, or could give me some pointers.

Much appreciated!

James

Originally posted by @jsdgibb in https://github.com/jaromy/ableton-live-command8/issues/1#issuecomment-620984241

jaromy commented 4 years ago

Hi James,

Everything seems right so far, nothing glaringly obvious from the steps and screenshots you've sent. At this point, I'd say do a quick sanity check - verify that you are getting MIDI data from the Command8 to your computer in general.

On the Command8, adjust the fader or twist and encoder or button, etc, and from within Live, you should see the MIDI activity indicator blink. If not, then you'll have to dig further. I like to use MIDI Monitor (on Mac), or MIDI OX (Win). That will help troubleshoot basic connection/driver issues and make sure that you have all of your MIDI connections set up correctly.

Cheers, Jaromy

ghost commented 4 years ago

Hey Jaromy,

Thanks for the reply!

The Ableton MIDI Track Indicator In is blinking when I move the faders etc. and MIDI Monitor is tracking everything too:

[image: Screen Shot 2020-05-04 at 10.51.30 AM.png]

Should this then automatically have control over the faders in Ableton on start up?

I feel like a link is missing in telling Ableton to use Command8 somehow.

Any ideas?

Thanks heaps, James

On Sat, May 2, 2020 at 6:53 AM Jaromy notifications@github.com wrote:

Hi James,

Everything seems right so far, nothing glaringly obvious from the steps and screenshots you've sent. At this point, I'd say do a quick sanity check

  • verify that you are getting MIDI data from the Command8 to your computer in general.

On the Command8, adjust the fader or twist and encoder or button, etc, and from within Live, you should see the MIDI activity indicator blink. If not, then you'll have to dig further. I like to use MIDI Monitor (on Mac), or MIDI OX (Win). That will help troubleshoot basic connection/driver issues and make sure that you have all of your MIDI connections set up correctly.

Cheers, Jaromy

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jaromy/ableton-live-command8/issues/2#issuecomment-622515309, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFKQH57RDOHCRC4RIBKRFZDRPMLA7ANCNFSM4MXJFV4Q .

jaromy commented 4 years ago

Hi James,

Well, that is a good sign that the Ableton MIDI indicator is blinking. Can you attach the screen shot again? I'm not seeing the image, just the placeholder text.

Yes, Ableton should just automatically link to the Command8. I noticed that you have "sync" enabled for Command8 in the MIDI preferences window. I would disable that, as there is no MIDI sync messaging exchanged between Ableton and Command8. I don't believe this is the root cause of your issue, but it can't hurt to go ahead an disable this anyway.

Cheers, Jaromy

ReeceKetley commented 4 years ago

I am also having this issue i loaded the preset with Midi-OX put it in standalone mode and i can see midi input but only when i use the faders and encoders but it does nothing.

ReeceKetley commented 4 years ago

I'm able to midi map the device and even get the faders to respond but the play buttons along with leds and most of the other buttons don't work.

jaromy commented 4 years ago

Hey Reece, sorry you are having the same issue. Curious - what version of Ableton are you running? I'm on version 8, so I'm wondering if maybe something has changed in the Ableton code for remote scripts.

On Jul 16, 2020, at 1:40 PM, Reece Ketley notifications@github.com wrote:

I'm able to midi map the device and even get the faders to respond but the play buttons along with leds and most of the other buttons don't work.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jaromy/ableton-live-command8/issues/2#issuecomment-659660027, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEBZ3WQTJMBIE3IJQFOOKXLR35QUZANCNFSM4MXJFV4Q.

jaromy commented 4 years ago

Also - unfortunately the none of the transport buttons will work (play, FF, stop etc). This is by design, I couldn't find a way to map/assign these in the remote scripts. You might be able to MIDI map them though? I can't remember if I've tried this, it's been a while since I've used my Command|8 with Ableton.

LED's also will not work, again by design.

The following buttons are supposed to work: select, solo, mute for each channel. Also the top row of buttons on the Command|8 - "EQ, Dynamics, Insert, etc".

Cheers, Jaromy

On Jul 20, 2020, at 1:54 PM, code@jaromy.net wrote:

Hey Reece, sorry you are having the same issue. Curious - what version of Ableton are you running? I'm on version 8, so I'm wondering if maybe something has changed in the Ableton code for remote scripts.

On Jul 16, 2020, at 1:40 PM, Reece Ketley <notifications@github.com mailto:notifications@github.com> wrote:

I'm able to midi map the device and even get the faders to respond but the play buttons along with leds and most of the other buttons don't work.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jaromy/ableton-live-command8/issues/2#issuecomment-659660027, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEBZ3WQTJMBIE3IJQFOOKXLR35QUZANCNFSM4MXJFV4Q.

ReeceKetley commented 4 years ago

I tried 8.22, 9.5 and 11.7 still not working. However i've decided to reverse engineer the Command|8 i've been able to make every button./encoder/fader work correctly. I've also been able to make the screen display custom content i'm currently working on LED's and motorized faders.

i've had to create a dameon in C# to do all this along with a new virtual midi device but i'm going to be releasing all the source code once complete, regardless you midi remote scripts are good starting block for as i still need to write those.

jaromy commented 4 years ago

Cool that you are able to reverse engineer the Command|8 and get the screen working (and hopefully also LEDs). That would be a nice addition.

On Jul 20, 2020, at 2:35 PM, Reece Ketley notifications@github.com wrote:

I tried 8.22, 9.5 and 11.7 still not working. However i've decided to reverse engineer the Command|8 i've been able to make every button./encoder/fader work correctly. I've also been able to make the screen display custom content i'm currently working on LED's and motorized faders.

i've had to create a dameon in C# to do all this along with a new virtual midi device but i'm going to be releasing all the source code once complete, regardless you midi remote scripts are good starting block for as i still need to write those.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jaromy/ableton-live-command8/issues/2#issuecomment-661345852, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEBZ3WU4ES6XGN2S63XI7I3R4S2CFANCNFSM4MXJFV4Q.