#131

apologies - looks like the instructions on that page weren’t updated indeed. fixed now, added the diagram to that page as well.

#132

@scanner_darkly did the teletype sync function get implemented so far?
Thanks!

#133

just to make sure, you mean having a teletype op to send a clock to orca’s heart? unfortunately, in the last couple of months had zero time for coding as i was going through the hell of painting my apartment. just got back to OH last week and i’m refactoring it so will be a while before a new version.

if you use it on a module with a trigger input (like ww or ansible) you could just use a trigger output on teletype and sync it that way as a workaround.

2 Likes
#134

thanks for the reply @scanner_darkly
Yes i meant running orcas hearth on teletype, and having it synced to an external clock. I think i read it was a future feature?
Good luck with the painting!
cheers

#135

edit: confirmed it does work that way and updated the doc.

patch a clock source to trigger input 1. you will also want to turn off the internal clock (since teletype doesn’t detect when something is patched to trigger inputs), you can do it on the delays page, 3rd button from the top in the rightmost column. although leaving it on when using an external clock can make for some interesting irregular rhythms too!

1 Like
#136

Thanks @scanner_darkly sorry i did not have the time to test yesterday, it’s great news to know the teletype can be clocked! it’s makes it very usable in an environment!
gracias

1 Like
#138

Diving into OH again, so inspiring. Here’s a noodles from today - OH sequencing JF/Rings (fm op mode)/Plaits (granular cloud mode AUX out (sines) into wavefolder) and Plonk (bass). Little bit of 33rpm wow from Gigahertz Wow VST and room reverb from Valhalla.

4 Likes
#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