#203

it’s actually working fine today so far. I’ll try that if it happens again

*now i’m getting monitoring but no playback. Might be something to do with excluding commands. once i did that, the trouble started (today, at least. but i was also doing it some point when the problem first started)

Summary

script load: /home/we/dust/code/compass/compass.lua

cleanup

script clear

including /home/we/dust/code/compass/lib/arcify.lua
pset >> write: /home/we/dust/data/system.pset

script run

reading PMAP /home/we/dust/data/compass/compass.pmap
Engine.register_commands; count: 0
___ engine commands ___
___ polls ___
amp_in_l
amp_in_r
amp_out_l
amp_out_r
cpu_avg
cpu_peak
pitch_in_l
pitch_in_r

1 Like
#204

Yesss! Super glad to hear that :slight_smile:

#205

it’s working fine again after reset. but it was getting to the point where i wasn’t even getting monitoring again before i did that. must be command exclusions, i don’t know. i’ll stay away from those for a while maybe

oh ok, so softcut would mute monitoring too then. makes sense

1 Like
#206

Yeah, the / command will mute (and unmute) Softcut completely, and you can adjust how fast or slow the fades are using the Level (slew) control in the params. As a test, I’d record a bit of audio into a loop, stop recording, then put a few /s in your command sequence to more deliberately hear the effect.

Actually, no – the / command should have no effect on incoming audio in any way. All it does is simply affect softcut.level. If you still have that video you were in the process of uploading, feel free to share it with me in a dm and we can take a closer look!

1 Like
#207

Oh man, I deleted it. I’ll record it another one shortly. Next time it happens. Sorry about that. I don’t mean to keep stressing you out over this

1 Like
#208

anyone else not getting any randomization from the k1+ k3 combo? curious why it was changed from the long press of k2? i personally find having a free hand to be doing something else and avoiding combo presses unless necessary optimizes the flow of things.

2 Likes
#209

What sort of wizardry is this??

1 Like
#210

@claasp — thanks for the feedback, that makes a ton of sense. Randomization is working for me, when I hold K1 and the press K3, but there are probably moments where a quick combination of the two isn’t registered. I had to rethink button presses as additional functionality was introduced in 2.0+, but I’d be happy to revisit this and see if it could be optimized.

@pfig With a grid connected, you can stop and start the sequencer with the right-most key in the bottom row! Makes it easier to trigger commands via grid at your own pace :slight_smile: Check out this section of the manual for more details.

4 Likes
#211

Ah I skipped it, as I don’t have a grid yet :slight_smile: Thank you!

2 Likes
#212

Makes sense! It sounds like stopping the command sequence would be useful for you without a grid? Would love to hear your thoughts on that…

#213

I think being able to stop the command sequence without a grid would be a very useful feature.

2 Likes
#214

Sweet. All of this has given me a good nudge to rethink keys and encoders this weekend. Thanks!

6 Likes
#215

Alright! I’ve got an idea re. keys + encoders and would love to hear feedback if anyone has any.

As the list of script actions grows, I think it’s time to introduce two modes on the main page of the script: PLAY and EDIT. The idea is to use a long press of K1 to switch between them.

Play Mode

In Play mode, you’ll have easier access to the most common actions:

  • Randomize commands (K2-short)
  • Clear commands (K2-long)
  • Toggle recording (K3-short)+
  • Stop/start sequence (K3-long)
  • Select step (E2)+
  • Select command (E3)+

+ Unchanged

Edit Mode

Secondary actions are accessible while in Edit mode.

  • set loop start point (E2)
  • set loop end point (E3)
  • set sequence length (K2 + E2)
  • clear buffers (K3)

My thinking is that these actions aren’t taken too often while playing, so it’s ok to nest them on a different layer. Feel free to challenge my assumption :slight_smile:

The goal of this is to reduce the number of key/enc combos, and - hopefully - make navigation/playing easier in the process.

10 Likes
#216

Yeah, sometimes I’d just like to pause for a bit and let the loops play, it would be great to have the ability to do this without a grid :slight_smile:

As for the 2 modes, I personally prefer that to using a “shift” key, definitely!

3 Likes
#217

That’s sounding pretty good @Olivier and makes more sense. Although I do find clearing the buffer useful during playing. If things build up and get a little outta hand I’ve on many occasions just quickly cleared buffers while it’s playing and kept jamming. Maybe keep that in play mode with a long press if K2 + K3?
Also while your feeling like tweaking the code a little further, I do really miss having the - and + commands effects the playback speeds over randomness because you could plan out the pitch shifts a little more or just see when it takes you with a touch more control. With all the randomness I’ve found sometimes I’m getting too much 2x when I’d like it to be more around x.5 x1 and the reverse equivalents.
I understand you may not want to go back to that functionality so I was thinking maybe a workaround/new feature would be having a min and max setting in parameters that would let you say, put + commands to no more then x1 and - to say x-2 for example. Either that or a probability parameters so I could set it to play less x2 or more depending on what vibe I’m going for. This one could be fun! Keeping the ! command at full random should stay though as that’s already a great way to let things just happen.
Anyway just some things for you to consider.
Loving compass either way. Thanks for all the hard work!

4 Likes
#218

This is all good stuff! I agree with you completely on the + and - — I haven’t thought about those in a while, and it makes perfect sense to revert them back to their previous, more linear behavior.

I have to say, everyone’s feedback over the last couple of days has been super helpful. It’s always good to focus on little details.

5 Likes
#219

This sounds super helpful, and at least to me seems like a logical division :slight_smile:

1 Like
#220

Sorry if I’m missing this in the docs… is there a way to save sequences?

1 Like
#221

Not as of yet! I’m always keen on implementing this, but it always seems way above my head when I starting digging in. Maybe an intrepid Compass user would be open to submitting a PR?

In my mind, saved sequences would be playable somehow. I’d love to see a bank of 8 slots on the grid in which command sequences can be saved and loaded.

3 Likes
#222

I’d love to tackle this. I will take a look at how it’s handled over in loom.

Love the idea of making recall playable as well. Do you imagine that as a new “page,” or somehow fitted onto the existing main one?

3 Likes