#9

https://soundcloud.com/k-blamo/cortesiax2

#10
#11

is/are there any special setup/requirements/initiation to get monolase to function on max6 64gs?

1 Like
#12

Not used this in aages but it should work fine. Is it varibright? I don’t remember if I put the clipping stuff into monolase, but the version of it in The Party Van (page3) will work with varibright or legacy LEDs, so 64gs should work a-ok either way.

1 Like
#13

thanks @Rodrigo

1 Like
#14
#15

image.png640×1136 191 KB

1 Like
#16

So many other things on my plate at the moment, but in rewatching the original demo video for this the other day, I was struck by how much better it would sound using karma~ as the core of this. Once you kick in the really heavy modulation you get oodles of clicking/discontinuity artefacts which takeover the overall sound in an uninteresting way.

Perhaps one day.

2 Likes
#17

:slight_smile: …and it’s really cool now, thanks!

image.jpeg3024×3024 1.42 MB

feliz año nuevo

#18

i appear to have isolated my issue to the serialosc grid connection box not allowing me or not sensing my grid. this box works in old tpv, cg and other programs. so i think something might be odd within monolase. what i mean is that my grid works in all my other apps etc. no troubles. it is non-vb gs 64. using max6 and runtime. mac. not newest os.

#19

It could very well be an older version of serialosc. Try grabbing the serialosc that’s in the tpv folder and put it in the monolase folder and seeing if that works.

1 Like
#20

i tried that. no dice. no big deal. i just love the standalone aspect of the smaller apps rather than gargantuan nature of tpv.

1 Like
#21

Yeah I can see that.

So it just doesn’t show up at all? (as in not in the dropdown menu of serialosc)
Or does it connect but not do anything in the app itself?

1 Like
#22

my grid doesn’t show up in the serialosc box, as if it isn’t sensed despite having good connection with everything else. so i guess it for some reason isn’t connecting within app. i thought about trying to manually enter it through that port entry. but i’m not sure that would work, and i don’t know my port.

#23

in the monolase app
the words above the serialosc box say-
/sys/prefix /coco
actually a button
~push it
…it resets the serialosc device to /coco

maybe…

1 Like
#24

tried that to no apparent effect.
did grab screenshot of max window.

something about zeroconf. wasn’t that the connector thing before serialosc?

i also tried opening the serialosc app within ml and it appears to be the genesis of the connection issue as nothing happens with either the old so app or the one i copied and aptly named from the functioning tpv vers. something within the serialosc app doesn’t want to connect to my gs64.

#25

i also tried to use the monome home app and those port numbers from the screenshot to see about manually entering port # data. to no avail.

#26

'sup dude
it’s cool that you gonna rock the monolase!
nice when you post all the details about your setup

it’s possible that my system has an older serialosc version, that needs zeroconfig files
in the externals folder of max
maybe something there…

the old forums have really helped-
different from what you’re seeing, but…
http://archive.monome.org/community/discussion/11282/serialosc-and-first-time-problems/p1.html
http://archive.monome.org/community/discussion/12026/max-runtime-error-solved-/p1
http://archive.monome.org/community/discussion/12861/serialosc-issues/p1.html
…it’s also cool to see that back-in-the-day there were issues, that got resolved on the forum
tech support is way better when we have people that know, like @Rodrigo on the line :slight_smile:

1 Like
#27

yes! i hope i have listed the pertinent system details. i can share more if t’would be helpful.

thanks for sharing those old resources. interesting to read. my problem may well be contained in there but wasn’t readily apparent.

#28

Right right. Yeah that’d be a suuuuper old serialosc version.
I would imagine it still works if you add the zeroconf externals in there. I’m surprised it didnt work when you replaced that version of serialosc with a newer one.

2 Likes