Ok…working now… strange sorry for that

1 Like

this seems to have done it for others:

there isn’t yet, but that’s what the Music Hackspace sessions are hopefully going to bear! in the meantime, the manual and menus are pretty linear in terms of concepts, so i’d encourage starting at the top with a simple goal [record some audio (or import it) and loop it] and feel free to let me know where snags hit and hopefully the MH sessions help!

3 Likes

Woah what an idea! I hadnt even thought of the amazing generative patches possible via crow. So much to try, so little time

2 Likes

Wait wait wait - TF is this Midigrid you’re talking about?

omg i’ve been away for so long i didn’t know that people got the Launchpads working?

5 Likes

hey @dan_derks There’s probably something wonky on my end here but I can’t get multiple parameters to be modulated by the macros. Say I set up macro 1 with rate, filter, pan and start point and map macro 1 to a fader on my midi controller (nanokontrol2), only the first parameter (rate) seems to be affected? I’ve made sure the macros (1)(1), (2)(1), (3)(1) etc are set to active…

edit: got it! needed to wrap my head around the numbers on the macro screen. everything working fine :relaxed:

2 Likes

ah, awesome! glad it all got sorted, thank you for closing the loop!

for others who might run into the same q’s, macros can be thought of as a forest. you have 8 trees:

  • macro[1]
  • macro[2]
  • macro[3]
  • macro[4]
  • macro[5]
  • macro[6]
  • macro[7]
  • macro[8]

each tree (aka. macro) has eight branches (aka. parameters it can simultaneously control).
eg. macro[1] will control:

  • macro[1][1]
  • macro[1][2]
  • macro[1][3]
  • macro[1][4]
  • macro[1][5]
  • macro[1][6]
  • macro[1][7]
  • macro[1][8]

so, when setting up multiple parameters to be changed by macro[1], you want to work down the branches of the macro[1] tree, rather than across the macro forest (macro[1], macro[2], macro[3], etc).

meta

you can link macros, so that a change to macro[1] will be mirrored to macro[2] (and its branches). this is a good way to control more than eight parameters with a single midi-mapped macro, but it definitely makes the branch/tree concept a little more abstract :evergreen_tree:

eg. if macro[1][8] is set to control macro[2], then macro[1] now controls:

  • macro[1][1]
  • macro[1][2]
  • macro[1][3]
  • macro[1][4]
  • macro[1][5]
  • macro[1][6]
  • macro[1][7]
  • macro[1][8], which by extension controls:
    • macro[2][1]
    • macro[2][2]
    • macro[2][3]
    • macro[2][4]
    • macro[2][5]
    • macro[2][6]
    • macro[2][7]
    • macro[2][8]
4 Likes

Im trying cheat codes for the first time and alas i get no sound. Trying to use it with a sample rather than live buffer is there a way to know on screen that i have it in the correct mode. Thanks

1 Like

hey hey! stoked for you to dig in :slight_smile:

from page 5 of the manual:

that page should have all the steps you need to switch to clip mode, select a sample, and confirm it’s loaded.

some troubleshooting tips:

  • do you see a waveform? if not, then the clip is either not loaded or the bank/pad is not pointed to the correct clip
  • if you do see a waveform and can confirm that the playhead is moving across the audio, check to make sure that the cut system level is turned up
  • least likely, but still possible: is the level on the cheat codes [levels] screen turned up?

happy to help with more info (are you using a grid? or just the on-norns controls?)
also, in case it helps, all this setup stuff will be covered in detail at the Music Hackspace workshop :slight_smile:

1 Like

Thanks again, will have a cold beer and peruse the manual now

1 Like

Such a fun script! :nerd_face:

I would like to drop an idea for a button combo on the grid for transposing the pitch of the samples assigned to the pads. Like +1 and -1 note. Maybe this could be handy :v:

1 Like

for sure, a great idea! currently, you can transpose pads via the [loops] menu — a good stop gap for now :slight_smile:

2 Likes

mannnn I just gotta say sometimes its the small things… the “global” portion of the “pad to note setup” is fucking brilliant. being able to have each bank go to three separate midi channels then go up to global and set the scale, octave, root note from there for all there channels at once… so slick!!!

4 Likes

Mine is when you save a collection “saved” flashes in large bold print! The little things.

3 Likes

haha for sure! I normally save via pset but saved a collection last night and saw this! you are so right

2 Likes

Your CC2 videos are really helpful, thanks for making these!

3 Likes

I’m glad to hear, thank you :blush:

1 Like

I know real estate is tight but the more I use the pads to play midi notes I’m finding that I wish there was a dedicated pad to enable/disable the midi note output on each bank. :thinking:

The way I’m using midi notes out now is to play different tracks on the OP-Z and then record what I am playing back into CC2 on the buffer for that bank. It would nice to be able to switch off the midi note output quickly so you could then just play the slices with the pads.

4 Likes

totally agreed! i’m planning on doing a small update in the next week or two which will allow folks to assign the remaining keys on the main page to any one of a batch of actions – so like, if you don’t have an arc (which the four keys under each bank control), you can just reassign one of them to something like toggling MIDI output, or using those to pull up pages on norns without clicking around, or tap tempo, etc :slight_smile:

i’ll keep this one in the log for assignable actions! thanks for the ping!

tho for now, you could map a MIDI controller under PARAMS > pad to note setup to quickly toggle bank x MIDI output? on and off

10 Likes

So great, I knew this probably was already on your radar!

Yes, the midi controller idea did cross my mind as well but I will wait till you make the update as it will be so cool to have it right there on the grid.

Thanks as always!

1 Like

perfect! midi transposition possible? its really perfect if not though!