11.1-MIDI-In language reworked #2443
Conversation
etc/doc/tutorial/11.1-MIDI-In.md
Outdated
| default. (Note that this added latency can be configured via the fns | ||
| `set_sched_ahead_time!` and `use_sched_ahead_time`). This 0.5s latency | ||
| is being added to our `:piano` synth triggers as it is added to all | ||
| synths triggered by Sonic Pi. Typically we really want this added | ||
| latency as it means all synths will be well timed. However, this only | ||
| makes sense for synths triggered by code using `play` and `sleep`. In | ||
| this case, we're actually triggering the `:piano` synth with our | ||
| external MIDI device and therefore don't want Sonic Pi to control the | ||
| external MIDI device. and therefore don't want Sonic Pi to control the |
There was a problem hiding this comment.
if we add a . here the following word should be capitalized ?
|
Hi, thanks for this. I’m currently very happy with the informal voicing of the documentation. However, I am interested in grammar, punctuation fixes and rewording where things are particularly unclear to the reader. If you could constrain your changes to these then I’d be happy to consider it. As it currently stands these changes feel like they deviate too far from something I’d write :-) |
| button and see if it appears. If you're still not seeing anything, | ||
| the next thing to try is to consult your operating system's MIDI config | ||
| to see if it sees your device. Failing all that, feel free to ask | ||
| questions in the public chat room: http://gitter.im/samaaron/sonic-pi |
There was a problem hiding this comment.
I think the gitter chat is mainly for development chat? The in-thread forums or maybe the GitHub issues page may be more suitable here.
There was a problem hiding this comment.
Correct. Additionally, the gitter chat room is pretty much obsolete now, and we will always point folks elsewhere.
Moved to main from #2007