#53

Just got everything up and running. This is fantastic, thank you for putting this together!
Ive noticed a couple of things in the brief hour or so I was playing. My set up is norns-crow-ansible-jf.
Ive found turning on JF in the config page a little buggy. At first I was entering the config page as stated but I was exiting by pushing the preset button on the grid, this seemed to always disconnect JF. I was able to reconnect by using Norns and Awake as Awake has a JF reset function, I still had to select JF as an output in Awake to kick JF back into life. I did however notice if I push the button next to the USB port on Ansible to exit the config page it seemed to maintain the i2c connection.
Another thing I noticed is the LEDs on JF are extremely dim, Im presuming this is due to the volume per voice?
Would love it if by default they were bright enough to know things were happening.
I also noticed that only 3 voices are active in JF polyphonic mode instead of cycling through the 6 voices. Is the a constraint or is it possible to allow the full 6 voices to cycle?

1 Like
#54

There is a JF settiings config mode for selecting JF.VOX or JF.NOTE as well as setting your default octave - see this https://monome.org/docs/ansible/advanced/#ii-leader-mode

2 Likes
#55

Interesting, this seems to work OK on my bus that also has Teletype and a few other modules. I will need to try a bit later with just crow as a leader and see if that makes a difference. I would expect toggling JF off and on in the Ansible i2c config page to also reset JF since this also toggles the JF.MODE.

Yeah, the velocity used for notes is determined by the Kria duration parameter, so the default velocity is less than the maximum. This can wind up feeling a bit odd in other apps, interested to hear other ways to decide what value to use for velocity.

So this is because Ansible sends note-off messages and doesn’t know which mode Just Friends is in. The note-off behavior is important for being able to play Earthsea in SUSTAIN mode, for instance. When JF is in SUSTAIN mode, all six voices should be used, but in TRANSIENT and CYCLE modes it seems that an i2c command of JF.NOTE <pitch> 0 is interpreted as a zero-velocity trigger to the next voice, which winds up skipping every other voice. Through studiously listening to crows gossip I’ve gleaned that an upcoming JF firmware update would allow Ansible to (occasionally) check which mode JF is in, but I’m curious to know if @Galapagoose thinks treating JF.NOTE <shift> 0 basically as a “rest” in TRANSIENT and CYCLE modes is intended behavior.

2 Likes
#56

Thank you for clarifying some of my questions. Interesting about the JF note behaviour. I’ll be testing things out again tonight so if i find anything else thats odd ill let you know. When things do work its so much fun. Playing JF with Earthsea is wonderful. I also plugged my op-1 into Ansible and played JF like any poly synth which blew my mind :exploding_head: Thanks again for that hard work!

2 Likes
#57

This update is fantastic. I’ve had ansible for 3 years or so and it was the lead in to the whole world here. It is now what I had imagined it could be at the outset but at a fraction of the cost in funds and HP. Please direct me to further reading if available, but I’m wondering how to get TXo to do the following (could not find it):

  • How do I set the root for TXo (in Kria for example)? It doesnt seem to respond to TO.OSC.SET or similar commands

  • I thought maybe the Kria gate length setting might work to set the envelope length but they do not appear to (although i think this would be a great option).

Edit to ask if there is an amplitude setting for the TXo oscillators like Velocity for JF? Or if there is some proxy for one?

1 Like
#58

This probably is just getting immediately overridden by the TO.OSC messages Ansible is sending. I don’t know that there’s a way around this, would maybe need something like TO.OSC.OFF that behaves kind of like JF.SHIFT.

This should work, Ansible is sending TO.ENV n 1 when the gate goes high and TO.ENV n 0 when it goes low.

No, this would be cool but I already felt the velocity / duration relationship was slightly strained. Open to suggestions here, the duration alt parameter seems like one possibility though I’m hesitant about the best option for a whole UI page (and am not sure about the memory / flash requirements of an additional parameter).

2 Likes
#59

I’ve been doing a bit of testing today and I have found that TO.CV x V y can set the amplitude of each voice. I put it in the init script for my purposes but I guess it would work great dynamically too.
I was mistaken and the duration parameter is working but I’m finding it has a minimal affect. I’ll test some more. Maybe changing the default envelope decay time might give better results.
A TO.OSC.OFF or similar offset for the TXo oscillators would be amazing. Is this hard to implement? My skills are limited to playing
I’m also getting freezes across my i2c modules since putting TXo back in (with teletype, w/, jf, crow and the teletype backpack -can’t remember the name) but I will read above to trouble shoot. Thanks again for an amazing update to an amazing ecosystem

#60

Hi there, apologies if this is not the correct page to post on. I just successfully updated ansible to 3.0, but now when I power up the module with a grid, it does nothing. The grid won’t power on and TR lights 2 and 3 are on, but the module seems to be otherwise frozen/unresponsive.

#61

Weird. So does it work if you plug the grid in after powering on? Are you powering the grid directly from Ansible or using an external USB power supply?

#62

i would try to reflash and double check there were no errors. two stuck lights normally indicates a blank chip or bad startup

1 Like
#63

@csboling I’m powering direct. Reinstalled the firmware. All good now, thanks! Must have been an error as you said.

1 Like
#64

So many thanks for this update !!!
I dreamed to control er301 with my arc + ansible !
Could you share please this JSON file for we can use the ansible as i2c leader to control er301 parameters ?
It would be so great !!
I haven’t a Grid, and can’t buy one ( sold out )…
It would be so great to manage this fonction without a grid :wink:
As the ability to tune the cv outs :wink:
I’m very interested by your proposition.

1 Like
#65

I’m way late to the party; would you mind linking to info on this? I looked through the 3.1.0 documentation and didn’t see anything.

I sometimes find that the TT moves a bit faster than I’m able to realistically keep track of.

#66

they are in the official doc under Maths section: https://monome.org/docs/teletype/manual/#maths
scroll down a bit (or just do a search for N.CS).

1 Like
#67

: 0

I must’ve been looking int he wrong place. These are amazing! Gosh dang… That’s so freaking rad!

1 Like
#68

What kind of UI do you think would be a good way to program this kind of thing with an arc? Seems possible to maybe tuck away a configuration page behind some panel button combination. I also think tuning with an arc seems like a really nice feature. The trick is figuring out what kind of “menu diving” makes sense with the existing arc apps.

Accomplishing this just with JSON files is doable if that’s the semi-permanent I2C configuration you want to use, it seems like a bit of a pain to change it this way. I can try and create the JSON settings but I don’t have an ER301 to confirm them with.

1 Like
#69

Thanks so much for your answer ! And for these perfect solutions !
In fact, I think implementing these 2 configuration options would be so great and would have sens ( due to the power of the Arc and Ansible duo ).
It could be a master configuration, with impact on both Levels and Circle apps ( I like the idea that, with the er301 controled by Arc and Ansible, I can play live with the Circle or Levels switch, for to dynamically chage the er-301.
“a configuration page behind some panel button combination” would be perfect !
With an arc per i2c possibles outputs ( JF / TXo / er301 ), and a simple “two choices” ( on / off ) per ring ?
About my setup, I play with Arc > Ansible > crow > er-301.
I’ve ever write a lua script that sends prests ( tables ) to 16 SC.CV into er-301.
Does it still work if Ansible become i2c leader mode, please ?
Also, I plan to tell to ansible via crow to change Levels pattern. Could you tell me the perfect syntax for to do this ? I use ii.levels.preset(5)
Would it be possible to change also presets via crow ? To switch app ? And the Circles presets to ?
And also, When in i2c leader mode, It’s the same as when I send i2c from crow for my presets ? I must to add SC.CV objects in the er-301 ? Which adresses ?
Many thanks for your precious help !

#70

Hi All. Wondering how difficult it would be to implement a random waveform in addition to the triangle and saw options in Cycles. Thanks!

3 Likes
#71

More wave forms would be super nice for Cycles! +1

4 Likes
#72

think that should be relatively doable - i dabbled in making an arc envelope generator for ansible earlier this year with moderate success, and consulting some of the firmware wizards suggested that it would just be a matter of mapping some predefined tables to the DAC output for non-linear waveshapes

would be happy to tackle such a thing (and maybe finish that envelope generator!) if time allows in the near future

5 Likes