Satellite: run teletype scenes on ansible

[xeric]

Oh man this is a game changer – I might need to buy another Ansible!

[shellfritsch]

wow this is so cool. i can make my own ansible apps now
thank you so much for putting in the work. can’t wait to try this out.

assuming that this shouldn’t share the same i2c bus as teletype - yeah?

[scanner_darkly]

you can definitely have both on the same i2c bus as long as you don’t have multiple leaders using the bus at the same time (and even then it might just work in some cases).

[desolationjones]

Trigger 1 as a metro override is making more sense to me now. There’s value in having that method common to all Satellite scripts. I thought Ansible hardware didn’t have cable detection, though, so how does it decide when to switch between internal and external clock?

FWIW I think tying trigger input 2 and keys 1 & 2 to script calls would really open things up for the gridless. Not that there are many gridless Ansible owners, but perhaps they are employing their grids elsewhere!

And speaking of the gridless, will there be a non-grid mode method for loading scenes? I was thinking Mode key could do next scene on short press, previous scene on long press.

[shellfritsch]

@desolationjones

non-grid mode method for loading scenes?

or Mode + Key 1 (prev) / Mode + Key 2 (next)

[scanner_darkly]

@desolationjones

I thought Ansible hardware didn’t have cable detection

it does have detection on input 1.

@shellfritsch

@desolationjones

non-grid mode method for loading scenes?

or Mode + Key 1 (prev) / Mode + Key 2 (next)

yeah, this makes sense. and a long press on mode to save the current scene.

[xeric]

Cool – so triggering metro doesn’t actually have to happen at regular intervals in that case? Could I hook up a Walk trigger to input 1 and it won’t do anything until I send a trigger? Or will it be more like a tap-tempo kind of situation?

[scanner_darkly]

yeah, you can do that. i thought about implementing tap tempo for metro, but it’s something that you could just code as part of a scene.

[Justmat]

what if the inputs we’re configurable? so that something like…

sat.in 1 $3

in your TT script, would use in 1 to trig script 3 of the loaded scene.

[scanner_darkly]

that’s definitely an option. another option is adding a grid interface to map keys/inputs to scripts. not sure it’s something i would add though - trying to keep this simple, and i see satellite being something you would specifically write scenes for, so you could just make sure that anything that needs to be triggered is located in scripts 1-3. another point to consider - without a screen, it’s much more difficult to figure out what’s going on, so flexibility can come at a cost of having to check for more potential issues.

[scanner_darkly]

posted new version:

• CV outputs didn’t use correct values - fixed
• key buttons 1/2 will trigger scripts 1/2
• input 2 will trigger script 3
• long press on mode button will save current scene (white LED will blink to confirm)
• mode + key 1 will load previous scene
• mode + key 2 will load next scene

[Gexex]

attempting to flash my Ansible on mac with the update_firmware_command file returned an access error.

I’m on the admin login and get info shows full read & write access. this file is simply a shortcut for a terminal command, yes?

sorry, I’ve never had this issue flashing an Ansible firmware, whether ‘factory’ or OH.

[zebra]

open terminal, navigate to location, type
chmod +x update_firmware.command
and retry

[Gexex]

thanks, I didn’t have an opportunity to test this as I stumbled upon the cause of my issue: terminal did not like the brackets in my pathname

[shellfritsch]

thinking about using this to connect midi ops to er-301. for direct ansible “leader mode” control over 301 do i need a powered busboard/pull-ups or should it be good to go?

[csboling]

You need something with pullups, to my knowledge neither device has the hardware. Note however that the Just Friends v4.0 firmware enabled its (weak) pullups so if you are also using JF this may be sufficient.

[shellfritsch]

ah ok. thanks for clarifying.

[scanner_darkly]

this version doesn’t have the midi in ops yet, i’ll merge them to the main beta and this version in the next few days!

[scanner_darkly]

i’ve updated satellite firmware to include the new additions to the latest teletype beta (MIDI in ops, disting ex looper ops, fix for LAST).

[desolationjones]

Inspired by Mutable Stages and driven by my desperate GAS for a Buchla MARF, I present GARF, my first Satellite scene. This 4-channel, 8-step sequencer requires a F8R (or any 16n-equivalent) and allows you to independently input up to eight step lengths and step CVs for all four output channels. You should be able to run multiple Satellites with one F8R, though I haven’t tried it yet.

IN 1 jack is clock input.

IN 2 jack is a reset trigger input for all 4 channels.

Tap KEY 1 between 1 - 4 taps: this captures the current fader values as the tapped channel’s step lengths, 0-8 clock ticks each. A step length of 0 inserts a reset instead.

Tap KEY 2 between 1 - 4 taps: this captures the current fader values as the tapped channel’s step CV values.

GARF: tt00s.txt (2.1 KB)

Bonus script: F8R + Satellite becomes a 4-channel clock divider. Division on faders 1-4, delays up to 1 sec on faders 5-8. Input 1 for clock. Either keys or input 2 are resets.

SATDIV: tt01s.txt (1.2 KB)

And here is a support script for calibrating the faders within the Satellite. Set faders all to minimum then press KEY 1 to set minimum fader calibration. Set faders all to maximum then press KEY 2 to set maximum fader calibration.

FADERCAL: tt02s.txt (1.1 KB)

EDIT: Apparently my latest revision broke the script on Satellite but not Teletype. @scanner_darkly is there an issue with the STATE OP on Satellite for determining whether a key is held?
EDITEDIT: Fixed! And I have confirmed that STATE is not working, neither is SCRIPT.POL for key release events.