Talk:Pulse Channel frequency chart: Difference between revisions

From NESdev Wiki
Jump to navigationJump to search
Line 5: Line 5:
Sort of, just a little more user-friendly. It's a simple reference for people who want to know which two bytes to plug into $4006-7 (et al.) in order to obtain a desired musical pitch, without getting bogged down in tables, calculations, formulas, ASCII diagrams, etc. Every reference I've been able to find seems to consist heavily of the latter, when all I want are those two little bytes! --[[User:Dr. Floppy|Dr. Floppy]] ([[User talk:Dr. Floppy|talk]]) 22:30, 14 October 2013 (MDT)
Sort of, just a little more user-friendly. It's a simple reference for people who want to know which two bytes to plug into $4006-7 (et al.) in order to obtain a desired musical pitch, without getting bogged down in tables, calculations, formulas, ASCII diagrams, etc. Every reference I've been able to find seems to consist heavily of the latter, when all I want are those two little bytes! --[[User:Dr. Floppy|Dr. Floppy]] ([[User talk:Dr. Floppy|talk]]) 22:30, 14 October 2013 (MDT)
:In my experience, someone developing a music engine doesn't want ''a'' pitch but instead a ''set'' of pitches to use for all the notes that will be played over the course of the program. Does your music engine store pitches in musical phrases as two bytes (a literal period) or as one (a note number)? I understand that the latter is more common in real music engines. --[[User:Tepples|Tepples]] ([[User talk:Tepples|talk]]) 07:58, 15 October 2013 (MDT)
:In my experience, someone developing a music engine doesn't want ''a'' pitch but instead a ''set'' of pitches to use for all the notes that will be played over the course of the program. Does your music engine store pitches in musical phrases as two bytes (a literal period) or as one (a note number)? I understand that the latter is more common in real music engines. --[[User:Tepples|Tepples]] ([[User talk:Tepples|talk]]) 07:58, 15 October 2013 (MDT)
::Yes, my engine (which officially became "real" over the weekend) uses a complete set of pitches from A-1 to B-7, invoked by single bytes. My lookup tables are arranged in a nonstandard fashion due to the aesthetic design choice I made early on: #$C4 indicates "play Note-C in the fourth octave", so the two relevant bytes need to be the C4th entries in their respective data tables. It was this nonlinear approach that had me wishing for a cut-and-dry reference like the one I eventually created and submitted. --[[User:Dr. Floppy|Dr. Floppy]] ([[User talk:Dr. Floppy|talk]]) 23:37, 17 October 2013 (MDT)


:What purpose is this user-friendly for? This table isn't good for someone looking to code an NES music engine. It can't be copy-pasted into code, and typing all of them by hand would be rather tedious and error prone. The [[APU period table|other page]] provides both a ready-made code block and also a program to generate them for you, both of which are directly useful for that purpose. Having a table like this is maybe useful if you want to look up a single pitch at a time for some reason, but who would want to do this? - [[User:Rainwarrior|Rainwarrior]] ([[User talk:Rainwarrior|talk]]) 08:27, 15 October 2013 (MDT)
:What purpose is this user-friendly for? This table isn't good for someone looking to code an NES music engine. It can't be copy-pasted into code, and typing all of them by hand would be rather tedious and error prone. The [[APU period table|other page]] provides both a ready-made code block and also a program to generate them for you, both of which are directly useful for that purpose. Having a table like this is maybe useful if you want to look up a single pitch at a time for some reason, but who would want to do this? - [[User:Rainwarrior|Rainwarrior]] ([[User talk:Rainwarrior|talk]]) 08:27, 15 October 2013 (MDT)
::It's useful for those who are using a non-linear format for their frequency storage in order to make actual music ''coding'' easier. To illustrate, the C-Major scale in Retrodriver™ format is C4-D4-E4-F4-94-A4-B4-C5. --[[User:Dr. Floppy|Dr. Floppy]] ([[User talk:Dr. Floppy|talk]]) 23:37, 17 October 2013 (MDT)


:Another one to potentially merge with as well: [[Celius NTSC table]] - [[User:Rainwarrior|Rainwarrior]] ([[User talk:Rainwarrior|talk]]) 08:25, 17 October 2013 (MDT)
:Another one to potentially merge with as well: [[Celius NTSC table]] - [[User:Rainwarrior|Rainwarrior]] ([[User talk:Rainwarrior|talk]]) 08:25, 17 October 2013 (MDT)

Revision as of 05:37, 18 October 2013

Merge

Isn't this the same as APU period table? --Tepples (talk) 20:27, 14 October 2013 (MDT)

Sort of, just a little more user-friendly. It's a simple reference for people who want to know which two bytes to plug into $4006-7 (et al.) in order to obtain a desired musical pitch, without getting bogged down in tables, calculations, formulas, ASCII diagrams, etc. Every reference I've been able to find seems to consist heavily of the latter, when all I want are those two little bytes! --Dr. Floppy (talk) 22:30, 14 October 2013 (MDT)

In my experience, someone developing a music engine doesn't want a pitch but instead a set of pitches to use for all the notes that will be played over the course of the program. Does your music engine store pitches in musical phrases as two bytes (a literal period) or as one (a note number)? I understand that the latter is more common in real music engines. --Tepples (talk) 07:58, 15 October 2013 (MDT)
Yes, my engine (which officially became "real" over the weekend) uses a complete set of pitches from A-1 to B-7, invoked by single bytes. My lookup tables are arranged in a nonstandard fashion due to the aesthetic design choice I made early on: #$C4 indicates "play Note-C in the fourth octave", so the two relevant bytes need to be the C4th entries in their respective data tables. It was this nonlinear approach that had me wishing for a cut-and-dry reference like the one I eventually created and submitted. --Dr. Floppy (talk) 23:37, 17 October 2013 (MDT)
What purpose is this user-friendly for? This table isn't good for someone looking to code an NES music engine. It can't be copy-pasted into code, and typing all of them by hand would be rather tedious and error prone. The other page provides both a ready-made code block and also a program to generate them for you, both of which are directly useful for that purpose. Having a table like this is maybe useful if you want to look up a single pitch at a time for some reason, but who would want to do this? - Rainwarrior (talk) 08:27, 15 October 2013 (MDT)
It's useful for those who are using a non-linear format for their frequency storage in order to make actual music coding easier. To illustrate, the C-Major scale in Retrodriver™ format is C4-D4-E4-F4-94-A4-B4-C5. --Dr. Floppy (talk) 23:37, 17 October 2013 (MDT)
Another one to potentially merge with as well: Celius NTSC table - Rainwarrior (talk) 08:25, 17 October 2013 (MDT)

Tuning

If you're going to have a chart like this you should declare the nature of the tuning used. Presumably this is equal temperament using A-440Hz but this should be explicitly stated, as it is an arbitrary choice. - Rainwarrior (talk) 08:23, 15 October 2013 (MDT)