Hi, I'm developing a Java3D application that also uses speech synthesis. Java3D, as you all know, is pretty cpu intensive, the speech synthesis not so much. Unfortunately, during periods of significant 3D activity, the speech is delayed, paused and can become stuttering.
I have tried playing around with the relative threads - even though the speech engine itself is a native application and more difficult for me to control. Anyway, I wasn't able to get any satisfactory results.
However, quite by chance I discovered that the performance is significantly improved if I use 'javaw' to run my application rather than 'java'. I wouldn't say the problems are totally erradicated but the pauses, stutters and delays are certainly much reduced. The difference is very, very noticeable.
I have no idea why this should be the case. My understanding is that the only difference between 'javaw' and 'java' is that the latter runs with a console. Since, I am not writing anything out to the console, I cannot see why there should be any difference at all. Maybe java keeps open a thread, I/O channels, I just don't know. There is certainly something different and my application is sensitive to it.
I have tried this on two different computers (3GHz, 1.5Gb memory desktop and a 1.2GHz, 512Mb laptop) and it's the same on both machines: 'javaw' gives consistently better speech results than 'java.
If anyone can shed any light on this, I would warmly welcome an explanation. I am mystified.
-Paul
=========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA3D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".