#337

Thank you!

What I’m interested in are vivid harmonic modulations… easy to implement transposition with JF.SHIFT, but not in combination with timed scale changes. Perhaps a more interesting-sounding approach would be sequencing just friends TIME and INTONE outside just type mode, but I feel closer to something immediately beautiful with the impossible–all i2c–approach.

I understand this could be accomplished with kria’s metasequencing, which I’ve found daunting for some reason. Or I suppose teletype control over ansible’s leader/follower mode could solve my problem easily… switching modes within a script, but that seems a funny workaround in this case.

#338

New build in the top post (7a8f852) contains (hopefully) fixed MIDI tuning behavior, and the option for a reset pulse in Kria to reset the metapattern playhead as well as the pattern playhead. This was mentioned quite a while ago, sorry for the delay. Access it by holding panel key 2 to access the config page and then toggling the “pattern” key on the grid (furthest bottom-right). Several users have requested this functionality, including @nmihalevich, @gebeata

I’m sure some folks are itching for Ansible leader mode support for all the new W/ I2C functionality – I’ve got loads of ideas for this but it will take some time. Wanted to knock out some of these outstanding issues and feature asks first.

9 Likes
#339

I understand not wanting to overload jf’s mix out, but i’m finding the volumes too low from ansible leader mode—far quieter than any other implementation of just type in my setup so far (none of which have clipped the output that I can remember).

#340

This was a bit of a design conundrum but the goal is to let you use the Kria duration parameter to control velocity so you can manipulate dynamics in your sequence. The values were chosen to have as much range as possible for this parameter. For modes other than Kria this is a bit weird, I’m interested in hearing feedback about what kind of UI you’d like to see for controlling JF velocity in other modes.

1 Like
#341

I remember that discussion, but that feature doesn’t seem to be working anymore. I usually have JF in sustain mode for detailed articulations, and the duration page is adjusting note-off-time. For my purposes, this is great: I prefer to use a filter or lpg after JF instead of adjusting velocity in kria.

But I did just test transient mode, and velocity is not effected by duration page… at least for me.

1 Like
#342

Great catch, really not sure what happened here but I believe it should be fixed in the top post (77f5309). Also fixed this issue where velocity values did not get reset when exiting leader mode.

3 Likes
#343

i’ve added the ability to control expert sleepers disting ex as a follower directly from ansible, beta firmware in the OP (contains everything from the previous beta build).

to enable, change the disting i2c address to 65 (Settings -> MIDI / I2C -> I2C address), then follow the steps described here. you should now see 4 follower buttons: just friends / telexo / er-301 / disting ex.

if you open the follower config page, there are 4 modes available for disting ex:

  • SD multisample, voices allocated by disting ex
  • SD multisample, fixed voices
  • MIDI (via a MIDI breakout) channel 1
  • MIDI channels 1-4

for meadowphysics mode 1 is best as it doesn’t cut off previous notes (it only sends 1 voice). if you want to use disting chord / arpeggiator functionality, also use mode 1 (due to how disting works). i think there are still some bugs when too many notes are playing - if you run into this, try reducing env time.

the very cool thing about disting ex is that it has built in pullups - so you don’t need any extra hardware other than a cable to connect i2c!

video demos:

string chords with earthsea
meadowphysics music box
digitone sequenced by kria

12 Likes
Expert Sleepers Disting EX
#344

@scanner_darkly @csboling is it about time for a new release?

3 Likes
#345

Yes, I think there are several important bug fixes it would be good to get out there. A few outstanding things:

  • We should get the new Disting EX functionality merged in.
  • I’ve PMed some users of older edition grid / arc for help testing a build that might resolve the longstanding timing glitch on USB connect issue. If you use older edition monome controllers with Ansible and would like to help test, please PM me!
  • There is an issue with how note tying interacts with the new Just Friends 4.0 firmware. I’ve been chatting with Trent a bit about how best to resolve this, the behavior in the currently posted beta might be confusing.
2 Likes
#346

Is there anything special that needs to be set on the Disting? My bus is Ansible, Crow, JF, and Disting. Ansible can play JF without trouble but no luck on Disting. It was locking up because of a flipped ii cable, but it’s set right now and no locks, Disting just isn’t responding when enabled in Ansible settings.

The i2c history isn’t showing anything either which is troubling.

#347

forgot to add - you need to change i2c address on the disting to 65:

Settings -> MIDI / I2C -> I2C address

if it still doesn’t work, try enabling pullups on crow and disabling them on disting.

1 Like
#348

Hot damn! i2c channel to 65 did the trick. This feels like magic. Thank you!

1 Like
#349

great to hear! do you have pullups enabled on the disting?

(should mention that 65 is also the address to use when using disting ex with teletype)

#350

The pullups are enabled. Even with Crow on the same bus, Disting does not respond without its own pullups enabled.

1 Like
#352

Found a bug on ansimble in midi to cv (mono voice) mode. Sometimes the gate output freezes and no longer responds to keyboard presses. It does switch back to normal operation sometimes, but most of times I had to replug the arturia keystep out of ansimble running the latest firmware. My guess is that when you start playing legato the gate output locks up.

1 Like
#353

Using the beta build from July 18th on the Kria Presets pages I have 5 lit buttons in the 6th column. The pattern is one at bottom, one off above that, and then four dimmed buttons. These are not on the right 8x8 side of the grid but on the left. If I press them, I cannot turn them off. The bottom one just flashes bright when I press it while the 4 above it can be toggled bright or dim but not off.

#354

this sounds like the i2c leader mode settings.

Currently, the only interface for turning on leader mode uses a grid. In any grid application, go to the preset page by pressing the button next to the USB port. Follower device toggles are arranged vertically, just left of center.

2 Likes
Monome ansible kria in depth overview and tutorial
#355

Hello,

I have a serious issue with Ansible since I have Disting Ex on my i2c bus.
Sequencing with Kria work but when I change the app, my i2c crash and nothing respond to i2c (Txo, ER301, JF and Disting). I also try to send command from TT to Txo or Ansible in TT mode but nothing respond.
I have to power off, unplug Disting’s i2c cable, power on.
if I want to sequence the disting again I must go back to the Kria application (because the other apps cause the i2C to crash), then, again turn off, reconnect the i2c cable from the disting, then turn on again.

My configuration is (on my TT i2c bus) :

ER301, SS, Ansible x2, Txi, Txo, TT, Crow, Disting.

TT, Ansible and Disting have all the last beta firmware.
All the applications work perfect when the disting is not connected on the bus.

#356

Can you try and reproduce the issue with as few devices on the bus as possible?

#357

Ok yes, so I have test with, on the bus of TT, Ansible x1, Txo and Disting. It’s the same problem. When I skip to the other apps it crash all my i2C connections.
More précisions for debugging it.
Before power off I have to switch off Disting i2C. (It’s not necessary to unplug the cable)
Power off.
Then power on.

I have to switch off i2C Disting before to change app. Then switch ON and it’s work.

I2c also crash when I reset a blank preset (from the config menu when i2C Disting is active)
I also try an other i2C cable but nothing change.