#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
#27

Ah, right. Yeah.

Fair enough. So thatā€™s a non-starter.

Oh but then I really canā€™t resist. The wikipedia article is really not bad:

But honestly you donā€™t need to read up on it.

And thatā€™s the important part and ideally we can come up with a way to best take advantage of your interest. If we had something like a compendium of Frequently Asked Questions, would you be interested in contributing if we found an easy way for you to do so?

#28

ppqq, thanks for the background information. I was kind of laughing at myself reading that Git paragraph, as I could actually feel my eyes glazing over. A couple synapses dislodged themselves. I mumbled.

Kidding aside, I can easily try to write at least a version of the firmware instructions which address the confusions that were present for me. I donā€™t know if it will work for everyone else, but I can just post something here, as a starting point, and we can go from there. I donā€™t want to step on anyoneā€™s toes though; if tehn wants to remain sole custodian of that then I want to respect that.

The last time I was seriously involved in the world of music production, I developed an accidental sideline writing copy, bios, one sheets, promo materials, etc., for various record labels, distribution houses, artists, etc. I was a musician/composer, not a writer per se, but people kept noticing that I had a certain facility for writing, they needed writing, and started asking me to write for them, and eventually I had to tell them to give me money. It started to take real time.

Anyway, I like writing. Itā€™s easy to whip stuff up. I imagine not unlike code writers with code.

#29

Though Iā€™ve just updated to firmware 1.1 and Iā€™m still getting no grid feedback from Config2 (Key2).
Iā€™m using a grayscale 128, which may have something to do with it.

I am able to toggle Note Sync (with no feedback) by pressing (1, 1) on the grid, but Iā€™m not sure how to change Loop Sync mode with no feedback. It seems to be in ā€˜Allā€™ mode. I couldnā€™t find anything in the documentation about how to change Loop Sync.

Any assistance would be greatly appreciated.