#167

Possible bug report for @scanner_darkly.

Record two simple patterns in both slots one and two.
Enter pattern select mode.
Activate pattern 2. All good.
Then activate pattern 1.
No gates seem to be sent for pattern 1.
Going back to pattern 2, gates appear AOK.

Exiting pattern select mode seems to make things ok again.

Might be operator error. Will fiddle more today.

UPDATE : it appears to be some kind of “stuck note” issue. If you switch patterns at the exact time a particular note is playing, that note appears to get stuck on, effectively taking voice priority, pushing notes in the new pattern to the next voice … if that makes sense.

3 Likes
#168

how was your voice allocation set up?

it’s supposed to kill any pattern notes that are still active when switching patterns (or restarting the same pattern), but possible there is a bug somewhere, and it doesn’t happen. if you can reliably reproduce, could you try stopping playback and see if that clears the hanging note?

if it doesn’t, can you try changing the edge mode between hold and fixed and see if that helps? (it kills both pattern and live notes when you change the edge mode).

#169

I know you aren’t currently adding features to this, but an idea…

What if we could select both the Forward and Reverse runes simultaneously to activate some sort of pendulum playback? At first I was thinking about another rune altogether, but the layout of that page feels nice the way it is.

1 Like
#170

unless it’s somehow really time consuming to implement i’ll consider including it!

3 Likes
#171

Just installed the firmware for this and getting just the slightest semi-hang of it… wow, so much fun! Good job @scanner_darkly scanner_darkly : - )

#172

new build, incorporates the official 1.6.0 release:

ansible.hex (265.6 KB)
ansible.zip (86.4 KB)

there were some merge conflicts so possible some bugs crept in. as i’m concentrating on finishing teletype community help with testing will be much appreciated!

8 Likes
Ansible 1.6
Ansible 1.6
#173

As soon as I can steal another A->A cable from work ill get this up and running!

1 Like
#174

When I try to update my Ansible with this hex/firmware, it seems to just blank out the device. After updating, Grid don’t light up when I connect it to Ansible. Tried several times, switching back and forth between this and the 1.6.0 firmware.

#175

i just tried using both the hex file and the zip file posted above and can update successfully with both.
so the 1.6.0 works fine but this one doesn’t? can you check that it downloaded fully? the hex file size should be 271945 bytes.

the only other thing i can think of, there will be a pause 3-4 seconds when you run it for the first time after installing a new firmware while it initializes blank presets. but you will get that with 1.6.0 as well.

anybody else is not able to install the firmware?

#176

Hm, weird! I’ll give it another try asap.

#177

I am about to install now, will let you know in an edit.

Edit: Everything worked out great for both of my Ansibles. Thanks, @scanner_darkly!
@Plym, I hope it works out!

2 Likes
#178

Oh, great. Sorry for the confusion @scanner_darkly! I’ll give it another try tonight. Thank you for the amazing job with this.

1 Like
#179

welp, this just rejigged my ‘minimal performance rig’ plans…

incredible work, as ever.

any shot this is still planned for a final release?

2 Likes
#180

yep, i’ll include it when i get back to working on this again. it’ll be a few months though before it happens!

3 Likes
#181

it is possible that the midi-cv tools are broken on this release?
i’m trying to use a novation remote sl 25 mk2 (which works with es FH-1) with ansible with no results. no light on the led either.

#182

that part of code wasn’t touched at all, but possible that somehow a bug was introduced. are you able to try the official 1.6.1 release and see if the issue exists there as well? also, you need to have the midi controller connected before you turn it on as that’s how ansible determines which mode to run.

#183

mmm thanks… i’m thinking maybe it’s because the novation always starts on Automap mode… perhaps it’s not recognized by ansible at power up…

in fact if i power it externally, exit automap and then power up ansible i now can see the white led. but still cycling thru all 16 midi channels no response. also: if i press the preset button the led goes off and it doesnt turn on after power cycle. i have to plug in the grid, power off, then power on again with the keyboard to have the white led back on. long press of the preset button doesn’t cycle thru the various modes either. i think this keyboard is not recognized by the module.

#184

yeah, not sure - sorry, i don’t know much about the midi implementation. if you could try the official 1.6.1 version that would help isolate the issue.

#185

thanks anyway :slightly_smiling_face:

#186

I did not know about this until now

what on earth? you are incredible @scanner_darkly !

9 Likes