#139

sounds lovely, thank you for posting it!

1 Like
#140

Hi @scanner_darkly orcas heart has already taken over on of my ansibles and one teletype!
What a great script!
Any new on implementing wave changing of the connected txo?
Many thanks!

2 Likes
#141

thank you! nothing new i’m afraid - i’m still in the middle of a big re-write (basically rewriting orca’s heart from scratch, with the goal of re-using the same code for different platforms), and that got delayed by various things. not sure yet whether support of txo waveforms and additional sound parameters is something i’ll add to the existing version or the new one.

i am planning a small update to the existing version soon though, so will consider this!

1 Like
#142

thanks for the detailed info @scanner_darkly looking forward to the new version! don’t want to derail the post but could polyearthsea be implemented on teletype?
Thanks a lot

#143

i did get it running on teletype when i added teletype support to multipass. just need to decide how to use the display - i’ll add it to the todo list.

1 Like
#144

Thanks @scanner_darkly!

#145

Hi I have OH on my Ansible and would like to use it with my i2C device JF, ER301 and Txo. If I understand well I need a powered bus. So, I have shape some cables to adapt the powered bus original designed for the Teletype.
But it seem not work for me. Is it possible to use the powered bus on the Ansible ?

#146

can you post a picture of the powered bus and how you have it connected?

#147

image
image3024×4032 3.47 MB
image
image3024×4032 3.26 MB

Yes here a picture @scanner_darkly
I hope the photos are clear enough.

#148

@scanner_darkly the Ansible power on and works but I am not able to control the JF Er301 and Txo thru i2C

#149

a bit difficult to say from the pics - check that SDA is connected to SDA, SCL to SCL and GND to GND (and GND should go to where the white lines are on the backpack).

are you able to control them from the original ansible firmware? also, try connecting only one more device to i2c and see if you can get that working. i assume you saw this? https://github.com/scanner-darkly/orcas-heart/wiki/i2c-setup

1 Like
#150

@scanner_darkly i ]m kind of confused with orcas heart on teletype.

On the docu page it says:

modules that have a dedicated clock input can be clocked externally. on ansible and teletype trigger input 1 is the clock input. on ansible trigger input 2 is reset. since teletype is not capable of detecting whether something was connected to a trigger input, you will need to stop the internal clock manually - that’s 3rd button from the top in the rightmost column on the delays page.

But then:

teletype:

trigger input 1 is reserved for clock in (future version)
trigger input 2 is reset
trigger input 3 toggles between scales
trigger input 4 toggles scale A transposition by an octave up
trigger input 4 toggles scale B transposition by an octave up
trigger inputs 5-8 not currently used
CV input not currently used

So can trigger input 2 on teletype be used or not as a clock reset?

Many thanks!

#151

yes, trigger input 2 on teletype should work as reset and trigger input 1 as clock input (you want to disable the internal clock when using the clock input on teletype). i’ve updated the doc.

1 Like
#152

Ok thanks @scanner_darkly I have check and all was connected, change nothing but it’s work now :thinking:
TT bus work with Ansible :heart_eyes::smiling_face_with_three_hearts:

1 Like
#153

I have 2 TXo and 2 Ansible on my TT bus.
Ansible 1 is « classic app »(Kria etc…)
Ansible 2 is OH

I would like control by i2C, 1 Txo with classic app from Ansible 1 and the other Txo with OH from Ansible 2.

Is it possible to modify the firmware of Ansible 1 or 2. Or maybe there is a script that I can send from teletype to Ansible for routing the i2C message to the Txo 1 or Txo2 ?

#154

no, ansible currently can only send to one txo, same with orca’s heart. it’s not just a matter of changing the firmware - you would be running a multi leader set up, which is not currently supported and can cause i2c issues. the easiest solution is to just put them on separate i2c buses.

1 Like
#155

Ok thank you for clarifying it.
Maybe one day it will possible to « cross » 2 (or more) i2C devices…

1 Like
#156

Hi @scanner_darkly hope you are doing well!
Im revisiting this teletype script, and i have been reading on the docs that 2 txo can be controlled if they have different i2c addresses?
Also i think i asked you some time ago, would it be hard to choose waveform from the txos? Is there a way i could look into this?
Thanks a bunch!

#157

yeah, you can have 8 voices with 2 txos. you don’t need to change any settings in orca’s heart itself, just change the address on one of the txos for outputs 5-8 as described here: GitHub - bpcmusic/telex: Open source modules designed to interface with and expand the capabilities of Monome's Teletype.

it’s not possible to change waveforms from orca’s heart currently (it might be in a future version). one option would be to run orca’s heart on a different module and use teletype to send waveform commands to telexo (you would have to stop orca’s heart while you do that to avoid issues with multiple leaders sending at the same time).

#158

Thanks for the info and support @scanner_darkly . I have the two txo already setup with different addresses with the jumpers on the back of the pcbs.
I think i will use my teletype with its outputs and use the txo for other duties then.
Thanks for your help!
Cheers