cue audio (headphones) crashes using 2 soundcards with asio4all on win7 64bit

Bug #732977 reported by jkone27 on 2011-03-11
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Mixxx
Critical
Bill Good

Bug Description

when i activate the cue (headphones) button, everything goes fine till at a certain moment, the sound starts sparkling and cracking, looks like the audio buffer reaches its limit and crashes. after a while the sounds get back good in hadphones but with a huge delay (like half a second maybe or something like that) so you're not able anymore to mixxx your tracks easilly.

luckily the master output goes fine instead (no sparkling at all)!! :) so people when i play don't get it :D

i have also problems using BCD3000 native asio drivers. they don't seem to work with mixxx on windows7 64bit

cheers from italy

jkone27 (jkone27) wrote :

forgot PC specs, sorry! Toshiba Qosmio

Screen 15.6 inch WXGA HD LED Backlight TruBrite (1366 x 768)
Processor Intel Core i5-430M (2.26 GHz)
RAM Installed (Max) 4GB DDR3 1066MHz (8GB), 2 slots
Storage Space 500 GB at 5400 rpm
Graphics Card Nvidia Geforce GT 330M 1GB GDDR5 dedicated 2.3 GB TurboCache
Optical Drive Blu-ray/HD DVD burner
Audio System 2 speakers Harman Kardon
Webcam 1.3 Megapixels with microphone
Network Wi-Fi b / g / n + Gigabit Ethernet
Bluetooth Yes, Bluetooth 2.1 + EDR
Card Reader 5 in 1
Output (s) video HDMI, VGA
Fingerprint Reader Non
Input (s) / Output (s) S / PDIF / Headphone, Microphone
ExpressCard Non
Firewire Non
USB 4 USB 2.0 including 1 e-SATA combo
Operating System 7 Windows Home Premium 64 bit

For the ASIO driver problem, you'll need a 64-bit ASIO driver if you're using the 64-bit version of Mixxx. Otherwise, I *think* using the 32-bit version of Mixxx with a 32-bit ASIO driver will also work on a 64-bit OS.

i already have a 64 bit version of BCD3000 driver but it doesn't seem to work
good. maybe it's a driver problem, anyone has tested BCD3000 asio driver on
window 7 64 bit?

thanks

Giacomo
For the ASIO driver problem, you'll need a 64-bit ASIO driver if you're
using the 64-bit version of Mixxx. Otherwise, I *think* using the 32-bit
version of Mixxx with a 32-bit ASIO driver will also work on a 64-bit
OS.

--
You received this bug notification because you are a direct subscriber
of the bug.
https://bugs.launchpad.net/bugs/732977

Title:
  cue audio (headphones) crashes using 2 soundcards with asio4all on
  win7 64bit

Status in Mixxx:
  New

Bug description:
  when i activate the cue (headphones) button, everything goes fine till
  at a certain moment, the sound starts sparkling and cracking, looks
  like the audio buffer reaches its limit and crashes. after a while the
  sounds get back good in hadphones but with a huge delay (like half a
  second maybe or something like that) so you're not able anymore to
  mixxx your tracks easilly.

  luckily the master output goes fine instead (no sparkling at all)!! :)
  so people when i play don't get it :D

  i have also problems using BCD3000 native asio drivers. they don't seem to
work with mixxx on windows7 64bit

  cheers from italy

To unsubscribe from this bug, go to:
https://bugs.launchpad.net/mixxx/+bug/732977/+subscribe

________________________________

Da: Sean M. Pappalardo <email address hidden>
A: <email address hidden>
Inviato: Ven 11 marzo 2011, 06:07:53
Oggetto: [Bug 732977] Re: cue audio (headphones) crashes using 2 soundcards with
asio4all on win7 64bit

It's my understanding that ASIO (and PortAudio using ASIO) only supports
opening one sound device at a time. I'm not sure why it's even letting you
start two devices, but that may explain why it's dying. Since you're using
Win7, can you try using WASAPI and see if that causes the same issue?

On Thursday, March 10, 2011 18:25:56 you wrote:
> Public bug reported:
>
> when i activate the cue (headphones) button, everything goes fine till
> at a certain moment, the sound starts sparkling and cracking, looks like
> the audio buffer reaches its limit and crashes. after a while the sounds
> get back good in hadphones but with a huge delay (like half a second
> maybe or something like that) so you're not able anymore to mixxx your
> tracks easilly.
>
> luckily the master output goes fine instead (no sparkling at all)!! :)
> so people when i play don't get it :D
>
>
> i have also problems using BCD3000 native asio drivers. they don't seem to
> work with mixxx on windows7 64bit
>
> cheers from italy
>
> ** Affects: mixxx
> Importance: Undecided
> Status: New

jkone27 (jkone27) wrote :

i'm quite used using it with mutiple sound devices...

http://www.asio4all.com/

was i doing something wrong? i mean that's the power of asio for all i think,
isn't it?

if i use it on single devices usually double stereo channels becomes un-usable
(at least for me),
so if i want to split headphones and master, i cant do that,
wheras i could do that with native ASIO drivers, like behringer for BCD3000 but
it's not working for me anymore on win7 64bit (even if i have the right drivers
installed)

________________________________
Da: Bill Good <email address hidden>
A: <email address hidden>
Inviato: Ven 11 marzo 2011, 18:59:53
Oggetto: Re: [Bug 732977] [NEW] cue audio (headphones) crashes using 2
soundcards with asio4all on win7 64bit

It's my understanding that ASIO (and PortAudio using ASIO) only supports
opening one sound device at a time. I'm not sure why it's even letting you
start two devices, but that may explain why it's dying. Since you're using
Win7, can you try using WASAPI and see if that causes the same issue?

On Thursday, March 10, 2011 18:25:56 you wrote:
> Public bug reported:
>
> when i activate the cue (headphones) button, everything goes fine till
> at a certain moment, the sound starts sparkling and cracking, looks like
> the audio buffer reaches its limit and crashes. after a while the sounds
> get back good in hadphones but with a huge delay (like half a second
> maybe or something like that) so you're not able anymore to mixxx your
> tracks easilly.
>
> luckily the master output goes fine instead (no sparkling at all)!! :)
> so people when i play don't get it :D
>
>
> i have also problems using BCD3000 native asio drivers. they don't seem to
> work with mixxx on windows7 64bit
>
> cheers from italy
>
> ** Affects: mixxx
> Importance: Undecided
> Status: New

--
You received this bug notification because you are a direct subscriber
of the bug.
https://bugs.launchpad.net/bugs/732977

Title:
  cue audio (headphones) crashes using 2 soundcards with asio4all on
  win7 64bit

Status in Mixxx:
  New

Bug description:
  when i activate the cue (headphones) button, everything goes fine till
  at a certain moment, the sound starts sparkling and cracking, looks
  like the audio buffer reaches its limit and crashes. after a while the
  sounds get back good in hadphones but with a huge delay (like half a
  second maybe or something like that) so you're not able anymore to
  mixxx your tracks easilly.

  luckily the master output goes fine instead (no sparkling at all)!! :)
  so people when i play don't get it :D

  i have also problems using BCD3000 native asio drivers. they don't seem to
work with mixxx on windows7 64bit

  cheers from italy

To unsubscribe from this bug, go to:
https://bugs.launchpad.net/mixxx/+bug/732977/+subscribe

jkone27 (jkone27) wrote :

sorry for my low-level knowledge, but i don't know much about wasapi,
do they work on audio latency like asio drivers?

i only found this on the web about wasapi, but it's not very useful for me

http://msdn.microsoft.com/en-us/library/dd371455(v=vs.85).aspx

Bill Good (bkgood) wrote :

According to http://portaudio.com/trac/ticket/76 PortAudio (the library we use to interface with sound hardware) only supports one ASIO device at a time. Like I said, really not sure why you're able to open 2, might be a PortAudio bug (or maybe they've made progress on that ticket and the fix just isn't totally working yet, who knows).

I know WASAPI has both an exclusive and shared (mixed) mode. I'd imagine the shared mode is higher latency than the exclusive mode (which is practically equivalent to ASIO) and I don't know how to distinguish between the two modes in software, but I've always gotten very low latency with WASAPI in Mixxx and I know Sean (one of our Windows guys) recommends WASAPI.

thank you so much! i will try and report my results

best

Giacomo

________________________________
Da: Bill Good <email address hidden>
A: <email address hidden>
Inviato: Sab 12 marzo 2011, 13:52:19
Oggetto: [Bug 732977] Re: cue audio (headphones) crashes using 2 soundcards with
asio4all on win7 64bit

According to http://portaudio.com/trac/ticket/76 PortAudio (the library
we use to interface with sound hardware) only supports one ASIO device
at a time. Like I said, really not sure why you're able to open 2, might
be a PortAudio bug (or maybe they've made progress on that ticket and
the fix just isn't totally working yet, who knows).

I know WASAPI has both an exclusive and shared (mixed) mode. I'd imagine
the shared mode is higher latency than the exclusive mode (which is
practically equivalent to ASIO) and I don't know how to distinguish
between the two modes in software, but I've always gotten very low
latency with WASAPI in Mixxx and I know Sean (one of our Windows guys)
recommends WASAPI.

** Bug watch added: portaudio.com/trac/ #76
  http://portaudio.com/trac/ticket/76

--
You received this bug notification because you are a direct subscriber
of the bug.
https://bugs.launchpad.net/bugs/732977

Title:
  cue audio (headphones) crashes using 2 soundcards with asio4all on
  win7 64bit

Status in Mixxx:
  New

Bug description:
  when i activate the cue (headphones) button, everything goes fine till
  at a certain moment, the sound starts sparkling and cracking, looks
  like the audio buffer reaches its limit and crashes. after a while the
  sounds get back good in hadphones but with a huge delay (like half a
  second maybe or something like that) so you're not able anymore to
  mixxx your tracks easilly.

  luckily the master output goes fine instead (no sparkling at all)!! :)
  so people when i play don't get it :D

  i have also problems using BCD3000 native asio drivers. they don't seem to
work with mixxx on windows7 64bit

  cheers from italy

To unsubscribe from this bug, go to:
https://bugs.launchpad.net/mixxx/+bug/732977/+subscribe

jkone27 (jkone27) wrote :
Download full text (3.8 KiB)

it doesn't work at all with wasapi for 2 sound devices simultaneously.

i think that's because they work at different sample rates,
infact when i try 44100 it's ok for BCD but not ok for my internal audio card,
while 48000 works on my laptop soundcard but not on bcd.

if i use wasapi, it shows only 1 channel on my BCD while it has 2 stereo
channels outputs (1 for headphones and 1 for master),
so i can't use one only audio device at a time.

i need headphones

what asio for all does is resampling everything at 44100 so that's how it works
with multiple soundcars maybe?

i'm just guessing without knowing

________________________________
Da: jkone27 <email address hidden>
A: <email address hidden>
Inviato: Sab 12 marzo 2011, 14:25:11
Oggetto: Re: [Bug 732977] Re: cue audio (headphones) crashes using 2 soundcards
with asio4all on win7 64bit

thank you so much! i will try and report my results

best

Giacomo

________________________________
Da: Bill Good <email address hidden>
A: <email address hidden>
Inviato: Sab 12 marzo 2011, 13:52:19
Oggetto: [Bug 732977] Re: cue audio (headphones) crashes using 2 soundcards with

asio4all on win7 64bit

According to http://portaudio.com/trac/ticket/76 PortAudio (the library
we use to interface with sound hardware) only supports one ASIO device
at a time. Like I said, really not sure why you're able to open 2, might
be a PortAudio bug (or maybe they've made progress on that ticket and
the fix just isn't totally working yet, who knows).

I know WASAPI has both an exclusive and shared (mixed) mode. I'd imagine
the shared mode is higher latency than the exclusive mode (which is
practically equivalent to ASIO) and I don't know how to distinguish
between the two modes in software, but I've always gotten very low
latency with WASAPI in Mixxx and I know Sean (one of our Windows guys)
recommends WASAPI.

** Bug watch added: portaudio.com/trac/ #76
  http://portaudio.com/trac/ticket/76

--
You received this bug notification because you are a direct subscriber
of the bug.
https://bugs.launchpad.net/bugs/732977

Title:
  cue audio (headphones) crashes using 2 soundcards with asio4all on
  win7 64bit

Status in Mixxx:
  New

Bug description:
  when i activate the cue (headphones) button, everything goes fine till
  at a certain moment, the sound starts sparkling and cracking, looks
  like the audio buffer reaches its limit and crashes. after a while the
  sounds get back good in hadphones but with a huge delay (like half a
  second maybe or something like that) so you're not able anymore to
  mixxx your tracks easilly.

  luckily the master output goes fine instead (no sparkling at all)!! :)
  so people when i play don't get it :D

  i have also problems using BCD3000 native asio drivers. they don't seem to
work with mixxx on windows7 64bit

  cheers from italy

To unsubscribe from this bug, go to:
https://bugs.launchpad.net/mixxx/+bug/732977/+subscribe

--
You received this bug notification because you are a direct subscriber
of the bug.
https://bugs.launchpad.net/bugs/732977

Title:
  cue audio (headphones) crashes using 2 soundcards with asio4all on
  win7 64bit

Status in Mixxx:
  New

Bug description:
...

Read more...

Bill Good (bkgood) on 2011-03-22
Changed in mixxx:
assignee: nobody → Bill Good (bkgood)
jkone27 (jkone27) wrote :

I haven't figured it out yet. BCD3000 asio desn't seem to work on mixxx with windows 7 64 bit!

can someone give it a try????

best,
Giacomo

Bill Good (bkgood) wrote :

Another person with this bug: https://bugs.launchpad.net/mixxx/+bug/667651/comments/9. ASIO does seem to be a common denominator.

This might be related: http://www.portaudio.com/trac/ticket/108, ml thread http://thread.gmane.org/gmane.comp.audio.portaudio.devel/7006 (although the symptoms are different).
I'm going to see what sort of info I can get from Mixxx and ASIO on my own system, and see if the PortAudio devs know anything about what's going on (I _still_ don't get what PA is letting people open two ASIO cards when their website explicitly says it's not currently possible).

RJ Ryan (rryan) on 2011-10-05
tags: added: crash multi-soundcard
Changed in mixxx:
importance: Undecided → Critical
RJ Ryan (rryan) on 2011-10-05
tags: added: needs-triage

ASIO4ALL corrals the various devices using WDM drivers into a single ASIO4ALL virtual device with as many channels as the total of all of the sub-devices, so PA thinks it's opening a single device. But since they each still have their own clock crystals, there will always be sync issues between them (heard as sparkling/crackling.) Mixxx includes code to prioritize the Master output so that you don't hear it there, but the only way to fix it is to use a single audio device with as many output channels as you need.

(Oh and please don't quote the whole E-mail when you reply. It clutters up the bug report severely.)

Changed in mixxx:
status: New → Confirmed
Daniel Schürmann (daschuer) wrote :

Related Bug #1398714

JosepMa (josepma) wrote :

An old bug, many things have changed since, but I would like to share my findings:

---------------
CPU: Core 2 Duo 1.5GHz
OS: Win 10 64bit
Asio4all: 2.11
Realtek HD audio: ALC268, drivers 6.0.1.7535
Hercules DJ Console 4-Mx: (2016 drivers). For all the tests, except explicitly said, configured with the WDM driver mode.
Mixxx: 2.1.0 alpha (november 2016)
---------------

Test 1: ASIO API on Mixxx, both soundcards as ASIO4all (It might require configuration of which soundcards and channels use). Hercules Master and realtek headphones. 5ms latency. 44Khz.
- In this mode, Mixxx works in single soundcard mode. Soundcard synchronization is done by ASIO4all.
- Playback works without issues initially.
- From time to time, there's a break on the audio, both master and headphones. Mixxx shows the graphics as running.When audio is recovered, usually the playback position goes back to where audio stopped, although in one case it didn't (or so it seemed).
- intercard latency is very good (i didn't need to change it from mixxx settings).

Test 2: ASIO API on Mixxx, Hercules as ASIO, Realtek as ASIO4all. Disabled the corresponding options in asio4all (so that it does not enable Hercules through it).
Hercules refuses to load if i add the realtek one. Deck 1 workaround didn't work here. It's as if the mode only accepted one soundcard.

Test 3: WDM-KS API: Hercules Master and Realtek headphones. I also had to connect Hercules channels 3-4 to something, in this case Deck 1. Else it refuses to open the soundcard.
- "Default (long delay)" mode works very good, I actually had to add 1ms latency to the master, instead of the headphones, but could have lived without it.
- "Experimental" mode gives an "unanticipated host error"
- "Deactivated" mode gives constant skipping.

Test 4: WDM-WASAPI API: Hercules refuses to load if i add the realtek one. Deck 1 workaround didn't work here. It's as if the mode only accepted one soundcard.

Test 5: Directsound API: Hercules master and Realtek headphones, 11ms latency, 44Khz
- "Experimental" (no delay) synchronization mode does not work -> headphones get no sound
- "Normal (long latency)" mode works fine. latency (as expected) is long, seems to be a bit more than the configured audio latency. Listening with one speaker in one ear, and that same channel of the headphones on the other ear, I added 18 ms to the headphone latency.
- "Deactivated (short delay)" mode worked fine initially but soon it lost synchronization and the headphone output started to get some "clicking" that could only get restored by reiniting audio (for example, changing this same setting). I added 4ms of latency using the above mentioned method.

Test 6: MME API: I briefly tried this. Seemed to behave like Directsound. It required a higher latency (i used 22ms).

So, with all these, for multiple soundcards, and given my setup, the best type of connection was WDM-KS, with Directsound the second best. Obviously, since I don't require multiple soundcards, I'm fine with ASIO.

It might require investigation why I couldn't get ASIO or WASAPI to work with two soundcards.

Daniel Schürmann (daschuer) wrote :

Thank you!
It is nice, that you can confirm the "Do not use ASIO4ALL" advice.

> I also had to connect Hercules channels 3-4 to something, in this case Deck 1. Else it refuses to open the soundcard.

What is the error message? What says the mixxx.log?

> "Experimental" mode gives an "unanticipated host error"

This is a very first report that "Experimental" fails. Do you have something in the mixxx.log?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.