There is a way to fix this without any registry hacks.
-----Original Message-----
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On
Behalf Of DJX
Sent: 27 April 2017 03:18
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: MAGIX low latency driver
No, it's what it usually does when opening, checks for all connected devices
(virtual or physical.
I had a feeling that the registry hack would be my only real choice, thanks
for confirming.
I figured I'd ask those of you who have been using the program, just in case
there was some hidden option I missed or a utility that MAGIX had made
available to you guys or something.
I guess I'll make a reg file for the client that he can run/import to remove
the entries, just in case MAGIX ever add the driver back in to the registry
through an update.
Thanks, DJX
-----Original Message-----
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Chris Smart
Sent: Wednesday, April 26, 2017 10:14 PM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: MAGIX low latency driver
Oh sorry! Ok, and there's no way to tell Sonar not to scan at start up?
I'm thinking you'll have to go the registry route then.
At 10:06 PM 4/26/2017, you wrote:
That would work, but the issue we are discussing is that jaws losesspeech.
speech when running sonar because of the low latency driver.
Getting around the issue inside of samplitude is no problem, but the
problem is when sonar scans the device list at startup, the low latency
driver is activated and thus takes over the sound card.
HTH, DJX
-----Original Message-----
From: ddots-l-bounce@xxxxxxxxxxxxx
[mailto:ddots-l-bounce@xxxxxxxxxxxxx] On Behalf Of Chris Smart
Sent: Wednesday, April 26, 2017 10:02 PM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: MAGIX low latency driver
Switch Jaws to something else, such as your better audio interface.
In my case, this was my Focusrite interface. Go into Samplitude. Tell
Samplitude to use that better interface, i.e. switch it from using the
Magix Low Latency driver. Now, switch Jaws back to your cheaper output,
motherboard sound, etc.
I did this a few months ago when installing X3, so I apologize if I
have that slightly incorrect.
the idea is: 1. switch Jaws to better interface.
2. Tell Samplitude to use your better interface, not the Magix driver.
3. Switch Jaws back to your cheaper output that you're using for
Windows Sounds etc.
At 08:08 PM 4/26/2017, you wrote:
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:
<mailto:ddots-l-bounce@xxxxxxxxxxxxx>ddots-l-bounce@xxxxxxxxxxxxx
[mailto:ddots-l-bounce@xxxxxxxxxxxxx] On Behalf Of DJX
Sent: Wednesday, April 26, 2017 7:04 PM
To: <mailto:ddots-l@xxxxxxxxxxxxx>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:
<mailto:ddots-l-bounce@xxxxxxxxxxxxx>ddots-l-bounce@xxxxxxxxxxxxx
[mailto:ddots-l-bounce@xxxxxxxxxxxxx] On Behalf Of Joey Stuckey
Sent: Wednesday, April 26, 2017 7:00 PM
To: <mailto:ddots-l@xxxxxxxxxxxxx>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:
<mailto:ddots-l-bounce@xxxxxxxxxxxxx>ddots-l-bounce@xxxxxxxxxxxxx
[mailto:ddots-l-bounce@xxxxxxxxxxxxx] On Behalf Of DJX
Sent: Wednesday, April 26, 2017 6:54 PM
To: <mailto:ddots-l@xxxxxxxxxxxxx>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
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
----------------------------------------
"There are two means of refuge from the miseries of life: music and
cats." - Albert Schweitzer
PLEASE READ THIS FOOTER AT LEAST ONCE!
To leave the list, click on the immediately following link:
ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe
If this link doesn't work then send a message to:
ddots-l-request@xxxxxxxxxxxxx
and in the Subject line type
unsubscribe
For other list commands such as vacation mode, click on the immediately
following link:
ddots-l-request@xxxxxxxxxxxxx?subject=faq or send a message, to
ddots-l-request@xxxxxxxxxxxxx and in the Subject line type faq
PLEASE READ THIS FOOTER AT LEAST ONCE!
To leave the list, click on the immediately following link:
ddots-l-request@xxxxxxxxxxxxx?subjectsubscribe
If this link doesn't work then send a message to:
ddots-l-request@xxxxxxxxxxxxx
and in the Subject line type
unsubscribe
For other list commands such as vacation mode, click on the immediately
following link:
ddots-l-request@xxxxxxxxxxxxx?subjectúq or send a message, to
ddots-l-request@xxxxxxxxxxxxx and in the Subject line type faq