I’ve spent an afternoon with CC2 today. It’s so inspiring, thank you for making such a wonderful thing. I’ve been working entirely on norns (shield) and it has given me some surprising and frankly incredible patterns. Big props to the euclidean mode especially. Next up for me is downloading the M4L patch and getting everything set up with the Launchpad Mk1.

I have only had my norns shield for a couple of weeks and am bristling with the possibilities. I can’t wait to see how it shapes and bends my future compositions. I am lucky to have arrived simultaneously with the launch of this beautiful tool. To have read about the journey and the collaborative nature of it all makes it even more special.

3 Likes

this was from my first session w/ cc2, a rough flying saucer attack cover/homage:

this is not a very deep usage of cc (and clearly still figuring out the delay page) but I like how the drums unexpectedly came together in this stretch

5 Likes

Thx for the bug fix :slight_smile:

and thx for the headsup on the external input. A way to play with it on the delay page would be extra awesome. (it’s starting to be my favorite function)

What i liked about the previous view was that you instantly get a overview of where all the loop and record windows are. This is the most important function for me … BUT a way to change those loop windows in that view would also be handy and then you will end up with the original controls.I used cheat codes 1 alot as a 3 playhead delay looper kind of thing where i played alot with the A B and C “playheads” and the record window this isnt as practical in this version because you don’t have a view of what your record window is and where your different loops begin & end.

Do you have enough details?

3 Likes

still exploring everything the update has to offer but…
here is last night’s session with five Lorre Mill Double Knots running into Cheat Codes 2…

6 Likes

Spike be all:

11 Likes

some more bugs :slight_smile: arc erases start end points L2, L3,
grid pattern play doesn’t show start end points moving as previous version? and when I try to record arc movement on top of the playing pattern is tricky.

dang, @speakerdamage + @SPIKE, these are heavyyyyyy. absolutely wild side id of the script, i love it :slight_smile:

@swhic, i don’t think i fully understand what’s happening, so let’s get on a DM! :sparkles:

2 Likes

Hey Cheaters,
Made my first little tutorial about generating patterns synced with ableton link. Pretty basic run down for experienced users but it might be helpful nonetheless (*and it was fun making!)

33 Likes

I just loaded up cc2 this morning and it is amazing!!! I’ll have to spend some time with the docs open to get used to the new commands. I absolutely love the alt lock per pad group. The filter controls feel more intuitive and performative than v1. Haven’t even touched the delay page yet but I’m excited to get deep into it later.

@dan_derks congratulations on this and thank you!

1 Like

:rofl: :rofl: :rofl:
such is my life in the simplest of terms.

funny thing…
i used to involved in a charity that…for about five years…would gather as many drummers as they could under one roof for a World Record sort of thing.
(had Terry Bozzio with us one year)

and that amount of noiz all at once and by so many levels of ability…is absolutely incredibly immersive to say the least.
:stuck_out_tongue:
also…
i experimented with running all those Double Knots into three simultaneous instances of Cheat Codes 2 running live loops. (the previous session was with only one CC2 running)
should have that madness posted soon.

4 Likes

Hello lovely people, I’m having a great time with CC2. I’m wondering if someone can help me with a small problem I have. I’ve so far been creating tiny patterns only on norns. Today I decided to explore the M4L patch with a launchpad. The problem I’m having is that I can’t trigger the pads.

More details here for anyone who might be able to lend a hand…

Summary

I have the meta-actions and rate changes successfully mapped to the launchpad which work perfectly.

Pad 1 on bank a is C2 according to M4L. Looking at the Launchpad manual top left is C2. But when I hit it nothing triggers.

I wondered if this maybe a Launchpad issue. Alas not! This also happens when I tried C2 on Launchkey mini.

I’m thinking I may have missed something obvious… Any help much appreciated :pray:

Try setting the M4L patch to C-2 (C minus 2), which should be the lowest value you can set.

On the Launchpad, C-2 is top left: first column, first row. The Launchpad’s C2 is first column, fourth row down.

3 Likes

if @Philternaut’s good advice doesn’t do the trick, could you please share a screenshot of your ableton session? if midi is flowing correctly from the controller, then any VST or instrument after the cc2 m4l device should also receive and play the expected notes — it passes all midi through.

lmk how it goes! :slight_smile:

1 Like

Thanks @Philternaut, I had misread that! Neither hitting fourth row (C2) nor changing patch to C-2 work still.

Here is my screen shot:

Thanks so much.

1 Like

mm, what if you either switch monitor to In or rec enable the track with the bottom button under the track’s solo button?

just to make sure the device is working, you can also draw a midi clip with a few notes in the range — i’m away from home at the moment, but happy to test later as well :slight_smile:

Also worth checking Live menu > Preferences > Link/MIDI > Input:Launchpad Mini has Track enabled?

Nothing with either of those things. Monitor in changes nothing. Record enable sets that clip recording with the launchpad, haha. Attempted both with Launchkey too to no avail.

Checked just now, all midi devices have Track enabled.

Oof, thanks for checking. Try this Ableton project (attached), banks a & b are set up with midi clips that work on my setup. I tested this with my LP mini which appears to work in this project to trigger the cheat codes pads. First two rows are bank a, second two rows are bank b. Check the M4L device’s IP address, of course :slight_smile:

cc2_m4l_test Project.zip (78.7 KB)

2 Likes

as someone said above, I was not totally connecting with CC1, but this version is revelatory. having the waveforms to look at when editing loops is soo helpful, I would never have guessed. amazing work, the UI is so attractive and I am making music I like on it, which is everything.

I seem to have found myself in a state where I can’t get to the K1 menu, and am therefore unable to change volumes, change params menus, shut down, etc. CC2 is playing a nice loop of some RW blackbirds on an Idaho reservoir so not too depressing but I was hopping around the buttons cavalierly, might I have set it into an alternate command state I don’t know about yet? this is Fates, btw. I get this when I press K1:

3 Likes