A class or method to convert integer and float to scientific pitch notation?

[smoge]

You’ve prototyped a DSL for music notation, which is invariably fun but also very specific.

Either way, for your code to integrate into the SC ecosystem, you must develop an OOP design for the elements (pitches, accidents, durations, tuplets, ties, dynamics, etc.). Perhaps the most logical step would be to think of a quark that exactly mirrors the elements of musicXML. No need to build a complex system at this point. Keep it simple there.

Then, in a separate quark, you implement your DSL, that will combine all these objects.

You already made a proof-of-concept, it works. Well done!

[smoge]

Hi @rdd

I found your stuff on rhythms quite exciting. It seems that this relationship between duration and traditional notation (tree) is a very slippery arithmetic. Not every rational number can be expressed as a duration; at the same time that of the rational numbers accepted by this arithmetic, some correspond to only one duration, while others can have 2, 3, or 4 different durations. Verifying this with QuickCheck tests (durationToRq . rqToDuration :: Duration → [Duration] ) was curious:

https://gist.github.com/smoge/a0b9bfd19778fccbdb88090bb9a438c9

Strangely, some notation systems (such as GUIDO) only accept the Rq values, and it does not seem correct that it is possible to generalize an inference. Therefore, these systems will fail in less simple cases. (Correct me if I’m wrong.) As far as I understand, both representations are complementary.

I want to delve deeper if you have more references on this. I also see you have a lot of exciting stuff there, from Barlow to Larry Polansky and many others. I didn’t have time to check it out yet.

[prko]

@nathan

Putting anything in core is a big responsibility;

My programming skills are not professional. I cannot always be responsible. The first step in publishing should be to use Quarks, unless some people in the development department check and repackage my code.

@nathan

But at some point, someone’s probably going to want to transpose notes and convert them back to music notation while handling accidentals correctly (both for readability in sheet music and correctness in case of non-12edo tunings), so you’ll need a pitch encoding layer in between note name strings and frequencies.

While developing my idea, I also think transposition. For example,

\a4 + \p5 // midi pitch number + perfect fifth

returns:

e5

With OOP design, it would be as follows:

A4.() + P5.() // midi pitch number + perfect fifth

returns:

A5

@smoge

Either way, for your code to integrate into the SC ecosystem, you must develop an OOP design for the elements (pitches, accidents, durations, tuplets, ties, dynamics, etc.).

Yes, I also think it! This is why I proposed the following classes (I changed the name as Notator):

@prko

Notator: a subclass of the class Object, and an abstract parent class for ‘Notator Library’.
├ Attribute: an abstract parent class for its subclasses
╎ ├ Staff
╎ ├ Clef
╎ ├ Tempo
╎ ├ TimeSignature
╎ └ KeySignature
├ Entry: an abstract parent class for its subclasses
╎ ├ Intensity: a class that creates an instance of an Intensity class
╎ ├ I: the abbreviation of Intensity
╎ ├ Hairpin: a class that creates an instance of a hairpin
╎ ├ H: the abbreviation of Hairpin
╎ ├ Rest: a class that creates an instance of a rest
╎ ├ R: the abbreviation of Rest
╎ ├ Note: an abstract class for each pitch class name and the attachment to the note instance:
╎ ╎├ A: a class that creates an instance of note utilising the pitch class a
╎ ╎├ B: a class that creates an instance of note utilising the pitch class b
╎ ╎├ C: a class that creates an instance of note utilising the pitch class c
╎ ╎├ D: a class that creates an instance of note utilising the pitch class d
╎ ╎├ E: a class that creates an instance of note utilising the pitch class e
╎ ╎├ F: a class that creates an instance of note utilising the pitch class f
╎ ╎├ G: a class that creates an instance of note utilising the pitch class g
╎ ╎├ Articulation: a class that creates an instance of articulation for an instance of note
╎ ╎├ U: the abbreviation of Articulation
╎ ╎├ Tie: a class that creates an instance of tie for an instance of note
╎ ╎├ T: the abbreviation of Tie
╎ ╎├ Slur: a class that creates an instance of slur for an instance of note
╎ ╎└ S: the abbreviation of Slur
etc.

However, there are some problems here:

1. Rest is already a subclass of Operand. So, I think the Note class and its subclasses should exist as the subclasses of Operand.
2. Then, SPN and PitchClass by @josh should also be under Operand?
3. The notation of such musical information using OOP design seems to lose readability… The code seems to be very complicated.

[smoge]

@prko

With OOP design, it would be as follows:

A4.() + P5.() // midi pitch number + perfect fifth

The code snippet you’ve shared doesn’t seem to follow a typical object-oriented design as in sc. In this kind of operation you posted, you’d have separate Pitch and Interval classes and functions defined between them. If you define classes for pitches and intervals, their interactions can be considered vector space arithmetic — or, more simply, “affine space”. For instance, you could subtract one pitch from another to derive an interval or add an interval to a pitch to determine a new pitch (as demonstrated in your example).

https://en.wikipedia.org/wiki/Affine_space 1

I imagine A4.() + P5.() are just pitch literals operating with interval literals, but even then, it’s not a very convenient literal.

How you will implement this can be a separate code from the code to create musicxml. This way, it will be more modular and more helpful to others. For example, I don’t see the need for an interval class in the musicxml quark.

[rdd]

Yes, it’s not a linear relation, c.f. rq_to_duration at:

https://gitlab.com/rd--/hmt/-/blob/master/Music/Theory/Duration/Rq.hs#L65

There are lots of nice notations for duration, the “Bel” notations, for instance, are rather nice:

https://gitlab.com/rd--/hmt/-/blob/master/Music/Theory/Time/Bel1990/R.hs#L78

[prko]

I made two classes SPN and PitchClassSet with help documents that can be used with the SC-IDE help document browser.

https://scsynth.org/t/note-names-pitch-classes/8061/3?u=prko

My PitchClassSet class is independent of @josh’s PitchClass class.

Any comments are welcome, but we should discuss the subject on the thread which @semiquver made. That thread does not include musicXML-related perspectives.

Thank you for all of your feedback.

[prko]

@smoge

How you will implement this can be a separate code from the code to create musicxml. This way, it will be more modular and more helpful to others. For example, I don’t see the need for an interval class in the musicxml quark.

@rdd

Thank you for your opinion. I am also speculative to apply this notation (A4.(\eighth) etc.) It is complicated as my expectation.

I should have time to reflect the concept in the articles you mentioned (Affine Space, Representing Music with Prefix Trees, and the codes of @rdd). By August I should have finished what I did over the summer. My work process is not that fast due to many gaps in programming skills.

[prko]

I have made a Quark library related to this thread. It seems to work with the examples given, but needs further work. SPN and PitchClassSet are in this quark library.

GitHub - prko/Notator: musicXML File Writer for sclang

Detailed help documents are provided for each class, as well as a Notator score guide!