#116

Are you going out of the JF into a Nearness? I had noticed you had all 6 outs patched into SOMETHING right next to it and it dawned on me last night while playing around trying to get some stereo spread out of the output of the JF that maybe that’s what you were doing there…

1 Like
#117

Yep. TELEXn. That way all 6 voices can be panned. Except I had accidentally left Milky Way’s secondary setting that adjusts the panning of the input channels to a central location that essentially collapsed my beautiful panorama into a narrow field :confused:

2 Likes
#118

Ya! Great idea! I’m gonna have to get me one of those. The lack of spread on the 6 voices now that I’m using Crow is driving me nuts.

1 Like
#119

TXn + JF = soulmates

7 Likes
#120

Not sure if this is a question specifically for Awake but has anyone encountered issues with crow clock out stability? I can’t get it to reliably clock my Pam’s New Workout - the Pam’s always either shows the clock drifting by +/- 2bpm, or shows “unstable!” when I’m trying to use crow as the master clock.

#121

yes! long story short, it’s a pam’s thing / not a crow thing. discussion/solution starts here: ^^ crow help: general (connectivity, device q's, ecosystem)

#122

Hi All,
Having problems with Awake Rings, getting an “error: init”

Maiden details 
# script load: /home/we/dust/code/awake-rings/awake-rings.lua

# cleanup

# script clear

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

pset >> write: /home/we/dust/data/system.pset

# script run

loading engine: KarplusRings

Engine.register_commands; count: 8

___ engine commands ___

amp f

bpf_freq f

bpf_res f

coef f

decay f

hz f

lpf_freq f

lpf_gain 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-rings/awake-rings.pset

### SCRIPT ERROR: init

/home/we/dust/code/awake-rings/awake-rings.lua:296: attempt to call a nil value (field 'pan')

stack traceback:

/home/we/norns/lua/core/norns.lua:126: in field 'pan'

/home/we/dust/code/awake-rings/awake-rings.lua:296: in field 'action'

/home/we/norns/lua/core/params/control.lua:77: in function 'core/params/control.bang'

/home/we/norns/lua/core/params/control.lua:59: in function 'core/params/control.set_raw'

/home/we/norns/lua/core/params/control.lua:49: in function 'core/params/control.set'

/home/we/norns/lua/core/paramset.lua:247: in function 'core/paramset.read'

/home/we/norns/lua/core/paramset.lua:265: in function 'core/paramset.default'

/home/we/dust/code/awake-rings/awake-rings.lua:311: in global 'init'

/home/we/norns/lua/core/script.lua:77: in function 'core/script.init'

[C]: in function 'xpcall'

/home/we/norns/lua/core/norns.lua:127: in field 'try'

/home/we/norns/lua/core/engine.lua:90: in function </home/we/norns/lua/core/engine.lua:88>

>> reading PMAP /home/we/dust/data/awake-rings/awake-rings.pmap

I’ve read through the thread, hoping someone hit this before, though I was half awake so may have missed it. Still getting the hang of things. Any help appreciated.

edit: To clarify, Awake runs in the background but I can’t get to the UI to edit the sequence.

I’m running the most recent version pulled down via maiden (attempted an update this am, most recent version installed).

I’ve tried removing everything contained in data/awake-rings to no effect. Same errors in matron.

Also, Awake runs just fine. It’s only awake rings throwing the error

#123

I’ll take a look. Are you running the latest version of the code on github? And have you tried removing the files under data/awake-rings??

#124

I got an identical error running Awake yesterday. But the script still booted and ran just fine. Let me know what you find out!

#126

Getting the same pan errors as @coreyr @mattlowery with the rings version of awake today. I’ve tried loading the latest from GitHub, and cleaning out the awake-rings files in data as well.

#127

OG awake has some new parameters that deal with panning. Awake-rings appears to be a fork, but with exactly the same name and path, but which is not in sync with its parent? Recipe for problems? Rename?

2 Likes
#128

It started out as that, since it was clearly the easiest way to keep in sync with the changes to Awake. It’s now in a repo, with a different name, so I’m not sure what you mean by name and path?

I’ve been manually merging in the changes made to Awake, but perhaps I’ve missed something? (Works on my Norns!).

#129

yeah sorry that was totally my misunderstanding, was searhcing on phone and found reference to old fork, not new repo. sorry

now that i’m not looking on a dumb phone, i instead interpret the error message above to mean: whatever verison of KarplusRings engine is being loaded, doesn’t include pan commands that correspond to the ones added to PolyPerc engine. (so yet again this is an annoying side effect of the no-duplicate-classes restriction; we really need to finish integrating the workaround for that, allowing compatible copies of script and engine to be bundled for deployment. continued apologies.)

but anyways, for now @coreyr @sunbeamer @mattlowery make sure you have also updated the we repo since i’m guessing that’s where you got KarplusRings. looks like it should work on the latest.

5 Likes
#130

Huh, thanks @zebra, that does the trick. My WE was only a few days old I thought but I must be wrong.

1 Like
#131

same problem here with awake-rings. where is the we repo? Update via maiden doesn’t solve the issue.

#132

You’ll find it under the new Norns package manager, and also here: https://github.com/monome/we

2 Likes
#133

done thank you…

#134

hi did you ever get this sorted? Ive run into the same issue and I too have never coded. Thanks!

#135

I deleted we via maiden then reinstalled, that did the trick.

2 Likes
#136

since the most recent Norns update it seems im getting an error init upon loading the kr rings script. It does actually load but I do not have any control over the script. Does this need to be updated or?