[Sugar-devel] Outreachy - Going Beyond Equal Temperament in Music Blocks

[Sachithra Dangalla]

I understand now. The bottom line is that the UI must restrict the user
from adding more than one of the same note. (Right?)


> *...I need to think about it. Sachi-D, if you have time, please make
> mockups for a) multiple pitch blocks to define different names (nominal
> values) for the same pitch for your design and mine and b) your design with
> a single "define pitch" block.*


I will definitely think through and come up with designs.

Right now I'm trying to list down the things that must be done in the
project, in order to come up with a timeline (since the deadline is near).
[1] is a draft timeline I created in order to clarify the expected
outcomes. I have a better understanding about the expected frequency
mapping process(but the inner details and time have to be filled later).

After mapping the frequencies, the next focus has to be on transformations
such as adding half-steps, intervals and mode - as Walter said on a
previous mail. But I still have a lot to figure out about them. Or will
they be understood while actually implementing the project?

I would really appreciate it if you can comment your ideas in the following
sheet.

[1] - Google Sheet -
https://docs.google.com/spreadsheets/d/1Jkp1rpCVn6fIIg6xIYnDhHebzFAcxogqtpMaJezBI0c/edit?usp=sharing

Regards,

*Sachithra Dangalla,*
Undergraduate B.Sc.Eng.(Hons.)
Department of Computer Science & Engineering,
University of Moratuwa,
Sri Lanka.

<https://plus.google.com/u/0/+SachithraDangalla93>
<https://lk.linkedin.com/in/sachithradangalla>
<https://comexile.blogspot.com>

On Sun, Mar 26, 2017 at 8:55 AM, Devin Ulibarri <devin at ulibarri.website>
wrote:

> On Sun, 2017-03-26 at 00:11 +0530, Sachithra Dangalla wrote:
>
> What I had in mind was as follows and I think I might have missed
> something important:
>
>
> [image: Inline image 2]
>
>
> I read this and the subsequent emails and I get it now. BTW, these
> diagrams are helpful--thanks! :)
>
> We have no preordained rules, per se, about how to do design these.
> However, I have thought about it and can say what I see as the pros and
> cons for your design.
>
> Pros
> * Maybe it is good to get the octave arg out. I need to think about it,
> but it seems weird to have the octave arg in the stack.
> * I like your rationale that it is similar in function to the calc block.
> It is worth exploring.
>
> Cons * In my digram, you could put multiple pitch blocks in with different
> names (e.g. "Do" and "C") to define multiple names for the same pitch. With
> your design, you can do the same, but it seems too easy to accidentally add
> multiple pitch blocks WHILE CONSEQUENTLY defining multiple frequencies for
> each of those names which is illogical. We cannot have a single nominal
> value calling multiple frequencies. We can, however, have multiple nominal
> values mapped to a single frequency (ability to call same frequency using
> different names).
>
> ...perhaps, if we went your direction, it may be better just to have a
> single "define pitch" block taking multiple arguments (instead of a
> separate "define pitch" block for each.
>
> ...I need to think about it. Sachi-D, if you have time, please make
> mockups for a) multiple pitch blocks to define different names (nominal
> values) for the same pitch for your design and mine and b) your design with
> a single "define pitch" block.
>
> Best,
> Devin
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20170326/54f6c708/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 135332 bytes
Desc: not available
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20170326/54f6c708/attachment-0001.png>