#27

Oh excellent! I’m sure there’s a way to query the port from serialosc with PD as to avoid hardcoding it like that. That would be a nice addition.

This shell-script method with serialosc-device was a way to get up and running and proof of concept, but it isn’t necessarily the best way. I just couldn’t get serialoscd (the daemon) running correctly, which is designed to automatically starts/stop when a Monome is plugged in. It would seg fault for me when launching.

1 Like
#28

@quilime i’m not used to command line or github but have made it thru part of your instructions

how do i copy scripts onto the organelle?

#29

Hi @gila

Did you get WifI setup and are you able to connect to the network from your organelle? If you got that far, you can find your ip for wlan0 with ipconfig, and then SSH into it from your computer and copy scripts that way.

I’m going to see if I can streamline it a bit – perhaps by including everything in the Patch so you don’t have to install anything.

1 Like
#30

@gila Try this bundled version. I’m working out a way to distribute patches without any command line work.

https://github.com/quilime/organelle-monome/archive/bundle.zip

Copy the over the patches to Patches/ folder on the USB, and put the include folder outside of Patches/ so it looks like this:

Patches/
include/

Let me know if this works. I am curious if the serialosc binaries run without needing to be installed on your system and the port is the same (it’s hardcoded at 10405). You may have to manually adjust the port if it’s different, like @halvves had to do.

1 Like
#31

[quote=“quilime, post:29, topic:233”]
Did you get WifI setup and are you able to connect to the network from your organelle?
[/quote]i think so (script ran w/o errors and i was able to check the ip address)
just not sure how to verify it’s working correctly cause i’ve not done anything like this before

i don’t mind the adventure and most of your instructions are clear…i just have no background working in terminal to move files around

[quote=“quilime, post:30, topic:233”]
Try this bundled version. I’m working out a way to distribute patches without any command line work.

https://github.com/quilime/organelle-monome/archive/bundle.zip

Copy the over the patches to Patches/ folder on the USB, and put the include folder outside of Patches/ so it looks like this:

Patches/
include/
[/quote]thanks, really helpful

i’m gonna try this and report back

#32

IMG_1582.JPG2307×2448 2.14 MB

  • after getting the scripts in this bundle it still seems i need to install some dependencies, right?

  • are some of the steps for installation needed each time i power up? or will the organelle recognize the network card and monome automatically?

#33

Hi @gila,

Looks like it can’t find the includes. I updated the paths to be absolute. Download this new bundle and delete/replace the old ones.

https://github.com/quilime/organelle-monome/archive/bundle.zip

Verify the includes folder is on the root of the USB, not inside the patches folder. The folder structure on the Organelle’s USB should look like this:

  • usbdrive/
    • include/
      • monome/
    • Patches/
      • …
      • Monome/
      • Monome Basic Poly/
      • …

I assume you have a “vanilla” organelle without anything special installed on it, so this is a good test. I’m hoping you don’t need wifi installed or running with this method. No special setup should be needed.

I am testing with a 128 Grayscale. What monome do you have?

1 Like
#34

i’ve got a 128 too, from the most recent edition

will test with this bundle
thanks!

#35

[quote=“quilime, post:33, topic:233”]
Verify the includes folder is on the root of the USB, not inside the patches folder.
[/quote]done

[quote=“quilime, post:33, topic:233”]
I assume you have a “vanilla” organelle without anything special installed on it
[/quote]correct

monome appears connected

IMG_1588.JPG2299×1639 458 KB

still no lights

#36

Ok Cool!

Can you open a terminal and run the following? Could you copy and paste the output? (or take a picture)

/usbdrive/include/monome/start-serialosc.sh

Edit: I’ve confirmed on a formatted Organelle that the serialosc port can be different every time, meaning it doesn’t work to hard-code the PD patch. If serialosc-device runs properly, and you do see a port number, you can edit the serialosc.pd patch manually.

In the meantime, I’m working out a way to dynamically get/set the serialosc-device port from PD.

#37

hey i know this is basic stuff for most of you so thanks for walking me thru the process

apparently libmonome is missing

“error while loading shared libraries: libmonome.so.l: cannot open shared object file: no such file or directory”

i tried to download but do you have any suggestion if it says: unable to access…could not resolve host

mabye i need to post in the wifi thread but whats the easiest way to tell if i am actually connected to wifi?

#38

An easy way to check you are connected to internet is with the ping command:

ping www.google.com

should return something like this:

64 bytes from 216.58.195.132: icmp_seq=0 ttl=53 time=31.403 ms

if it is connected, otherwise it will complain or just hang while it waits for response. Hit Ctrl-C to stop it.

1 Like
#39

Ah ok, looks like serialosc may not be installed correctly. So the “bundle” idea may not work since it needs those shared libraries installed a specific location. Thanks for trying that out.

Yes, you need to make sure you can connect to the internet over WiFi – but only for installation. Getting WIFI set up was the trickiest part for me… Little things like making sure my wifi hotspot was 2.5ghz (rather than 5Ghz), for example.

I ended up reformatting my Organelle with a bare OS on an extra SD card so I could make sure the installation steps worked, and compiled it all into an installation script. It should be much easier to install now. I’ve also made some updates to my patches, the serialosc.pd patch now knows the correct port. Once you can confirm you can connect to the internet from your Organelle, try the new installation procedure. Here’s a the zip download for convenience.

1 Like
#40

Ok, I think I figured it out a solution with the bundle again. Could you try it one more time? If this works, no WiFi needed.

I now include the precompiled binaries in the bundle, and tell the OS to look at the usbdrive as a library location with symlinks. Kind of a hack, but worth a shot, as it gets around having to install WiFi.

Download this bundle bundle.zip, and follow these instructions. Let me know how it fares.

1 Like
#41

This is sounding cool. It is nice to have an install path that doesn’t require WiFi. Another option might be the shell object that is part of Pd-extended (you can download it compiled for Organelle here). I was experimenting with it once to make an ‘installer’ patch that would install some extra OS stuff. So in this case you could have an ‘Install Monome’ patch that would have all the resources and a shell script for putting them in the correct places.

Also a side note, do you know about this https://etcher.io/ for burning SD card images? It is cool because people can use it to write SD card images who might not be comfortable doing so on the command line.

1 Like
#42

The Installer patch is a great idea! I’ll give that a shot.

#43

Thanks @oweno, the Installer patch idea is a really cool solution. I just bundled all the binaries and scripts and made a little installer that displays its progress on the OLED.

@glia, want to try one more thing? No WiFi needed. Download these new patches: bundle.zip

Run the “Monome-Install” patch first. Start the install by pressing AUX. If it installs correctly, the Monome should blink and each key should illuminate when pressed. The “Monome Basic Poly” patch should play sound.

2 Likes
#44

ooh. i really like what you’ve done to make setup scripts. i’m going to try this method soon.

#45

finally got lights!

used the installer and it worked (then froze)
gonna restart the unit and try to configure to make some sound

1 Like
#46

Interesting about the “freeze”. If it does that again, plug in a Monitor and start the gui, and see if there are any errors in the PD console.