#170

Hi Gerald (welcome!)

Not sure if you’d already worked through the studies or not - Study 5 hits on some basics of using OSC from Max (should be similar from pd).

Here’s a copy of Study 5 if you want to grab it and drop it onto your device (at ~/dust/code/we/study/) study5.lua (3.4 KB)

for your situation (mimic a grid) I think what’s needed is a little OSC-to-grid library… so that maybe you could drop this in, change a line or two of code and get the touchosc grid working with other scripts.

I’m gonna try a few things and report back.

#171

hi gerald curious if you’ve made any progress on this?

#172

It mostly works. Needs a bit of help. Thread here:

#173

On study 4, with my GS64 I’m not able to get the sequencer running.
It’s surely related to the non varibright quality of my grid but is there a workaround?

#174

are you able to get any lights to turn on? do you get key feedback? do you have the grid selected in the SYSTEM > DEVICE menu?

#175

Yes, my GS64 is working. I can use it with apps like Awake.
I’m reading the studies. In the Physical part, I cannot get the sequencer running. Since my grid is a non varybright one, this could be a syntax thing.

#176

I also have a GS64, and I can’t get the sequencer to run, either. After copying and pasting the code from the lesson (which comes after “let’s take this decoupling a step further”), I have the following error:

# script init
metro_stop(): pthread_cancel() failed; error: specified thread does not exist
metro_stop(): pthread_cancel() failed; error: specified thread does not exist
>> reading PMAP /home/we/dust/data/sketches/grid_test/grid_test.pmap

I tried changing the sequence length and modulo to 8, but to no avail. I also saved the script and restarted in case it was an engine thing, but from the command line I can make it make notes. I can also ask it what position it’s in, and it remains in the init position. It’s also worth noting that the grid redraws – I can choose values and they are stored in the appropriate tables.
I change g:led(i,steps[i],i==position and 15 or 4) to
g:led(i,steps[i],i==15)
so I can see all the steps, but the metro doesn’t run. I can get the other metro scripts to run without using the grid. And the grid works with Earthsea.
Thoughts, anyone?
– note, running GS64 on DIY Norns/3B+ with no USB hub, plugged in with sufficient power supply

#177

sorry i don’t have any particular insight on the actual problem (will look if i get a minute), but fwiw:

those pthread_cancel errors happen a lot, somewhere metros are sometimes being “double stopped”, i haven’t been able to track it down but have also not observed any resulting problems.

#178

Yeah, I’ve now re-run the script and am not getting those errors any more… (sequencer still isn’t running tho).

#179

a quick visual inspection suggests that study 4 is using old and wrong syntax for specifying metro callback and thus it is not working. try changing callback to event. (i also think it’s gratuitously confusing to name the callback function count when the metro count field is also named that.)

@tehn or whoever, looks like study 3 has been updated but study 4 needs a look

2 Likes
#180

Got it!

So the tutorial declares all the counter stuff outside of/before init(), so I moved it into init() (like study 3) and changed counter.callback to counter.event, and now everything works properly.

1 Like
#181

since you’ve got the thing in front of you maybe its a great time for a PR!

1 Like
#182

It will be my first one… I’ll try to figure out how to do it! :grimacing: :sweat_smile:

5 Likes
#183

Where is a good place to read about the UI class?

Aside from the source, i’ve found this: https://monome.org/norns/classes/UI.html

Any suggested places i should check out to maybe see an example usage?

#184

There is a UI demo in the we repository here.

2 Likes
#185

Exactly what i was looking for, thanks!

1 Like
#186

Ah my we package was super out of date on my norns, looks like i was missing out on lots of neat things there.

1 Like
#187

Pedalboard has a fair bit of UI widgets. I’ve also used them a bunch in the mi-engines test scripts (although I wonder if my implementation is a little wacky)

#188

Is there a way to detect the pitch of audio input without hearing the audio input ? It seems like audio pass through is a default, I can’t find any code that enables it . . . nor a way to disable it. Is there a way to do so ?

#189

Small wish for a possible future study(although I’m not sure how complex it would be to do):

How to combine 2 existing scripts.

4 Likes