Deprecated: mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in /storage/content/49/145849/famitracker.com/public_html/forum/classes/dbHandler.php on line 29
FamiTracker
You're probably doing something wrong. Care to give more details?
_______________________
Follow me on [url=https://twitter.com/jrlepage2a03]Twitter.
I record (some) NSFs on hardware. Feel free to [url=http://www.famitracker.com/forum/posts.php?id=3633]request a hardware render.
I have tried fixing this in various ways but nothing seems to work those include:
C-4 00 F ---
--- -- - ---
D-4 -- - 302
or:
C-4 00 ---
--- -- 302
D-4 -- ---
I even removed any instrument settings to see if that could be effecting it. What I also find weird is that it will work in one channel but not the other. I'll post an example, maybe that will help.
Ironically, using 302 like you have in your example seems to fix the problem. 344 was apparently too fast... which is a little confusing.
The N163 channel is playing an octave higher, and the same speed works just fine. I thought the pitch changed faster the higher you go - this is a little counter-intuitive.
Does the Namco chip use a separate pitch table, or is the xx value getting interpreted differently in those channels?
EDIT - Oh, nevermind. Playing around with it, every expansion seems to react differently to changes in pitch. I'll just assume for now this is something beyond my current comprehension, though if someone feels like cluing me in I'll be happy to listen.
_______________________
The only things certain in life are death and uncertainty.
[quote=Necrophageon]The N163 channel is playing an octave higher, and the same speed works just fine. I thought the pitch changed faster the higher you go - this is a little counter-intuitive.[/quote]
It's the opposite - with N163 the pitch changes faster the lower you go.
_______________________
[quote=iGotno_scope]im going to continue making this crazy stuff then after a while my style will be so sick that you will be like damn suuun that shit is so sick i dont even get it. i will be like bro its ok.. you dont have to.[/quote]
The 2A03 and most other chips choose frequency by dividing the CPU clock by an integer. For these the the greatest frequency resolution is at the lowest frequencies, and the least is at the highest.
The N163 and FDS instead choose a frequency by accumulating phase (effectively multiplying base frequency by an integer). This means they have less resolution at their lowest frequencies, and more resolution at their highest frequencies.
VRC7 is in its own weird place where it's an accumulator, but it also has an octave exponent, which for the most part hides the resolution differences.
I'm always amazed at the comprehension you have for this stuff Rainwarrior. To me it's just Numbers and letters. Trial and error. Listen and re-listen until you like what you hear. lol.
_______________________
[url=http://soundcloud.com/fezuke/sets]My 8-Bit Soundcloud
[url=http://soundcloud.com/fezuke-2/sets]My Other Project Soundcloud
I do this kind of thing for a living, so I have daily practice at it. For the most part someone else did the reverse engineering to figure this stuff out. I just know how to read and understand the information at [url=http://wiki.nesdev.com/w/index.php/Category:Audio]NESDev.
Rainwarrior's analysis is correct, however, I don't understand why jsr decided to maintain the freq-values not inverted in the N163. I mean, why a lower speed value is faster than a high value?. This is no intuitive and a simple touch in the code should fix it.
I think if you're going to tamper with the code in that respect, you might as well make it equally sensitive for all values wouldn't you?
_______________________
Follow me on [url=https://twitter.com/jrlepage2a03]Twitter.
I record (some) NSFs on hardware. Feel free to [url=http://www.famitracker.com/forum/posts.php?id=3633]request a hardware render.
