#7

It just returns my command prompt. Nothing else.

#8

Right, reboot the computer (sorry!).

Try which -a brew again, and if it still returns nothing then can you paste the output of ls /usr/local and ls /usr/local/bin

#9

i can confirm this bug. it happens when running kria: neither side of the grid responds as the docs say it should when trying to change note or loop sync. this is on the default firmware, pre-1.0. will test the newest version later.

it looks like the homebrew installation didn’t properly set environment variables, such as updating ${PATH}. or it may have been installed in your home directory somewhere, not systemwide in /usr. according to the homebrew docs, your version of OSX is too old – 10.10 is the required minimum. you may need to grab an older homebrew download and follow the instructions for certain workarounds.

1 Like
#10

I had to make sure to not have the USB cable plugged in to the module when powering up in bootlouader mode.

#11

That’s expected behavior. Pre-1.0 didn’t have the config menu. You can see that Note + Loop Sync are new in 1.0: Ansible 1.0

1 Like
#12

Thanks everyone for the input.

Okay, so Config 2 doing nothing is expected. I’m still grappling with the upgrade. Sam, I tried the additional commands but they didn’t work, which after reading loflow’s comments, is expected.

I tried to follow and make sense of the links related to older Homebrew docs, but that’s simply out of my depth, and I don’t have the time to get familiar enough with what’s happening in there to make it work.

I’m upgrading my OS; it’s time I did anyway, and we’ll try again.

Anyone care to speculate if the freezing is related to pre-1.0 as well? I was running two tracks, nothing complicated, in Kria.

#13

Updated to OSX 10.12

Ran Homebrew install again. Seemed to work, but got asked for a password. Stumped. What password?

Hit enter, seemed okay.

Ran brew install dfu-programmer and nothing happened.

Ran the update script anyway, and got this:

/ansible-1.0/update-firmware.command: line 3: dfu-programmer: command not found
/ansible-1.0/update-firmware.command: line 4: dfu-programmer: command not found
/ansible-1.0/update-firmware.command: line 5: dfu-programmer: command not found
logout
Saving session…
…copying shared history…
…saving history…truncating history files…
…completed.

[Process completed]

Stll did not work.

I’ve tried several times, booting up Ansible with USB cord connected, with it not connected, restarted computer, tried everything again, still no luck. Nothing happening on Config 2.

#14

Should be your user account password. If you don’t have one, it’s possible you need to create a root account?

(Sorry, not really a Mac guy but taking a stab.)

#15

Yep, what ppqq said. I was stuck at the password thing for a while, but you just enter your computer’s user account password that you would use to log in to your computer, download an app, or change a security parameter, etc.

It should work as expected after that!

#16

Thanks for that.

Yes, that’s what I thought.

My “what password” was partly in reference to the lack of any mention of it in the documentation; to that, and to any of the other potential issues I’m encountering. I don’t script, and until Friday, had never heard of Homebrew, never used my terminal, and things like git, ruby, perl, brew, etc., mean nothing to me.

I used my standard password my Macs have always asked me for when updating software, etc., and the password was accepted–i.e., there was no “incorrect password” response–but then nothing happened. I tried it twice. The second time, I walked away for half an hour to let the thing run, and nothing happened. Then, both times, when I tried to close the terminal window, I got a warning message asking if I was sure I wanted to terminate the session.

I also tried entering “brew install dfu-programmer” after entering my password, then running the script again after booting up Ansible, and again, no luck.

My frustration level is increasing. It would be really great if someone from Monome could address this here.

#17

The install requires an Internet connection I believe. Also, you might want to temporarily disable your security settings. This shouldn’t be an issue but you never know.

I understand your frustration with never going thru processes like this. But once you get things working, it should continue to work. So future upgrades should be a breeze.

#18

Paging @tehn. There are a lot of threads in this forum, and just one tehn.

Can you paste the output please?

1 Like
#19

Thanks, and I have that on that system. I was tabbing back and forth between the instructions on Monome’s site, the Homebrew site, etc.

Thank you too; there was no output at all. The insert point moved down one line and remained there, blank.

#20

i’ve been keeping track, but the information posted here by other gracious users is incredibly detailed and correct-- they’ve been getting to it before i do.

first, let’s figure out if you actually have installed homebrew. did you do it again and enter your password?

if it succeeded, you should be able to type “brew” into the terminal and something besides “command not found” will show.

#21

Good to know; thank you.

Yesterday evening, after updating my OS to 10.12 and making sure everything was stable, I re-ran this, directly from Homebrew’s site, per instructions:

/usr/bin/ruby -e “$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)”

Fumbled around with the password confusion, then started over, repeated the entire process, trying my standard admin password, and received no response other than the insert point moving down one line.

I’m sorry I’m not at home right now, so I won’t be able to re-try until this evening, but I will start from scratch again then.

…

I do wish that the accompanying firmware update documentation had been a little more thorough in addressing steps. The key omissions exist between the lines here:

"…line of text into Terminal.

after this is installed, you should be able to simply type:

brew install dfu-programmer

get the firmware…."

It would have been helpful if there was a sentence that indicates what a successful installation actually looks like, prior to typing another command. I had no idea whether or not terminal was actually ready or not to receive the next line of code.

Next, if I can simply type brew install dfu-programmer, what am I actually supposed to see after that? The documentation doesn’t tell me, so I don’t know what I’m looking for.

Those are the two main problematic sections, although a minor third point is the aforementioned button issue, as the documentation says “…the front panel button…” whereas there are three buttons.

Sorry to nitpick, but while coding is obviously not my strong point, general writing is. To try to keep this in the spirit of open source and constructive criticism, I would be glad to help edit and expand these instructions once I actually get it to work and understand the process. From a few other comments in this thread and elsewhere, it’s clear to me that I’m not the only one who’s not completely understood the process.

I will report back this evening after trying again.

1 Like
#22

thanks for the feedback. i’ll add your suggestions to the documentation to make this process more clear.

and i know this is weird stuff-- i suppose in the past it’s just worked the first time for people so nobody has taken issue. we’ll get your setup working tonight.

#23

Thanks tehn.

I got it to work this time.

I didn’t do anything differently than before except wait at a couple critical points. This is where further expansion in instructions would be helpful, as terminal offers no feedback that anything is happening (i.e., a progress bar). A note indicating where/when to expect to wait would be helpful. Here’s a screen shot of my installation, with two clumsy red arrows indicating where I had to wait about two minutes and seven to eight minutes respectively, which were quite surprising intervals. Again, if I expected that, then I could have left it alone. But since terminal offers no ‘progress bar’ as it were, those of us not versed in this stuff are adrift. Is anything happening? Did it fail? Did it succeed? Will I know if either conditions are actually achieved?

Anyway, I’m very relieved. I’ve been running Kria and MP back and forth, and so far, no freezes either.

The interface is a delight of course.

screen shot jp.jpg762×802 138 KB

2 Likes
#24

Thanks for the detailed info. Thinking back to my issues I think I gave up and walked away, which probably gave it the time it needed.

#25

Great write-up!

:thumbsup:

For the intrepid/generous, we kickstarted a special repository for just these kinds of user-driven docs. I briefly mention it here but it bears repeating…

If you’re not keen to jump all over a git work-flow to submit documentation directly to the repo (not that it’s too bad) but are interested in capturing some of these ideas I’d be more than happy to help turn them into docs. Feel free to message me or file issues in the issue tracker and mention me (@pq) and I’d be happy to help.

:beers:

1 Like
#26

Do I have to register to file issues in issue tracker? I’m sort of leery of getting involved there, if only because it’s taking me a step further in to a world–software/firmware/whateverware coding–I have no real interest in. What even is a “git?” (rhetorical question, you don’t have to answer!).

I am interested in the code aspect of Teletype, but given that that’s part of the process of actual music-making (vs. software making), I can deal with it.

Also, apologies in advance for anyone taking umbrage at the possibly-false dichotomy of ‘music making coding vs. software coding;’ dangerous territory…I know!

All of that said, I’m glad to try to help in whatever way I can with comments/editorial.

1 Like