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