Login:
Menu:
Post: Author:
FamiTracker > General > Show Off Your Work > [A Cappella] Super Mario 64 - Slider Owner: Church_Manner New post
Page 3 of 3 Sort: Goto Page: << Previous [1] [2] [3]
Posted: 2015-03-16 23:53 Reply | Quote
Im_a_Track_Man

Avatar

Member for: 5546 days
Location: Plantation, Florida
Status: Offline

#66959
Tracker > Engine speed > custom.


Posted: 2015-03-17 00:03  (Last Edited: 2015-03-17 00:13) Reply | Quote
Stratelier



Member for: 4363 days
Status: Offline

#66962
Church_Manner wrote:
@anybody Is there a way to make a quicker change than what the sequence editor allows? It seems to be in 16 millisecond increments, but I have an idea that will only work if the increments can vary.

Those increments are defined by the speed of the NES audio engine. The defaults are 60Hz (16ms) for NTSC and 50Hz (20ms) for PAL, but you can specify a custom engine speed if you really need to (in the Tracker menu). It'll still sound mostly the same, the timing just won't be 100.0% true to what the actual hardware can produce.

Also: a MMC5 version of the same tune, by w7n_mariohacker

_______________________
Where to find me:
YouTube: http://youtube.com/user/stratelier
DeviantArt: http://stratadrake.deviantart.com/
Posted: 2015-03-17 00:05 Reply | Quote
Im_a_Track_Man

Avatar

Member for: 5546 days
Location: Plantation, Florida
Status: Offline

#66963
Stratelier wrote:
it just won't be 100% true to what the actual hardware can produce.

You can play overclocked NSFs on a powerpak, though to be fair, not a lot of people have one.

Posted: 2015-03-17 07:27 Reply | Quote
Xyz_39808

Avatar

Member for: 5589 days
Location: South Texas
Status: Offline

#66987
Using the word "overclocked" is incorrect as it implies you are doing something with the clock. What's happening is simply that you're using some other process that is NOT waiting around for an NTSC/PAL VBlank NMI to generate your engine interrupts and are using some other process.

In fact, the Famitracker driver itself doesn't actually use NTSC or else it'd play at 60.1 frames/second. FT plays at exactly 60 so it's already using some other process and using the custom engine slider is just altering that process.

Page 3 of 3 Sort: Goto Page: << Previous [1] [2] [3]