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
I think it would be nice to have the BPM marker on the status bar change its calculation based on the row highlight, rather than fixing itself to believing that only four rows belong in a "beat". This way, I can change to row highlight to 6 to more easily introduce triplets, and the BPM marker would be accurate.
_______________________
[url=http://icesoldier.me]Website (includes FTM's of my covers)
But what of BPM values that would otherwise produce odd row highlighting? There are some very odd BPM values where songs won't seem to flow at an even pace.
_______________________
Technology: the one thing that's hated & cursed at by all engineers, technologists, scientists & technicians!
I'm not sure what you mean here. I didn't mean adjust the 'tempo' value that affects how many ticks are in a single row. I mean take the current speed/tempo values and use the row highlight to adjust the label in the status bar on the bottom.
For example, at speed 6/tempo 150 the BPM marker reads "150 BPM", but if I change the row highlight to 6 and 12 (to make it easy to write a song in 6/8 time), I want the label to read "100 BPM". It's an admittedly low-priority request, but I adjust the row highlight often enough that the label has become nearly meaningless to me.
_______________________
[url=http://icesoldier.me]Website (includes FTM's of my covers)
I like this idea, but another thing that could be extended onto this is one thing that could very well be useful to some, who knows.
As we all know, using speed 3 instead of speed 6 allows for more capabilities - though it says 300 bpm below. Now while this makes sense, I'm yet to see an actual 300 bpm song that sounds good -- they're normally just 150 bpm.
I guess this could be done with the above; using the row markers to actually tell if it's a proper 150 bpm song using 4/8, but still, it would be nice.
Another thing would be nice is averaging of rational tempo, but that'll probably take way too much time not be worth it in the end.
This is very easy to add. I've changed it now so it works like your example, changing the row highlight to 6 will display 100 BPM (the second highlight option is ignored).
[quote=icesoldier]Excellent! Thanks for the reply and action! Out of curiosity, what happens when the row highlight is 0? It seems like an accident waiting to happen.[/quote]
They disappear.
[quote=icesoldier]I knew that, I meant what happens to the BPM marker? I think there's a divide by zero error hiding in the shadows.[/quote]
This is something that needs to be performed by a professional idiot. I will gladly do so when the public beta is out.
[quote=icesoldier]Excellent! Thanks for the reply and action! Out of curiosity, what happens when the row highlight is 0? It seems like an accident waiting to happen.[/quote]
If the highlight is zero then the default rate (4/16) will be used, this is to avoid a division by zero.
Well, looks like it's time to bid farewell to "900 bpm" tracks then! Not that that's a bad thing - I've always called them full speed tracks myself. I've always thought "900 bpm" was a silly way to call them. :p