Talk:APU Noise: Difference between revisions

From NESdev Wiki
Jump to navigationJump to search
No edit summary
No edit summary
Line 1: Line 1:
Curiously, the noise channel's frequency counter [http://uxul.org/~noname/chips/cpu-2/no-metal/stitched/final/ on the die] isn't an ordinary counter - it's an '''11-bit linear feedback shift register''' (with taps at the 9th and 11th bits); when I take the counter values from the on-die ROM and run the LFSR until the result is '10000000000', the cycle counts (for NTSC) match once multiplied by 2 (note that this means the PAL frequency for $1 is almost definitely wrong). --[[User:Quietust|Quietust]] 04:58, 23 January 2011 (UTC)
Curiously, the noise channel's frequency counter [http://uxul.org/~noname/chips/cpu-2/no-metal/stitched/final/ on the die] isn't an ordinary counter - it's an '''11-bit linear feedback shift register''' (with taps at the 9th and 11th bits); when I take the counter values from the on-die ROM and run the LFSR until the result is '10000000000', the cycle counts (for NTSC) match once multiplied by 2 (note that this means the PAL frequency for $1 is almost definitely wrong). --[[User:Quietust|Quietust]] 04:58, 23 January 2011 (UTC)


"randomly 93 or 31 steps long otherwise. (The particular 31- or 93-step sequence depends on where in the 32767-step sequence the shift register was when Mode flag was set" - seems worth mentioning that, while random, there is only one 31 step pattern [1101000100101011000011100110111], and it occurs 1/1057 of the time.  This compares to the 352 different 93 step patterns that occur the other 1056/1057 of the time.
"randomly 93 or 31 steps long otherwise. (The particular 31- or 93-step sequence depends on where in the 32767-step sequence the shift register was when Mode flag was set" - seems worth mentioning that, while random, there is only one 31 step pattern [1101000100101011000011100110111], and it occurs 1/1057 of the time.  This compares to the 352 different 93 step patterns that occur the other 1056/1057 of the time. --GreyRogue
: From a musical point of view, the problem is that the harmonic content of the waveform varies widely, with no ability to control or even appreciate correlations between the harmonics, and the question whether the specific sequence has 31 or 93 steps is irrelevant.. Far more relevant is the relative rarity of the LFSR waveforms that have a loud 31st harmonic.
: From an emulation accuracy point of view, the relative probability seems like a distraction. What is the purpose of mentioning this?
: Here's the relevant thread that resulted in me adding that to the wiki: https://forums.nesdev.org/viewtopic.php?t=11535 —[[User:Lidnariq|Lidnariq]] ([[User talk:Lidnariq|talk]]) 00:23, 18 April 2021 (MDT)

Revision as of 06:23, 18 April 2021

Curiously, the noise channel's frequency counter on the die isn't an ordinary counter - it's an 11-bit linear feedback shift register (with taps at the 9th and 11th bits); when I take the counter values from the on-die ROM and run the LFSR until the result is '10000000000', the cycle counts (for NTSC) match once multiplied by 2 (note that this means the PAL frequency for $1 is almost definitely wrong). --Quietust 04:58, 23 January 2011 (UTC)

"randomly 93 or 31 steps long otherwise. (The particular 31- or 93-step sequence depends on where in the 32767-step sequence the shift register was when Mode flag was set" - seems worth mentioning that, while random, there is only one 31 step pattern [1101000100101011000011100110111], and it occurs 1/1057 of the time. This compares to the 352 different 93 step patterns that occur the other 1056/1057 of the time. --GreyRogue

From a musical point of view, the problem is that the harmonic content of the waveform varies widely, with no ability to control or even appreciate correlations between the harmonics, and the question whether the specific sequence has 31 or 93 steps is irrelevant.. Far more relevant is the relative rarity of the LFSR waveforms that have a loud 31st harmonic.
From an emulation accuracy point of view, the relative probability seems like a distraction. What is the purpose of mentioning this?
Here's the relevant thread that resulted in me adding that to the wiki: https://forums.nesdev.org/viewtopic.php?t=11535Lidnariq (talk) 00:23, 18 April 2021 (MDT)