Matt McVickar's dashboard

I have to agree. I have been playing TTR every chance I get, and yet when I play against my husband, who's played maybe 3 times, he beats me. we are tapping at the same time, and sometimes I can see that's he's off, but he's consistently getting a better score for those times we're tapping together and it's driving me crazy -- what is he doing that i'm not doing? i can't figure it out! grrrr. (also glad to know someone else thinks 'sad but true' is off -- there's rhythms in there that are coming AFTER the rhythms in the song, it's gotta be messed up!)

I changed my mind. I now follow the visual clues more than the beat in the music. Sometimes I even play with no sound at all and get a higher score that way. I still feel though that it's hard to hit the notes perfectly – vib, on July 21, 2008 09:30

Thank you! then I'm not the only one with the feeling that there's something wrong with Sad But True especially.
It might even be out of sync with several beats. Some taps seem to be meant to follow the horns but are several beats behind IMHO.

Perfect response from Nightmare. Some indication of the actual match to the desired timing is desperately needed. There may be problems with synchronization, as well, which could be more-easily identified and communicated, if this were the case (e.g. I *know* I tapped right as the dot intersected the line; but the game didn't register it at all)

Some taps require hitting them on the beat, others require syncopation - but some seem to be completely unrelated to the beat of the song (e.g. "Sad But True" - half the song has dots which intersect the line at ~.25 sec after the beat)

Barring problems which need to be addressed, at least having some visual cue as to what is expected, and how the user has done, would be helpful.

This is always the biggest problem with rhythm games. Syncing is always an issue because of delays in hardware (aka speed of sound vs speed of light), so it's sometimes difficult to get songs to match up nicely with what buttons are supposed to be pressed.

I've also had the problem of finding the window on this game, and being a long time rhythm game player (Read: DDR, ITG, PIU, IIDX), it really frustrates me that although you can obtain different point values for hitting a circle at a certain time, there is no indicator as to how close you were to the ideal value for each note.

No rhythm game is ever synced perfectly, and it's up to the user to be able to determine just how early or late a song is in comparison with its chart, whether it be just a tiny bit early, or even really late. Without some form of visual cue as to how accurately you hit each note, you're really just stumbling in the dark, hoping that you're getting that 150 points on every note, when in most cases you aren't, due of course to syncing and its inherent imperfection.

In short, visual cues need to be added to each corresponding point value, whether it be like other rhythm games do it with "Perfect", "Great", simply flashing the point value obtained (Preferably with different colors), or in some other unique way.

my feeling is rather than match the moment it hits the line you should listen to the beat and take that as your cue

Dont know if it matters, but using iStats pro widget the process name is also "fluidinstance" rather than the name of the app (as it shows correctly in activity monitor)