Thanks Dude -all sorted - nice and responsive ui again… No idea how that happened

1 Like

Here’s what happened - you added a new script from the Librarian that included an engine that was already installed. In this case it’s because your we directory is out of date and had an old engine in it from a previous software update. You should probably update the we scripts from https://github.com/monome/we

4 Likes

Im super interested in Norns polyphonic capabilities.

If I simply plug in a keyboard, how many voices will i get?

How many samples of instruments can i control - or is it just synth voices?

I know it is all open source, but i’m curious what is out now.

That’s dependent on the script and its sound engine. Most of the scripts currently in the library range from monophonic to seven or eight voices, but I’ve also used an engine of @zebra’s with 64 voices of (only) sine waves. Usually the limits on voices aren’t arbitrary, they’re based on what the sound engine can produce without breaking up.

Also bear in mind not every script exposes its sound engine directly to midi input, so it is important to check the requirements in each script’s library post to see if it works with midi input and output. Some scripts use their own sequencers, or expect a grid or arc rather than midi input.

2 Likes

Check out the Library for the currently available scripts/instruments. For keyboard playing, checkout @markeats Molly The Polly or @tehn’s Earthsea (earthsea is part of the ash collection). There are others, but those come to mind :smiley:

Hey, thanks for getting back to me so soon! Here is what comes up:

SCRIPT ERROR: init

/home/we/dust/code/mlr-master/mlr.lua:280: attempt to call a nil value (field ‘phase_offset’)

stack traceback:

/home/we/norns/lua/core/norns.lua:185: in field ‘phase_offset’

/home/we/dust/code/mlr-master/mlr.lua:280: in global ‘set_clip’

/home/we/dust/code/mlr-master/mlr.lua:417: in function ‘init’

/home/we/norns/lua/core/script.lua:71: in function ‘core/script.init’

[C]: in function ‘xpcall’

/home/we/norns/lua/core/norns.lua:186: in field ‘try’

/home/we/norns/lua/core/script.lua:160: in function ‘core/script.run’

/home/we/norns/lua/core/script.lua:146: in function ‘core/script.load’

/home/we/norns/lua/core/menu.lua:423: in field ‘key’

/home/we/norns/lua/core/menu.lua:164: in function </home/we/norns/lua/core/menu.lua:141>

reading PMAP /home/we/dust/data/mlr-master/mlr/mlr.pmap

(apologies for any weird formatting)

You need to rename the folder to mlr/

edit: @tehn, this apparently didn’t work/is not the solution to this particular problem.

Hello, yesterday I had a chance to load Otis onto Norns and when I went to take advantage of it, I accidentally created something like “untitled.lua” When I hit the minus sign to remove this mistakenly created blank Lua patch, my whole CODE folder was deleted. @Justmat has accidentally deleted this folder too and I’m sure we aren’t the only ones. while we were chatting, he suggested there should be a confirmation message that one would need to accept to delete something as important as that whole folder. Don’t know if we could implement something like that in Maiden.

now to get me back up and running… what’s the most efficient way for me to get everything back to normal? Should I try to install 2.0 from scratch? other options?

also, at this point, if I do reinstall 2.0 from scratch, would certain issues be fixed in the official firmware like @lazzarello FM7 having a duplicate engine to something in the studies (I can’t remember the issue I had but it was something like that)? or does that need to be manually adjusted again?

thank you all in advance for any help you can offer me.
-Brendan

if that’s all that you deleted you just need to create the code folder again (~/dust/code) and add whatever scripts you want (+ restart), being sure not to add duplicate engines. FM7 is no longer in we so no need to worry about that one in particular.

Plan is to disable deletion for the code folder in maiden

2 Likes

@speakerdamage @zebra thank you for your help. all good now! :slight_smile:

2 Likes

Trying to sftp into Norns through Cyberduck to update some scripts, which I do all the time – as recently as yesterday with no issue.

Last thing I did yesterday was update Orca and everything seemed to be working fine.

Today when I SFTP’d in I got a message that the “connection failed (connection rejected)”.

Haven’t changed anything on my computer or Norns.

I rebooted my computer and the Norns a few times.

One time I was able to connect and update one script. then after updating the script the Norns disconnected and I got the same “connection failed (connection rejected)” message.

Now I’m getting that error message every time.

Also can’t seem to connect to maiden through the browser.

Apps on Norns seem to otherwise be functioning fine.

Any thoughts?

Check the IP for norns on the system wifi page as it can change

I re-entered it manually. It was the same but the issue is still persisting.

I see a number of similar reports that seem specific to cyber duck, maybe worth checking another client? (Transmit, FileZilla, terminal &c)

IOW: can you ‘ping’ Norns IP from terminal? If so, can you ‘ssh’ or ‘sftp’?

(You did say maiden wasn’t working either, so I dunno)

1 Like

when I try to ssh in terminal I get a message that says:

ssh_exchange_identification: read: Connection reset by peer

Also: maiden working fine in hotspot mode. But still not connecting when on my normal wifi connection. I tried deleting my wifi account and re-adding to Norns but still having same issues.

I used Transmit and it worked fine.

No idea why the other methods aren’t working but I’ll take what I can get…

Is it possible in 2.0 to have the tape playback go through the reverb chain? I can hear it going through the compressor, but it’s not affected by the reverb settings and there is no rev tape input parameter. (Tape also doesn’t show up on this diagram in the docs.)

Having tape skip reverb in the default configuration makes a lot of sense, but if you want to play something back with reverb, does one of the existing scripts make that possible?

its not possible with the current routing scheme. tape playback is summed after cut send, after aux send (reverb), before insert (compressor). this is all internal to crone client.

full routing diagram:

it’s not hard to change this and could be a cool thing to have. (add send busses for tape->cut, tape->aux.)

2 Likes

Cool, thanks! I managed to convince myself that no reverb was the correct artistic choice for my immediate needs, but this does look like a straightforward addition, I’ll try to put together a PR.

1 Like