#10

I can’t remember - do the monobright grid leds have a threshold brightness level?

I can probably variable-ize the brightness levels and make it an easy diy script edit to adjust for a monobright.

I will also make check and make a tweak for grid width so a 64 works properly

2 Likes
#11

I think the threshold is 15 or 16, which ever the brightest setting is.

#12

4 steps per-led variable brightness for 2011 grids…

#13

right - but would still need to dig in the code to see what the (varibright) level values are mapped to.

#14

Acoustic guitar through randomized sequences of gates. Took awhile to sort a good BPM to align with the strumming: too fast and the chord ended too late; too slow and the gating ended before the chord fully rang out. This is a little first-time experiment with the new Torii script (version 0.3.0) by @okyeron running on a Fates (aka an open-source Monome Norns port). A Zoom H4n served as the microphone, and that’s a little Boombotix REX speaker in the foreground.

7 Likes
#15

Update 0.3.2

  • added param grouping/separators (requires norns 200323)
  • moved to local beatclock lib to add params separator
  • added variable array for grid led brightness, so you can tweak those levels for older non-varibright grids.
9 Likes
#16

So much fun to run my Volca Keys through this, straight back to 90’s trance heaven :stuck_out_tongue:

FYI if anyone tries this and gets no output, you likely need to update the R engine (via Maiden) and reboot.

2 Likes
#17

finally had a go with this one tonight.
super cool!

can’t seem to get MIDI clock input working though.
(i know it’s still a work in progress)
:slight_smile:
when i set Torii to EXT clock it just stops until i set it back to INTERNAL clock.

just to make sure i was getting clock into norns i ran the script VIALS and it was working with EXT clock.

#18

I’ll check it out.

How is clock being sent? (What device) Are you sending a start/stop from there at some point?

1 Like
#19

Hi there, love the script! Not sure if it was just my set up but do the gates still let through some dry signal when they are fully closed(active)? It sounded like I was always getting some amount of dry level through. Would be great to have control over the dry/wet amounts. Thanks!

#20

Check your MIX page levels to see if MON is turned up at all. That’s pretty much the dry/wet control right now.

I’ve not tested with the new update yet, so there might be some weirdness

1 Like
#21

sending from a NAVA 9 drum machine into a iConnect box.

yes…start and stop messages.

thanks for the help!!!

1 Like
#22

Thanks, that did it fine!

#23

Updated to v0.4.0

  • reworked to implement global clock
  • requires norns version 200424
  • submitted to community script repo
7 Likes
#24

question re:global clock and crow integration. I’ve updated to the latest version of Torii, and i’m trying to clock it externally via crow. I can select crow as a clock input from the global clock settings, and it appears to be picking up the correct bpm. but, in the Torii params, the choices are only clock internally or externally. theres no specific setting for crow. and when I select external, it doesn’t seem to be picking up the global clock.

i know you’re hauling ass on the mi engines (which will be epic), so no rush on this, but when you get a chance, would be greatful if you could take a look see

#25

huh… I can’t remember what I did there. Will need to take a look.

There might be a left-over param thing I didn’t fix for global clock. I’d think the CLOCK params would override. (like ignore the params int/ext thing?)

Since I don’t have crow its hard to test that use-case.

@gnome666 Something sounds wrong about this. In the current script there are no other params for clock internal/external. Only global clock in the CLOCK section.

Are you seeing v0.4.0 at the top of the script?

#26

hey ya!

been delving into Torii as of late.
:stuck_out_tongue:
would it be possible to add clock dividing to Torii so the user could run the sequence at different speeds?

also…
when i activate a step i can’t turn it back off or remove it.
the light will turn off on the bottom Grid row but the audio will still pass through.

it also has a longer envelope time when i activate a step instead of the short envelope that it seems to default to at startup.

to get around that i have to hit random(K2) so it will “reset” any steps that i may have activated.

#27

Hey Spike! thanks for the report.

I’ll have to take a look at these things. I probably don’t have the steps checking env params when they get added.

How are you activating the step and then removing it? From the encoders or grid?

Clock dividing seems doable tho.

1 Like
#28

i’m activating steps from a Grid.

#29

update v0.5.1

  • added clock divider (see params)
  • fixed grid keys activation for steps
  • row 7 will clear the env amount if hit while selected

Todo:

  • look at env changes getting properly updated

Questions:
From the grid - Currently a step needs to be activated (row 8) and have an envelope amount (rows 7-1) for it to play. I don’t have a way to zero the env from the grid tho. Is that needed?

1 Like