#96

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.

#97

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
#98

that just made my night.

1 Like
#99

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

4 Likes
#100

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
#101

Hi,

unfortunately I still have two issues:

  1. No feedback on screen

After mapping volume 1-16 to the controller (Sensel Morph) these work on the audio level but I still don’t get any visual feedback on the screen. No error messages in maiden.

  1. Error and black screen after mapping scale mode and root note

This is what I reproducibly get after trying to map scale mode and root note:

invalid param set 
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 'core/script.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
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 'core/script.redraw'
	/home/we/dust/code/sines/sines.lua:293: in function 'key'
	/home/we/norns/lua/core/menu.lua:44: in field 'event'
	/home/we/norns/lua/core/metro.lua:169: in function </home/we/norns/lua/core/metro.lua:166>

I am running the current version of Sines (just updated) on a Fates with the latest update. I also did delete /we/dust/data/sines every time I started a new try.

#102

I guess this might be related to what I get when I update via maiden.
“sines update failed: worktree contains unstaged changes”

1 Like
#103

Yes, thanks. I also noticed that.

I then deleted Sines completely and installed it again (which admittedly does not address this issue :wink: ).

I’ll wait until the repository is updated and see if the issues are gone then…

#104

I’ll have a look later

:edit the root scale/mapping issue is related to errors in how I’ve implemented the build_scale() function. I need to simplify how the note stuff works I think.

1 Like
#105

it just means you have made changes to something in ~/dust/code/sines (maybe unintentionally.)

update will wipe out these changes, so maiden takes a conservative position and doesn’t let you do it.

1 Like
#106

Thanks for explaining!

#107

I just noticed, that’s not correct. I don’t get visual feedback on changing the volume via midi. I now also checked with mapping detune and fm and these controls do give visual feedback.

#108

I’ve been noticing that if I go to params to change the scale, returning to “sines” gives me a blank screen. Also had some weirdness/crashes when changing too many of the note values. I’ve had some weirdness generally with my norns shield so I’m taking everything with a grain of salt, the changing scales issue has been consistently repeatable (never worked for me).

#109

I’ve pushed a change which hopefully fixes the scale/root note midi map issue. pick it up from maiden.

It’s also possible to now choose the root note from a midi keyboard, but in my limited testing, this only worked when i had a midi keyboard as device 1. I can’t explain why this works with keyboard as device 1 only.

@renegog very wierd that you can’t use the root/scale stuff. can you try this latest version please?

2 Likes
#110

any errors in maiden? please try the latest version.

#111

Hi @Oootini,

the error is gone. Great. I can map scale modus and root note.

But still there is no visual feedback for the volume though the midi control actually controls the volume. Only if I then move e. g. the attack slider (I have mapped volume, attack and decay right now) the screen switches to the current volume bar but the volume bar itself only moves if I use the encoders.

Am I the only one experiencing this behaviour? A problem of fates?

Let me know if I can do anything to help.

#112

I will test later. However is fates as up to date as norns? There was a general update on the 14th.

#113

Nope. I don’t think so. This is the last update I am on.

#114

Maybe a fates issue then? I can’t test this. Anyone else? This works on shield with latest update.

#115

There was an update here that changed screen levels: Norns: update 201202

1 Like