MrP

If you go into the options it's on the first page. Auto backstep on stop (ms). Mine's set normally set about 300ms, just set it to 0 if you need to. If it's rewinding while you're pressing a button then simply make sure you check all your key assignments for the foot pedal in the options, and the hotkeys.

Has already been answered here in the support documentation: http://www.nch.com.au/scribe/kb/1283.html

Has already been answered here in the support documentation: http://www.nch.com.au/scribe/kb/1283.html

They might be corrupt, can you re-download them or get a fresh copy of them? If they don't play in other softwares then they're probably corrupt.

Have you managed to find anything and can you give an update?

Sounds very promising! I eagerly await your update...

Yes, it gives me this for the play button: RD 00 02 00 RD 00 00 00 This for the rewind or right button: RD 00 04 00 RD 00 00 00 This for the fast forward or left button: RD 00 01 00 RD 00 00 00 And also shown in the top box is: Microsoft Wireless Desktop Receiver 1.3A and it's shown five times. I've also gone back to the 4.35 version of scribe. I'm not sure how old the pedals are, maybe 3 to 5 years? I really don't know.

So to follow up: I've got a new hdd (SSD Kingston 64GB), and I'm now running Windows 7 32bit and Office 2010. (A completely fresh rebuild, all new programs install etc, not a copy of an image or anything like that). Still the same thing happens, and it also happens if I change the play button to different physical buttons on the foot pedal, although it happens much more with the middle (normal) play button. I'm very hestitant of going out and buying a new foot controller to solve the problem, as I don't think this is it. Given that it works no problem with version 4.35 of Scribe, I think it's much more to do with the code as I've changed pretty much everything else. Would you be willing to revisit the coding of the pedal (particularly it's the VEC USB 1)? There defintely was something wrong with the coding in the first changes because of the new version releases fixed the problem to an extent, but it's still happening. I would be extremely grateful if you would revisit the coding - there's nothing else available on the market that really matches Scribe

I haven't tried excessively whilst not running Office 2007. So I can't really say for sure. I've just ordered an SSD, I will go from XP to Win 7 and from Office 2007 to 2010, on a completely clean and fresh install. If this solves the intermittant problem then we will know it's an interaction problem somewhere on my system. It might be within Office or XP or both. I don't have many other programmes running. I tried it without AV and firewall etc, no difference. I'll post back after my upgrade to report. Another possiblity is that my pedal and its firmware doesn't like the new code, whereas other firmwares are okay with it? That's just popped into my head from what you've just said.

No I don't have access to one to test, but I was thinking of buying the VEC-2 version, BUT A) I'm not sure if mechanically it's any different? When I use 4.35 or earlier before the code was changed, I have no problems at all, which means it can only be software coding. I am thinking maybe it is an interaction problem with other software, such as office 2007? Did you test it standalone or with other software running? Or it may be something to do with Windows XP, although my system has the latest updates installed. Mostly when I first boot the machine and start working on a document it might be okay for the first five minutes or so, but then it'll creep in and happen more often. I am thinking of upgrading soon to Windows 7, and buying a SSD to do the job. So obvously a fully fresh install. I do appreciate all your help and effort it trying to help me

As an update, the problem happens signficantly less if the tap lock feature is used, and then unlock timeout is applied. Although it does still happen, but only very occasoinally compared to if the tap lock is not used at all. Edit: Actually, cancel that, it's progressively got worse, so in fact no difference.

Also I thought; how long are you testing for and what OS do you use? And what pedals?

It's after a random period of time, but as it starts to happen it seems to get worse and more apparent. For instance on one piece of audio it was after nearly five minutes, and then it would happen about 70 percent of the presses thereafter. On another piece it would happen after a few seconds, and then continue, again about 70 percent of the time. It might have something to do with the way memory is used? I don't know? Is it not possible to release the old pedal code for the newer software? The old pedal code just works, whereas the new one doesn't very well. I don't know why it changed because the pedals haven't, or not that I can see? I'm going along fine with 4.35 at the moment, but I really want to use 5.04 or the later release in the future.

Hi, Just to say I've tried 5.04 and presses and releases are still quite often ignored, obviously it's very frustrating! I've had to revert back again to 4.35. I like the addtional features of the time formatting and the audio compression adjustment in the later releases, could we see a new version with the old pedal code that worked perfectly? Pretty please? I don't know why it needed to be changed, because now it doesn't work. I've spoke to other people and we all have the same problem. The problem creeps in after a period of time and then becomes really obvious and puts you off your work.

Hi, There's a 5.04 but the release notes haven't been updated, could we know what's changed in the latest version please?