#42

Maybe I didn’t understand completely, but this sounds to me like Levels in volt mode, when not clocking it/running a sequence. You can use it as 4 offsets.

#43

Yeah I could do that, but I could also generate offsets in that way from Rene or Maths or whatever. It just felt so right the way it was implemented in capstarc, in a visceral kind of way, like the faster or more I turn the ring the more voltage it generates with that beautiful visual feedback. That way it feels like turning a record by hand or moving a playhead on a tape or cranking a dynamo and generating something. Also, friction makes this stuff ‘feel’ even closer to something real, you have to keep turning the ring or the voltage drops to zero and done that way it’s really unstable too, you can hear your hand in the movement thanks to how high-res the arc seems to be. It’s one of the few experiences I’ve had with digital stuff where all the layers in between my input and the sound seem to totally disappear. Hope that makes more sense, sometimes I find it hard to articulate this stuff.

1 Like
#44

Yes, this is an idea that came to me too - not only for using it with sample players but also with sequencing. It could output faster cycle speed relating clock/trigger signals then. Maybe reading out the current cycle speed from a teletype command?

#45

Definitely makes more sense - I think there is a space in the Arc/Ansible world that hasn’t been explored yet, for sure. I also am really blown away by the feel of the Arc - there’s nothing quite like it.

#46

Maybe a fringe case, but there could be something nice in setting friction (and maybe force?) per ring when in unsynced mode. Maybe through TT?

If not this, general TT control of those parameters as already-implemented would also be fun. I could imagine a drunk walk on friction would make for lively control, like CY.FR.SET 0 DRUNK 64. Or a script that brings the Cycles to a dead stop over a controllable period by adding friction.

edit: woof. I’ve realized how hard it is to conceptualize TT ops…I’d imagine there also needs to be an amount of friction argument in something like a CY.FR.ADD. Maybe using the 0-255 range. so CY.FR.ADD x y z where x is the ring, y is the amount of friction to add, z is the time (optional). so, that prior example would be CY.FR.ADD 0 255 * M 32 for a full stop over a period of 32 Metro clicks.

5 Likes
#47

Yes, CY.FORCE X Y and CY.FRIC X Y per ring as teletype operators would be really great!

:heart_eyes_cat:

2 Likes
#48

It would be nice in both cycles and levels if there was a way to keep the offset/octave, clock div, etc. pages up without holding the buttons. This way you could more easily “play” the pages while you cycle though a pattern. I hope that makes sense

Also the ability to clock the channels separately in levels from teletype would be sweeeeeet.
Had some other tele integration ideas but can’t seem to recall them at this time

1 Like
#49

Yeah, different clocks (and different lengths ?) for the 4 Levels’ channels would be awesome…

#50

I thought there were no individual channels but scenes with four values in Levels.:thinking:

#51

I suppose that could have been the original idea, which makes perfect sense. I was just thinking it could be interesting. Also the ability to choose between level and cycle per knob would be cool. Probably a headache to implement. Also I have a feeling this could be possible with the Arc ops for tele that @scanner_darkly mentioned a while back

I know that if I really want these to happen I should probably wtite the code myself, but I have no experience with that and it’s pretty intimidating. But it’s never to late to learn

1 Like
#52

Could we get some way to add offsets in Cycles? Another menu page, or maybe via TT? Something like…

 CY.OFF 1 V 2

Or maybe I am missing some other way to do this?

#53

I think it is essential that we can update the firmware separately from managing the presets. I don’t care if it’s a complicated, command-heavy procedure; I’m getting enough complicated sequences in Kria that whenever I update the firmware recreating them is becoming impractical.

5 Likes