#43

Not sure if this is the proper thread to ask but, I know a previous version of Kria had clock multiplication and division per channel and the multiplication was removed due to frequent errors… Any chance that feature may resurface? It would be incredibly useful for building polyrhythms. I’ve tried clocking Kria very fast and dividing each channel to compensate but it’s not nearly as intuitive as the old firmware seemed to be (and limits division possibilities heavily).

#44

Updated to1.6.1 (april 17 2018) to get secondary functions (note repeat ,etc). Update said success, and new functions released in that firmware are now working.

Have flipped between kria and MP, no change. Also unplugged grid and plugged in ARC, still no change. Power cycled and entire case and flashed firmware a 2nd time with same version. Light is still on.

#45

can you try flashing an older version?

otherwise this seems like some hardware glitch. if so, e-mail info@monome.org

#46

Thanks for your help. I went back down to 1.52 and then back up to 1.61 again with no improvement. Just noticed as well, the 4th trigger does NOT emit a trigger either, I thought it was just the light.

I have a second Ansible next to it that works fine at 1.61, same case, same update procedure so I assume it’s hardware. Sent monome an email.

Thanks again,
Josh

#47

Pretty sure this isn’t a bug, but an issue with my specific unit but I don’t know where else to post regarding this.

Basically my new Ansible doesn’t send cv signals in any mode, and the cv column lights don’t blink or anything upon powering up. I installed the module in my case and updated the firmware first thing (cv lights blinked on during initial startup, I’m pretty sure) but acting as midi host or with a Grid plugged in, only gate signals go out.

I’ve tried downgrading the fw but the issue persists.

Thanks

#48

I’d like to report a bug that involves the OP-1 and Ansible in Midi (mono) mode.

If I try to use the OP-1 “pitch-shift” (shift and either ‘<’ or ‘>’) it will freeze ansible requiring the usb cable to be removed and reinserted before it becomes responsive again.

Monome ecosystem firmware development backlog
#49

I know this is an old topic, but it seemed like possibly the best place to ask about this, rather than starting a new thread. I have two Ansibles in my case currently, one running Kria and one running Meadowphysics. I was playing a set on Twitch last Friday night (http://www.twitch.tv/pacificnorthwes/), and I noticed (not for the first time) that when I was moving the usb cable from my Grid between Ansibles, that the clock/tempo would often stutter a bit, resulting in Kria becoming out of phase with my drum machine (TR-09, providing clock pulse). Meadowphysics may have had the same issue, but I wasn’t paying as much attention there and it wouldn’t be as obvious in my purposes whether it was out of phase. Any way to avoid this? Would using something like the Switch help?

If it matters, my clock is running through a passive mult, but no other clocked modules seemed to have any hiccups.

#50

I believe this has been a known issue for a while, I may be able to try and investigate.

2 Likes
#51

Ah, cool. I was trying to find whether anyone else had recorded it and was looking for clock, tempo, stutter, phase, phasing, etc. :slight_smile:

#52

i seem to recall there was a discussion about this somewhere on lines but can’t find it now. i think it’s related to this delay:

and i think i made an experimental firmware that had the delay removed - @jlmitch5 was it for you? not sure why the delay was added, and it’s possible that removing it will work for some grids but not for others. might be worth experimenting with it though.

1 Like
Ansible / Switch Bugs
#53

I remember there was some tempo stalling when switching grid between poly earth sea (white whale) and teletype using 2:1…there was also an issue of missed keystrokes on some mechanical keyboards. Could it be related to either of those by chance?

#54

yeah sounds like the first one (not related to the keyboard issue, that was a separate issue). do you remember by any chance where we discussed it?

#55

I went looking and can’t find anything, sorry! I will say I don’t remember installing an experimental firmware that wasn’t start/end updates on grid control mode, or the keyboard thing

1 Like
#56

And this is why we comment our code. :smiley: Thanks for your quick help, folks!

#57

found it! :slight_smile:

also see this reply and this reply

and the fix was indeed to comment out the delay_ms(200) line.

2 Likes
#58

indeed :wink:

3 Likes
#59

Hello.

Just got Ansible.
When I run Kria or the two other app, there is no Cv out from the outputs. Only a low static negative voltage.
Is there something wrong ?

Thanks

Jeremy

#60

hahaha… well done. :smiley:

Seems like an irksome value to change if I understand the implications. When you say responsiveness, you mean the Ansible essentially “missing” Grid button presses, right?

#61

no, this delay is related to initialization code when a grid is connected. so if this delay is removed, there is a risk that some grids will not get recognized or something like that. from the limited testing we did back then it worked fine but the delay was added for some reason, so possible that it’s needed for an older grid revision or when the library is used by other hardware (like aleph).

1 Like
#62

You can’t get triggers to fire either? But the grid does light up and respond? Maybe check that the pin headers connecting the PCBs are well-seated, could have got jostled in transit?