#49

Curious if preset backups are something we can expect sometime in the foreseeable future. I know it’s a non-trivial task and there is probably a lot of stuff already on the list.

I only just got my Ansible last week and I’m just getting a feel for it so haven’t yet made a lot of patterns, but I felt inspired to add some Teletype ops that I thought would be useful ((Teletype) CV from Ansible while running Kria on TT) and now I’m endeavoring to get some longer gates that relate to the clock ((Kria) durations relative to clock/division). I think after that, I’ll stop futzing with the firmware and just use the thing, but ultimately it’d be really nice to not have to choose between nuking my presets and continuing to tweak the code.

I wonder if maybe an alternate solution would be to incorporate this functionality into Teletype. By the looks of (Teletype) USB Disk Mode Interface, Teletype has a pretty serious related feature on the horizon. With all the momentum happening around Teletype development, maybe this new USB Disk Mode could also help manage a library of Ansible presets?

1 Like
#50

I have a strange issue in Meadowphysics app on Ansible. In 8TR mode tracks 5-8 produce no triggers on CV outs (as I understand they should).

And in other modes tracks 6-8 produce a trigger on TR1 out in addition to a note output (but not track 5).

Could you please clarify? Thanks!

EDIT: I will try to update firmware first…

#51

have you loaded a clean/new preset?

#52

I’m having a CV out problem with MP. I have been monitoring the problem over the last few weeks and can’t find any consistency to it. I’ve read through all the threads (I hope and have read a few many times) but couldn’t find anyone reporting the same issue so i thought I’d post the issue here as it is similar to the problem posted above. The problem is that after some/any period of time the CV outs stop outputting any note data, the corresponding trigger outs continue as usual. I am working on a patch for a performance so the settings are specific and consistent:
I’m running 1.5.0
Ansible is always externally clocked
I am using 2 CV/Trig voice setup
Nothing fixes the problem except power cycling (at least I haven’t found anything else)
The problem seems to happen more when switching from Kria to MP but after trying to narrow the problem down i have found that is has happened after using only MP after power cycle and in one case almost immediately after a cycle
@tehn you have suggested loading a clean/new preset a couple of times above for similar errors. I can’t seem to get a clear preset. I am taking the existing data to each preset. This may be the key to the problem. Is there a way to reset all the MP presets without clearing the Kria presets?
I’m hoping this is basic user error and appreciate any direction

#53

Firmware update fixed it. Thanks!

#54

I’m attempting to clock a patch based on the Cycles Pulses, but the time in between pulses is irregular, it comes off sometimes like swing, but it’s a bit more like a stutter. It makes it really hard to drive the Tempi (samples 2 gates to sync), as all of the outputs stutter when it hits an off beat. It happens at any division and at any speed.

It seems like maybe a rounding error or issue syncing with an internal clock maybe? There is almost a pattern too it, but it’s different depending on the speed of the cycle/divisions.

Any thoughts?

#55

I just recently received my Arc and had the same finding last night as well!

I tried sending the pulses to a bunch of different things, but found the pulses to be audibly irregular. Seems like it should be fixable in the firmware as I’ve found the internal clock on Kria to be solid.

#56

I’m trying to do a predictable arrangement using meta sequencing but am having trouble with reset signal only resetting the top row - the patterns.

Am I wrong in thinking that the second row - the divider - should be reset as well?

#57

Just wondering if there is a chromatic scale option?
Or an unquantized scale option?

#58

If you have no scale selected, you get full range 0v-10v. Then once you switch to scaled mode the first option is chromatic

1 Like
#59

Amazing!
feel totally dumb asking but how do you unselect a scale?

#60

not a dumb question!
when holding the second of the 2 state buttons on the front panel, the first settings menu will appear on the arc. there you can select scaled sync, scaled unsynced, full range synced, and full range unsynced. i’m probably not using the correct terminology so i will link you to the manual which lays everything out with beautiful diagrams.

https://monome.org/docs/modular/ansible/

also i just realized i was assuming you are using the arc modes (cycles and levels)

#61

Cool! Thanks.
I’m using it with a grid though, is it still the same?

#62

ahh see i’m not too sure as i don’t currently own a grid (not completely true) and therefore have never used the grid mode (not a lie)

check the manual and good luck!

1 Like
#63

I see…
I’ve had a look at the manual and it seems to only refer to scales when in grid mode, can’t see an option to remove the scale to work in 0-10v like the arc. I think this is a must have option for grid mode too. Not sure how they would do it due to the number of buttons. Had an idea to use a button twice. Dim = one semitone and Bright = two semitones?

#64

You’re not describing the same thing, though. Levels/Cycles in 0-10V mode is (I believe) entirely continuous. No quantisation whatsoever. By contrast, what you’ve described for Kria/Meadowphysics is still quantisation, only to semitones (which is entirely possible, albeit for a range of eight semitones bottom-to-top).

I think it’s reasonable given the grid is a digital instrument and the mapping of a row to a pitch is fairly consistent in both Kria and Meadowphysics.

(It certainly doesn’t feel like a ‘must-have’ to me: it feels like a maximialist box-ticking feature, rather than a feature which fits with the design philosophies present in Kria).

#65

I understand that.
I guess what I’m trying to get at is I use a lot of the scales in the ornament and crime that involve micro tuning.
Having recently joined the monome realm I’m totally in love with it, I’d be stocked if the two (Kria and Meadowphysics) could play nice with the o&c.
The scale system on grid I’m honestly still getting my head around and having no option to unquatize means double quantizer clash.
I really like to have these two play nice or ultimately just add more scale presets that have the micro tuning ready to go.
As o&c is open source and all the scales are listed in cents and DAC values.
Hoping these could be implemented. I’m sure many would.

I can never go back from monome now and it’s hard letting go of old ways I just believe we could all be if it here.

Ansible Kria Feature Requests
#66

i’m sorry to say i don’t think there’s a good solution to the issue you guys are talking about.

sequencers are by definition “quantized” as they output a series of defined values. even if these values are not semitones they are going to be fixed.

a standalone quantizer like o&c takes full range voltage and outputs the nearest value in its table. but if you give it two totally different voltages that are still closest to one table entry, it’s going to give you the same note. so what i think you’re asking for is for Kria to map itself to assigned o&c table values, which you just can’t do with CV (this is a good i2c use case.)

this is to say, you can’t unquantize a sequencer like you’re suggesting. even if the values are “off” they’ll still be the same amount of off on each trigger.

so, the scale feature isn’t maximalist or feature creep. a less complex (and far far less useful) option would’ve been each step is 1v increments, but that wouldn’t even be useful with quantizers.

the scale builder is not complicated-- it just requires that you consider how scales are built. the bottom row is the root note. if you move this to the right, it will add semitones to the whole scale-- the scale is built incrementally. the next row up from the bottom is the second note. if it’s all the way to the left (0) it will add nothing, hence be the same note. if you set it to 1, then you have a semitone difference upwards. for a chromatic scale, set all the upper notes to 1, so each note increases by one semitone.

and then these scales can be saved and changed quickly. if you’re looking to do microtonal you can use an attenuator (though this would be fiddly, and always reduced-equal-tempered). a truly flexible tuning system would really require some sort of Teletype remote, or direct communication with o&c via i2c

of course, please correct me if i’m making any incorrect assumptions—

4 Likes
#67

I struggled with getting what I wanted out of ansible scales for a long time before I made the obvious step of making the scales and saving BEFORE going off and messing with everything else. I’ll just have every interval playing ascending as a starting point, then go make some scales and crucially hear what they’re doing in a really clear way, and only then go to triggers and durations and polyrhythms etc. Like I said, sorry if that’s really obvious but it took me a while to arrive at this workflow which I now love. Hope that helps some people.

2 Likes
#68

I think what you want is to be able to use the Kria sequencer to play the scales in O+C but Kria always outputs an 8 note scale which doesn’t map well to O+C’s microtonal tables. Is this right?

If so, I very simple solution would be to output the CV from Kria to an attenuator or amplifier which scales the voltage output up or down proportionately. This will unquantize the voltages (from an 8 note scale, at least) coming from Kria as long as you don’t set your attenuator or amplifier to unity gain - so literally, almost any setting - so that O+C can map them to any scale you choose without the output always being mapped to notes in an 8 note scale. The notes will still be fixed but at a voltage of the Kria note output x the attenuator/amplifier setting which will not be mapped to any particular scale at all. Think Turing Machine where you are picking the random voltages yourself.

For instance, take your Kria CV output and map it to channel 2 of a MATHS. Set the channel attenuverter knob to something like 3:00. Take the output of channel 2 to your O+C for microtonal quantization. You control the scales in O+C, you control the notes with Kria+Grids, you control the general range with the MATHS channel 2 attenuverter.

If I’ve missed your point entirely, then carry on.

4 Likes