#81

@tehn – gah. i feel like a dummy, but i have no idea how to get the max standalone working with aalto.

edit: it is working in ableton. so i guess my real question is, should aalto work in max standalone?

everything’s responsive on my 128. i choose “plugin” as the output in meadowphysics, aalto as the plugin. things are cascading on the monome, but no audio. the output visual on aalto isn’t showing anything, so i know it’s not just setting an audio driver.

any ideas?

#82

screenshot? is the output fader turned up? the audio driver also might still be incorrect-- double check it?

#83

smh. it was the driver. thanks @tehn. damn, there’s a lot of moving parts to this life. love it, though. thanks for the quick check.

1 Like
#84

i love the new mp but it’s hard to use for mono-bright monomes…

#85

image.jpeg2592×1936 2.64 MB

Anybody has any idea as to why this would be the case?
MP running the 2.0 version
TT running the 1.1 version

#86

Works on my side
MP 2.0 version
TT 1.1 version

#87

also working for me-- that’s somewhat confusing. maybe try reflashing-- are you seeing other 1.1 features working?

#88

Yes. I am able to trigger scropts with commands, or from keyboard etc.
So def 1.1 TT features working.
I have II scripts working fine with WW and ES at the moment, but not MP.

#89

none of the MP scripts work?

#90

The old II MP commands are “accepted” by TT, but they do not have affect on the v2.0 MP behavior.

#91

understood. i need to test and check the code clearly. but still confounded that MP.STOP isn’t accepted.

#92

confirming that MP.STOP and all the other mp II commands work with my setup. are you confident the II cable is seated? i know that ribbon is a major pain.

#93

Yeah, that was the first thing i checked. I replugged it etc.

Would a problem with a cable cause TT to say that the MP.STOP syntax was wrong??

#94

definitely not. how long ago did you flash the firmware? i’m wondering if somehow the wrong version is on there?

#95

TT firmware? hmmm not sure. i am pretty sure i downloaded it as soon as it was up. just did not have that much time to really explore until recently.

the TT firmware i have is tt-1.1 beta with the hex file dated 11/17/15

#96

i’d suggest getting the newest-- out of beta. the 1.11 has a new euclidean rhythm op contributed by sam

#97

will update the firmware to the newest (looking forward to trying the Euclidian patterns embedded in the code!)
hopefully my problem is the simple case of the “beta” firmware issue.

#98

i do expect that’s the problem. i added a bunch in between beta and release.

#99

OK, just got around to updates.

I installed the TT 1.11 which seems to work fine, and indeed does NOT reject the MP.STOP x command like it did with the beta version.
HOWEVER it still does not affect MP. And neither do any of the II MP commands.
(while the II commands control the WW and ES just fine.)

As a test I have installed the previous version of MP, and TT II commands work fine with the previous version of MP (which perhaps rules out the faulty ribbon connection as a cause of the problem).

Re-installing the MPv.2 makes the II TT commands stop working with MP.

#100

i’ll reflash my mp2 and recheck.

1 Like