#65

The original Earthsea is clockable via teletype. I like switching between the original timing and a steady or modified teletype clock.

2 Likes
#66

Yes, of course. Sorry. I don’t have a TT. I was talking about the “regular” way of clocking.

#67

Ah, sorry - you are roght of course! I tend to forget that there are actually who do not use a teletype. I2c over Earthsea was one of the main reasons I got one. Sequencing irregular sequences is such a great fun.

#68

When I ever understand, how Teletype actually works, I might just get one, too :slight_smile:

1 Like
#69

Just spotted this…
@scanner_darkly and @freqout could you please possibly merge the 2 works?
that would be amazing…the transposition feature + earthsea WOW

(edited: forgive me if I am asking too much )

#70

I’ve submitted a pull request to the main monome repo for Ansible. once it gets accepted and merged, @scanner_darkly will be able to pull it into his branch.

5 Likes
#71

Is it too early to request some demos? As an Earthsea owner (and fan) I’d really love to see this in action, and perhaps participate in some pros/cons/compare/contrast discussions. Thank you for your help.

1 Like
#72

It’s not possible to update the Ansible firmware without losing presets, right?

#73

Super amazing work!

With regards to talk about multiple mono mode… I had a thought:
Considering we’re already working with kind of a fretboard/string layout, we could build upon this model and have notes pressed on different rows play simultaneously, but have monophonic stealing along a single row. This could get complicated, maybe this is more of a Teletype/Grid project (which I might take a shot at next week), but just thought I’d throw the idea out there.

1 Like
#74

i will merge @freqout’s features when i see a corresponding update to the ansible docs— calling all those who appreciate his contribution— help make sure the docs don’t fall behind

15 Likes
#75

looping/cutting does sound awesome. thanks :slight_smile:

any more thoughts on overdub?

#76

when you say the time page, do you mean the edge mode? perhaps i didn’t explain well… here is what i would like to add:

  • runes for double/half speed can still be included as before
  • there will be additional runes for smaller speed adjustments, say by 25%
  • speed change will be non destructible (right now if you double the speed you lose precision)
  • when you apply the speed runes you will have 2 choices - to increase/decrease note length proportionally, or to keep them intact
  • regardless of how the speed runes were applied the edge mode will override pattern note length when in fixed or drone mode
  • for fixed edge mode you will have the ability to apply the current length to all pattern notes (destructible change)

and a couple more related things:

  • i’ve changed the edge mode to be per pattern (saved with the pattern)
  • i’m planning on making linearize rune non destructible, so you can go back to original timing.

external clock completely ignores pattern note intervals and length. runes will not work as mul/div (which i believe is also the case with the teletype clock). tbh the more i play with earthsea the more i think ext clock goes against its nature (at least in its current implementation, i’d rather see it do something more interesting, like stretching/shrinking patterns based on the clock - i am not planning on adding this however).

yep, as @freqout mentioned once his changes are merged into the main branch i will pull them into my version.

i’ve been posting clips on my instagram account. i’m afraid that will be the extent of it for now. i started a new job on monday and my time is depressingly limited at the moment… the best way is to install it and try it out!

unfortunately, not.

i’m afraid this will be better for a teletype/grid implementation as you mentioned. i’ve got a concept for voice allocation in my head that should play nicely with some additional (hopefully exciting) features i’m planning.

yes! definitely coming. i’ve got some interesting ideas for it too… :slight_smile:

5 Likes
#78

Ha! Twenty characters of Old Skool! :slight_smile:

1 Like
#79

sorry for the confusion; i’ve been deep into kria and meadowphysics over the last week, so i had somehow thought their time settings (the two grid rows) could be set on earthsea in the same manner.

still, being able to clock ansible earthsea somehow, at the very least by syncing play/rec to a trig, is desirable. the way that teletype handles earthsea II clocking, where each tick plays the next recorded pattern event (note, shape), would be really handy in ansible earthsea. for example, a regular clock pulse is pretty much automatic pattern linearization/quantization. or, send it a randomly fluctuating clock to generate unpredictable note events–like a slow burst clock from Qubit Chance.

#80

both are already implemented in the latest beta. trigger input 1 advances to the next pattern event (it will autodetect when something is connected to it and stop internal timer), trigger input 2 resets/starts playback.

1 Like
#81

finally got around to playing with it last night, and it is awesome! i’ve never had an earthsea, so that might contribute to my excitement, but loved the immediacy it brought to playing with the rack. i agree that overdubbing + mlr position playing sound like great ideas!

the only issue I had was with voice allocation. i could’t really play freely on top of the sequence without the voices getting mixed up i know a full featured quad mono mode isn’t in the future, but how possible/simple would it be to implement a sort of “voice locking” with the overdub feature (ie. you play a sequence with first voice, which locks it and playing/overdub starts with next available voice). totally unsure if this is possible, or already planned but just wanted to throw my opinion in.

regardless of that, thanks again @scanner_darkly for the awesome work!!

5 Likes
#82

i like that idea a lot :slight_smile:

4 Likes
#83

it’s a cool idea, but it means that we would need the ability to select different pages in patterns. i still think it would complicate the concept quite a bit (you have patterns which are collections of voices which are collections of notes). this would mean complicating the UI as well, especially if you consider being able to disable or overdub specific voices. and then you’d need the ability to copy or merge voices.

i think keeping patterns simply as collection of notes that get played over whatever voices are assigned to that pattern is more intuitive. i’ve been playing with it and being able to reassign voices is a lot of fun! which brings me to…

ansible.zip
ansible.hex

new beta:

  • voice allocation - press leftmost button in the bottom row, you’ll see a 2x4 block, left 4 buttons select pattern voices, right 4 buttons select voices for live playing. try different combinations for both! (please note when recording it will use pattern voices, not live voices)

  • octave keyboard shift - same page as voice allocation, 3&4th buttons from the left in the bottom row

  • edge mode implemented (as mentioned above it is now configurable and stored per pattern)

  • i disabled runes for prev/next pattern, since you can use buttons and it’s easy to switch patterns in pattern view. you’ll notice the runes are still there though - they will now reverse patterns! :slight_smile:

edit: the octave keyboard shift implementation is not working properly (it works for live but will also transpose patterns). i should have a fix tonight, apologies to folks who already downloaded - i’m trying to use as much of my time for development as i can, unfortunately that means less extensive testing.

16 Likes
#84

Awesome!
You are on fire!

2 Likes
#85

@scanner_darkly, I know it’s not really an important thing, but can we have the control buttons on the main page be dimly lit?

Also, thank you for the work you have been putting in on this! It’s really turning out great :smiley:

2 Likes