#30

hi @egon77 and welcome back!

this is very strange behavior as what you’re describing with clock release/lock is what should happen when you insert/remove the jack. have you tried with different clock signal? or what happens when you attenuate the signal?

#31

Is it possible the unusual clocking behavior might be the result of using a bipolar square wave as a clock? I seem to recall weirdness with using bipolar LFO outputs as clocks…

…if you have something like a Maths to scale and shift the signal into positive territory that might be something to test.

1 Like
#32

Hi @tehn, It’s good to be back! Thanks! I’m loving this module.

You and @ngwese are both onto something there. All the LFO’s in my system appear to clock the monome the same incorrect way. BUT, the external clocking did begin to work correctly when I attenuated it with a VCA ( I had to sort of find a sweet spot on the knob to get it to work)

But ngwese suggestion also worked, to merely offset the pulse into above-negative territory without the need for attenuating got it to clock as advertised as well.

These fixes work for me! Thanks!

1 Like
#33

I have external clock problems too, from any korg device (sq-1, volca mix etc.) it kinda skips so the sequencers start getting skaty behaviour, this is true also of my expert sleepers disting clockable lfo mode, and some others. i can boost the signal with maths to rectify. the clock out of the keystep works fine - but that’s quite a chunky object to carry around outside of the modular…

#34

I found that a clock pulse of about 25 ms seems to work well. I’m sending clock from a Teletype, so I can fine-tune it. :slight_smile:

#37

Howdy,
I installed the newest ansible firmware(1.6.1) and based on this PR(https://github.com/monome/ansible/pull/30) I thought that setting note durations to max would tie notes together. When I actually try this though by cranking up the durations on 2 neighboring triggers, I still get a double trigger on my envelopes. The ansible trigger lights does appear to remain solid throughout but no matter what envelop I hook it up to(intellijel dual ADSR, Tiptop Z4000), i still get the same behaviour implying to me that voltage is going low if even for a very small amount of time. Am I doing something wrong?

Monome ecosystem firmware development backlog
#38

It’s pretty easy to reproduce this behaviour. It doesn’t seem to matter if kria is clocked internally or externally. Just create a small sequence where two neighboring notes have a maximum duration set. I found that the note will NOT tie on MOST devices.

Double Triggers:
Initelljiel Dual ADSR
TipTop Z4000 envelope
Shapershifter
NI Manis Iteratus

Single Trigger:
Make Noise Mysteron.

#40

Just noticed after updating firmware on Ansible that the 4th/last gate light is always lit solid orange. Everything seems to work. Tried power cycling but no change. Any ideas?

#41

To which firmware version did you update?

#42

have you tried switching applications? does it change when going between MP and kria?

#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