#183

woah these are really fascinating features. i’m onboard. i’ll add these to the backlog.

yes, phenomenon are coming to the editor! i had to figure out some other things first before that could be implemented. and a first step in pattern “chaining” is in the oven too, which is hopefully both simple and versatile. it is going to be implemented as a phenomenon called “lacuna” - i would very much love to hear your feedback once that is out.

thanks so much for all the ideas :sunglasses:

3 Likes
#184

I haven’t used Yggdrasil yet so I’m just kind of thinking out loud here based on reading the docs.

Being able to have columns of different lengths makes polymeter trivial but what about polyrhythms? I see you can set different BPM per column so it seems possible to set one column to 8 steps say, and another to 5 with a BPM that takes the same amount time. That does require some (probably beyond) mental math though. I wonder if there is another way to enable the same goal, or if a function to set the BPM polyrhythmically is something other people are interested in. Meaning “set column two to take the same amount of time as column one despite having a different number of cells”.

1 Like
#185

amazing : ) looking forward and curious to see how lacuna is implemented with regards to the structure of tracks and index.

I thought of two more things, that might have been mentioned already:

  • setting macro value per slot would be very cool, like parameter locking.
  • setting ypc sample start position (per slot also) to allow for classic tracker sample chopping of loops.

the math is simple. using your 5 row + 8 row example:
8/5 = 1.6 so change the clock of the 5 row track to 1.6 (assuming the 8 row track is set to clock 1). et voilà!

3 Likes
#186

The script runs on a global bpm but the individual tracks can have very different clock divisions. I.e. row one clock;.5 and row two clock;3 or even very close but slightly off like 1x and 1.05x for slow phasing!

2 Likes
#187

And now I’m thinking about programming Piano Phase…

1 Like
#188

v1.0.13

  • NEW Long messages scroll back and forth.
  • NEW Long text entries in the terminal and editor scroll.
  • NEW Jump to the beginning of the next (or end of previous) word with mod + left and right arrows.
  • CHANGE Press enter to dismiss the editor when there are no changes.
7 Likes
#189

CHANGE Press enter to dismiss the editor when there are no changes.

that was quick! New jump is also a nice little workflow enhancer, sweet : )

2 Likes
#190

you snuck that in right under the line while i had that file open XD

yeah i use that jump move all day long and it’s been killing me not having it. also the scrolling in fields was needed to enter sample names for YPC in the editor. THERE IS A METHOD TO ALL OF THIS.

5 Likes
#191

Scrolling will also allow me to see the third parameter change when chaining 3 voice change commands with &&!

1 Like
#192

&& is what made me go “oh no…”

1 Like
#193

if you updated to v1.0.13 before reading this post please update again. there was a strange merge issue and the editor title bar won’t appear for you.

@2197

you can do this with 1 2 synth;m2;75. i’ll clarify the docs.

4 Likes
#194

ah, makes sense — thanks!
EDIT: @tyleretters perhaps it’d make sense to add macros as a view option as well then? toggle with v;m1 and v;m2 for instance.

2 Likes
#195

two observations:

  • when having tracks of different depth, you can still enter notes below the bottom of the shorter tracks. for instance, I’m running a project where track 1 is 32 steps and track 2 is 8 steps, and I can still enter notes and commands on step 9-32 in track 2, and they will play and loop back to the top after playing the last command in the track.
  • in the editor, the cursor always jumps back to the YGG row after entering any command. I think it would be nice if it stayed on the line you were at. I noticed this trying to find the right drum sound on a monomachine, increasing midi values step by step while looping playback, but the cursor keeps jumping up every time I press enter. the same goes for finding the right velocity level.

also, when I plugged in a new small usb-midi interface I just got, yggdrasil froze and stayed at the start screen, letting me scroll through the frames – pretty fun : ) works again after a sleep though!

#196

ahh, these are great points. yes i’ll address these.

is the freeze bug reproducible? if so, can you share the steps?

EDIT: can you share steps to reproduce the depth bug, too? in your example tried doing 2 20 c3 but the note didn’t appear at 2,20.

#197

I think what happened was that I pressed K1 while the splash screen was showing and entered the norns system menu - devices - midi, looked if it had found my new usb-midi interface, which it had, and then I pressed K1 again to go back to yggdrasil it was stuck on the splash screen. I can’t seem to reproduce it though.

I’m not sure under what exact circumstances it happens. it seems a bit random. I can reproduce it every now and then, but then the exact same steps won’t make it happen the next time. I always try to get there using channel 1 as my longer channel, and 2 as my shorter, but once the “bug starts working”, I don’t have to have any channel being of that depth for it to happen. I can set all tracks depth to 8, enter 2 100 c5 and it will make track 2 100 steps long and enter a c5 at row 100.

tracks being set to clade;midi somehow seem to be part of it. in the video, only track 1 and 2 are midi tracks, and I can’t change the depth of other tracks by inputing commands on rows out of bounds on those.

possibly changing midi channels back and forth influences it? sorry I can’t give you a more exact report. I’ll let you know if I figure out more details. I have 16 as my default track depth.

here’s a video of it happening, so you can see how it behaves (in the video, track 2 was 8 steps deep to begin with, then I entered the c#5 at 2 12 via the editor, which made it 12 steps long. then I started filming):

1 Like
#198

v1.0.14

  • NEW Select samples in editor without typing them. (!)
  • NEW Edit macros in the editor.
  • NEW “Off” phenomenon to send MIDI off signals to all notes on the track.
  • NEW View macros with v;m1 and v;m2.
  • NEW Toggle synth encoder override while in Y Mode with p.
  • NEW Execute arbitrary routines with routine;anthropocene.txt.
  • CHANGE After committing values in the editor, the last selected field remains selected.
  • DEV Refactor commands to each use individual files.

sample select demo
routine docs
off docs

@2197 this is actually intended behavior! my thought was if you’re explicitly telling yggdrasil to put a note a slot deeper than the track, you also want the track to go that deep!

9 Likes
#200

Whoa. Those new features look wild with possibility. Off to the docs!

1 Like
#201

If I’m looking at this correctly, while not a save state, you could theoretically load a routine and build a full snapshot with a routine?

1 Like
#202

precisely. really good for configuring your gear, for example. also your runs are great starting place for routines - everything you do is saved anyways. so just go ahead and build a snapshot and look in /data/yggdrasil/runs and open the latest file.

(routines can load other routines…)

1 Like
#203

haha, of course! it absolutely makes sense and is indeed better that way. but why doesn’t it always behave that way? sometimes when I add a note or other command to a slot deeper than the track it does not deepen the track, while sometimes it does. I don’t really understand under what circumstances/criteria it makes the track go deeper.

so many brilliant things in this update. the new editor is absolutely killer, and routines is such a cool idea!

1 Like