#524

alternatively, at the moment you could connect SC to all the output channels and simply redirect the norns supercollider output (here: https://github.com/monome/norns/blob/master/sc/core/CroneAudioContext.sc#L62)

(this will change in norns 2.0 release, which doesn’t use supercollider for output mix. but murray’s suggestion will still be broadly applicable.)

1 Like
#525

Thank you. I will take a closer look at that tomorrow and try both suggestions :slight_smile:

Edit:

The jackconnect and jack_disconnects work fine / I created a script, unfortunately I’m having issues with the clock source with this interface so I will not use it with the RPi, it’s too hard to debug and not very handy in my setup.

Remap channels 
#Inputs

jack_disconnect supernova:input_1 system:capture_1
jack_disconnect supernova:input_2 system:capture_2
jack_connect supernova:input_1 system:capture_5
jack_connect supernova:input_2 system:capture_6

#Outputs

jack_disconnect supernova:output_1 system:playback_1
jack_disconnect supernova:output_2 system:playback_2
jack_connect supernova:output_1 system:playback_9
jack_connect supernova:output_2 system:playback_10
#527

I know it’s an old post, sorry but I have exactly the same problem with Maiden (not connecting to Matron and SC), did you find a solution/the cause ?

I tried to disable my Firewall, I tried on Safari, Chrome, Ipad. There’s no obvious error message in the logs…

#528

Dumb question - but what’s your maiden path? ~/maiden/ ?

and then check your paths in ~/norns-image/config/norns-maiden.service which gets copied to /etc/systemd/system/norns-maiden.service on norns-image setup

Mine looks like this

[Unit]

Requires=norns-maiden.socket

After=norns-matron.service

[Service]

Type=simple

User=we

Group=we

WorkingDirectory=/home/we/maiden

ExecStart=/home/we/maiden/maiden.arm -fd 3 -app ./app/build -data /home/we/dust$

[Install]

WantedBy=norns.target

also maybe check ps aux for what’s running

we@norns2:~/norns-image $ ps aux | grep maiden
we         377  0.0  0.9 804184  9024 ?        Ssl  Jan02   0:00 /home/we/maide/maiden.arm -fd 3 -app ./app/build -data /home/we/dust -doc /home/we/norns/doc
1 Like
#529

If I’m understanding things correctly you can access maiden (the editor) but the matron and sc repl’s aren’t connecting.

Several things worth checking:

  • Ensure you are using the systemd units or the various start.sh and stop.sh scripts to start matron and supercollider, those script ensure that the processes are run under ws-wrapper which provides the web socket connections maiden uses to talk to matron.

  • If you pulled a very recent prebuilt copy of maiden off GitHub (like the 0.10) release there was a modification to the repl configuration made during recent development which shouldn’t have been committed. I just corrected that mistake. Verify that the repl-endpoints.json file in your copy of maiden looks like this: https://github.com/monome/maiden/blob/master/app/public/repl-endpoints.json

  • If the repl-endpoints.json file matches what is up on GitHub and the ws-wrapper processes are running then I would look for errors in the Javascript console of you web browser and verify there isn’t a firewall on either you computer or the rpi which is blocking connections on ports 5555 and 5556.

1 Like
#530

Thanks for your replies @okyeron and @ngwese

Yes, the path is exactly the same for me.
/etc/systemd/system/norns-maiden.service

Yes, that’s correct. And yes, I pulled Maiden 0.1 a few days ago. My repl-endpoints.json looked like this:

{
"matron":"ws://norns2.local:5555",
"sc":"ws://norns2.local:5556"
}

But I’ve just made the modification…

{
    "matron": "ws://maiden_app_location:5555",
    "sc": "ws://maiden_app_location:5556"
}

…and the issue is now solved, Maiden connects to Matron and SC. Thanks a lot !

1 Like
#531

Oh cool. Glad you got it working.

1 Like
#532

Hi!

I have a DIY Norns with 6 GPIO buttons.
I do not have room for encoders in my case, so I thought about mapping the 2nd encoder’s GPIOs to 2 of my buttons.
Now, how should I go about doing this?
Should I modify some part of matron’s code handling the encoders, or go for the dts overlay files instead?
I did the latter to get the key buttons to work, but I don’t know how to set things in a way that let me use an encoder only with buttons.

Thanks.

#533

Just throwing in this idea: some kind of Teletype-like Norns derivative with a few extra DC coupled ADC/DAC channels would be really, really cool. (or maybe just keep it stereo in/out and add a jumper connector to patch it into a Crow or two on it’s side, just so that projects made on it are fully compatible with a standard Norns + Crow setup)

1 Like
#535

I’m legit curious if the global economy (including supply chain) for Monome products is interesting enough to motivate hardware cloning operations. In a way it gives me hope to think that a boutique electronic music instrument company has done so well it attracts attention of the global bootlegging industry. If a bootleg market emerged it could be considered a compliment. “Wow, we’re doing so well companies are copying the products,” but at the same time you’d probably have to lawyer up, support nightmare, PR nightmare, etc, etc.

A colleague of mine had this happen to a product he worked on called TV-B-Gone. It’s comparable in that it attracted international attention, which caused bootlegging operations to manufacture units and sell them on Alibaba.

#536

Have folx been able to connect/light their monome with just the onboard USB power? I ran into some issues with random reboots when trying to power a lexicon alpha with just an RPi3+, and I’m not sure if I should try and mitigate by using an ext5v with the audio interface or buying a power usb hub that’ll work for both the lexicon alpha and a 128.

In the meantime I’m just using the standard audio out :stuck_out_tongue:

#537

I guess it depends on your definition of “bootleg”.

Novation Launchpad
Akai APC
Ableton Push
Livid Block, Ohm
Synthstrom Deluge
Polyend Seq, Medusa
Adafruit Untz, Trellis
etc

But I’m probably being too clever and you really do mean an exact duplicate. I’d be astonished if an Alibaba cloner got the fasteners right, let alone the beauty of the PCB design. Have you ever looked at the inside of one of these machines? I’m sure you have, and I imagine you’d agree that they are designed to a higher bar than typically disposable electronic products.

I still think @tehn should bring back the 256 though. It’s my most treasured monome device.

7 Likes
#538

I would definitely supply separate power to the grid. It’s a thirsty beast and so is the RPi.

1 Like
#539

I’m interested in this board for another project I’m working on. What info are you willing to share?

#540

Well, I can share the schematic or a spare board of this prototype, PM me if you want ^^

#541

Has anyone attempted running the pre-2.0 code on pi yet?

Im having crone issues and not sure how to debug

#542

Not yet, but will do once it’s imminent for release ( or released :)). - I’m not sure how ‘fiinished’ it is at the moment , and don’t want to create noise around something that’s not known not to be quite ready yet.

2 Likes
#543

Not looking to create noise about it really. I contributed some bits and I want to get my test/demo scripts updated with other system changes. Devs are focused on the main hardware so I don’t want to delay/derail any effort there.

#544

@okyeron happy to help debug if you want to post compile errors to the pre-2.0 github issue

1 Like
#545

i wasn’t suggesting you were … i was saying why I hadn’t tried to upgrade it yet.
if its in a “stable” state, a point where testing and feedback is useful - then id be happy to give it a go.

1 Like