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?

I would try then to go back to 4.35 which I'm using at the moment to get around the foot pedal ignoring releases and presses. It might solve other problems in doing so, but it sounds like it isn't linked to Scribe to me.

Have you got other USB devices plugged in? I would unplug everything and try just the one pedal. It might be something like the power is being shut off to the USB port possibly. Replugging it back in then activates it?

To update you, I completely uninstalled all NCH software (which was just Scribe and Pedable) I cleaned the registry using CCleaner and ran the cleaner also. I manually removed the folders in both the Application Data folder and the Program Files folder. I had no traces of the software left. I then installed V4.35. It required to download piehid.exe which I allowed it to. I have had absolutely NO releases ignored AT ALL, nothing missed, not a beat! I have worked the rest of the day using 4.35 and it's been totally fine regarding pedal presses / releases. I am in no doubt in my mind that the code for the VEC Infinity USB 1 after version 4.35 is to blame entirely. Something also I should mention to rule out hardware. I changed the play buttons on the pedal while I had 5.01/5.03 installed to the left and right buttons (rewind / forward). It made no difference and releases and presses were still ignored. I am totally convinced 200% that the problem is the software code for the pedal after version 4.35. (4.35 working fine) Therefore, would it be possible for you to make a release whereby the pedal code of 4.35 is used, but the software keeps all the features of the newer versions. I particularly like the ability to change the time format under the to mmm:ss unstead of h:mm:s (or similar). Also the new auto-volume feature for quiet parts is quite useful! Please let me know your thoughts.

I will reinstall 4.35 and try (I think I did this before and the pedal worked fine, but I will do it again to make sure.) I've briefly tried the pedal with a few other software products, but the problem didn't occur, which would point to the pedal code of Scribe. However, I do like Scribe much better than anything else, so I'd love to be able to use the software without the ignored press/releases. Would it be possible to make a release with the old pedal code with the new features of 5.01/5.03 specifically for uses with the VEC USB1 foot pedal? Would this be possible, and take not too much time? Also, do you have any version available to download prior to 4.35? And even earlier?

Is there any news or update on this issue? I'm still getting some ignores, but not as much. I've uninstalled my firewall (Zonealarm) and anti-virus (AVG), disabled internet access of course, but it made no difference really. I don't know if it's down to the pedal or the program. I have the USB VEC 1 pedal. Any suggestions I could try?

Just look under the duration column? Maybe I've missed something, it seems really obvious???

Hi I'll try to provide as accurately as poss...(my machine is also a gaming machine, so pretty well spec'd) * What are your PC specs? (CPU, RAM, OS, etc.) MS Windows XP Professional 32-bit SP3 Intel Core 2 Quad Q6600 @ 2.40GHz 4.0GB Dual-Channel DDR2 @ 399MHz 5-6-6-18 MICRO-STAR INTERNATIONAL CO.,LTD MS-7514 (CPU 1) ATI Radeon HD 4800 Series 512MB ATI Radeon HD 4800 Series (ATI AIB) ATI Function Driver for High Definition Audio - ATI AA01 160GB Volume0 (SCSI) * Can you post all the diagnostic information from Options -> Controller -> "Controller setup wizard..." -> Next -> "Show plug and play controller diagnostics"? Plug and play controller diagnostics for Express Scribe v 5.01 (Windows 5.1): USB device Vendor ID: 0x045E Product ID: 0x00F1 Revision: 0x0002 Path: \\?\hid#vid_045e&pid_00f1&mi_01&col01#7&3588a6dc&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} Usage page: 12 Model data: Key: N/A USB device Vendor ID: 0x045E Product ID: 0x00F1 Revision: 0x0002 Path: \\?\hid#vid_045e&pid_00f1&mi_01&col03#7&3588a6dc&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030} Usage page: 12 Model data: Key: N/A USB device Vendor ID: 0x045E Product ID: 0x00F1 Revision: 0x0002 Path: \\?\hid#vid_045e&pid_00f1&mi_01&col04#7&3588a6dc&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030} Usage page: 1 Model data: Key: N/A USB device Vendor ID: 0x05F3 Product ID: 0x00FF Revision: 0x0100 Path: \\?\hid#vid_05f3&pid_00ff#6&108e319e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} Usage page: 12 Model data: Key: VECInfinityINUSB Company: VEC Model: Infinity IN-USB-1 / IN-USB-2 --- End --- * Does the problem only happen on pedal presses? Releases? Both? Both * Is the press / release ignored completely, or is there just a long delay before it's recognised? Completely ignored, no delay * Does the problem happen always / often / occasionally / rarely? Is there a particular sequence of events you can use to reproduce it? Often and regularly regardless * Does it matter how long the audio is? How many channels it has? How long it's been playing? No relation to any type of audio or length * Can you reproduce the problem using the keyboard short-cuts, system-wide hot-keys, or mouse clicks, or does it only happen when using foot pedals? Only problem with USB infinity foot pedal * What are your settings in Options -> Controller -> "Tap lock"? Normally tap lock unchecked, but it doesn't matter, presses still get ignored * What type of drive does your Options -> "Disk Usage" -> "Data folder" point to? Fixed (e.g. C:)? USB? Network shared? Fixed C: Two 7200 SATAII Hdds in RAID 0 setup * Does the Performance tab in Windows' Task Manager show high CPU usage when the problem happens? No. I also set the priorty of Scribe to high/low/normal in task manager and it makes no differences. Please let me know if you need more questions answered! I hope we can get this sorted out, then everything will be great!

Hi, Some of the foot presses are still being ignored. I would estimate about 30-40% (VEC Infinity USB1) Also, the hot keys don't seem to function exactly the same as pressing the forward/rewind button manually with the mouse. They seem to skew the audio until it reaches the point it's meant to, rather than a clear step. I wonder if there's a reason for this and if it could be looked into? Also I'm wondering when a newer version will be available, the foot presses is a really annoying problem. Kind regards MrP