#410

Fair enough and that makes total sense now!

Also, midi sync is rocking now with Norns following the OP-Z’s midi clock and stop/start messages perfectly. :clap:t2:

1 Like
#411

There is some odd behaviour of the parameters menu scrolling after script runs for some time. Encoder functions normally on other sections of the script and outside of it

1 Like
#412

i’ve noticed this occasionally, but haven’t been able to reliably repro – i think it just has to do with a race condition re: the custom key hold times on some of the menus. if you hit K2 to back out of the parameters to the EDIT/PSET/MAP screen and re-enter the EDIT section with K3, it should clear up fine :slight_smile:

under normal circumstances, this type of header-jumping is actually a feature, if you press k3 on any of the parameter headings :sparkles:

1 Like
#413

I tried but unfortunately no luck. Will see if it will go back to normal after rebooting the script as soon as I finish working with it.

1 Like
#414

maybe try using encoder 1 to navigate around the system menus a bit too? it does clear up easily, i just can’t remember the exact combo, apologies! if this continues to be problematic, any steps to reproduce the onset of the issue will help :revolving_hearts:

edit: ah! @Moneo , i was able to repro – it’s a weird one, though. using E1 to navigate away from the parameters and back clears it up.

1 Like
#415

Another question: myKorg Nano kontrol 2 is fully recognized by norns but my small Korg microkey air is not (in usb mode not bluetooth)… What kind of midi keyboard is compatible with norns and CC2?

#416

Iirc I was seeing that behavior most when having used the long press of key 1 inside cc2 which is sort of latching in some instances? (this was with the previous update, will try and see if it can be reliably reproduced on the current version later today).

#417

from what i can tell, that keyboard should be compatible. what leads you to believe it isn’t recognized? does it now show up in the SYSTEM > DEVICES > MIDI menu? if it helps, this thread is a nice running list of norns-friendly accessories: https://llllllll.co/t/friends-of-norns-gear-accessories-etc

yeah, it’s a tough one to repro. i was able to get it by doing some weird key combos on the [loops] screen and essentially colliding the key hold timers (i guess they’re somehow outrunning the norns system menu logic?), but i feel like it’s rather rare – if folks are running into this a lot, tho, lmk!

1 Like
#418

Hey there, two questions.

  1. How do i make midigrid work with Launchpad Pro mk3?
  2. Is there any video startup guide? I want to dig into this script but everytime get intimidated and lost in it. This is my proverbial Octatrack:)
1 Like
#419

Ok…working now… strange sorry for that

1 Like
#420

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
#422

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
#423

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
#424

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
#425

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
#426

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
#427

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

from page 5 of the manual:

image
image928×408 3.92 KB

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
#428

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

1 Like
#429

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
#430

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

2 Likes