KnowBrainer Speech Recognition
Decrease font size
Increase font size
Topic Title: MS Word 2007 causing DNS to freeze PART 2
Topic Summary: Dragon Log
Created On: 06/28/2012 06:33 PM
Status: Post and Reply
Linear : Threading : Single : Branch
 MS Word 2007 causing DNS to freeze PART 2   - drbhomer - 06/28/2012 06:33 PM  
 MS Word 2007 causing DNS to freeze PART 2   - Chucker - 06/28/2012 08:58 PM  
 MS Word 2007 causing DNS to freeze PART 2   - massdoc - 06/29/2012 12:01 AM  
 MS Word 2007 causing DNS to freeze PART 2   - Chucker - 06/29/2012 10:36 AM  
 MS Word 2007 causing DNS to freeze PART 2   - massdoc - 06/29/2012 02:20 PM  
 MS Word 2007 causing DNS to freeze PART 2   - massdoc - 06/29/2012 09:34 PM  
 MS Word 2007 causing DNS to freeze PART 2   - Chucker - 07/01/2012 10:25 AM  
 MS Word 2007 causing DNS to freeze PART 2   - massdoc - 07/01/2012 07:42 PM  
 MS Word 2007 causing DNS to freeze PART 2   - Chucker - 07/02/2012 12:03 PM  
 MS Word 2007 causing DNS to freeze PART 2   - massdoc - 07/02/2012 08:38 PM  
 MS Word 2007 causing DNS to freeze PART 2   - massdoc - 07/06/2012 01:30 AM  
 MS Word 2007 causing DNS to freeze PART 2   - R. Wilke - 07/06/2012 04:22 PM  
 MS Word 2007 causing DNS to freeze PART 2   - massdoc - 07/08/2012 03:20 PM  
 MS Word 2007 causing DNS to freeze PART 2   - R. Wilke - 07/08/2012 03:49 PM  
 MS Word 2007 causing DNS to freeze PART 2   - massdoc - 07/08/2012 04:13 PM  
 MS Word 2007 causing DNS to freeze PART 2   - R. Wilke - 07/08/2012 04:23 PM  
 MS Word 2007 causing DNS to freeze PART 2   - massdoc - 07/12/2012 01:51 PM  
Keyword
 06/28/2012 06:33 PM
User is offline View Users Profile Print this message


drbhomer
Junior Member

Posts: 35
Joined: 12/14/2006

Please see attached Log



Dragon5.log
Dragon5.log  (978 KB)

 06/28/2012 08:58 PM
User is offline View Users Profile Print this message

Author Icon
Chucker
Top-Tier Member

Posts: 9671
Joined: 10/10/2006

Brian,

First, keep in mind that it is best to keep all your posts relating to a particular topic in the same collection of threads. Creating a new post only tends to confuse those who have not read your initial post.

Second, I would check with your vendor from whom you purchase DMPE because there is a more current update (11.00.304.530) that has a couple of bug fixes in it.

Third, in looking over your Dragon log, you either have corruption in your program files, mycmds.dat (custom commands), or you have a corrupted user profile. In your case specifically it appears that Dragon is the cause of your problem with Microsoft Word, which is unusual because it usually the other way around.

The first thing that I would try is either running a Repair of DMPE and see if that fixes the problem or get the update and install it will accomplish exactly the same thing.

If that doesn't fix the problem, then I would try creating a new user, skip training import your custom words using the standard "Import list of words and phrases..." Method because it is highly possible that your vocabulary is corrupted and that is what has corrupted your user profile, if in fact your user profile is corrupted, which it may not be. That's why running a Repair first or downloading and installing the update is what you should try first.

If you have created your own custom commands, I would export them and then import them into your new user profile, if you have to create such.

Your Dragon log shows a major crash that is specifically related to program files that manages your custom commands. While there are a couple of other issues that may be related, my guess is that you may have a corrupted user profile.

Let us know if any of these suggestions fix your problem. If you still continue to have the same problem after doing any or all of the above, then you might want to run a repair of Microsoft Office 2007, or uninstall and reinstall Microsoft Office 2000. Don't worry about your data your Outlook files if you are using Microsoft Outlook because uninstalling and reinstalling Microsoft Office does not lose any of your data.

Chuck

If anything can go wrong it will, and at the worst possible moment. - Murphy's Law

-------------------------

 06/29/2012 12:01 AM
User is offline View Users Profile Print this message


massdoc
New Member

Posts: 16
Joined: 01/06/2012

Originally posted by: Chucker Second, I would check with your vendor from whom you purchase DMPE because there is a more current update (11.00.304.530) that has a couple of bug fixes in it.

I hadn't heard this. Would it solve the latency issues with the correction box? I purchased DMPE (11.00.300.312) from KB. How do I get this?



 06/29/2012 10:36 AM
User is offline View Users Profile Print this message

Author Icon
Chucker
Top-Tier Member

Posts: 9671
Joined: 10/10/2006

Brian,

I didn't look at all of the release notes for the update, but the delay in the correction (Spelling Window or Correction menu) box displaying or functioning is not a bug. It generally is a system configuration issue (i.e., slower processor, less RAM then optimal, too many applications running simultaneously, etc., yada yada yada). For example, I have one system configured with DMPE 11.00.304.530, but before that I had the earlier release that you're currently using. I never had a problem with latency with any aspect of dictating using that version. Then again, I'm running it on a Toshiba Satellite laptop with a Core™ i7 2670QM 2.3 GHz second-generation Sandy Bridge processor with 8 GB of RAM, 6 MB of L3 cache and running under Windows 7 64-bit. In short, I'm driving a sports car with a good bit of horsepower, while you're driving a Volkswagen beetle. The problem with your experiencing latency under any condition is more your hardware configuration than anything else. Try moving the Speed vs. Accuracy slider all the way to the left (Fastest Response) and make sure that the "Pause required before commands" is not set to more than 300 ms (i.e., three tick marks from the left).

Regardless, to answer your question specifically, it is unlikely that the update will change anything as far as latency with the Correction menu or Spelling Window because Nuance development has tested and is unable to duplicate the problem on any of their systems

Chuck

Be careful what you wish for. You may find that what you get is not what you expect, or what you want. - Aesop (620 BC - 700 BC modern interpretation)



-------------------------



 06/29/2012 02:20 PM
User is offline View Users Profile Print this message


massdoc
New Member

Posts: 16
Joined: 01/06/2012

Thanks Chuck,

I'm running 64-bit Win7 with an i7 920 CPU with 12 GB RAM on Asus Rampage II GENE Mobo. Speed v. accuracy is fully to the left and pause before commands is 1-1/2 lines from the left. I use Word 2010 64-bit and AVG free antivirus. This is so frustrating

Bill



 06/29/2012 09:34 PM
User is offline View Users Profile Print this message


massdoc
New Member

Posts: 16
Joined: 01/06/2012

Chuck,

I just wanted to clarify what I meant by prolonged latency with the correction box. When I say "correct that," the box appears without latency. However, when I spell the word in the box, there is about a 10 second delay before the letters appear in the correction box.

Bill
 07/01/2012 10:25 AM
User is offline View Users Profile Print this message

Author Icon
Chucker
Top-Tier Member

Posts: 9671
Joined: 10/10/2006

Thanks for the clarification. However, I knew already that that was what was occurring because others who have installed DMPE were having the same problem. I just never experienced that. DMPE, even the version that you have installed, never gave me a problem with the Spelling window as far as any latency problems were concerned.

I know that your hardware is ample for running DMPE, but my guess is that there some kind of software or hardware interaction that's causing the latency. Why don't you attach a copy of your Dragon log as Brian did above? We may be able to track it down that way.

Chuck

"Many of the things you can count, don't count. Many of the things you can't count, really count." Albert Einstein

-------------------------

 07/01/2012 07:42 PM
User is offline View Users Profile Print this message


massdoc
New Member

Posts: 16
Joined: 01/06/2012

To attach a log, do I do so immediately after a latency occurs with correction or does it not matter?

 07/02/2012 12:03 PM
User is offline View Users Profile Print this message

Author Icon
Chucker
Top-Tier Member

Posts: 9671
Joined: 10/10/2006

massdoc,

your Dragon log is a continual record of all the activity. If you look at the location where your Dragon log is stored, you may see both the Dragon log and its backup. If you have the backup log (Dragon.bak.log), attach both the Dragon.bak.log and the Dragon.log files. There is no need to wait because any information pertinent to the latency issue will show up in one or the other of those logs.

Chuck

"If the automobile had followed the same development cycle as the computer, a Rolls-Royce would today cost $100, get a million miles per gallon, and explode once a year, killing everyone inside." -- Robert X. Cringely

-------------------------

 07/02/2012 08:38 PM
User is offline View Users Profile Print this message


massdoc
New Member

Posts: 16
Joined: 01/06/2012

Hope I did this correctly.

 07/06/2012 01:30 AM
User is offline View Users Profile Print this message


massdoc
New Member

Posts: 16
Joined: 01/06/2012

Chuck, can you or anyone else discern anything from my Dragon logs? Thanks.

 07/06/2012 04:22 PM
User is offline View Users Profile Print this message

Author Icon
R. Wilke
Top-Tier Member

Posts: 4391
Joined: 03/04/2007

Originally posted by: massdoc Chuck, can you or anyone else discern anything from my Dragon logs? Thanks.

 

It seems like Chuck is missing in action, as ofttimes before after asking users to submit their log file.

However, it isn't really necessary to provide the entire log files, just like you mentioned before, the most critical point being where the problem occurs. Therefore, in order to make it easier for us, just delete the current one which in turn will result in Dragon creating a new one, and use it until the problem occurs, and then take a copy of it immediately afterwards thus showing the scenario right at the end of it, which will make it easier to determine what it is really.

Then post it and we will see what we can do.

Rüdiger



-------------------------

Well, it's past the point where we can make any changes in the code, but we can still make changes to the Easter Egg!



 07/08/2012 03:20 PM
User is offline View Users Profile Print this message


massdoc
New Member

Posts: 16
Joined: 01/06/2012

Thanks, Rudiger,

I did as you suggested and have attached a truncated log. There was a prolonged latency with correction near the end. These latencies usually range 5-10 seconds and are frustrating when making many corrections. I hope you or someone can spot some cause.



Dragon6.log
Dragon6.log  (14 KB)



 07/08/2012 03:49 PM
User is offline View Users Profile Print this message

Author Icon
R. Wilke
Top-Tier Member

Posts: 4391
Joined: 03/04/2007

Massdoc,

so here is the scenario you are referring to:

' that's the correction command probably below
15:06:03 SigQual[ uD 1032 | Nd 0 | sN 35 | cD 270 | wF 0x00 | aF 0x00 | dA 0.0 [25639] | sA 18.7 [25639] | Rt C ]
15:06:03 [x64] (SDK-redirection) Connected to ActiveServices from IL=2 PID=0x734
15:06:11 Info: aborting recognition, mic abort
15:06:11 [x64] (SDK-redirection) Connected to ActiveServices from IL=2 PID=0x734
' that's when merging the acoustic archive starts
15:06:11 LOG (VBar) Begin mergeAcOptArchives
15:06:11 ACO: Info: ClsNISTWavFilepen(, mode=32) successful.
15:06:11 ACO: Info: ClsNISTWavFile::close()
15:06:11 ACO: Info: ClsNISTWavFilepen(, mode=32) successful.
' leaving out about 20 lines of the log file now
' ...

' here is when it comes to an end
15:06:50 ACO: Info: ClsNISTWavFile::close()
15:06:50 LOG (VBar) End mergeAcOptArchives
15:06:50 LOG (Perf): Merge acoustic archive = 38420 msec
' the entire process took almost 39 seconds, started at 15:06:11, finished at 15:06:50,
' so the counting was correct


I admit I couldn't tell you why it is taking so long, but the question is, how do you actually correct, via voice command, or via keyboard input. Otherwise, you might as well turn off storing corrections in archive, under "Tools - Options - Data", and removing the checkmark accordingly, although this would be kind of radical. On the other hand, the only purpose in storing to archive is to collect data for running the optimizers on, to further adapt you acoustic model, and if you don't do it, or have done already to some amount, it really isn't so much necessary. I would just give it try.

Rüdiger



-------------------------

Well, it's past the point where we can make any changes in the code, but we can still make changes to the Easter Egg!



 07/08/2012 04:13 PM
User is offline View Users Profile Print this message


massdoc
New Member

Posts: 16
Joined: 01/06/2012

Thank you for your quick reply. I use voice command for corrections because I am quadriplegic and using the keyboard is arduous. Would removing the check mark affect this?

 07/08/2012 04:23 PM
User is offline View Users Profile Print this message

Author Icon
R. Wilke
Top-Tier Member

Posts: 4391
Joined: 03/04/2007

You are always good to go using voice commands in order to correct, using the keyboard would interfere immensely instead. I would just try removing the check mark as described in order to determine whether latencies would disappear.

-------------------------

Well, it's past the point where we can make any changes in the code, but we can still make changes to the Easter Egg!

 07/12/2012 01:51 PM
User is offline View Users Profile Print this message


massdoc
New Member

Posts: 16
Joined: 01/06/2012

Unfortunately, that did not help.

Statistics
27371 users are registered to the KnowBrainer Speech Recognition forum.
There are currently 0 users logged in.
The most users ever online was 2028 on 04/05/2013 at 07:36 PM.
There are currently 335 guests browsing this forum, which makes a total of 335 users using this forum.

FuseTalk Standard Edition v4.0 - © 1999-2013 FuseTalk™ Inc. All rights reserved.