#1

-Two different rotation directions in sync mode.
-Built-in attenuators

#2

+1 to attenuators. levels like functionality would be very helpful

1 Like
#3

+1 to attenuators. levels like functionality
that would be handy.

1 Like
#4

I thought this is already implemented:

2 Likes
#5

I wonder if it wouldn’t be nice - if it makes sense - to be able to change the frequency of the pulse output of Cycles. It would not be a phase indicator then anymore but I think in combination with friction it would be nice to have, for example 4, 8, 16, 32 pulse cycles per round, maybe in combination with or adjusted from teletype.

Think of an wheel of fortune, nudged and then slowly expiring, triggering notes or anything while doing so…then being nudged again with a trigger from Meadowphysics (or teletype again to keep the primary interface tidy)

:grinning:

#6

I just noticed that the last part was a stupid idea unless it would be possible to combine some force information with the nudge. So maybe a command that emulates a gesture on one knob like II CY.NUDGE X Y to give it a nudge of the strength X in direction Y.

Could be understood as an advanced version of a simple cycle reset via teletype. A side effect could be that cycles could be used with no arc connected - if app change via teletype would be possible.

Or is this stupid?

#7

  1. How about randomness as a another (teletype-) selectable waveform?

  2. Some wow&flutter would be nice on the single cycles, set by a teletype command and going from very slightly to not so slightly.

#8

+1 for this. building on that, brainstorming on an interface to drop “pulse” markers along the ring in realtime - for irregular rhythmic entries.

other ideas:

  • tt commands to reset cycles independently
  • tt commands to reverse cycle direction
  • specify a “window” in the cycle. when a wall is “hit” direction is reversed, while still honoring the physics feels. springy ping-pong.
1 Like
#9

It seems that when in sync mode there is some kind of underlying offset frequency present in cycles that reduces the CV-amount or its range. I did not explore it on the scope since mine is analogue and might be to slow for LFO observations but it is hearable when you modulate pitch with it (second cycle to osc pitch in the vid).

Also I wonder what the general frequency range is. When I am in sync mode with a faster primary cycle the synced ones get down again at some point when increasing the multiplication factor.

Another feature request after some exploration of cycles would be to have some more division factors beyond ½.

After all playing cycles is big fun and leads to interesting new sound/song structures. Using friction to stop it is huge step forward in LFO/modulation technique. I hoped it would be like this but was’t totally sure before - but playing LFO’s like an actual instrument is a big thing. I even change configurations while playing or switch to Levels and hadn’t thought that this would work that good.

#10

Hooked it up on the scope after all and listened to the CV out - I find the outcome a bit irritating. There seem to be some audio rate modulation going on and the cycles are actually stairs?

https://youtu.be/k0XYvJ5T6QI

#11

the default slew must be miscalibrated-- i’ll check this out.

#12

@tehn I am not sure if you are referring to the stepped voltage issue with this or to the strange modulation on amplitude, shape and offset cycles shows. Or is it connected?

The voltage Levels puts out is stepped too.

#13

do you have another cv outputting module to test your scope?

definitely doesn’t look as stepped here…

https://vid.me/DLoV

#14

That’s strange - I am afraid I don’t need a scope for this, just ears. But if it helps I compared Levels to Batumi here and proved my scope to be simply alright.

So what’s going on there?

https://youtu.be/tdykwwabBlA

#15

you may want to open a dedicated thread or email monome directly… it’s quite OT and therefore might be overseen

#16

doubled the dac refresh rate in this build which should reduce the stepping effect.

ansible-1.2-2.zip (69.1 KB)

the offsetting shown before is an artifact of the dac refresh rate vs. spinning lfo rate. i honestly designed cycles for lower rates-- where the visuals make sense and don’t go into wagon-wheel mode, which is where you start seeing artifacts.

one way to minimize artifacts is to constrain the output amplitude-- not yet documented feature added last month upon request: hold key 2 and press key 1 momentarily-- continue holding key 2 and now you’re in attenuator “mode” where you can scale down the output

2 Likes
#17

Thanks for the taking the effort!

I think I can live with the shape/offset artifacts and take them as a special flavor if we agree in them being a feature then. Not too bad sounding rhythmic beatings anyway at higher speeds.

The steps have been a bit distracting though…

#18

@tehn After a short test I am very happy about the outcome! CV is smooth as smooth can be now on both, cycles and levels. I actually do like the fast cycle behavior as it matches perfectly with the wagon-wheel effect on the Arc and becomes playable in a very nice manner - so please let as keep this goody…:heart_eyes:

But, what I noticed too is, when you switch mode from, say, Levels to Kria there is a quite long slew until the CV has changed from the level it has in Levels to the level Kria determines.

#19

i’ll check the mode-switching slews/dac updates, thanks for the heads up

edit: i wasn’t able to replicate any problems with slew as you’re saying. the CV output doesn’t “reset” on mode switch (but the slew rates do). so if you use levels to set CV 4 all the way high, it’s not going to reset when you turn on Kria until track 4 of kria outputs a new value. it should not slew (this is what i’m seeing).

#20

seems like a nice idea.

1 Like