#213

Sharing would work fine if the library functions were shared too. :slight_smile:

But honestly, I like the shadow script idea better because it will result in less clutter … especially if the init has a shadow for its shadow :smiley:

#214

as long as it’s confined to the scene itself. but sharing a scene + global function library would not be feasible (it would replace your own library). but with being able to copy scripts from another scene you could just dedicate one scene as your global library, and the scene you share would not have a dependency on it and be still self contained.

2 Likes
#218

It bears mentioning that those are many volunteer hours.

13 Likes
#219

I urge you to calm down a bit and then re-read the discussion above. It’s very hard for me to see how you came to this perception of the situation.

Right after you asked what that person thought the “spirit of teletype” was, they answered and explained (well put if you ask me):

Several users as well as tehn himself have explained what ideas were important for the conception of teletype and thus represent the general spirit behind the design decisions. They have also outlined (better than I could have) why it may in fact represent an issue to remove limitations, particularly for the guidance of new users and less experienced programmers.

I understand that it can be frustrating to see a bunch of people argue for the exact opposite of what seems like the best solution to you, but I don’t think you’re being fair in your judgement of the situation.

I think this is the least elitist place I have so far found on the internet. Anyone who wants to partake in a discussion is actively included and everyone seems to try their best to keep discussions calm and polite.

6 Likes
#220

I think it ~can be~ an important part of the instrument. I don’t use the physical trigger inputs very often, I prefer to build scenes that self-reference and fold in on themselves into code origami. I don’t have a very large system and don’t have a lot of fun-to-control trigger sources available, and being able to call scenes from other scenes is what made me actually gel with teletype. I can code more fluidly because I’ve spent hours and hours and hours messing with it, not necessarily because of spatial dynamics. Line number usage is at work all the time with the pattern matrix.

surely this implies a sin of even greater gluttony? :wink: I’d rather put
$480 towards a dev to create a branch with additional scripts.

re. teletype as architecture
i’ve been handed a really incredible set of building tools. i have at least 7 different choices of building material in infinite amounts. amongst these tools and items are 8 doors. ive also been handed a law- because ive been handed 8 doors, i can only have 8 rooms. a pleasant house is easily within reach. but i have had to learn to enter into every creation by first fully taming my thoughts of what i want to see. a disappointing starting place, though i suppose skyscrapers do litter.

the palace isnt sacred until its built~

did anybody play simtower?

simtower-the-vertical-empire_19

#221

Love the idea. It would fit right into my current practice to set up a param knob to act as a meta param that swaps several scripts with their shadow scripts as a compositional/performative thing. I’m curious, do you have some draft syntax in your head here?

On physicality: I’ll say that I will often times just externally trigger 1 or 2 scripts, and then have those call other scripts (which aren’t physically triggered) with a bunch of EVERY's as a sort of clock division-type thing. I do not feel that this is counter to the “spirit of teletype”, as I could easily re-architect those to utilize external triggers instead.

Which leads me to something @infovore said that I’ve been thinking a lot about in terms of this thread

This is one reason why shadow scripts appeal to me. I want things to be very simple to move around and rearchitect. I do not think rearchitecting a teletype scene should feel like the undertaking of excising some piece of code in an enterprise software project. I don’t think timeline goes too far in this way, but the indirection/abstraction it enables definitely increases the risk of it’s use becoming more static and less close to modular synth patching.

Also, I definitely think any sort of solution should consider future portability as @simondemeule has mentioned a couple times.

5 Likes
#222

I got to say that at first I was very excited by the shadow scripts idea that appeared to me as a nice way to expand the lengh of initial scripts. But the more I think about it the more I feel that TIMELINE would be a better choice as it not only expand an existing functionnality (it solves the need for longer scripts) but it add a new way of thinking and organising the scenes. $$ doesn’t seem to push the TT concept further. So in short I see $$ as a way to enhance my scenes and TL as a way to explore new paths.

3 Likes
#223

+10,000,000 for Shadow Scripts. :slight_smile: It solves the “More space” dilemma while keeping things sorted in a way that is instantly familiar.

7 Likes
#224

Personally I like the shadow scripts much more than the timeline. It is unclear to me how editing the timeline would affect pieces in script that reference it. I’m a bit confused about the shadow script proposal though. Do they allow more than 6 lines? I hope so! If they are line limited than I don’t see much point.

What about patterns? They really go hand-in-hand with additional script room. I find the teletype very limiting for polyphonic sequencing now. More script room is great, and fixes some of the problem. We need more patterns too. I run out of script length now because I have to use bitwise operations to store more data per pattern. I wouldn’t have to do that if I had more patterns.

1 Like
Teletype - Programming a keyboard to send stored commands
#225

I agree

which reminds me…

patterns are a canonical part of the OG teletype core functionality that had no corresponding physical place

seems like there has always been a weird tension between direct physical links and more removed info hovering on a separate layer

imo pattern and timeline feel related
both similarly detached from a direct physical anchor (or specific use case)

7 Likes
#226

While the open discussion of features on discourse if great, it does seem that the ideas get scattered across the thread (can someone point me to the key proposal for shadow scripts?). Is there a wiki or similar that we could use to capture the proposal and options?? It might be that this could then form the basis for extending the documentation as the features get pulled into the mainline and released.

2 Likes
#227
2 Likes
#228

shadows scrips sounds like an elegant/amazing idea :slight_smile:

4 Likes
#229

nothing happening anymore overhere…
any news on this front?

4 Likes
#230

I am still hoping… :grin:

2 Likes
#231

Longer init script would be enough for me. :smiley:

#232

makes me sad that nothing really came of this

i thought the ideas exchanged were some of the most exciting i’ve ever heard of within this community

mabye the time wasn’t right for some reason

4 Likes
#233

I’m so excited about the other updates that I don’t mind if this comes sooner or later. :slight_smile:

2 Likes
#234

Definitely agree. I’d also like to voice that this thread was a super exciting to me and hope that something will come of it.

1 Like
#235

I had the chance to buy a second hand Teletype module two months ago, this module is amazing and now that I’m playing with the grid ops I’d also like a longer Init script if that’s technically possible. The 8 scripts and 6 lines per script limitation is a good exercise (like when I decided to choose a 2x84 hp case instead of a 2x104) but with the grid ops yeah a longer Init script could be useful. I also have two TXo+ and an ER-301 so the Teletype is now a major element of the case. A frustrating thing that I’ve encountered is not being able to write IF and L on the same line, I have to call another script.
IF X: L 0 15 PN 0 I RRND 256 RRND 3638

With these PRE, sometimes I wish I could “tell” the script “ go the the next line” with a symbol like “>” when I don’t have enough space to write the conditions, haha. But the new “per script” variables are already a very useful addition.

2 Likes