#39

sorry to be so dramatic, it was just really crazy. no idea what i did. but 100% connected to my lack of understanding about the world.

i am sorry and remain so grateful for your work, presence and guidance.

i did check that monolase version and it works, seems to sense my grid. but still no actual interaction with the grid. i did delete those zeroconf externals you first sent as i was afraid of bogeyman. so that may be the prob there.

but my absolute necessity audio side is working, so i am no longer feeling ill. would still love to get ml working, but i amy have just learned my lesson…

1 Like
#40

Can you stick a print object here and see what it spits out when you press buttons on the grid?

Screen Shot 2017-01-10 at 23.40.11.png750×462 52.8 KB

Also, it could be that this era of serialosc doesn’t take messages formatted that way. Can you go to the inspector of serialosc (as in press Command+i with the grey serialosc object selected) and then add “coco” to the arguments area:

Screen Shot 2017-01-10 at 23.42.04.png794×306 17.7 KB

Then save and restart Max/Monolase.

2 Likes
#41

scarry…
and, if you got the PV working,
cocolase in there is the same thing :slight_smile:

monolase user manual
https://raw.githubusercontent.com/monome-community/collected/master/monolase/Monolase%20-%20Instructions.pdf6

image.png640×1136 84 KB
image.png640×1136 72.2 KB
image.png640×1136 82.4 KB

#42

i will try that when i’m back up in there and post results

#43

-if monolase sees your grid in serialosc,
then you’re on!

image.jpeg2580×1935 2.03 MB

select grid, click connect
click adc, select 'file
click open, choose file
click stop, changes to start
click dsp off, changes to dsp on

click cocolase button left and right
(or bottom row grid buttons
to turn cocolase on)

if you need to, click configure dsp button to select routings(soundflower…)
my grid’s got no lights on the top row, but the buttons still toggle
plz let us hear what you create :slight_smile:

#44

oh looking like bingo on the arguments coco

love love

test test

back soon

rodrigo, you are a powerhouse. big bad knowledge exploding left right front center below around beyond and through

most serious deep gratitude

:pray:

2 Likes
#45

lol, happy to help!

Glad that worked in the end.

That was actually fun trying to troubleshoot something like that. Like speaking to someone on the phone while they go through a time machine…

1 Like
#46

ok, yeah now here everything is working.

my stream of consciousness:
i would like to figure out how to migrate my 3 favorite max apps (choc grinder, monolase, and crazy arbitrary sample cut/grid assigment) into max4live in order to have native fluency within one environment rather than the need for routing with soundflower.

i want to try to figure out how to map grid control (with tilt) to chocolate grinder control.

and i would love to figure out to map tilt to some parameter in the samplecut program.

so grid integration with all and then move into max4live.

yup. no idea best place to start.

frankly i should probably be happy everything is at a baseline functioning at least mostly as intended.

#47

You know, that’s exactly how I started off.

Back when I first started doing monome stuff (and “grown up” Max stuff), there weren’t options like Pages, or Sum, etc… so I set about building my own ‘hybrid’ app. With a couple of those smaller apps being tests that later got folded into TPV.

I’ve not done any monome stuff in M4L so I can’t comment specifically on the difficult, but I would imagine it’s quite easy these days with Sum, and BEAP, to adapt existing patches into that environment.

I would start simple, and literally just move monolase into there, as it’s a standalone patch with no subpatches, then once you have a handle on the workflow, take a look at chocolage grinder, which has a couple of subpatches.
In terms of mapping that, it would be good to look at the version of it in TPV (in terms of the UI, the code for TPV is quite complex/big), which is kind of modelled on tml. Or I also posted a ‘modes’ teaser in the TPV thread which has some better cd skipping behaviors in there, so it would be worthwhile looking at that as well. I guess it depends on what/how you want to control things from the grid (and tilt)

2 Likes
#48

indeed! thanks @Rodrigo
'time machine genius
peace and respect
from a different time zone

image.jpeg3024×3024 1.4 MB

nice @dude
your tunes sound great now,

cool you can now shred them through the monolase :slight_smile:
'cause you know, as they say in madrid
'if a goat floats…

2 Likes
#49

thank you! much work to do on tunes. in fact that is always my main artistic priority. and has always been (on last 3 attempts) the thing that gets in my way of learning max as my fluency with my studio is so much stronger in studio work than itb max work. i make so little progress with max. with studio i require no handholding. with max it feels like only way i can get by is with massive handholding. so i give up easily as the burden to others tends to be higher than i believe is reasonable.

1 Like
#50

That’s definitely how it goes, but slowly and surely the handholding needs to be less and less.

1 Like
#51

is javascript used at all in monolase or the chocolate grinder?

#52

Nope. At some point I experimented with a javascript OSC-route replacement, but not in these two.

#53
#54
#55
#56

yes, perhaps I can make some updates someday…
:slightly_smiling_face:

monolase
wishlist-
add ~karma engine (smoother, less digital clicks)
monobright compatible (top row toggle)
user selectable bit reduction (8,12,16)
export .wav audio file within the app (no soundflower audio routings required)

and it’s super cool now!
these tracks went through it…

3 Likes
#57

2 Likes
Monolasem4l
#58

Been playing with this today at @abalone’s urging.

  1. it’s awesome
  2. I have no idea what I’m doing
4 Likes