#103

I am not sure - I think as soon as this is official with a manual one would go through it could be clear that there are two config pages. The glyphs are indicating the same behaviour for different features in the end and having the division setup on the clock page is already an indicator.

I will look into the USB preset JSON file thing as soon as I have some spare time again and then try to send you a file.

#104

@csboling I have a quick question and haven’t had time to try any of the betas just yet. But what I have seen from the videos is amazing. Thankyou for all these updates!

On the original v1.6.1 Kria one thing i found frustrating was having the master tempo being set in the global menu, and not set per preset. This mean’t when i play live, each preset played at the same default global tempo unless I clocked externally. This also mean’t that if I changed the global tempo, it effected every preset. The way I use Kria is basically, every preset is a complete song and I want each song to have its own default tempo. I know you can clock divide per preset, but is it possible to have a master tempo set per preset? My workaround for this is to set the global tempo quite high and don’t change it, so then, I have room to divide it down on each preset.

1 Like
#105

This seems possible but would take a bit of doing. I might want to make sure it still works if you try to load a global clock setting, since I’m not sure if other users are maybe relying on the existing behavior? Seems like it makes a lot of sense though, and something that if it’s going to be changed should happen before the 2.0.0 release.

2 Likes
#106

I can understand that and backwards compatibility is really important.
I wouldn’t want breaking changes were you could potentially lose work or have to edit prexisting tunes made in v1.6.1. So I would still want global tempo to be there, but as an option.
How about having the global tempo set as normal “on” in the default globals but also an option to switch it “off” in global. With the default being “on” as normal so it doesn’t affect older firmwares. When you switch it “off” there is some option that appears in a preset?

I’d be interested to know if other Kria users are happy about the way the global tempo is currently setup and if it effects them when they move from preset to preset. I just find it a bit frustrating because I could never remember the original tempo I used for each preset. I used to take photos of the master tempo, then gave up and just kept it the same for all presets.

1 Like
#107

This sounds great and I think since this wouldn’t affect any existing behavior unless you opt in, it wouldn’t be so critical to have it ready to go this release. Since the global clock frequency is such a core piece of configuration I’m a bit hesitant to try and do this and be confident that it’s been thoroughly tested on top of everything else that’s changed. I think probably I will follow up with you on developing and testing this to go in the next version.

New build (afbc529) has a simplified tuning UI and some bug fixes. I think I’m basically ready to call this feature-complete for 2.0.0, but I am planning to put a little more time into looking for bugs, new and old.

8 Likes
#108

as a possible addition to v2 would leader i2c mode be worth considering? something very simple:

  • a choice between follower mode (how it currently works) / leader sending to txo / leader sending to just friends / leader sending to er-301 - this would be shared by all apps / presets. could be simply 4 button switch on preset page?
  • no custom mapping, 4 txo/jf/er-301 voices simply mirror ansible outputs
  • no glide support - i don’t think i2c would handle it well
  • because of the above, probably only enabled for grid and midi apps?

should be a fairly trivial change using polyES/multipass code.

5 Likes
#109

TXo and ER-301 both support messages for setting the slew duration, would it be sufficient to send these once to the appropriate follower when a glide setting is changed?

1 Like
#110

Any chance to implement as well the possibility of channel output/routing selection per pattern as in polyES?

#111

haven’t thought of that - great idea, this might do the trick!

i think this would overcomplicate the UI too much.

#112

Didn’t realise it was a UI matter, thought it was about disk space. If it is a UI matter, would it be confusing if these assignment options appeared only in the ES app?

#113

if something were to be added for free voice mapping ala polyES, it would be more consistent to apply it to each app, not just earthsea.

i’ve heard complaints that polyES voice assignment is too complex, which is fine for polyES - if you’re willing to learn it you’ll have the ultimate flexibility and some really neat tricks that come with it, and since polyES is a standalone alt firmware you know what you’re getting (although you don’t ever have to touch voice/output assignment for basic use). but adding it to ansible would likely create confusion for more users.

i would just see the leader modes as a simple way to send notes over i2c (and, used with MIDI app, a way to sequence TXo or JF with MIDI).

5 Likes
#114

@csboling: what changes, if any, need to be made to the documentation to reflect all the new functionality?

5 Likes
#115

I’ve been trying to keep the docs updated as I go, so there are descriptions of the tuning page, new sync options, etc., but if you’re offering to make some more sweet grid UI diagrams that would rule!

3 Likes
#116

I have been dreaming of this! Im down sizing and have to loose one of my ansibles (polyES is on that one) and i would hate to loose the ability to use JF in JT mode and of course sequencing the ER-301.
So i would love to see this implemented. I have a suggestion for voice assignment and UI interaction.
How about having the option to switch between sequencer pages.
So 1st page is using Ansible’s outs, 2nd would be Just type and 3rd would be ER-301.
Maybe it could be in the scale page near the mutes?

*extra awesomeness would be adding 2 more tracks to kria for i2c.

3 Likes
#117

This is probably not possible due to flash storage/memory limitations. Unless you wanted to compile a version with just Kria and no other apps, which would I think be pretty straightforward, but perhaps laborious – then again so would be figuring out all the places where Kria assumes 4 tracks.

#118

ahh i see no worries. It was just a thought to utilise the 6 voices on JF. 4 voices is still amazing!

1 Like
#119

Trying out the tuning method described today to try and calibrate the 4 channels of Ansible. I am quite daft with these things so please forgive what might be a question that maybe misses the point.

I’m basically sending the cv outs to the same input on the ER 301 I’m able to get a reading of the outputs from there. My readings of 0v are Ch1 (-3 cent), Ch 2 (21-22 cent), Ch 3 (3-4 cent), Ch 4 (17 cent). How do I calibrate them, because with the current interface, when I am at 0v, I cannot actually reduce the amount, meaning the channels that are sharp, I cannot bring them down. Was this tuning table meant to calibrate the 4 channels or to only have differently defined tuning tables?

#120

Yeah, it’s intended to calibrate tuning tables as a primary use case. The top 4 rows are for dealing with different tracks. At the initial note slot, Ansible is sending a value of 0 to the (unipolar) DACs, so it can’t output a voltage any lower than that. Therefore you can’t correct in software for these absolute offsets from 0V, but this interface is intended to let you get all the CV outputs in (better) relative tune with each other. You would need to nudge all pitches up to have some foot room and then go down from there, or else calibrate all DACs in a generally upward direction so that things stay linear – I think I should probably add a mod key that lets you nudge all note slots by the same amount to facilitate the first option, since that will probably be easier to keep things roughly linear.

I will try to write up more thorough calibration instructions later, but roughly:

  • Since your highest output for a DAC value of 0 is at +22 cents, bring the other tracks in line with it. Pick the lowest note slot by pressing the first note slot on the group of 12 highlighted keys in the top four rows. You can increase the voltage output of this note slot by using the keys on the right side of the bottom row.
  • Once you’ve adjusted each track, go to the next octave – the octave select is on the left side of the 4th row from the bottom. Repeat the adjustments for each track using the lowest note slot of the octave. You probably want these to generally increase in value with Track 2 staying the same, to match how you calibrated the first octave.
  • Once you’ve dialed in each octave, tap the second key from the right on the octave select row to do a piecewise linear fit between octaves.
  • You should now be able to switch back to other Grid apps to check if the tuning sounds okay. If you’re happy with the tuning be sure to go back to the tuning page to commit it to flash (with a long-press of one of the right 2 keys on the octave select row - note that long pressing the second key from the right will do the fit between octaves before saving) before you power off. If you haven’t saved it yet you can tap the single key on its own on this row to restore the saved tuning, or long press it to restore the factory default tuning.
5 Likes
(Re)calibrating ansible CV voltage output
#121

Thanks! So I have tuned all the 4 channels to +22 cent (1222 1st Oct / 2422 2nd Oct / etc), does that seem sort of correct? But wow the channels where kinda off between Octaves as well, hopefully this helps! Thank you for so much of your work!!!

#122

The tuning is a known problem on both Ansible and Teletype - see this thread