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
This is a bit of a feature request but thought I would ask. I have been trying to sync FT to a MIID clock (from Ableton Live specifically using MIDI Yoke). An FT VST or Rewire would be amazing but just being able to sync BPMs would be helpful.
Is this feature planned perhaps in a future release?
On a similar vein, I was thinking of using a real NES for some things. I know there's MIDINES but I also like the idea of burning EPROMs. My tests for recording NES game music to Live were met with mixed success. For playing NSFs on a real NES, am I able to guarantee a certain BPM? I know it may end up as a fractional BPM due to the timing of the NES itself but is this even predictable?
Thanks!
By the way, I'm really enjoying FT! Haven't done tracking much lately but it seems to be such a damn good fit for chips which FT has been hugely helpful with!
[quote=m00dawg]For playing NSFs on a real NES, am I able to guarantee a certain BPM? I know it may end up as a fractional BPM due to the timing of the NES itself but is this even predictable?
Thanks![/quote]
Maybe some more elaboration would be good.
[quote=nicetas_c][quote=m00dawg]For playing NSFs on a real NES, am I able to guarantee a certain BPM? I know it may end up as a fractional BPM due to the timing of the NES itself but is this even predictable?
Thanks![/quote]
Maybe some more elaboration would be good.[/quote]
This is an aside from the FamiTracker clock sync. In fact I guess I should have posted this in another post but that said:
My thought was since the NES derives things from NTSC that being able to guaranty an exact BPM might be difficult. I might have a BPM of 150 but it's actually 150.1 or something like that. Correct me if I am wrong on that one. In fact, I would like to be wrong there because if I can set a proper BPM and it really is that, then syncing might be less of a headache.
This is really for using a real NES to play my song and import it back into something like Live or even use it for live performances (the latter of which would be precarious due to the syncing concerns and means I would likely need a MIDINES at that point).
The reason I want to use a real NES is that it seems to sound deeper and dirty than the harsh tones from my computer. Granted, that means using something like the VR6 chip is just about impossible but still
Sorry to break this to you, but the beats per minute that a note plays isn't completely related to the TV's frequency.
In an NES, it's true that the entire system's clock mechanism is tied to the TV's frequency (which is 60 Hz in North America & Japan, whereas it's 50 Hz everywhere else). And it's true that every program that runs on an NES (including music data) is clocked through at this speed.
However, the frequency only determines how fast the music's data is streamed from the cartridge into memory (before being sent to the output). By what I understand from FamiTracker & the way music is programmed for the NES, the beats per minute is mostly controlled in software. Latching a MIDI beat clock to 60 Hz would work in terms of preventing clock drift, but it's not enough for the problem at hand.
And since a MIDI beat clock needs a time code along with said frequency latch to be completely synchronized, this would mean something extra would have to be added into FamiTracker; the ability to produce a time code that your MIDI hardware can understand.
_______________________
Technology: the one thing that's hated & cursed at by all engineers, technologists, scientists & technicians!
[quote=m00dawg]...My thought was since the NES derives things from NTSC that being able to guaranty an exact BPM might be difficult. I might have a BPM of 150 but it's actually [u]150.1[/u] or something like that. Correct me if I am wrong on that one...[/quote]
~150.00600024BPM for 60Hz as I know of (there is no exact 60Hz, only (1000000 รท 16666) Hz) although I could be wrong as well.
That confirms that for live performances, I would have to use MIDINES and compose songs using that manner.
Otherwise, I can simply record the NES and fix the BPM in Ableton Live. It does pretty good beat-matching and, when it's off, you can help it out using some beat detection and things. So the fact that it's not 150BPM for instance, is not a huge issue.
I actually expected what TechEmporium and nicetas_c confirmed.
...but back to MIDI clock sync in FamiTracker itself
Yes; that would mean a separate algorithm would have to be added in FamiTracker. One which would have to be tied with the speed & tempo settings that you can edit in the program.
Some sort of a math equation would help for this; Here's what I'm proposing as a simple algorithm (though I may be wrong; the experts like nicetas_c or Delek can prove me wrong):
B = T (6 / S)
where B is the total BPM, T is the tempo value & S is the speed value.
To confirm this:
At a speed of 6 & a tempo of 150, the track runs at 150 BPM. At a speed of 5 & a tempo of 150, however, the track runs at 180 BPM.
_______________________
Technology: the one thing that's hated & cursed at by all engineers, technologists, scientists & technicians!
If i'm right the NSTC its not exactly 60hz, in fact its 59,94005994005994005994005994006hz (60*1000/1001).
So the tempo of FT to be in sync with the NES need to be 149,85014985014985014985014985BPM. Of course i could be wrong.
@Delek yes but if we were using FamiTracker like a software instrument that would be a non-issue? Basically like using it as a VST in which we were not going to plan on running it on real hardware (or if we were we would have to fix the clock manually).
That's basically what I have been looking for - a good Nintendo VST but the ones I found are lame or hard to use over a tracker interface so FT really fits well there save for the MIDI sync problem.
) 