Demo on IG

6 Likes

Updated to v1.0.4

  • Added XPLSN page/feature
  • Tweaked FNDTN display
  • FNDTN auto sets to either startup sequence or last preset
6 Likes

Really enjoying these additions to Awake thanks.

I’ve long wanted performative presets mapped out to a second page on Grid and this is giving me encouragement to learn how to do it myself :ok_hand:

3 Likes

This version of Awake has been a lot of fun to explore, and the FNDTN has been especially useful - now looking forward to the XPLSNs!

1 Like

So glad to hear!

Playing around with XPLSNs last night, I realize I need a ‘light fuse’ button. Having the fuse immediately active can be a bit unexpected especially if the sequence is about to end.

Other thoughts:
Add a XPLSN type for inversion/mirroring.
Add a button to immediately apply the XPLSN or activate the fuse at 1.
Not totally sure XPLSNs are ‘musically useful’ - curious to hear impressions.

@Deru I’ll see if I can expand the code to set multiple FNDTNs, requires some refactoring.

2 Likes

That would be really interesting thanks!
I wonder if they could be pulled from other presets? Hmmm… Would that make sense?

Updated to v1.0.5

XPLSN changes:

  • Added light fuse/snuff fuse so fuse doesnt start immediately after you select a value
  • Added light quick fuse to light fuse = 1 with a button
  • Added types fndtn1-4 to support new fndtn presets

FNDTN changes:

  • Added 1-4 preset slots (this could be literally any amount but felt like 4 was just right)
  • Changed reset to foundation behavior - it will no longer reset the sequence position to start

Note: setting up complimentary foundations and changing them with XPLSNs is lovely, since XPLSNs always activate right as the sequence restarts

@Deru not sure how to pull from the ‘top level’ preset data but I feel like FNDTN preset slots work pretty well! I actually need to look into whether these are saved with the ‘top level’ presets… hmm, probably not. I hope to eventually get a grid and would love to surface some this stuff to the grid interface for performance purposes.

4 Likes

Amazing. I’ll check this out soon thanks.

1 Like

I used the new fuses on Awake-Mod to control my modular for tonight’s Sonic Sound Synthesis interlude - it was really handy being able to set all the steps to change or revert to the foundation at a more or less known future point while tweaking the knobs on the other side of the studio. I’ll definitely be using this more and more.

3 Likes

That’s awesome! Is there a link/time stamp on the show where I could listen?

Updated to v1.0.6

  • Refactor additions to separate lua files
  • add OPTION octave down/up buttons
  • keyboard support - really opens up the performance capabilities!
4 Likes

I had a play with 1.0.5 last night and I think you’re right about the multiple fdntn presets. They’re great and pretty much serve my performance ideas. As you eluded to, if these function were mapped to the grid (saving and recalling) it would fully check that box I think. I’m sure this is a great first project for me so I’ll keep it in my ‘eventual’ pile unless someone else wants to get to it first!

Cheers for this script.

2 Likes

Just awaiting the upload to Mixcloud from the station - will post here when it’s available.

Update: online now at mixcloud

The first 2021 session has been archived at Mixcloud: Mixcloud

1 Like

@shoggoth
i tried to update to 1.0.6 tonight.

all i get is an error:init message.
this was on multiple norns on the current OS.

thanks for any help!

Hmm… I recloned from github on my Norns to make sure I was getting the same copy as you and I don’t have any errors. Maybe try pulling again? If you still have an error, can you open maiden and copy/paste the error that’s posted to the matron console?

1 Like

ok…
finally had a chance to get back to this.
:slight_smile:
just re-downloaded and installed from GitHub.

it was still giving me the error init thing on multiple norns.

just did a re-install on norns #1 and it loads and goes to the Read Me page and then it just jumps back to the primary OS screen that has SELECT> SYSTEM> SLEEP>.

here is the report from maiden:

Summary

script load: /home/we/dust/code/awake/awake-mod.lua

cleanup

script clear

including /home/we/dust/code/awake/lib/halfsecond.lua

including /home/we/dust/code/awake/lib/keyboard.lua

including /home/we/dust/code/awake/lib/fndtn.lua

including /home/we/dust/code/awake/lib/xplsn.lua

including /home/we/dust/code/awake/lib/mod.lua

script run

loading engine: PolyPerc

reading PMAP /home/we/dust/data/awake/awake-mod/awake-mod.pmap

m.read: /home/we/dust/data/awake/awake-mod/awake-mod.pmap not read.

Engine.register_commands; count: 6

___ engine commands ___

amp f

cutoff f

gain f

hz f

pw f

release f

___ polls ___

amp_in_l

amp_in_r

amp_out_l

amp_out_r

cpu_avg

cpu_peak

pitch_in_l

pitch_in_r

script init

starting halfsecond

pset >> read: /home/we/dust/data/awake/awake-mod/awake-mod-01.pset

pset :: /home/we/dust/data/awake/awake-mod/awake-mod-01.pset not read.

SCRIPT ERROR: init

/home/we/dust/code/awake/awake-mod.lua:337: attempt to call a nil value (field ‘pan’)

stack traceback:

/home/we/norns/lua/core/norns.lua:138: in field ‘pan’

/home/we/dust/code/awake/awake-mod.lua:337: in field ‘action’

/home/we/norns/lua/core/params/control.lua:104: in function ‘core/params/control.bang’

/home/we/norns/lua/core/paramset.lua:437: in function ‘core/paramset.bang’

/home/we/norns/lua/core/paramset.lua:430: in function ‘core/paramset.default’

/home/we/dust/code/awake/awake-mod.lua:351: in global ‘init’

/home/we/norns/lua/core/script.lua:105: in function ‘core/script.init’

[C]: in function ‘xpcall’

/home/we/norns/lua/core/norns.lua:139: in field ‘try’

/home/we/norns/lua/core/engine.lua:91: in function </home/we/norns/lua/core/engine.lua:89>

@SPIKE did you try nuking your ~/dust/data/awake-mod/ folder?

1 Like

nuked it.
did a fresh install and a sleep.
now it goes back to the error:init message.
here’s the maiden data:

Summary

script load: /home/we/dust/code/awake-mod/awake-mod.lua

cleanup

script clear

including /home/we/dust/code/awake-mod/lib/halfsecond.lua

including /home/we/dust/code/awake-mod/lib/keyboard.lua

including /home/we/dust/code/awake-mod/lib/fndtn.lua

including /home/we/dust/code/awake-mod/lib/xplsn.lua

including /home/we/dust/code/awake-mod/lib/mod.lua

script run

loading engine: PolyPerc

reading PMAP /home/we/dust/data/awake-mod/awake-mod.pmap

m.read: /home/we/dust/data/awake-mod/awake-mod.pmap not read.

clock: ignoring resumption of canceled clock (no coroutine)

Engine.register_commands; count: 6

___ engine commands ___

amp f

cutoff f

gain f

hz f

pw f

release f

___ polls ___

amp_in_l

amp_in_r

amp_out_l

amp_out_r

cpu_avg

cpu_peak

pitch_in_l

pitch_in_r

script init

starting halfsecond

pset >> read: /home/we/dust/data/awake-mod/awake-mod-01.pset

pset :: /home/we/dust/data/awake-mod/awake-mod-01.pset not read.

SCRIPT ERROR: init

/home/we/dust/code/awake-mod/awake-mod.lua:337: attempt to call a nil value (field ‘pan’)

stack traceback:

/home/we/norns/lua/core/norns.lua:138: in field ‘pan’

/home/we/dust/code/awake-mod/awake-mod.lua:337: in field ‘action’

/home/we/norns/lua/core/params/control.lua:104: in function ‘core/params/control.bang’

/home/we/norns/lua/core/paramset.lua:437: in function ‘core/paramset.bang’

/home/we/norns/lua/core/paramset.lua:430: in function ‘core/paramset.default’

/home/we/dust/code/awake-mod/awake-mod.lua:351: in global ‘init’

/home/we/norns/lua/core/script.lua:105: in function ‘core/script.init’

[C]: in function ‘xpcall’

/home/we/norns/lua/core/norns.lua:139: in field ‘try’

/home/we/norns/lua/core/engine.lua:91: in function </home/we/norns/lua/core/engine.lua:89>

That is odd because I didnt touch anything with the engine parameters. Do you perhaps have a different version of the PolyPerc engine elsewhere where pan isn’t specified? It’s not part of my lib because I assume you have the standard awake installed and Norns barks if there are two of the same engine. Maybe try reinstalling vanilla awake since I rely on that engine?

Also - if anyone has suggestions on managing engine dependencies better, I’m interested (though should be fairly safe to assume everyone has vanilla awake/PolyPerc).

Also also - how do I tag this post with ‘Norns’?? It has totally escaped me

1 Like

AH HA!
(not the band)

so i nuked every version of AWAKE that was on norns (there were four) and all of their data folders as well.

did a fresh install of just AWAKE and AWAKE-mod and it’s all working.

note for anyone else running into this:
you need to install the original AWAKE otherwise the MOD version will complain that the PolyPerc engine is missing.

thanks guys for the help!

also…
@zebra could you add the norns tag to the Awake-mod thread?
it’s not appearing in the norns library search.
:slight_smile:

1 Like

Great! I could create a copy of the engine/rename it if this is a common problem.

Updated to v1.0.7

  • remapped K1/K2/K3 on keyboard
  • scale increased to 24 steps above root note
  • added oct up/oct down/delete on keyboard
  • added oct up/oct down/fractal xplsn types

fractal was inspired by the Qu-Bit Bloom documentation. I don’t own one but thought the various types of modifications on a base sequence were interesting.

3 Likes