@okyeron: Thanks again for taking the time for the explanations. Your assumption about my “power-level” :smiley: is completely correct, and so I am happy to say that I got the hang of using Cyberduck to manipulate norns’s data via wifi.

But I just don’t understand why Cyberduck can display & manipulate norns’s files only via wifi, but not via USB–whereas the terminal application seems to be able to display & manipulate norns’s files via USB. As far as I understand it, in both cases there are 2 computers having a network connection. What is–in layman’s terms–the difference between the 2 connections that causes Cyberduck not being able to do what the terminal app can do, which is using a USB connection for data manipulation?

My apologies to everybody else on this thread for derailing it, I promise this will be my last post on this specific topic.

There’s a bit of magic happening behind the scenes to allow the USB connection to do that.

The reason for the discrepancy is a matter of the protocol used for communication. Terminal + USB is using a serial protocol to talk to the norns. Terminal + WiFi is using the SSH protocol. The serial protocol communication over USB in this case will only work with a terminal.

2 Likes

There are protocols that can transfer files over serial, or even form a network stack (eg ppp).
So it’s possible these could be setup , if it’s not already present.
(Sorry don’t have a Norns to test/be more specific, so don’t know if this is possible the console serial connection)

1 Like

“NONE (error: AUDIO ENGINE)” .
Reboot, hard-reboot,
Tried syncing from USB without success it just stops the sync straight after I selected it.

This happened after updating norns no scripts working currently. My back up drive was damaged so I can’t sync from USB either.

The direct USB connection is using 1970s level technology, e.g. using a dumb text terminal to connect to a main frame. This is a serial connection (i.e. like MIDI).

In order to use SSH/SFTP we need to a computer network running TCP/IP (i.e. the internet).

As @TheTechnobear suggests, we could use 1980s/1990s era technology (PPP)1 to ‘tunnel’ an internet connection2 over the serial connection. This is how we got the internet on the dial-up modems we used to use. IIRC it was always a bit of a pain to get working.

All in all, it’s just easier to skip that and use more modern connection methods (such as WiFi or Ethernet), these are far easier to get running problem free in Linux.

Hope that helps.


1 Although PPP is still used to today, often in DSL lines via PPPoE
2 Yes… I know it’s actually lower level than IP

5 Likes

don’t knock 80’s technology it was super cool :wink:
I do think however to support this mode, it does have to come with the obligatory modem bleep sounds, so we can all reminisce in its glory. (perhaps) slightly more seriously, the main issue is speed, if you do this, downloading large ‘tapes’, will also transport you back to the 80’s, and reading a book whilst you wait for the download.

but id agree given its slow, and needs careful client setup, its not really that convenient (unlike usb networking via rndis, which is super useful imo).
anyway, just mentioned it as possible, in the rare case, that ‘its all you have’.

if you want a one wire (power+networking) solution, and/or closed wired network, I think probably power over ethernet with splitters, though admittedly the dongles are a bit of a pain in the neck.

3 Likes

@okyeron, @sam, @TheTechnobear: Thank you for the explanations…

…and no, I spent too much time listening to my modem bleep sound to want this technology back :slight_smile:

1 Like

If I edit one the pre-loaded scripts in maiden, it seems like these edits are automatically stored after power-cycling. I was surprised that no explicit save command seemed to be required. Is this correct?

1 Like

i’d guess maybe the changes are being cached in the web browser. can’t imagine they are actually being saved to disk without asking to. try refreshing maiden?

[sorry, correction below]

here’s what I did.

  1. start norns, setup hotspot, connect to hotspot, start maiden
  2. in maiden, open script awake, edit script
  3. sleep norns, close maiden
  4. restart norns: script edits still active
  5. setup hotspot, connect to hotspot, start maiden
  6. in maiden, open script: script edits still active
  7. in norns, reload edited script: script edits still active
  8. in norns, load different script, then load edited script: script edits still active

running norns180707.
never clicked save script.

how do I get back the original, un-edited version of the script?

Did you run the script from maiden? That will save it.

Yes, I did press run in maiden, but I have to admit that it feels unexpected that just running a script also saves it, especially as there is a dedicated save button above run.

So how do I get the unaltered version of the script back? I think it would further encourage experimentation with scripts if running a change did not automatically overwrite the original.

Feature request: integrate git into maiden, for both local and remote operations.

1 Like

You can view the original scripts at https://github.com/monome/dust/tree/master/scripts and just copy and paste the contents into maiden to revert.

3 Likes

ah, sorry my head is not really in the game right now.

yes, running a script also saves it. “running a script” currently requires loading a file from disk, compiling it and executing it.

i agree, it’s a little unexpected.

opened GH issue, please weigh in there if there are other thoughts (esp. @tehn, @ngwese)
https://github.com/monome/norns/issues/473

2 Likes

Thanks much!

One small bug: If you create a new script in maiden and run it (which automatically saves it as untitled), clicking the pencil icon in maiden’s script list to rename it does not work, although the untitled script is selected. You have to click the untitled script in the script list first, then clicking the pencil icon brings up the renaming screen.

I really don’t know anything about git, otherwise I would file this bug on my own. Please, can somebody guide me thru the steps necessary to be able to file a bug in git? Or is it OK to post bugs here and hope that the norns contributors write the bug in git?

the github docs are pretty decent.

https://help.github.com/articles/creating-an-issue/

but really all you need is a github account:

https://help.github.com/articles/signing-up-for-a-new-github-account/

and with that, you can go right to the maiden issue tracker and open a bug.

feel free to PM me if you hit any snags; i’m also happy to open the issue for you if this gets onerous.

1 Like

…the current behavior is far more finicky than it should be and there are interactions which produce reasonable but unexpected results. While opening issues on GH ultimately minimizes the work around capturing bugs - it is certainly okay to express confusion or describe behavior which seems bug worthy here.

1 Like

Can norns already work with an arc, and are there already scripts using arc that one can learn from?

2 Likes

Not yet. @scanner_darkly ran into some problems with adding arc support. There’s a pull request that is a start if somebody wants to pick up the effort.

1 Like