.score note name input -- wrong octave?

Discussions, advice, bug reports and much more about the "bach" environment.
Post Reply
you sir name
Posts: 2
Joined: Thu Apr 11, 2019 4:40 pm

.score note name input -- wrong octave?

Post by you sir name » Thu Apr 11, 2019 5:02 pm

Hi,
with bach.score, I'm using gathered syntax with note names because that's simply easier to read than midicents, but bach.score seems to misread the note names by an octave: C4 comes out as 4800 midicents when it should be 6000.

(I did not find an attribute like @middleoctave, but maybe there is something like that somewhere?
I imagine this would be easy to fix?


bach.n2mc has that "middleoctave" option, but is buggy in other respects: It only understands the anglo note names when you don't specify the octave:
E.g., C A G E works but C4 A3 G3 E4 doesn't.

As for solfège, Re4 La3 Sol3 Mi4 works; but "So" for G does not - may be good to include that because the l is easily overlooked and some people don't bother with it in their solfège practice.

Fwiw, I'm still on Max 6.1.10, with bach v.0.8.0.1b, OSX 10.11.6.

Thanks at any rate for your work on this great external, I couldn't imagine what Max would be without it...

danieleghisi
Site Admin
Posts: 1347
Joined: Fri Dec 03, 2010 1:25 pm

Re: .score note name input -- wrong octave?

Post by danieleghisi » Fri Apr 12, 2019 10:34 am

Hi,

since bach 0.8, bach has C5 as middleC. This is non-negotiable, we have already discussed it here:
http://forum.bachproject.net/viewtopic. ... le+C#p2501
You also find it in the doc:
1) Extras-> What's New -> Pitches
2) see #pitch+syntax in the help center

Latin letters for note names cannot be used any longer.

bach.n2mc is deprecated but still works fine for backwards compatibility; [C4 A3 G3 E4] given to bach.n2mc work fine on my machine, if they don't on your machine please post the patch snippet.

d

you sir name
Posts: 2
Joined: Thu Apr 11, 2019 4:40 pm

Re: .score note name input -- wrong octave?

Post by you sir name » Sat Apr 20, 2019 2:51 pm

Oh ok, that makes some sense! Now I just have to find a way to apply some +1200s to only the notes in a ton of gathered syntax...

I know it's not up for discussion in terms of code, but I think it would be good to have a HUGE DISCLAIMER somewhere in the help (or even at multiple places in there) that your note names work differently from the standardized note names... even if it makes more sense arithmetically, you're still up against the weight of convention; hapless music theorists like me just assume they know what C4 means, and get very confused (I never considered looking that up in the help, precisely because it's such a familiar concept!).
In my case, I spent at least an hour figuring out what I did wrong until I realized that it must be something about the object...

At any rate, thanks for the reply.

Re n2mc, I just realized that I don't know how to post patch snippets to the forum, duh. Anyway it's really just:

(C4 A3 G3 E4)
|
[bach.n2mc]

which outputs (C4 A3 G3 E4) again for me, whereas (C A G E) comes out as 6000 6900 etc.

danieleghisi
Site Admin
Posts: 1347
Joined: Fri Dec 03, 2010 1:25 pm

Re: .score note name input -- wrong octave?

Post by danieleghisi » Sat Apr 20, 2019 7:25 pm

Hi,

your bach.n2mc example it works fine on my machine, I guess it was an issue we had already fixed. At any rate, I suggest that you move to using bach.p2mc instead.

As for the C4 convention, I understand your point, we'll think about it. However, let me just point out that there is no single standard for octave naming, and C4 is *one* of the standards (although admittedly the most used): you easily find software having C3 as standard, and also software having C5 as standard (supercollider is the first one that comes to my mind).

Best,
Daniele

danieleghisi
Site Admin
Posts: 1347
Joined: Fri Dec 03, 2010 1:25 pm

Re: .score note name input -- wrong octave?

Post by danieleghisi » Sat Apr 20, 2019 7:27 pm

And this is a quick way to apply +C1 on pitches only (copy the code and just paste it into Max; btw, you can get it with Copy Compressed):

<pre><code>
----------begin_max5_patcher----------
508.3ocwU00aaBCE8Y3WgkecrJ9FZeapZZ+HhhhLjaabUvFYLoYpJ+2m80PW
1Jkf1xVeAju19dtmiuG6W78nUxiPGkbGYEwy6EeOOLjMf2vXOZC6X8dVGtLp
.dVV8DMvMkFNpwvUr5c2zp3B83Th9FYudOnw8ENDskoq2wEOtQA0ZGtIYw2D
FPhCCs+xivAlPj0C6guEgv.6mu8rryEiIOZHXG6.rciYclbugo0JdUu1QOuW
oiG8.n53RgIEUfxNYYXXXFN4Ie+wum7CVnjz.ccrGg2nIqtOkjaRM4Aoj7kD
xpJlh77NlFLU.IJbM4aYjulrdbisJnCDZl1Tba1yEPsrWfoJcRMcj1tP5u2B
NAkReU5lRtyQctr.04jYk6xIk63+.MZt1lOQtOhdEYXZdhkTQEoXCU5bLr3+
BCaXsvdnYZRF+tjL3RGkNmSTZ7YmnuCQymlnerNm4zrG360FaR60VzF6NRJs
+Jls+O6hcG3tnVy5ucKJhrM9uR+NYupdrVGNWH+D6sPmlKva.NaM25VyjB7R
woXA3Xqkn+Rbxb43eNN4K.mrqftUtPcK7JnaWBmh2fiq8i01N3LQPrPX7YOI
cVz.bHW3FhODSUvA935wGWnLkwnnMtjdEVVzi4oT2VkaAknmiWH6aImARzCK
Xlm9ZYNdfVc+S9+.lto7S.
-----------end_max5_patcher-----------
</code></pre>

Tj Shredder
Posts: 34
Joined: Sun Jul 30, 2017 11:09 am

Re: .score note name input -- wrong octave?

Post by Tj Shredder » Sun Apr 21, 2019 7:27 pm

Ha, its worth to save this little gem as abstraction (and feed it with round brackets...; - )


<pre><code>
----------begin_max5_patcher----------
1065.3ocwXs0iahCE9YxuBKdpUMaDP.Bz2ppVs+HpphLfSh6B1HiYlL6n9ee
8MHbMkLYRadHQ4b7ky46b2utxxNgdFUYC9L3a.KqWWYYoHIIXY9ukcA7bZNr
RsL6TZQAhvsWq4wQm4J5vxx7W.7SHvm.zRDCxoL.kHoQAkXd5Iw8X1TNlfRo
0D0N8LDKgh0fIG2yPobsD4F4swYMHNdyNmcAdNMe7VCbCbjr1tciC36lSfTW
fI4HtRPcuPjVyan5XnhyTBMM4G+UnsjzOWsR905EhBDzyh8NBDJAIvzSaJ+D
3qtML02N+kRjVorsaE3IT4cNyowQJNdd2lB6NVg2Z285QLiZZzSK6C3bzSHV
ElR5bBVRKbGxVc1hDb9AUcPQqaIgIZRNsjXnmvM6OrkJjI.At.ApYJHx9bnu
8kiglgXjZrRTzDElIiHoLHDXAppDlp2rzt0v9BrFDKAOWGe4Og9JnzWhnMXo
vfeLml9unrthrsvSlfIkLTkvmGxMxdK6LzAXcNe+AJgWg+OkD3J8Ymf+AiDN
ISoNnD+uvvv7VE3HCmQIRgnmkPRt45DQIAJcKnqxnVAAVNwlEt.BXYFlUBkr
tJAxjFpjbTm.TgaNkl2mU69xQG3F1kXBY.JxokyyjgOd5J6MgJXVbsyVwoZe
MQycuvmfuuB9TezlCyyMQs8O9yPBt.xQbr1DHB5ZXhHPghdpJkQyy6ouZNOM
AmLgOdJ5YbF+j5h55LHVNtrwIxt0JmgOhp38owgGq5Soh+hFz6PpNwDCumiJ
JyEZQ+EzK6d2.1t425Q+Z445mqSkoqShteQxtYywG5pbe8C13E6IhI8Ci1EH
CRGltabJOu9LFm1aXpuc1MjU46MISdPXSArDkiJtN7rdAPjtTmqSbeDJZ28f
PdSiPgcEWYPT1dcBi8PNmgSp4ZGJqQfikso5f3dRzUUhDUtBZWPKj+6.7EEw
3HFn79Q+FGzgv+N2G.7G7d5fpji6K5T65IqWp9nTcc6Ha08e4bM024ViO6kK
ooSytYzTqmjgN2ocf2ErRKa1KAM7DMc55G665KgC+333fkAGtyBGNSCGd2Mb
boi.YO2yTJPooR9SiSUzZVZiGiNK5ZPe0TTZiiIs8G8s1bI.Wv2WjU5Vkg.8
Y+GUFBWnLDnwqGFNrDawtGnL3dC9CNOPawRjAuYkACwlgK9UE+d8szUmXDiD
Xtoms1d9mnouUWDt2mIS0ykxvWlbe1gOc8iTSI49Vl2bhArisuMD8JsQ7lPD
wzgUvinQPxG9pOHTbzfCTJ3KaAePLFA34ShlnERfnd+GA+S.3u29w6YP9fs5
JFQWGK8V5r6QcerB0Y0OwtFOFF7XPkQAMQcCZlIfY6k.lQ39RumsK3dhGcOZ
0avqNHuhAu1vfWZX7qLL+KLL70ETA+y8pBq94p+mbBdhJ
-----------end_max5_patcher-----------
</code></pre>

danieleghisi
Site Admin
Posts: 1347
Joined: Fri Dec 03, 2010 1:25 pm

Re: .score note name input -- wrong octave?

Post by danieleghisi » Mon Apr 22, 2019 9:46 am

Oh yeah, sorry for the square brackets, that was a sneak peek into the forthcoming bach version, where square brackets will be the default brackets for llll levels.
Don't worry, round brackets will still be completely supported, and backward compatibility with them fully preserved. Stick with them if you're up for it, but we have a good reason for this change, and you'll discover it in the forthcoming release ;-)

Post Reply