LaTeX/Markdown Manual

[JoshuaStorm]

Having a manual to explain the more menu-divey functionality would be great.

Utmost emphasis on ease of use, do not make more verbose than absolutely necessary.

[mulshine]

c'mon josh lets get going on this. jkjkjk

[JoshuaStorm]

Manual.pdf

@spiricom @mulshine
Here's the next iteration after I kept going back and forth on how to organize the manual. I think I'm finally decided on a style that isn't painfully academic or long-winded. Still got a bit to go (and probably should do something a little better than my MSPaint graphics) but I think this is the right direction now :)

Suggestions for doing graphics would be much appreciatteeddd

[JoshuaStorm]

Also I could upload my Latex to a manual branch if anyone else is interested in poking around
(for example, figuring out how to remove the extra blank pages between sections in the template I'm using, I find them kind of annoying for our use case)

[spiricom]

Hi - lookin' good! I like the manual format. I agree that we should figure out how to remove the blank pages between sections. some thoughts on the text so far: HOST is confusing since that's actually the term for what the MantaMate is in USB terminology. In the case of Manta paired with MantaMate, the Manta is the DEVICE. The only situation in which you plug in a HOST is when you plug it into a computer, and then the MantaMate becomes the DEVICE instead. Also, let's call the sequence modes Pitched vs Trigger and Full vs Split. (rather than dual-sequence) Mike and I were talking about redoing that part of the menu so that there is a hex for "sequencer 1 pitch/trigger", another for "sequencer 2 pitch/trigger" and a third for "full vs split", which would cover all the cases including modes with both pitched and trigger together. It also only takes up 3 hexes instead of 4. I like the basic walkthrough idea, it's looking like a good start. As for computer mode, yep it works. Just like when you plug in a midi keyboard, it takes MIDI and turns it into CV. As for USB midi keyboard mode, it currently puts noteon/off stuff out the 1v/o output and Gate out, and just routes CC#1, 2, 3, 4, 5, 6, 7, 8, 9 (or fewer if using duophonic, triophonic or quadraphonic modes) to the CV outputs. It would be cool to get a midi learn going on, where you push two buttons together or something and then turn your all your knobs, and it fills and array that it uses to map the CC#s to CV outputs. Did we test it with a DDR? I can't remember. Should definitely have recommended joystick models.

…

-Jeff

On Fri, Mar 10, 2017 at 8:58 PM, Joshua Storm Becker < ***@***.***> wrote: Also I could upload my Latex to a manual branch if anyone else is interested in poking around (for example, figuring out how to remove the extra blank pages between sections in the template I'm using, I find them kind of annoying for our use case) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#8 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAwMfAC3SS3WeSbVnBaQzvsAk5odEsDOks5rkf_dgaJpZM4KXg8y> .

-- Composer, musician, instrument designer snyderphonics.com * @snyderphonics