blast. i’ll log the bug and get it fixed. the bugs in this things are so gnarly.

1 Like

don’t know if this information helps, but if i set default track depth to 8, restart ygg, load a routine.txt that sets track 1 and 2 to depth 32, and track 3 and 4 to depth 16, then the hud track numbers on the left gets updated to 16 rows. track 1 and 2 gets dots indicating more rows, but i can’t navigate any further down (either by key arrows or entering 1 32 in the terminal: “1 32 is out of bounds”).
photo_2020-12-16 18.58.44

1 Like

v1.0.16

  • FIX Copy and paste slots works again.
  • FIX Copy and paste tracks works again.
  • FIX Copy and paste samples works again.
  • FIX Lucky phenomenon are no longer unlucky.

image

these bugs had all four

12 Likes

i know the demo video is a haddaway reference, but it also reminds me of the intro of this amiga classic:

6 Likes

oh wow i’ve never seen this before. this SLAPS.

1 Like

hey!
recently did a re-flash of my norns shield while trying to figure out a bug together with @unicity 's fourtunes script. i’m pinging them here because the bug there was also related the clock somehow? (see maiden error message below).

now when i’m running ygg, i always get a graphical freeze after a few (2-5) minutes of using. it has happened four times in a row. the sound is still playing, but i can’t enter any commands or navigate the tracker. i can press k1 to enter system menu and it is not frozen, but when going back to ygg (k1 again) it looks like all channels are highlighted and the whole gui is frozen and can’t be interacted with.
maiden gives me this error:

lua: /home/we/norns/lua/core/clock.lua:82: /home/we/dust/code/yggdrasil/lib/graphics.lua:383: attempt to index a nil value
stack traceback:
[C]: in function 'error'
/home/we/norns/lua/core/clock.lua:82: in function 'core/clock.resume'

i can enter params edit menu and change the clock tempo for instance, and it changes the playback tempo. i can also start/stop with k2, but not with the keyboard. any clues? : )

can you share your latest run files from when it happened? i’ll try to reproduce.

sure!
as you can see, very basic stuff. i mostly entered notes via the editor.

1st:

Summary
1 synth;v;2
1 synth;v;1
1 synth;v;3
oblique
1 synth;m1;12
1 synth;m2;12
1 synth;m1;32
1 synth;m1;62
1 synth;m1;42
1 clock;2
1 clock;2
1 clock;1
1 clock;.25
1 d;32
2 clock;.5
sync
2 synth;v;3
2 synth;m2;12
2 synth;m1;32
3 sha;1
3 shadow;1
sync
3 clock;.25
3 synth;m1;32
3 synth;m2;12
3 d;16
1 d;12
1 d;18
sync
1 d;12
sync
4 d;32

2nd:

Summary

1 clock;.25
2 clock;.5
1 d;32
2 d;24
3 d;16
4 clock;1.5
1 synth;v;3
2 synth;v;3
3 synth;v;3
4 synth;v;3
1 1 c4

Not sure if it will help, but I’ll mention that I was only able to reproduce @2197’s Fourtunes error when I reflashed and then ran Fourtunes. Even then, the issue goes away on its own on my shield the next time I run the script. Not so for @2197. I’d never seen this behavior until updating my norns system to the latest version, but I still suspect it’s something I’ve done.

Also, like here it doesn’t seem to be caused directly by clock but rather an attempt to index a value that is nil (in my case it’s passing a nil array when calling a musicutil function).

1 Like

thanks for clarifying! i just saw “clock” and had a reaction thinking “not again!”, but i see now how it’s not related.

1 Like

Oh I think “not again!” is still valid here - it’s the exact same line from clock that shows up in the trace, and it appears to be caused by an unexpected nil crashing the party.

1 Like

interesting.

@unicity did you restart a few times or just relaunch the script?

@tyleretters as far as I recall I can “fix” Fourtunes simply by reloading the script. And once that takes place, the problem doesn’t seem to reappear.

This app is great! I’ve never played with either live coding or a tracker, so this is especially fun. The phenomena are super fun!

Is there a way just to clear the phenomenon from a slot? I read through all the docs but didn’t catch this.

Also, random thoughts on phenomena backlog items:
A swap phenomenon that swaps one slots note (or lack thereof) with another:
Ex:
X y swap;x y of destination slot

Ratchets!

Not sure what to call it but I added a feature in an Awake fork (Awake-mod) where a certain step has a transpose value and a ‘step divider’ of when to activate that transposition (just for that instance).
Example: transpose slot 1 1 by +2 notes every 3rd time the slot is active. That would be an awesome feature here too! I called it mod trig, naming still isn’t clear to me on this one.
Ex:
x y modtrig;transpose value;step division

Endless thanks to your insanely generous contributions to this device/community.

EDIT: think I found a bug after the latest Norns update:
There are system wide issues when you attempt to load any script (even Yggdrasil) after the first load of Yggdrasil. If you load Yggdrasil only once it seems to work just fine.

script load: /home/we/dust/code/yggdrasil/yggdrasil.lua

cleanup failed with error: /home/we/norns/lua/core/clock.lua:38: bad argument #1 to ‘clock_cancel’ (number expected, got nil)

script clear

lua: /home/we/norns/lua/core/script.lua:65: attempt to call a nil value (field ‘clear’)

stack traceback:

/home/we/norns/lua/core/script.lua:65: in function ‘core/script.clear’

/home/we/norns/lua/core/script.lua:155: in function ‘core/script.load’

/home/we/norns/lua/core/menu/preview.lua:23: in function ‘core/menu/preview.key’

/home/we/norns/lua/core/menu.lua:140: in function </home/we/norns/lua/core/menu.lua:117>

clock: ignoring resumption of canceled clock (no coroutine)

this error i was experiencing seems to have disappeared now with the latest norns update. was using yggdrail for several hours yesterday at it all ran smoothly.

1 Like

@shoggoth thank you! i’m so glad you enjoy it.

no, there isn’t a way to clear just a phenomenon yet. gotta clear the whole slot.

swap idea is really cool. i’ll make a note of that. yep ratchets are in the “someday” file. i just got into electron stuff and trig conditions are still blowing my mind…

yeah this is the same bug we were working on with @2197. it seems to clears itself up.


@2197 thanks for sharing and sorry for the turbulence!!

3 Likes

So I had to make some changes in my app after the most recent Norns update, related to keyboard references (since they mimicked Yggdrasil). I tried the same changes in Yggdrasil and Im not getting the crash after attempting to load another app now. I renamed keyboard.lua to kybd.lua, changed the include reference to: kybd = include(kybd.lua) and I commented out the keyboard.connect command… but now the keyboard.event command doesnt fire when using the keyboard… however, changing to the new keyboard.code does fire that function… but now all the key references are busted since they are strings instead of integers. No clue if this helps in anyway but figured I would throw it out there.

v1.0.17

  • FIX Update for norns 210114.
  • DEV Remove unneeded clock.cancel() calls in cleanup().
1 Like

Hey Tyler,

Thank you for this awesome script. I am currently enjoying it a lot. I have one little problem though which is that it crashes when I try to change all synth voices to Rikki. Really strange. Has anyone else encountered this problem? Is there maybe a fix? Sorry if someone else asked the same question before.

you’re welcome! i’m glad you’re enjoying it. can you share one of the run files from the crash? it will be in dust/data/yggdrasil/runs.