as @okyeron mentions, make sure polyES is set to leader mode and you have some voices mapped to JF outputs.

i asssume you are powering the backpack if it worked with teletype removed. if you only use ansible + backpack + JF, the backpack must be powered.

to help isolating the problem, try just ansible, backpack and JF with no other modules connected or powered. also try teletype + backpack + JF and see if that works.

Finally in front of my case and removed everything except Ansible, JF, and backpack (powered). Here are my findings: still doesn’t work with this config but when I attach TT to the backpack again, it works again. Does this mean anything to you? I swear I had it working for a day or so without TT hooked up, before I rearranged my case, finding this problem. I tried two JF’s and different i2c cables. So what is TT doing to this equation that makes it work, I wonder?

I’d love to not have TT in my case right now and I’m hoping @bpcmusic stocks some txb’s again soon so I can skip all of this. I appreciate any and all help :slight_smile: thanks!

very strange - it could also be the pull-up resistor values, adding tt to the setup would affect that. but the backpack should have its own, i’m pretty sure i tested the ansible + backpack + jf setup combo, but will test it again. could you post pics of both sides of the backpack?

going to ask mods to move the latest posts to the i2c guide thread as it might be helpful for others troubleshooting i2c issues and it doesn’t sound like it’s polyES related.

1 Like

Teletype needed up selling so this is no longer relevant but thank you for your willingness to help so much. I wonder if I’m going to run into an issue with the new kria i2c that you suggested. Will I need a txb for that as well? Maybe I misunderstood but is ansible able to be a leader and does that mean I don’t need txb?

if you use ansible as a leader you will need to have something provide the pullup resistors and power to the i2c, so yes, you’ll need either a backpack or txb.

I feel like I’ve learned a ton reading the wiki and watching the videos, but haven’t seen anything that explains how to clear a pattern. Did I miss that somewhere?

there is no explicit action to clear a pattern, it happens when you record a new one (and if you arm it for recording it won’t delete the old pattern until you actually enter the first note, so you can always cancel it if you armed it accidentally without losing the pattern).

you could just record a rest and this will create an ā€œemptyā€ pattern.

1 Like

Pardon my ignorance, but how would you record a rest? As I understand it, recording on an armed track doesn’t actually begin until a note is played. Or can I arm, play nothing, and press playback to record a rest? Not in front of my system now, but that is what I have tried to do with no luck in the past.

yeah, you need to record a note or a rest at least for recording to happen. to insert a rest use the top right button.

That did the trick. Thank you @scanner_darkly

1 Like

So I’ve been spending some time trying to integrate polyearthsea into more complex patches. I’m looking for ideas to help ā€œsyncā€ things up, if that’s a possibility. Here is my set up.

Main voice is a frozen granular sample from a ZOIA that has a pulsing quality to it. The pulses drive an envelope follower set to ā€œcatchā€ the rhythm and goes to CV out on the ZOIA. That CV out gets converted via maths as a trigger and then clocks a Pam’s New Workout. This part seems fine. I can clock a snare in the rack for example, and it keeps time with the pulsing from the ZOIA.

When I send a clock into WW running polyearthsea, this is where I run into timing issues. What I hear after recording a brief phrase, or just even one note, seems to drift in and out of sync with the rest of the system. The snare on 2 and 4, and the pulsing granular sample are in sync with each other. I can’t tell if it’s slow, or fast, but can confirm the clock outs on the PNW driving the clock in in WW and the snare sample are both identical. I went as far as swapping channels to see if the snare would start drifting, but no luck. Snare would still be in sync, and polyearthsea phrases would be phasing in and out of sync.

Any thoughts?

I can sync polyearthsea with a clocked sample player in an ER301, using the pattern start trigger as a clock. But trying to bring timing into polyearthsea is where I’m finding difficulty.

would you be able to make a short video showing the issue? you can DM me if you don’t want to post here.

Definitely, I’ll put together something this weekend with a few examples. Thanks!

1 Like

Coming back to this after some time. Am using with Ansible. Note outputs work fine but gates seem to be emitting envelopes, with a variable amplitude and base CV level between channels. Can’t see any documentation of such behaviour here or in the instructions. Of course the possibility to output envelopes would be cool but is this expected behaviour…?

Am using with TXo CV/Gate and all working perfectly

Thanks!

you mean gate outputs on ansible itself? it’s not possible technically as these outputs can only output 0 or 10V, there is no way to set them to anything other than that. on telexo outputs you can use the voice config page to select either using TXo outputs as oscillators (in which case you’ll get envelopes applied to the outputs, and you can change attack/decay for each output on the output parameter page) or as CV/gates.

I do indeed mean that Gate (TR) outputs on Ansible itself. My understanding was that they could only be 0 or 10V but I’m definitely getting other values, with some slewing between.

0-1.7V on TR1
1.1-1.3V on TR2
0-0.2V on TR3
0.13- 0.17V on TR4
(measured on o’Tool)

When I last tested I think these values were higher

Super strange…

TXo all working fine thanks

hmm that’s super strange. can you try the original ansible firmware and see if you’re seeing a similar behaviour?

Sure thing. I’ll test it out next week when I have some time

1 Like

Reinstalled standard FW - all normal. Reinstalled poly earthsea FW - now Ansible gates working as expected. Seemingly resolved. How strange… thanks for the help. Will let you know if I come across any other wonky behaviour.

very strange. i doubt this is related to the firmware as there is just no way to specify anything other than ā€œonā€ or ā€œoffā€ for gate outputs. could be some hardware issue, perhaps it might indicate that it’s underpowered? (this is just a wild guess though).

1 Like