Hello everyone,
I'm curious as to what you consider the best or most ideal way to protect your notation systems....
Anyhow, is patenting the only way to go? Does publishing the information on a website/blog, and the corresponding copyright, offer any safeguards from infringement? My custom nomenclature, for instance, has certain 'data compression' characteristics (moreso than the rhyming schemes and others I've seen) that are as far as I am aware entirely unique. Would something like that be protected from straight copying if I were just to publish it on a website? I'm guessing not, but I'm quite fuzzy on the legal aspects concerning this; spent the last two years thinking only about the design, not the legal side. Perhaps not pragmatic but then I'm a bit of an idealist :).
Thanks!~Seth
Pinwheel Music Notation (coming...soon?)--
You received this message because you are subscribed to the forum of the Music Notation Project (hosted by Google Groups).
To post to this group, send email to musicn...@googlegroups.com
To unsubscribe from this group, send email to musicnotatio...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/musicnotation?hl=en
Don't holds it tight, give it away! Remove barriers, publish it, shout it from rooftops, kiss babies.
Hello everyone,
I'm curious as to what you consider the best or most ideal way to protect your notation systems. I've got a notation system that is radically different than anything I've ever seen, and while I know there is a very small chance it would be adopted mainstream, I think the fact that it has the fidelity of piano roll notation, while making the intervallic relationships and general order of the music much more visible than the piano roll (thus, ideally allowing it to supplant the piano roll in software, and then carry over seamlessly to printed notation), not to mention the improved visibility of the rhythmic structure of music and more, makes it at least a possibility. I've also integrated certain other aspects of theory, such as general transposition, scale memorization and transposition, etc into the design of the notation and nomenclature. As a plus, the notation also fits all of the MNP criteria.
Anyhow, is patenting the only way to go? Does publishing the information on a website/blog, and the corresponding copyright, offer any safeguards from infringement? My custom nomenclature, for instance, has certain 'data compression' characteristics (moreso than the rhyming schemes and others I've seen) that are as far as I am aware entirely unique. Would something like that be protected from straight copying if I were just to publish it on a website? I'm guessing not, but I'm quite fuzzy on the legal aspects concerning this; spent the last two years thinking only about the design, not the legal side. Perhaps not pragmatic but then I'm a bit of an idealist :).
--
You received this message because you are subscribed to the forum of the Music Notation Project (hosted by Google Groups).
To post to this group, send email to musicn...@googlegroups.com
To unsubscribe from this group, send email to musicnotation-unsubscribe@googlegroups.com
To unsubscribe from this group, send email to musicnotatio...@googlegroups.com
Hello everyone,
I'm curious as to what you consider the best or most ideal way to protect your notation systems. I've got a notation system that is radically different than anything I've ever seen, and while I know there is a very small chance it would be adopted mainstream, I think the fact that it has the fidelity of piano roll notation, while making the intervallic relationships and general order of the music much more visible than the piano roll (thus, ideally allowing it to supplant the piano roll in software, and then carry over seamlessly to printed notation), not to mention the improved visibility of the rhythmic structure of music and more, makes it at least a possibility. I've also integrated certain other aspects of theory, such as general transposition, scale memorization and transposition, etc into the design of the notation and nomenclature. As a plus, the notation also fits all of the MNP criteria.
Anyhow, is patenting the only way to go? Does publishing the information on a website/blog, and the corresponding copyright, offer any safeguards from infringement? My custom nomenclature, for instance, has certain 'data compression' characteristics (moreso than the rhyming schemes and others I've seen) that are as far as I am aware entirely unique. Would something like that be protected from straight copying if I were just to publish it on a website? I'm guessing not, but I'm quite fuzzy on the legal aspects concerning this; spent the last two years thinking only about the design, not the legal side. Perhaps not pragmatic but then I'm a bit of an idealist :).
Thanks!~Seth
Pinwheel Music Notation (coming...soon?)
~Seth
I've gone a long way to making it easier to learn music via the way theoretical concepts, transpostion, and scales (all intervallic relationships really) are very easily represented and, perhaps the most innovative aspect of my design, verbally, visually and mentally condensed.
Now, if only you could design a perfectly isomorphic guitar! (of course the redundancy of numerous pitches is always going to make that a less ideal instrument in an isomorphic sense, even with a non-conventional all strings tuned in fourths arrangement).
That will only make sense to those who've used Lisp to any degree
>I've seen system with triangles, pointing in different basic directions, filled, hollow, encircled, enclosing a circle and so on but that is way too complex when they got to be written on paper or seen on screen enough small to be possible to be followed in time during performance and basic time reference!
YES!
--
I've not had much time lately and haven't gotten to do check out all of the notations (and individuals' websites) yet, but those links save me a lot of time. Visually, my system is quite similar to Joe Austin's. I do keep a more traditional horizontal staff, and my approach to rhythm is different. The other primary difference is I've spent a lot of time designing the notation in Inkscape (as vector graphics) to test the visual fidelity of the unique symbols as they are shrunk down to the oft-smaller-than-I'd-like real world sizes. What good are twelve unique symbols if you can't distinguish them instantaneously in real world settings, right?
I think Enrique is right in that most of my design is not something completely new and never-before-thought-of, but I feel that it's the way it all works together that does in fact make it 'completely new' - in a sense. I still think my approach to intervals and the compression technique I use for scales, chords, (any note grouping, really) is unique. It's one of those ideas that technically could be applied to any notation system, but it would become so cumbersome in a system that is not visually/semantically designed for it that I'm pretty sure it would prove to be more work than it is worth in such systems. I'll be revealing what exactly this compression business I keep going on about is actually about soon(ish) after I unveil Pinwheel (there are still a few design decisions nagging me).
Also, I loved getting a good look at intervals as you show them in TwinNote. The truth is, intervals are probably more immediately apparent in TwinNote than in Pinwheel (or Joe Austin's system) thanks to the simpler design; you've got two note shapes and two note colors - I've got 4 and 3, respectively. The question then becomes is there enough value in having 12 unique symbols to justify their existence and the (mostly minor, in my estimation, but perhaps others disagree) setbacks they introduce compared to more concise designs without a unique symbol for each note.
The benefits to having 12 unique symbols that I've seen are:
*Completely erases the process of mental translation of converting a note head in a given space/line to an actual note. There is a true 1:1 correlation.
In some cases, this will actually make intervals clearer than even the clearest more concise notations; identical note two octaves apart, for instance, have a somewhat great vertical distance that might incur a bit of mental overhead to process even in a clear system like TwinNote, but with unique symbols, this is negated.
*The notation can be 'flattened' - that is, written on a single horizontal plane, if necessary (eg: a line of notebook paper). While that attribute might appear to be marginally useful at first, I think it actually proves to be quite useful as it allows the notation to immediately be used in something like guitar tablature, where pitch identification on a single plane is inherent in the notation's approach. Also, even though vertical separation intervallic cues are eliminated in such a system, the symbols can - with proper design - still show intervallic relationships when flattened.
*Maps effortlessly to isomorphic instrument layouts. While the layout of the instrument and its intervals will change the emergent patterns, visual patterns will emerge regardless of instrument (this is something that does not happen cleanly with a 4x3 system that is non-cycling, and is my only criticism as such of Enrique's reference head approach. On the flipside, his approach makes certain things more visually apparent - a half step is more visually intuitive in his design than in Pinwheel, and try as I might I have not been able to conceive of a way to make a uniformly cycling 4x3 system present that information as clearly. I do have some symbol modifications to help, though.)
*Kind of the inverse of the first point, it also has a 1:1 mapping in the reverse order; when speaking of note names, their symbol (and location on the staff) are immediate (once first learned). No mental translation required. This is a big benefit in comparison to TN, but the inclusion of an isomorphic staff in most alternative notations comes pretty darn close to this, so in comparison it's not a great selling point when comparing Pinwheel to other notations.
*It allows music to be read differently, I feel. Given that each note is a unique symbol, analogous to the unique characters in an alphabet, musical phrases can start to be read as "words." I know something similar happens with enough exposure to any system, including TN, but I have to wonder if the brain doesn't still process it differently. In working with Pinwheel, my n=1 evidence is that the brain does indeed process it differently. It just feels different.
The ultimate design would have a vertical element that denotes relative scale degree, while the unique symbol denotes absolute pitch (I feel this is far superior to the reverse design where vertical element denotes absolute pitch and the unique symbol denotes the relative scale degree, as all music of a given structure would appear identical. Given chord progressions would always look the same, and the structure of music would become extremely evident. I've not yet been able to make this design workable though; I technically can do this with Pinwheel but it requires a change to the note symbols and staff in such a way that a lot of clarity is sacrificed).
So the question is if those benefits outweigh the drawbacks in clarity and immediate visual simplicity. I tend to think they do in general, and especially for certain instruments, but others may disagree.
Perhaps a greater question is if the benefits of my imagined 'ultimate notation' - where relative pitch is displayed by vertical position and absolute pitch by unique symbol - outweigh the drawbacks. I've been thinking about this a lot lately. It seems that the beginner would find it more difficult, as even though a given symbol maps to a given pitch, that symbol is not always in the same vertical location. I think advanced musicians would actually find it easier as the structure of the music - chord progressions, relevant scales, voice leading, all of it - would become much much more evident, and would outweigh the minor drawback of variable vertical position for a given pitch. This of course could be (at least somewhat) mitigated - or, conversely, amplified - by the design of the unique symbols. The more orthogonal they are - and yet identifiable - the easier it should be to read note groupings as 'words.' Another key design decision is in the layout of the staff; when we read a written language, we don't have lines regularly interrupting our reading. I think that excessive staff lines are counterproductive to reading a vertical grouping of notes as a word. Yet, that's a bit of a catch-22 as how can the absolute vertical position be determined easily and intuitively without lines or some kind of demarcation that ultimately inhibits the fluid read-notes-chords-and-phrases-as-words approach? In written language we don't have this to worry about as we only work in the horizontal plane, and the duration of one word never exceeds or carries into the next. [Completely random side thought: That just got me thinking about designing - or at least contemplating - methods of flattening the notation and yet still conveying all necessary information. I'm going to ponder this and try my hand at a design, though I could see this turning into a multi-year refinement process, too. Eek! I'd love to see the structure of music be as apparent as the structure of a written sentence.]
Anyway, back to my original musing. I wonder if such a relative/absolute system would or could ever catch on?One more random thought - as someone became more advanced the 'vertical position denotes relative pitch' approach would actually facilitate reading note groups as words in a roundabout way. Once one knew all keys, seeing the vertical relative layout of say, a Major 7th chord starting on the 4th degree, you'd read the vertical grouping as a word; in this case a word representing "Major 7th chord" and would instantly know the right chord to play given the key (again, assuming one knew all keys).
The super easy transposition approach that Pinwheel facilitates makes this an easy process that even beginners could grasp (although beginners would not find this an instantaneous process, unfortunately.) Conversely though, they could just read each unique symbol in the chord and play it that way, and that's exactly what I'd imagine they do until they begin to learn and understand the underlying theory and structure of music. Once you have a grasp on structure and theory, you would reach the point you stop focusing on the trees (the individual unique note symbols at a given relative position) and instead see the forest (the 'word'; chord or phrase grouping).Actually, we can conceive of something similar in regular notation. Let's just assume that everything was written in a single clef - say treble clef - and the first line E did not represent E but represented 'root note'. Let's also assume, just for ease, only the use of sharps. So F# would not represent the pitch F# but instead "major second", G# = major third, and so on. Now, write ALL music in this relative key of E, and simply mentally transpose on the fly (yeah, it's ugly in TN, but possible!). That's basically what I'm proposing, except of course in a system where absolute pitch still *is* present via the unique symbols. This truly feels like it would be the ultimate notation. I would love to be able to scientifically compare such an approach to the same system of 12 unique symbols, but with both vertical position and unique symbol denoting the pitch (as is the current design of Pinwheel) and see how many more sight reading errors, if any, the relative approach would have. Of course, it would be amazing to see if the relative approach offered unique benefits to improvisation (and just general understanding of music. Surely it would let us compare and contrast various pieces and passages with MUCH greater ease) and such for more advanced musicians, although outside of anecdotal reports, I don't know how you could really quantify that.
~Seth
On Tuesday, October 30, 2012 9:11:01 AM UTC-5, Paul Morris wrote:On Oct 30, 2012, at 7:26 AM, Seth Hofslund <imagi...@gmail.com> wrote:I've gone a long way to making it easier to learn music via the way theoretical concepts, transpostion, and scales (all intervallic relationships really) are very easily represented and, perhaps the most innovative aspect of my design, verbally, visually and mentally condensed.Hi Seth,Sounds promising. I wholeheartedly agree that making interval relationships clear through isomorphism is key for making notation simpler, more intuitive, and easier to learn. When you get around to publicizing your Pinwheel system, I'd suggest including a comprehensive interval chart like the one I've provided for TwinNote[1], to demonstrate its consistency in the appearance of intervals.As far as other 3x4 notation systems, Joe Austin's is one that comes to mind[2]. It sounds like your system may have a somewhat similar approach, at least to the extent that it is also based on a 3x4 note pattern.I look forward to more details on your system!Cheers,-Paul M
Hey everyone. One quick question: are there any standard pieces that you guys are translating to your notation to show it off? If not, perhaps we should find a few pieces: something easy, moderately difficult, and very difficult, so that we can easily compare and contrast the various notations (at least on a simple, visual level).
Hi Roy;
I just tried mapping my notation to your vibraphone and I think you'll be extremely happy with the results. I love how easy it is; the two play together wonderfully. It's almost a 1:1 mapping - surely easier than it is on my primary instrument, the guitar. A question for you: have you thought of differentiating the 4 element in your system (ie differentiating each major third in some manner other than color?). I only ask because if you did, that would truly make it a 1:1 mapping. Actually, now that I look at it some more, a single marking (I'll explain this after I reveal more) placed only on given set of cycling major thirds would pretty much make it the mapping totally clear between your vibraphone and Pinwheel notation. I'm 100% that it could be explained to a beginner and have them reading and playing music within 10 minutes.
Glad to see that this maps so effortlessly to an instrument that I had not considered at all during its development (well, not directly. Of course I had isomorphic instruments in general in mind the whole time, but tried to keep the approach instrument agnostic). Proves to me the very universal nature of the design.
Now, if only you could design a perfectly isomorphic guitar! (of course the redundancy of numerous pitches is always going to make that a less ideal instrument in an isomorphic sense, even with a non-conventional all strings tuned in fourths arrangement).
On Tuesday, October 30, 2012 7:01:00 AM UTC-5, RoyP wrote:Hi Seth,
I have not tackled the notation system yet. As you know, I have a fully key transparent, symmetrical, 3x4 naming/numbering system, and visual coloring system for my 6+6 vibraphone. It is all of a piece, and is very playable. I eagerly await the development of a notation with similar properties, that is also as information dense as TN, and I'm looking forward to seeing your implementation.
Roy Pertchik
Design and Construction Consultant
NYS Arch., NCARB Cert.
381 Oxford Ave.
Palo Alto, CA 94306
917 294 6605
On Tue, Oct 30, 2012 at 5:00 AM, Seth Hofslund <imagi...@gmail.com> wrote:Great responses everyone. I knew this was a tricky subject and to be honest I had thought only little of protecting any ideas until talking to a friend in the software industry who said it might be wise to do so before revealing too much; and this coming from a guy who is not at all a fan of patents after seeing what they've done to the world of software.Truth is the notation started out as a strange phonetic system/grid to help me better learn the guitar. It kept growing and changing - often times radically - and finally I realized that it made sense to try and tackle a whole notation system. Anyhow, I'll try and keep this post short and address some of the questions asked.
>>"Are you aware of the reference head notation?"
Enrique, yes I am. Yours was the most radical concept I had seen and was what set me off on the idea of a notation that expressed much more data with less overhead compared to TN. I don't know where your system is at now or what has changed. It was over two years ago since I last looked at it. I took a quick gander at some of the other notation systems at the time and while there were a number of good ideas in many of them, I felt that they lacked the deeper cohesiveness I was seeking. If you're familiar with programming languages, I felt that many of the notations were analogously doing things like implementing reflection, etc, whereas I wanted the full cohesiveness of say Lisp. That will only make sense to those who've used Lisp to any degree; it's features look almost the same as other languages, but it's the way they all come together (primarily thanks to the syntactic regularity of s-expressions and the code-is-data-is-code approach) that truly sets Lisp apart. I owe you thanks Enrique for lighting the creative fire in me. It was actually one thing in particular about your notation that really got me thinking; - I remember you had some kind of interval naming scheme based on the three tiers of the note traces (sorry if I'm getting the terminology wrong). You had a naming scheme for lower/higher and alternate positions, I believe, and it was the inability to decipher exactly how many steps an 'alternate' interval actually was that set me off looking for another way.
>>"how does one navigate the existing protections on already available curricula and sheet music so you can make it available in your new notation?"
A good question, which I sadly don't have an answer for as of yet. Would writing software that converts files of a given type into Pinwheel Notation be against the law? If legal, that seems the best route. Let the user of the software be responsible for owning the rights to any music that they wish to translate to or from one notation to another.
>>And if this silliness doesn't make you laugh, perhaps you need a good cry.
LOL. No tears here Michael. Thanks for the laugh. I do realize the catch-22 nature of it all, and protecting something that there's currently no demand for seems to border on the absurd.
>>What do you want to protect your notation from? What is it in particular that you are concerned about, or want to achieve or avoid?"
Well, on the rare chance that it got the exposure and momentum I dream of, I envision it potentially supplanting the piano roll in software. In such cases, it would be nice to be able to leverage some licensing fee or something. Ideal, not necessary. Truth is I didn't create this with monetization in mind (I may have some off the wall ideas, but creating a notation system strictly with the idea of monetizing it is a bit too far out, even for me :P).
Now it's time to look more into the notation systems already present. I more or less created this in a vacuum, in fits and spurts, sometimes spending a week trying various symbols and shrinking it all down to 'smaller than I'd ever hope to see' sizes and making sure it all works and the fidelity of the unique symbols remains in tact. Sometimes I'd spend a week or two exploring what would become a creative dead end. Sometimes I wouldn't touch it for months and instead just focus on my playing. I've relearned I don't know how many different naming schemes I've used throughout its development. But I do need to see what else exists. Specifically, what 3x4 notation systems have been proposed? I've heard of naming schemes (Roy, do you have your own notation or is it just an internalized naming scheme that you use?) but full blown notations? I've kept out of the loop more or less intentionally as I didn't want to be influenced by others (I found this helped me a lot in the past with game design. You need a core understanding, of course, but to really innovate need to step away from the 'improve an existing design' and instead consider every element from the ground up, and consider all known and accepted approaches as potentially disposable.)~Seth
--
You received this message because you are subscribed to the forum of the Music Notation Project (hosted by Google Groups).
To post to this group, send email to musicn...@googlegroups.com
To unsubscribe from this group, send email to musicnotatio...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/musicnotation?hl=en
~Seth
--
You received this message because you are subscribed to the forum of the Music Notation Project (hosted by Google Groups).
To post to this group, send email to musicn...@googlegroups.com
To unsubscribe from this group, send email to musicnotatio...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/musicnotation?hl=en
----- Original Message -----From: Joseph AustinSent: Tuesday, November 06, 2012 1:50 PMSubject: Re: [MNP] Protecting your notation?
----- Original Message -----From: Joseph AustinSent: Tuesday, November 06, 2012 1:55 PMSubject: Re: [MNP] Protecting your notation?
Enrique, yes I am. Yours was the most radical concept I had seen and was what set me off on the idea of a notation that expressed much more data with lessoverhead compared to TN. I don't know where your system is at now or what has changed. It was over two years ago since I last looked at it. I took a quick gander at some of the other notation systems at the time and while there were a number of good ideas in many of them, I felt that they lacked the deeper cohesiveness I was seeking. If you're familiar with programming languages, I felt that many of the notations were analogously doing things like implementing reflection, etc, whereas I wanted the full cohesiveness of say Lisp. That will only make sense to those who've used Lisp to any degree; it's features look almost the same as other languages, but it's the way they all come together (primarily thanks to the syntactic regularity of s-expressions and the code-is-data-is-code approach) that truly sets Lisp apart. I owe you thanks Enrique for lighting the creative fire in me. It was actually one thing in particular about your notation that really got me thinking; - I remember you had some kind of interval naming scheme based on the three tiers of the note traces (sorry if I'm getting the terminology wrong). You had a naming scheme for lower/higher and alternate positions, I believe, and it was the inability to decipher exactly how many steps an 'alternate' interval actually was that set me off looking for another way.
--
You received this message because you are subscribed to the forum of the Music Notation Project (hosted by Google Groups).
To post to this group, send email to musicn...@googlegroups.com
To unsubscribe from this group, send email to musicnotatio...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/musicnotation?hl=en
----- Original Message -----From: Joseph Austin
--
You received this message because you are subscribed to the forum of the Music Notation Project (hosted by Google Groups).
To post to this group, send email to musicn...@googlegroups.com
To unsubscribe from this group, send email to musicnotatio...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/musicnotation?hl=en
for further discussion, see:Joe Austin
On Nov 6, 2012, at 2:54 PM, John Keller wrote:
Hi Joe,I totally agree that the main point of a rhythm notation should be where in the bar/beat to play rather than how long to hold notes. In traditional notation this is covered by grouping of notes. I think the system can be extended so that you can always see where notes are relative to the beat.An example is how I notated the right hand of Love Me Tender. Always beam quavers in beats (not 4 together) and eliminate single flags. Rests and ties can be notes without heads. For little kids I call a one beat note "play", and two (beamed) quavers "ea-sy". When i first showed this music to one 6 yo, she got what the opening meant straight away -say "ea-sy" but only play on the "-sy".Cheers, john K
For more options, visit this group at http://groups.google.com/group/musicnotation?hl=en
For more options, visit this group at http://groups.google.com/group/musicnotation?hl=en<Rhythm Syncopation 2012.tiff>
Re: [MNP] Support for chromatic staves in LilyPond
Joe,
thanks for the example Paul has made in LilyPond. Good and nice try though the symbol designs seem inconsistent as like borrowed form different visual styles.
Joe,
thanks for the example Paul has made in LilyPond. Good and nice try though the symbol designs seem inconsistent as like borrowed form different visual styles.
thanks for the example Paul has made in LilyPond. Good and nice try though the symbol designs seem inconsistent as like borrowed form different visual styles.
Yes. The diatonic symbols are the traditional shape-note symbols, but the others may be borrowed from the rhythm set.
I think he took what was in the standard font that comes with Finale.
Paul, I was heavily influenced by KlavarSkribo in designing StaffTonnetz.
As I've said before, my original intention was not so much to create a new notation as to devise a way to print notation as text,and the vertical orientation of KlavarSkribo inspired my approach. I also borrowed the stop/continue idea from KS.As for timing, I got interested in that from trying to play Beatles music, which is highly syncopated.Actually, it seems most pop/rock is syncopated.Which is why I think timing notation needs reform.And when playing keyboard, keeping both hands going,thinking of timing as "durations" of notes in the individual parts doesn't really work for me;I need to think in terms of the beat and when the individual notes come in.Even when singing, It's easier to synch with the beat than "count" the duration.
I also noted the challenge of occasional quick notes in an otherwise slow piece.My current solution is to expand the timing of the relevant measure.For an occasional few notes, I just use a smaller font and "squeeze them in" (similar to grace notes);I also use an alternate ink color to highlight such places.
With full scores (piano, band) it's not as frequent a situation as you might think,because at least on of the parts is usually moving!Indeed, one possible solution is to include a "drum track" as part of the score.For simple rhythm parts, this could reduce to a single "staff line"with the different parts below, on, or above the line, or possibly different head shapes or colors.I've considered using something like a clock-face "notehead" on a timing track to indicate the beats.
Principles of Rhythm Notation
PATTERN
· Music is poetry;
·
It should not be formatted as prose
· rhythm is a pattern in time
· pattern is characterized by repetition, periodicity
· pattern is discerned holistically—the forest, not the trees
· therefore layout is crucial to discerning visual patterns
· analogy: poetry: layout in stanzas, lines, feet
· _
· LAYOUT
· music should be laid out on a page in lines and stanzas
· each line is a musical phrase
· line breaks should match phrase breaks
· page breaks should match section breaks
· corresponding beats of consecutive lines should be aligned
· _
· UNITS
· lines consist of rhythmic beat-units analogous to poetic feet
· notation should treat beat-feet as units
· notation should not connect (tie, beam) units of different “feet”
· _
· the two “natural” rhythmic patterns are:
o cadence of walking, marching: Left, Right, Left, Right
o e.g. | q q q q | q q q q |
o heartbeat:
lub DUB – lub Dub –
e.g. q | h – q | h –
where q = quarter note, h = half-note
o “anacrusis”
is not just a property of the first measure
but of every phrase
o anacrusis
is a symptom of beat-units that start on an un-stress:
iambic, anapestic.
· 3-time (compound meter) music typically begins phrases on an un-stress
· Therefore: line breaks at phrase breaks will not necessarily break at measure bars!
· _
· ABSOLUTE vs RELATIVE
·
for sensing rhythm, occurrence relative to the
beat-pattern (absolute)
is more important than “duration” (relative or differential).
· SO: rhythm notation should primarily identify the beats and counts on which notes are struck, rather than the duration for which they are held.
· _
· MATHEMATICAL INTERPRETATION
· An issue: “compound-meter” music is usually said to consist of “three quarter notes” per measure
o This is mathematically untenable
o Three
counts in a measure should be called “three third-notes”,
not “three quarter-notes”
o (MIDI “solves” the problem by considering the “quarter-note” the unit)
o TN
also names the counts of a measure starting with “one”:
”one, two, three; one, two, three.”
o it
would be more computationally convenient to start with “zero”;
“zero, one, two, zero, one, two
then we could use standard modular arithmetic.
Joe,
I understand your passion with alternative rhythm notation, but I do not understand how a notation system that inherits TN rhythm notation could be an appreciated alternative for our times. Obviously the same is no alternative.
While looking for an alternative at least try not to inherit some of TN RN inconveniences and problems:
- The faster the music the more it additionally clutters the scores.
- Disastrous for conversion engines of score writers.
For example I would introduce the undefined beam, which is an equivalent of any number of beams, I find unnecessary or redundant that both the number of heads and the number of beams increase.
Combining this kind of idea with others (I played with) could move the symbolic notation of rhythm from manual times to our times.
Let me say in other words TN pitch notation has inconveniences, but rhythm notation has problem.