#238

still working on testing for the official pull request but I can send you the same build I sent @rikrak. it only has a single seed op instead of separate ones for each op using a random still works though!

#239

that would be great, thanks!

#240

Just had an idea for an op and wanted to get some thoughts and feedback

P.DIR Y / PN.DIR X Y

Controls directionality of P.NEXT / PN.NEXT

If Y is 1, NEXT moves forward (this is the default and the current behavior)
If Y is 0, NEXT moves to a random place within the current length of the pattern
If Y is -1, NEXT moves backward

You can already code up a pitch sequencer in a line (CV 1 N PN.NEXT 0), would be awesome to just have to set this one thing to change the direction of that pattern

As another idea, you could allow for any integers, not just 0 and 1, and that could set the amount of NEXT. In other words, PN.DIR 0 3 would make NEXT of pattern 0 move forward 3 indices each time it is called.

4 Likes
Monome ecosystem firmware development backlog
#241

I can see how this would simplify a script, but also think it could be confusing since we currently have P.PREV to decrement the index and P.RND to get a random value between start/end. The semantics of the word NEXT would be more ambiguous.

Maybe something like this needs it’s own new word? Also, something that I personally haven’t explored a whole lot are the Turtle ops which have some interesting directional options.

You could code this up currently by having a variable to set and 3 if statements, one each for NEXT, PREV, and RND?

2 Likes
#242

I didn’t know those two ops existed! This would actually be pretty easy to code up with some if statements and a variable.

EDIT: exactly what you said in your last paragraph :+1:

1 Like
#243

@scanner_darkly - I loved the idea you presented for the SCREEN op a while back:

Also, I’m finding that the ‘remember last view’ feature doesn’t work for me on 3.0.0, so I left a comment on the github commit.

4 Likes
#244

Sorry, it’s probably that I’m not Github-literate, but: Are the new features like DEL.R and such documented in some one place?

Thank you.

#245

It’s all right there in the user manual: https://monome.org/docs/modular/teletype/manual/

#246

Oh god, I knew it’d be something obvious but this is… In my defence, I looked at the PDF version of the manual. :smiley: Thank you, Mr. 2k.

1 Like
#247

replied on github, not sure why it’s not working in 3.0 official release, are you sure you’re not using a later beta? we made a decision to remove this functionality, so if you’re using a later beta it will always start on live screen.

re: SCREEN op - this should be carefully considered. say, if you use it to switch to pattern view and you put it in metro then it might prevent you from being able to modify the scene, and the only way you could get out of it is by either disabling the metro with the keyboard shortcut or by editing the text preset.

Monome ecosystem firmware development backlog
#248

Thanks for taking a look!

So it went in and was removed shortly after? Just curious - what was the issue with it?

My Teletype boots with 3.0.0 on the screen and is from the latest batch. I can update with the hash when I’m in front of it later if that would be helpful. It sounds like it’s actually a newer beta somehow.

I’m looking for a way to sometimes use Teletype without a keyboard or grid. The ability to choose the screen that comes up first in a scene would be helpful for this scenario. I can sure see why adding it in the metro would be problematic given your example! Is there a way to limit it to the init script or are all commands globally available as a rule?

#249

there was a suspicion it contributed to a bug with scenes being overwritten in flash. and it was the only thing that would write to flash simply because of a user switching scenes, which seemed excessive. the feature existed i think in 1.0? then broke at some point and didn’t work for a long time, then i fixed it, then we removed it. weird it doesn’t work with 3.0.0 but probably not worth investigating since we removed it anyway.

if we were to limit SCREEN op to the init script then it would be the only op behaving this way which is something i think we should avoid as a general rule.

to understand the use case better, which screen do you want to see when you load a different scene?

1 Like
#250

In most cases, it would be the tracker screen.

#251

another option could be just having an op to set up the default screen after loading a scene. it woudn’t be something you’d use in a scene but something you would execute from live screen and it would remember your selection until you change it again (similar to DEVICE.FLIP).

3 Likes
#252

being wondering is it possible to add EXP and LOG function into slew? Also i think TT will be a next level beast if this is possible
DEL 10: S: [some command]

Anyway, 3.0 is mind blowing. Thanks for the firmware upgrade!!!

2 Likes
#253

Sadly you only get one prefix per line. So you have to choose either DEL or S, not both.

(One common solution to this problem is to say DEL 10: SCRIPT 2 and then script 2 contains the S: [whatever].)

#254

yes that’s obviously one way to do it! however my point is, why sacrifice one $ for a line of simple command? :sweat_smile:

#255

Four months later I am loving J and K local variables! Thanks so much. :+1:

How do people feel about longer init scripts? :thinking:

2 Likes
#256

The prefixes giveth and the prefixes taketh away.

EDIT oh my bad this is the feature request thread. Yeah, I mean… it would be cool but I presume the limit to be there in the first place because there’s a big jump in parser complexity otherwise? I dunno.

2 Likes
#257

I just like to pop in here an add one little feature request to the teletype.

I would love there to be a way to recall all stored patterns without having to reload the preset. I discussed the idea while back with Scanner Darkly but thought I would put an official request on this thread.

What I tend to do is jump around patterns 1 and 2 and randomize sections of them to create new variations but it would be great to have some command that allows you to instantly bring back the stored patterns. It would really help to create a sort of song structure to my explorations. It would almost be like going to the chorus in a song or going back to an established Melody after doing a solo.

Just thought I’d add that to the list. Thanks for making the dopest module around and thanks for continually developing it!

4 Likes
Monome ecosystem firmware development backlog