#249

is it dangerous to run your grid off the teletype? i just installed the grid integration firmware and i don’t have an offworld yet so i tried plugging it into the grid and it seems to work. i just finished the trigger visualizer here: https://github.com/scanner-darkly/teletype/wiki/STARTING-SIMPLE and found that i could illuminate all of the grid buttons from teletype power by pressing all 8 buttons at once. it does get a little bit flickery with all the buttons lit up, but it’s flicker free with 7 of 8 buttons held down (112 grid buttons fully illuminated).

#250

i’m not sure how safe it is, but as there might be a chance it could damage it avoiding it would be probably a prudent thing to do.

you can do quite a bit with visualizer now, it might actually be an even better way to go through the studies as you don’t have to switch as often.

#251

hey guys probably a dumb question, just got delivered a TT and willing to give @scanner_darkly’s firmware a shot but how do you guys alternate coding/gridding in an easy way? is the only solution here to just plug keyboard -> code a little -> unplug keyboard -> plug grid -> test ?

Is that the workflow? thanks

1 Like
#252

Welcome (back) to the TT !
Well, yeah. You got it right. But you can do quite a lot from the Grid Simulator.

1 Like
#253

Ok bein merci @chapelierfou! will give that a go, can’t wait to try your rene simulator :slight_smile:

1 Like
#254

Good you’re asking! I have recently bought some parts for a solution… It’s ugly, but has been working great so far…

I got this usb switch:

Then I use two of these:

And a A-A cable which goes from the switchbox to teletype… Then the Keyboard to one “input” and the grid to the other, each via these adapters. Don’t forget to power the grid of course!!! I have a (monome) switch in between the grid connection.

Again, not pretty, but have it vertically standing at the side of my case, the long adapters hidden behind, and I can switch focus/input with the press of a button. (of course grid interaction stops when the focus is on the keyboard)

One caveat I found: some cables A-B wouldn’t work for some reason. Also had to sometimes re-power via the monome switch to re-gain focus on the grid. Using another cable fixed the issues I had. Might have been broken or poor quality cables. But this is still only tested for a few hours.

1 Like
#255

Oh that’s great, thanks for the heads up @sakul ! :slight_smile:

#256

Well I also use the (monome) switch with earthsea, so this isn’t an option for me.
BUT: My understanding is that monome switch powers the device on the USB A Port. I would expect this not be invertible. But someone with better understanding of the circuit would have to chime in sorry…

Edit: We are pretty OT. sorry guys! @Admins might move these to new thread…

#257

yeah never mind I actually don’t think it could work but your solution is great (and cheap!) thanks

1 Like
#258

Just a though:

G.GBTN.L group odd_level even_level
“set brightness level for all buttons in the group”

For this op, would it be possible to make it so that if you only enter 1 number at the end it will make the level uniform? Striped colour is cool but would be nice to get those 2 extra characters when not using (which for me so far has been the vast majority) :slight_smile:

#259

unfortunately not possible to have a variable number of parameters… it would need to be a separate op, and i think if it was added then being able to specify 2 different levels would become too much of a special case, so wouldn’t deserve its own op. so maybe we should just change it to G.GBTN.L group level?

#260

sorry for being dense, but I just made it through the whole grid studies and i still have no idea how to access the grid visualizer on the teletype. the first page of the studies mentions it:

“the grid visualization page which we’ll cover in a bit”

but it never came up again. is there somewhere in the docs that i missed where it is covered?

#261

In that case then I would probably leave it as is - it’s a fun feature and only 2 characters extra.

CTRL G on the live page

2 Likes
#262

this is a great find - i did consider giving something like that a try, but wasn’t sure it would work. if it does this would simplify things considerably!

#263

yeah, sorry, at this point it’s a race between me finishing the firmware or updating the docs, but i really need to describe it somewhere…

as @ghost mentioned, on live screen use CTRL-G to turn the grid visualizer on. press it again to enter the full view, then again to go back to live (all the usual keys still work so you can always switch to scripts/pattern view when you in grid visualizer view).

CTRL-arrow keys will move the selection. CTRL-SHIFT-arrow keys will define an area. the right side shows the current position and the area width and height. CTRL-Prt Sc will input them in the command line - handy for creating new controls. CTRL-space will emulate grid press. CTRL-/ switches between the upper and lower halves.

when you in full view you don’t have to press CTRL - this is so you can use grid scenes without a grid easily.

4 Likes
#264

With the MLR scene, did you have to use a delay on the trigger pulse after setting the slice index on the 301? I’m making a slice triggering scene and I’m finding that I need to set a ~12ms delay on the trigger to have the right slice be set. Was that your experience too or did you find a better workaround?

#265

to get slice selection working reliably on er-301 here is what i did:

  • a fixed delay unit after the trigger, set to 100% wet and 11ms. not sure if a shorter delay would work, need to experiment with it some more

  • sample player mode set to 12TET, this means for note selection i can simply do CV 1 N X where X is the slice number

3 Likes
#266

ooh fixed delay on the 301 side is a good idea. do you know if the cause of the lag on the teletype side or the 301?

#267

yeah, doing it on the er-301 side is really neat as it simplifies scripts quite a bit!

the lag is probably just due to the fact that CVs can’t change momentarily, and it’s likely on both sides. i’m curious though, will check with a scope when i get a chance.

1 Like
#268

Is scene backup and restore working in the latest build?
If there’s a parsing problem with one of the scripts, does it cause all scripts to fail to restore?
I have 22 scenes, most of which I’ve edited in a text editor on a computer (yes, I know that’s a no-no, but seriously?) I know I need to be on the lookout to ensure that LF line endings are in use. Any other gotchas I should be aware of?