#81

Sure thing. I figure RPis are cheap and norns is a bit complex, so there’d be benefit from clearer isolation, but to each his own.

3 Likes
#82

Once norns is running on an Rpi+PiSound it would be awesome if an OS image of that setup was uploaded

2 Likes
#83

Hi @zebra, not sure if this is something you’ve come across but long story short, I’m trying to get maiden working after having some success with both crone and matron, one of the requirements is the latest version of nodejs and npm. Anyway, when trying to use curl -sL https://deb.nodesource.com/setup_10.x | sudo -E bash - this is the output

## Installing the NodeSource Node.js 10.x repo...

Populating apt-get cache…

Any pointers would be great! I know you’ve got a lot on your plate.

Alex

#84

You need version 8 10 won’t work it’s in my notes that I was scolded for because they were messy does it say 10 in the official docs?

#85

Regardless, when installing it seems stuck at V4, I wasn’t sure if the list wasn’t updating because of the repository authentication fail or not.

#86

https://github.com/ngwese/maiden/blob/dev/app/README.md

That lists npm v6

#87

you want at least 8 or yarns wont work one sec lemme find my notes

#88

for node.js
curl -sL https://deb.nodesource.com/setup_8.x 1 | sudo -E bash -
then
sudo apt-get install -y nodejs

#89

Here are the “apt-get” based commands for Node.js installation and upgrading:

Use the following command to checked the current version.
node –v

We have to run the “update” command on the server to know the update packages before we upgrade it to a higher version.
sudo apt update

Run the following command to upgrading the packages.
sudo apt install nodejs

Run the following command again to check it has been done.
node –v

Once the upgrade has been completed you should have to upgrade the packages on the server with the command mentioned below.
curl -sL https://deb.nodesource.com/setup_8.x 1 | sudo -E bash –

Run:
sudo apt update

#90

@shreeswifty i finally sat down and made a basic but extremely commented script using SoftCut engine (same as MLR.) maybe something like this can be integrated into a study. it took me longer than necessary cause i also got ambitious with making a barebones sampler engine demo; maybe will get around to finishing that.


(2 asides:

  • i’ve found that i can crash scsynth by flapping around past 0 with negative rates. dumb.
  • dang, i’m not happy with the corners we cut for performance here. (linear resampling on playback, control-rate modulation of playback.) we’ve made some jack config adjustments, maybe we can squeeze the good-sounding stuff back in there.

these are related (ugen code) and i’ll put them on my list / on the GH issues.)

re: screen
sorry, my eyes kind of glazed over with the DPI / GL output. it seems like you’re trying to set up supercollider to do openGL stuff on rasbpi. ive never done this, and it has little to do with how we use SC in norns (we run it headless and do all gfx stuff through cairo in matron.)

i have proof of concept for building and running matron with cairo connected to x11 instead of framebuf

i’ll try and clean this up and get it together as a proper option when compiling matron (i don’t want to compromise norns hardware experience by always requiring libX11 and switching the setup at runtime.) but honestly i’m right in the middle of working week and this isn’t top priority (would rather work on audio side.)

6 Likes
#91

@Taubaland sorry, i’m not sure. @ngwese is the badass who did all the work on the webserver and maiden components.

(and oops, sorry about mixing up my replies.)

#92

I’ve been working on macOS and using homebrew which means I’ve been using very current versions of the build tooling (maybe current in an excessive way). I can imagine that older version of the tooling will work but I haven’t been testing that.

Given that you have the catfact deb repositories in your log output is it safe to assume you are trying to build maiden directly on the device? Building on the device isn’t a requirement and is not something I’ve actually tried since the toolchain would have consumed a ton a space…

…I can take a deeper look tonight about building with ubuntu 16.04 and on the device if that would help.

#93

yeah, i found the other day that 10 does not work on raspberry but 8 does i posted it a few posts up

#94

hey zebra
thank you for this and FWIW i am NOT i swear i am not fooling with GL for SC3 on raspberry there is a cool app i use for OSX but that error is there because of other stuff :slight_smile:
I only use GEM/pdp/pidip,pd-freeframe and pd-frei0r on raspi

#95

Thank you @ngwese,

Yeah, that’s what I was doing.

Sure, if that isn’t necessary, then it isn’t particularly urgent that it gets looked at.

@zebra, the stuff that I was taging you for was:

Just haven’t seen that before!

#96

ah thanks, makes sense. @artfwo actually set up the packaging on my server. my understanding is that these errors are NBD. @tehn we should probably move these to monome’s DO.

(mod hat: is this still particularly relevant to norns on Rpi, or more general dev?)

#97

(mod) @zebra sort as you see fit, your post above is universally relevant

#98

So I got “norns” working on the raspberry pi 3b+ (no pisound, just regular rpi audio out) and all is working like a charm (hearing sound, grid connecting, crone/matron and maiden working) except i can’t seem to get the norns screen visualizations working (also encoders and keys aren’t present at this time) :confused: has any1 been able to port the norns visualizations to supercollider GUI or something else that’ll work on a normal screen? Thanks :smiley:

5 Likes
#99

Would you mind to share your approach?

1 Like
#100

I just followed the setup instructions on the https://github.com/monome/norns/blob/master/readme-setup.md
I already had supercollider working with monome grid installed previously
Also had to build maiden using the setup instructions at https://github.com/ngwese/maiden/ (the release wasn’t working on my setup)

2 Likes