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
Welcome to the forums! This sounds pretty good so far. Here are a few things I felt were necessary to point out:
1. When making 2-channel echoes, such as the one in the 2A03 pulses, the echoed channel should have a Pxx effect applied to it. This is the "fine pitch" effect, which is used to make very slight adjustments to the tuning of a pitch. The default tuning value is P80, so for using echoes, P7F or P81 should work fine.
2. Tilt your DPCM samples. If you're using DPCM for drums, I recommend cutting the samples short to leave out any extra noise heard at the end. Then tilt the end of the sample all the way up to what I call the "zero level," where the DPCM volume is zero. This restores the volume of the noise and triangle channels.
3. Usage of hardware tempos vs. software tempos. Hardware tempos are tempo values in which every row has an equal number of ticks. Examples of 60 Hz hardware tempos: 150, 180, 128.57, 112, 100, etc. Keep in mind that each engine speed comes with different usable values. Software tempos are tempo values in which some rows have slightly different ticks than others, mainly to achieve more precise tempos. Engine speed does not affect software tempos. Examples of software tempos: 98, 135, 142, 197, 168, etc. Since some rows have different ticks than others, this can cause a swing type of sound. 98, a software tempo, is close to 100, a hardware tempo, so I recommend that you use 100 instead, because it will sound better and more consistent. I only recommend software tempos when using a tempo way outside of any hardware tempos, such as 138, 165, 119, etc.
If any of that was hard to understand, I provided a fix to better show you what I meant. Note the P7F effect in 2A03 pulse 2, differences in DPCM samples and the different tempo values.
.gif)
