Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pam's New Workout #64

Open
boourns opened this issue Mar 12, 2021 · 13 comments
Open

Pam's New Workout #64

boourns opened this issue Mar 12, 2021 · 13 comments

Comments

@boourns
Copy link
Owner

boourns commented Mar 12, 2021

https://busycircuits.com/alm017/
https://busycircuits.com/docs/alm017-manual.pdf

I think the cheat sheet should cover
basic navigation,
Per Trigger Adjustment parameters
CV assigning.
saving/loading settings

@benirose
Copy link
Contributor

How do we go about asking ALM if we can use images in the manual?

@boourns
Copy link
Owner Author

boourns commented Mar 30, 2021 via email

@benirose
Copy link
Contributor

OK. We might want to recreate some of it for the smaller screen anyways, similar to how the Mother 32 sequencer pages are, but the graphics in the manual are very helpful and I figure it's good to ask these kinds of things.

@boourns
Copy link
Owner Author

boourns commented Mar 30, 2021 via email

@benirose
Copy link
Contributor

benirose commented Mar 30, 2021

For the Extended Output Parameters, we could do a page for each:
Extended Output Parameters
Wave
Level
Offset
Width
Phase
Delay
Delay Divisor (Dly)
Slop
EStep
ETrig
ERot
RSkip
Loop
Quant
Logic

Or we could bundle them up like this:
Waveform Modifiers

  • Wave
  • Level
  • Offset
  • Width
  • Phase
  • Delay
  • Delay Divisor (Dly)

Rhythm and Randomization

  • EStep
  • ETrig
  • ERot
  • Slop
  • RSkip
  • Loop

Quantization
Logic

Any thoughts? The second option would be just 4 pages in the "Extended Output Parameters" section.

@boourns
Copy link
Owner Author

boourns commented Mar 30, 2021

Amazingly, nobody has ever complained about the layout of a cheat sheet, and sometimes I've done it one way and sometimes the other way. So if you feel strongly one way or another go for it.

To me, I think the second case makes more sense to me for this module, grouping them like that. That fits more with how I used the module when I owned one.

@benirose
Copy link
Contributor

Yeah, the second one makes more sense to me too, I think when information is sparse across many pages it can be a less useful tool. I should be able to start a draft on the General and Extended Output Parameters soon, but I was having a hard time following the manual on mutes, saves, and CV control so I'll work on those after I've received mine and played around with it a bit.

@benirose
Copy link
Contributor

Going to try to circle back to this in the next few weeks, I've definitely had time to play around with my Pams and know it pretty intimately now!

@boourns
Copy link
Owner Author

boourns commented May 27, 2021 via email

@dylhunn
Copy link

dylhunn commented Jul 31, 2021

I noticed this is tagged "ready to go" -- is this expected in an upcoming release?

@boourns
Copy link
Owner Author

boourns commented Jul 31, 2021 via email

@benirose
Copy link
Contributor

Sorry I let this one fall off my radar. I’ve had a lot of time with Pam’s since I first commented so I’ll try to commit some time to this in the next week or two.

@boourns
Copy link
Owner Author

boourns commented Jan 16, 2022

@benirose that'd be amazing! thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants