Hi Dave,

Tried the pause after each write command and now it's behaving even worse.

Hi Demon,

My last version I used wrote to bytes and not bits. Only got about 20 seconds (max) of record time. Was trying to extend it by writing to bits. I chose 29 bytes (about 24 seconds worth of recording) because I wanted to test the max out feature and was saving time by setting a lower limit. Once the code works, then I will increase the time.

As for the goto; you know, that is kind of redundant. It automatically does that with the while..wend loop. I must have done that for some other code in the past and just didn't think anything about it. I will correct that and see if it does anything.

I will fix the 29 bytes address, however, that should only be an issue when you max out the count, correct? If I only record for 3 seconds, I shouldn't get the playback I'm getting. Will fix that as well.

As for the 29 bytes and 100ms pauses; I'm trying to record inputs of varying lengths. The best way I know how is to test the inputs multiple times per second. That way if I press the left input or right input or both at varying lengths, it should be able to repeat that the left button was held for 7/10 of a second while the right was held for 9/10 of a second. 1/10 of a second come out to 8/10 of a second per byte. 29 bytes is 24 seconds. I will be increasing that time by increasing the bytes being used, however limited the time for testing purposes. That, at least, was my logic.

Tony