search

mixxxdj / mixxx

Mixxx is Free DJ software that gives you everything you need to perform live mixes.
http://mixxx.org
Other
4.38k stars 1.26k forks source link

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

Open mixxxbot opened 2 years ago

mixxxbot commented 2 years ago

Reported by: jkone27 Date: 2011-03-11T00:25:56Z Status: Triaged Importance: Low Launchpad Issue: lp732977 Tags: crash

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

mixxxbot commented 2 years ago

Commented by: jkone27 Date: 2011-03-11T00:33:53Z

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

mixxxbot commented 2 years ago

Commented by: Pegasus-RPG Date: 2011-03-11T05:07:53Z

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.

mixxxbot commented 2 years ago

Commented by: jkone27 Date: 2011-03-11T13:59:03Z

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
mixxxbot commented 2 years ago

Commented by: bkgood Date: 2011-03-11T17:59:53Z

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

mixxxbot commented 2 years ago

Commented by: jkone27 Date: 2011-03-12T10:38:41Z

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

mixxxbot commented 2 years ago

Commented by: jkone27 Date: 2011-03-12T12:33:24Z

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

mixxxbot commented 2 years ago

Commented by: bkgood Date: 2011-03-12T12:52:19Z

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.

mixxxbot commented 2 years ago

Commented by: jkone27 Date: 2011-03-12T13:25:11Z

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

mixxxbot commented 2 years ago

Commented by: jkone27 Date: 2011-03-12T14:15:00Z

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: 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

mixxxbot commented 2 years ago

Commented by: jkone27 Date: 2011-04-18T11:53:50Z

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

mixxxbot commented 2 years ago

Commented by: bkgood Date: 2011-05-06T06:50:44Z

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).

mixxxbot commented 2 years ago

Commented by: Pegasus-RPG Date: 2013-06-19T20:02:04Z

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.)

mixxxbot commented 2 years ago

Commented by: daschuer Date: 2014-12-04T07:26:16Z

Related Bug #⁠1398714

mixxxbot commented 2 years ago

Commented by: JosepMaJAZ Date: 2016-11-08T18:21:47Z

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.

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.

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

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.

mixxxbot commented 2 years ago

Commented by: daschuer Date: 2016-11-08T21:03:25Z

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?

mixxxbot commented 2 years ago

Commented by: daschuer Date: 2018-04-15T23:01:07Z

Lower priority since we have a solution, and can't do much in the Mixxx code base.