#227

Hey - thanks for the reports!

Yep, this is weird and I’m also seeing it as of the latest norns update. I can’t for the life of me figure out how it could be coming from Compass, as no changes were made to input/audio routing stuff. I’ll open a separate questions thread for troubleshooting.

If it helps, my workaround is to simply go to the global LEVELS page, and then just barely adjust the monitor level (bring it a hair down, then back up). This should get monitoring going again without the need for a reset.

Good idea! Will look into it.

1 Like
#228

Fwiw, I also had this problem (once!) with the old version of Compass for some reason, with the same fix.

2 Likes
#229

Easy peasy workaround — thanks!

I also just noticed that if I push any buttons on the functions page, even without alt to toggle/disable, it resets my command sequence.

Thanks so much for this app — so many wonderful sounds!

1 Like
#230

Thanks! Really glad you’re enjoying it.

Oh, yeah? My bad – will have to investigate this! The intention is for the command sequence to be reset only when you use K2 to exclude commands.

#231

Maybe resetting steps containing restricted commands to default C would work better?

2 Likes
#232

It works for me like 20% of the time

1 Like
#233

Sorry for the hassle. Got an update coming soon (likely this weekend) that will make all of these common gestures much more accessible!

1 Like
#234

not at all dude, this update is incredible, thank you for your hard work :slight_smile:

2 Likes
#235

3.1 release

requires the latest norns version (200424)

Clock

This update introduces support for the new and fantastic global clock system. As a result of this, a few (small) changes were made:

  • the default C command was made redundant, and so it’s been deprecated. [ is now the default, and simply runs at the base tempo. The other clocking commands still work the same.
  • speaking of base tempo, the internal clock speed param was also made redundant, as the clock system now lets you choose whatever tempo you want via params. Isn’t it great?!

Keys & Encoders

Key and encoder actions have been reworked in an attempt to make things easier and more accessible. I had originally conceived of creating separate modes that would each contain various actions, but that ultimately proved too cumbersome and slow during normal use. I opted instead to keep things simple.

See the updated manual for full details.

Command updates

  • The + and - rate commands work linearly (like they used to) instead of picking random forward/reverse rates.
  • I’ve decided to retire the short-lived / command. It was half-baked, and I think it caused more confusion than fun :slight_smile: The corresponding level slew param was therefore taken out of the params list as well.

Let me know if anything seems wonky!

25 Likes
#236

Awesome work - I love the new UX, and things feel way more playable for people without grids (me). Looking forward to making my first recordings with Compass soon!

2 Likes
#237

THANK YOU for the update!
worked flawlessly for tonight’s broadcast of noiz…

  • recorded a Folktek BUG into Compass
  • recorded a Double Knot into @dan_derks Cheat_Codes
  • extra percussion with @nattog VIALS

all three scripts running and synced simultaneously to a NAVA extra 9.

2 Likes
#238

Very cool to see/hear this - thanks for sharing @SPIKE

1 Like
#239

Sounds awesome @SPIKE! I actually have no way of testing external sync myself at the moment, so I’m glad it worked for ya :sweat_smile:

1 Like
#240

Wow, this update looks great. Thank you.

1 Like
#241

When I save a preset, it doesn’t save the functions I have active/disabled on the second page. Would that makes sense to add?

1 Like
#242

Totally, but perhaps beyond my ability at the moment — will definitely take note of it, though. Thanks!

1 Like
#243

really enjoying this script @Olivier, thanks! long time norns user but only try this recently… big mistake :slight_smile:
one question though, does the presets work? I’m trying to save but when I load it nothing is saved…

2 Likes
#244

Hey! Glad you’re enjoying the script. To your question, the pset file should save whatever you’ve set in the params menu (including things like midi mappings), but it won’t save command sequences – that hasn’t (yet) been developed. I may have misunderstood your question, though – let me know if I have.

#245

you are correct @Olivier, I was referring to the command sequences, the params menu are saving ok. I did not explain myself is the best way 'cause I’m really excited to have found this script :smile: any future date about saving the command sequences down the road?

1 Like
#246

Not at the moment, but it’s on the to-do list. I’m short on skills in this area (PRs always welcome), but would be glad to explore.

1 Like