This is a great addition! More for the Arc!

2 Likes

Cool, lmk and I’ll merge master from your repo into mine. These single scripts make merging diffs a bit complicated but I only have ~ 3 deleted lines so crossing my fingers.

I checked off almost all the items on my list last night. All that’s remaning is how to divide up the 16 voices into 4 groups for the arc LED rings to display as enc2 scrolls through the voices. I go back to the day job tomorrow so I won’t have as much time as the last few days.

update: I figured out the voices and LED ring display feature. So this script now does everything I was looking for before I started without breaking existing features! That I know of…

WIP pull request just so I don’t forget about this during the week. I did a tiny bit of refactoring, sorry! I think these changes create some neat live performance capabilities. I’ve been playing along to random music I’m listening while working and I can always get a nice little harmonic bed to add to whatever is playing. The encoder resolution is so high I can nearly sync envelope cycles manually to a beat!

1 Like

Could it be possible to have the option for the envelopes to be synchronized to an incoming midi clock and if so be able to set quantized multiplication/divisions of the incoming clock rate? Really great script BTW, thanks!

2 Likes

I’m using the metro subsystem. I think the new-ish clock subsystem would be better suited to what you’re looking for. Take a look at the docs and see what you can come up with. I haven’t worked with the clock module yet so I can’t estimate what kind of work would be required. At the minimum replacing all the metro methods with clock methods could be where to start.

2 Likes

Awesome! Give me a few days to process :slight_smile:

2 Likes

very cool script, really digging it, however i found a behavior that seems like a bug:

  1. make cool drone, setting some of the sines and settings the way you like 'em
  2. save as a PSET
  3. later load PSET

result: original drone plays perfectly, however the GUI and settings in the screen are all set to their original default settings/notes/etc. and any adjustment on the sines that were already in the PSET that was loaded get reset to the original values when attempting to tweak the saved values.

not a coder (yet), but seemed worth sharing, thx again for the script!

This is a legit bug. Working on a refactor that corrects this. Basically moving all settings to standard Norns params. Nearly finished.

2 Likes

This doesn’t appear to be in maiden anymore fyi @Oootini

1 Like

It is for me. Refresh?

Weird, not showing up for me even after refresh (probably something I’m doing wrong though)

Did you refresh the community catalogue?

in maiden go to project manager (third symbol from top on the left), click on available on the top, next to community click on the arrow circle… Sines is listed underneath showers and before skylines.

(Not sure how the catalogue behaves if your norns is not up to date).

Don’t know, what I am doing wrong but since I last updated (a few days ago and again just now) midi mapping and my controler works to control the sines but the display does only reflect changes when I use the encoders.

I don’t know whether this is the behaviour you are experiencing but it seems kind of similar.

Working for me now, think it was some sort of chrome cache issue. Cheers!

1 Like

updated to 0.8, grab it from maiden. this hopefully fixes all the gui/param issues. all params are now standard norns params, everything is midi mappable. Also added bit depth/sample rate fx.

i’m still a massive noob at this, so please shout if you find anything broken. thanks to @doomglue for patience and testing and @zebra for the sc help:)

4 Likes

Hi,

I just updated and got an error (and a black screen) in maiden while trying to set the root note in the param section:

invalid paramset
lua: /home/we/norns/lua/core/paramset.lua:357: invalid paramset index: note17
stack traceback:
	[C]: in function 'error'
	/home/we/norns/lua/core/paramset.lua:357: in function 'core/paramset.lookup_param'
	/home/we/norns/lua/core/paramset.lua:263: in function 'core/paramset.get'
	/home/we/dust/code/sines/sines.lua:319: in function 'redraw'
	/home/we/norns/lua/core/menu.lua:156: in field 'set_mode'
	/home/we/norns/lua/core/menu.lua:126: in function </home/we/norns/lua/core/menu.lua:116>
lua: /home/we/norns/lua/core/paramset.lua:357: invalid paramset index: note17

I am quite sure the update ran through because I can see the new and detailed param section. I am now on c09df64 (says maiden)

Thanks for your hard work! I am pretty sure that you are not a ā€˜massive noob’ anymore (that’s me you are talking about :slight_smile: ).

1 Like

Can you delete previous psets and try again?

edit: i think there is a bug related to sines.lua:218:

--allow root note to be set from midi keyboard
if d.type == "note_on" then
  params:set("root_note", d.note)
end

I’ve commented this out and will investigate. In the meantime, just update the app, it should work as before. I think norns can be picky when it comes to multiple midi devices. Maybe I need to specify where to expect, for example, the midi keyboard? midi.connect(1)

Edit: this bug is related to the code for setting the root note from a midi keyboard.

wow just tried this out and i love it! so meditative and instantly musical, but the bit and sample rate controls are a great touch for a bit of edge :slight_smile:

your long lost norns board is a ways from home but glad I could give it a lil taste of the leeside :pleading_face: in the immortal words of seamus heaney — visitations are taken for sinesss ~ ~ ~

… at least i think that’s what he said…

2 Likes

that just made my night.

1 Like

Pushed a very small, minor fix - slider values weren’t being saved with psets.

4 Likes

Thank you so much for this script. It’s just a complete delight to play with. I’ve been listening to it drone along for a few hours now whilst I read and I think I could listen forevermore!

2 Likes