#81

It could sound like anything. Whatever you put in comes out, but in time!

#82

@lloydcole so great, can’t wait to try this

reminds me of andrew pask’s looper ideas, discussed in his interview with darwin grosse : http://artmusictech.libsyn.com/podcast-055-andrew-pask

(brian has mentioned this podcast episode a few times, well worth a listen)

#83

great idea. Really inspiring.

#84

Simple Decay envelope. Why is this missing so many triggers ?

1 :
CV.SET 1 0
CV.SLEW 1 PARAM
CV.SET 1 V 5
DEL 2 : CV 1 0

1 Like
#85

Random question :
How to change the range of IN or PARAM ?
Let’s say i want to scale the PARAM to 0-1000.
I’d love an equivalent of [scale] in Max.

#86

i got this to work pretty reliably:

M:
CV.SLEW 1 RSH PARAM 4
CV.SET 1 V 5
DEL 1 : CV 1 0

but i don’t know why there needs to be a DEL in there, which must be a bug in the CV code. this might relate to why certain pulses are dropped at higher script rates.

to scale the input i used RSH (right shift) which divides by 2 per shift. so shift 4 divides by 16, getting 1024 max. you could also use DIV PARAM 16

1 Like
#87

Thanks you. Indeed, i won’t work without a DEL, happy to know it’s a bug, as i am also very concerned with missed pulses.
As for the scaling of values, it’s hard to have a precise output range, since decimal is not allowed and too high values are not allowed either.

#88

You can do hundredths of volts with the VV command.

VV 100 = 1V
then,
VV 101 = 1.01V

There’s certainly some tricks to working with integers only, and it requires a different mind-set to floating-point, but rest assured almost everything is possible as it is with FP.

#89

my tt arrived yesterday

genius!

in love with it already

i was worried it would feel “computery” and i’d be put off, but far from it. it feels like it’s opening up a whole host of opportunities for exploration with the modular. a bit like a baby aleph, or the cv half of one.

great job team monome! three happy goats for you: :goat: :goat: :goat:

1 Like
#90

Sure, but honestly i don’t see any way to effectively scale the [0 16383] domain to [0 1000].

DIV PARAM 16.83
won’t work since 16.83 would be quantized.

DIV MUL PARAM 100 1683
won’t since MUL PARAM 100 will easily cross the 32765 boarder.

#91

this is true.

i’d suggest doing this:

LIM 0 1000 RSH PARAM 4

you’ll get a tiny “deadzone” at the top of the knob. it’ll be around 2% of the turn so not noticeable.

#92

Ok. This totally acceptable in this particular scenario, but i can think of many other were it could be problematic.
Would a command like PARAM.RANGE a b be possible, useful ?

#93

i think a SCALE operation would be appropriate given the limitations of the system re: floating point and bit depth.

SCALE A B X Y I

A to B is the input range, X to Y is the output range, I is the value to scale. it’s pretty obtuse but serves the purpose you’re looking for-- and i do see how this might be desired.

PARAM.RANGE is not a bad idea but i’d prefer general solutions.

so this would translate to:

SCALE 0 V 10 0 1000 PARAM

yikes, but makes sense. i wanted to stay away from operators that had so many arguments.

#94

A Scale Operator would make me happy !

#95

SCALE would be hugely useful!

(Just wanted to add to the chorus of excited voices.)

#96

added

3 Likes
#97

Genius ! thanks for amazing features and support !

#98

Please excuse my ignorance here, but does this mean that SCALE will be added to the Teletype at next firmware update, or that it has been added and I can somehow update my Teletype and take advantage of this new Operator?

#99

Likely the next (upcoming) firmware update.

#100

Thanks. And we are still at 1.0, right now, right?