You have probably already done so, but there is a way to tell JAWS to use a
specific soundcard under Utilities | Soundcard.
Bill
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On
Behalf Of DJX
Sent: Thursday, April 27, 2017 2:12 PM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: MAGIX low latency driver
Hi Phil, yes I did uncheck the boxes in samplitude, went into settings for
the MAGIX driver, advanced, and uncheck the box for the onboard sound card.
I also made sure that it wasn't selected anywhere in sonar, which it isn't.
Still, when sonar starts up, it speaks the name of the MAGIX Low Latency
Driver 2016, and away goes jaws speech.
Regards, DJX
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Phil Muir
Sent: Thursday, April 27, 2017 9:16 AM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: MAGIX low latency driver
Hmm, not sure that you understood what I posted. You need to specifically
select the Magix Low latency driver and go into it's control panel and
disable all options under advanced options. Also before you go into
advanced options make sure you disable all checkboxes in the treeview.
_____
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On
Behalf Of DJX
Sent: 27 April 2017 13:42
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: MAGIX low latency driver
Phil, I did exactly that yesterday before posting my question, but the
driver still shuts off jaws speech when sonar starts up, despite the fact
that I unchecked the onboard card in the advanced options. The client's
interface is selected in sonar and only its drivers are check, as ASIO
drivers can only use 1 device at a time.
Regards, DJX
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Phil Muir
Sent: Thursday, April 27, 2017 3:57 AM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: MAGIX low latency driver
Yes indeed. The Magix Low Latency driver is indeed wrapping all other audio
drivers. The fix for this is easy enough. Choose the Magix low latency
driver. Open its control panel. Hit the advanced button and unselect any
check boxes in there. Then in Sonar unselect any other drivers and double
check that the input and output drivers for your soundcard (not the Magix
Low Latency driver) are checked then hit the apply button in Sonar. Go back
into audio options in Sonar and double check that everything you want to be
selected is. When Sonar starts up again it may report a message about the
Magix Low Latency driver but it won't be selected.
_____
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On
Behalf Of DJX
Sent: 27 April 2017 01:16
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: MAGIX low latency driver
The client has the scripts and inz file installed, so that's not the issue.
The issue is the driver stealing the outputs for the default sound card,
which makes jaws speech shut off. The issue I believe has to do with the
fact that jaws speech as most tts synths do runs at 32khz, while the card
and the drivers run at 48khz. If the driver puts the onboard card in
exclusive mode, that means jaws has no way of requesting a buffer at 32k for
the card, which results in no speech, though jaws works fine and windows
sounds and all come through fine. To further support my theory/hypothesis,
the ct sounds come through fine when running sonar, it's just speech that
doesn't work.
I should try this, experiment with Microsoft sapi5, though I think the
highest rate for those is also 32k.
The search/mystery continues! ;)
Regards, X
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On
Behalf Of James Malone
Sent: Wednesday, April 26, 2017 8:08 PM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: MAGIX low latency driver
I would have to agree. There has been talk on the VIP list about this
problem of the MAGIX low latency driver, but can't remember if a INS file
was needed or not. Jim
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Joey Stuckey
Sent: Wednesday, April 26, 2017 4:05 PM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: MAGIX low latency driver
I can't remember seeing that driver on the X2, but, Phil is probably the guy
to ask.
J
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On
Behalf Of DJX
Sent: Wednesday, April 26, 2017 7:04 PM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: MAGIX low latency driver
Thanks for the confirmation. Have you heard of any workarounds?
Does x2 have a Low Latency ASIO driver as well? I don't remember if it did
from the few times I installed it on customer's systems.
Thanks, DJX
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Joey Stuckey
Sent: Wednesday, April 26, 2017 7:00 PM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: MAGIX low latency driver
I have heard about this being a problem with 3X. I have 2X and have no
problems so far.
Joey
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On
Behalf Of DJX
Sent: Wednesday, April 26, 2017 6:54 PM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] MAGIX low latency driver
Hi list, I realize this question might be a bit off topic, as it's not CT
related, but I figured some of you might benefit from any forthcoming
replies.
I'm working on a customer's system who had both SONAR and Samplitude x3
installed on Windows 7.
It so happens that any time the MAGIX low latency ASIO driver is used, it
steals the default sound card's output, thereby eliminating speech. This
also happens whenever sonar opens and scans the list of ASIO devices. Short
of removing the driver from the registry, do Phil or Steve, or any other
Samplitude user have a workaround for this problem? Or perhaps you guys
haven't encountered it? I ran the ASIO control panel for the MAGIX drivers,
and under advanced unchecked the sound card, but it still kills jaws speech
any time the driver is activated or scanned.
This losing speech also happens when opening the samplitude options, while
the MAGIX low latency driver is selected.
Any ideas on how to solve it? I know I can do it through the registry, but
I'd like to keep that as last resort.
Thanks, DJX
