ah, well the reason the finalCount is set to 192 is that equals one beat. it is 8 bits of data sent 24 times. changing it would mean that it is no longer counting on the beat.
but i see what you mean about defining the number and using that ref so that it is easy to see what that number means.
but that is answered by question 2, why does it start at 192 and tip over to 193 on the first count? well this code was cut out of a previous project that followed the same clock signal, only it flashed a light. the first transition of the clock line was also the first beat so i wanted the light to flash on the very first transition as well as the 192nd transition. originally this had a pot that defines when the light flashes, if it is twice a beat, or every half beat etc, and in that code i did have #define for all the values, 192 was defined as normal speed, but i cut that bit out when trimming the code down and never put it back. i was going to put it back in as a comment.
as with choosing to call update display, the problem is with how i have written the code, update display needs to be called all the time or the LEDs wont light. they are switched on and off as each digit is written and need to keep cycling through to display it. but you are right and i was actually thinking about this last night, i could put some code in the loop that says if the number hasn't changed for more than, 10 counts of the clock for example, then don't change the value stored in the variable.
exactly! when you go through your code in a different way, you see it in a different way, i like to explain my code to my girlfriend, even though she doesn't understand, listen or care, just because i have to say it out loud and then suddenly it all makes sense!
again thanks for the pointers and taking the time to reply i really apriciate it, i am learning the arduino code on my own just by looking at other code and the reference page on the site, but i still don't know all the little tricks or standards.