NPhillips Posted June 3, 2003 Report Posted June 3, 2003 One should not have to wait for [go previous] to complete. As it stands, keying [go previous] runs the memory previous but one can [go previous] again, and again, and again as would could go forward with [GO]. Additionally, I believe [go previous] should go in reverse rather than to what was actually previous as it is more useful when programming a show. Now one is constantly keying [memory][x][GO] rather than being able to just hit [go previous] however many times is necessary. This also means the functionality needs to exists allowing a user to go to a memory in time or cut to that memory... override only does so much with a 60 second fade... Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.