#142

Mentioned this on norns:dust thread. Seem to be a bug. Opened GH issue, probably a silly error on my part

1 Like
#143

Cheers, I appreciate all the work you’ve done on this project. It’s a marvel.

#144

@zebra that’s totally my fault, i won’t let you take responsibility :slight_smile:

we’re actively trying to solve the lockup-on-wifi issue, i apologize for the alarm

3 Likes
#145

i have a Maiden Question just for clarity
Whn i have the Norns device connected i can edit and change the patches live and just press the play side arrow on the Maiden Website
and i think this was kind of answered i cannot “connect” to the norns/matron via software correct?
It would be super nice if say i am developing on the raspberry for like learning Norns etc… that i could edit lua scipts in the ~/Dust/shree/folder and hear them via SC

i hope that was clear

Also is ALL of Supercollider available for engines?
Like i know i want to make a gendy~ engine etc…

#146

{Pan2.ar(Mix.new(Gendy3.ar(0, 0, SinOsc.kr(0.1, 0, 0.1, 0.9),1.0, [100,205,410], 0.011,0.005, 12, 12, 0.12)), 0.0)}.play

for example

#147

Also is ALL of Supercollider available for engines?

supercollider core and sc3-plugins. includes GendyN

edit lua scipts in the ~/Dust/shree/folder and hear them via SC

i’m sorry i just don’t totally get it. you could connect to matron through some other client besides maiden if you want? including something in SC i guess?

can you put your intended usage more clearly? and is this something we should generally support, or is it more of a solo endeavor?

#148

matron/sc is running a norns

i fire up maiden and start editing a lua script
i press play
Norns plays my changes

earlier you said why don’t i do that in SC but i thought the idea was to learn the lua

#149

So maiden as IDE i guess long way around
Sometimes i really think a 5 minute phone call is ideal for clarifications LOL

#150

26 posts were merged into an existing topic: Norns: Development

#151

A post was merged into an existing topic: Norns: Development

Norns: development
#152

I think my TestSine engine might be a bit unhappy, I was having trouble to get the amplitude modulation to work in the first study, then pared it down to this code:

engine.name = "TestSine"

function init()
  engine.hz(100)
  engine.amp(0.8)
end

which provokes this error:

norns.script.load("study/SVSVSV/untitled.lua")
# script load
# cleanup
# script clear
# script run
loading engine; name: TestSine
<ok>
Engine.register_commands; count: 2
--- engine commands ---
amp (f)
hz (f)
------
--- polls ---
amp_in_l
amp_in_r
amp_out_l
amp_out_r
cpu_avg
cpu_peak
pitch_in_l
pitch_in_r
tape_play_pos
tape_rec_dur
------
# script init
### SCRIPT ERROR: init
/home/we/dust/scripts/study/SVSVSV/untitled.lua:5: attempt to call a number value (field 'amp')
reconnecting grid...
grid.reconnect (default)
reconnecting midi...

Has anyone seen similar? It’s late here so I’m fully expecting it to be something I’ve missed.

#153

Does the error go away if the init function is written like:

init = function()
   ...
end

? (I wouldn’t except it to but I’m also not seeing anything odd in your example but it’s early here and I haven’t had any coffee :coffee: yet)

1 Like
#154

How should one go about sharing scripts? I have very little github experience, so if it involves gh… details would be greatly appreciated!

#155

Thanks, I’ll give that a shot. I should also mention the sample code for the study throws the same error when modulating amplitude

#156

if you have a github account you could create a gist - just login and create it at https://gist.github.com/. generic example:

1 Like
#157

not sure what the best way to share them would be though. you could always just post it in the scripts thread, but gists are nice because each author could link to their gist page, others can comment, etc. and it might be less likely to get buried on here.

5 Likes
#158

20 characters of great idea!

#159

You mean just setting it right?

What does the repl tell you if you type the commands directly into it?

That is, at the >> type:

engine.name = "TestSine"

<enter>

engine.hz(100)

<enter>

engine.amp(0.8)

<enter>

What does it say?

#160

@dansimco

just a heads up that

engine.name = "TestSine"

doesn’t actually load the engine. the name is set, but the script-loader actually loads it behind-the-scenes with

engine.load(engine.name)

so if you want to directly try loading the engine do

engine.load("TestSine")

also your error is completely confusing. can you try rebooting?

1 Like
#161

What’re people’s battery experiences so far? I thought I’d read somewhere that the battery was meant to last longer than it’s seeming to. Any suggestions around leaving it plugged in and just topping it off like a phone? I get noise when trying to input audio if it’s connected to a laptop, so I usually skip that.

Or perhaps there’re stats elsewhere I’m missing?

It’s entirely possible that I’m just using it WAY too much :slight_smile: