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
Using volumes above 15 (F) for the saw results in problems for instruments that use channel volume to determine their volume. For example, if you have an instrument with volume "15 1" it will sound loud for a frame, then quiet from then on.
If the volume for the channel is 15, then it's "15 1," if the volume is 10, it's "10 1" etc. For the saw though, you set the volume over 15 with V01, so the volume for 16 is V01 0 which results in any volume in instruments being flattened to all ones. Same problem for all the other volumes in lesser amounts.
tldr; volumes above 15 are interpreted as x-15 by the instrument editor's volumes.
Slightly related: I really dislike the way FT handles VRC6 saw volume. More specifically, I dislike the inconsistent way it handles volume registers larger than 4 bits across expansions. The FDS has the full 0-32 range in its instrument editor, but the VRC6 saw has users go through this convoluted "duty cycle" setting (which makes no sense to begin with) + volume to get values outside the default range. Not only that, but volume values go up by twos, so there is no way to achieve inbetween values with the current system.
I'm in favour of a complete overhaul of the VRC6 sawtooth volume in a future revision of the program. We definitely need something more elegant than the current system.
_______________________
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.
*slowly raises hand*
... uhm ... how about a dedicated effect for larger registers like VRC6 Saw Volume or FDS Volume? I think Exx is obsolete since we got a volume column ...
_______________________
The purpose of a programming language is to protect the computer against the programmer.
[quote=Alexander283]*slowly raises hand*
... uhm ... how about a dedicated effect for larger registers like VRC6 Saw Volume or FDS Volume? I think Exx is obsolete since we got a volume column ...[/quote]
Or better yet, use Exx *runs*
_______________________
"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." -omgdonut
I can understand this being a problem due to instruments being shared across all VRC6 channels, including pulses which only support 4-bit volume.
I guess maybe have a checkbox that switches between 4-bit and 6-bit?
_______________________
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.
The current way is a compromise, I agree on that, but it was added to make it more similar to the square channels and thus easier to use (and easier for me to add). The duty thing was added only to allow users access the volumes where the wave starts to distort, not intended for regular use.
I think an option for allowing to select between 16 or 64 steps would be a good improvement, since it would both keep old files compatible and allow easier access to all levels. The user will then have to learn that saw volume are only good for levels below 42. I think it will be fairly easy to add as well.
I just don't like the inconsistency between the FDS volume macros and the FDS volume column, as the former goes from 0 to 32, wheras the latter, like all volume columns in FamiTracker, only allows values from 0 to 15 (F).
_______________________
Also known as UltrasonicMadness on other sites.
.png)
