??? 11/13/08 18:25 Read: times |
#160024 - Check for differences Responding to: ???'s previous message |
Have you looked at the communication on a scope to see if there is a difference?
Or have you augmented your code and had the code measure timing differences etc? Dummy-staring at code is best with everything is stone-dead, or when you have already used a process of elimination and figured out that it is a specific routine that does something wrong for some specific stimuli. In your case, you have different function with two different test cases. So your job is to figure out what differs. Such analysis is part of developing code (or hardware). Don't ask on a forum without first spending some time yourself. We can't measure on your hardware. We can't run test code on your setup. You can. Take advantage of that. |
Topic | Author | Date |
Midi trouble with Keyboard! | 01/01/70 00:00 | |
Blame the computer? | 01/01/70 00:00 | |
I'm lost | 01/01/70 00:00 | |
Check for differences | 01/01/70 00:00 | |
you are right... | 01/01/70 00:00 | |
First check grounding | 01/01/70 00:00 | |
==CODE== | 01/01/70 00:00 | |
Can I post... | 01/01/70 00:00 | |
MIDI Trouble | 01/01/70 00:00 | |
I can be wrong... | 01/01/70 00:00 | |
MIDI Trouble ... | 01/01/70 00:00 | |
Should be JB ACC.7 ... | 01/01/70 00:00 | |
Maybe I discovered something, but have no clue to solve | 01/01/70 00:00 | |
Midi Thru Problems... | 01/01/70 00:00 | |
Same problem | 01/01/70 00:00 | |
MIDI Head Scratcher .. | 01/01/70 00:00 | |
Data is arriving corrupted | 01/01/70 00:00 | |
tried simplest way | 01/01/70 00:00 | |
Already tried this | 01/01/70 00:00 |