|
Post by Michael Tippach on Mar 4, 2005 20:24:19 GMT
Trying to sort out the issue ASIO4ALL seems to have with Creative cards. I'm making this a sticky topic in the hope that everyone will post their troubles with CT cards in here so that I can keep track of things a bit easier. First, there was a bug in 2.3 that may have caused the application to hang. www.asio4all.com/A4Av24p2.exeThis one has this bug fixed and I would ask anyone with this problem to try this test version and report their findings.
|
|
|
Post by Theo on Mar 5, 2005 0:34:48 GMT
Hi Michael,
No luck with version 24p2. Neither the ASIO control panel nor Sonar will even launch. Again, I am using an Audigy 2 ZS.
Theo
|
|
|
Post by tylast on Mar 5, 2005 10:11:04 GMT
The A4A panel offline version won't launch when the Audigy is in the PCMCIA slot. It launches in Live, but hangs constantly!
|
|
|
Post by Michael Tippach on Mar 5, 2005 11:01:21 GMT
Hmm, we need to narrow it down a bit. There is a version of the 2.4pr2 with full debug output enabled: www.asio4all.com/v24pr2dbg.exeIf you could just run the desktop control panel and send the resulting a4apanel.dbg file, that would hopefully let me have some more information.
|
|
|
Post by tylast on Mar 5, 2005 11:03:14 GMT
OK, but where is the debug file saved to?
|
|
|
Post by trauma on Mar 5, 2005 12:59:43 GMT
Hi,
The 2.4 pre release version works fine for me with my onboard AC97 chip, but when I change the output jack to my SB Live's output; I cannot get sound from my Sound Blaster Live! (but it plays other programs' sounds) The ASIO4ALL control panel works fine, it shows my SB Live! in green and everything seems working fine but I cannot get sound from Reason 2.5
|
|
|
Post by Kermit on Mar 6, 2005 11:06:28 GMT
Hi Michael, First congratulations on a phenomenal job on these drivers, quite useful to a lot of people. Then, onto my problems. As I have posted before, I have an Audigy 2 ZS Platinum Pro, and it works perfectly with version 2.2 (I use the driver for 48/24 operation). From V2.3 onwards, the panel just 'hangs' and the driver is unusable. I have tried the debug build, and here is the log :
Start ENUM...DONE ============================ Start WDM Device Enumeration ============================
Device BUS NUMBER = 00494350 Creative Audigy Audio Processor (WDM) / Creative Technology, Ltd. / ctaud2k.sys Instance ID: 00000800 +SB Audigy 2 ZS DirectMusic Synthesizer [DF00] NumPins: 00000002 +Pin 00000000 Dataflow: 00000001 +SB Audigy 2 ZS Sw Synth [DF00] NumPins: 00000002 +Pin 00000000 Dataflow: 00000001 +SB Audigy 2 ZS Synth A [DF00] NumPins: 00000002 +Pin 00000000 Dataflow: 00000001 +SB Audigy 2 ZS Synth B [DF00] NumPins: 00000002 +Pin 00000000 Dataflow: 00000001 +SB Audigy 2 ZS MIDI IO [DF00] NumPins: 00000004 +Pin 00000000 Dataflow: 00000001 +Pin 00000002 Dataflow: 00000002 +SB Audigy 2 ZS MIDI IO 2 [DF00] NumPins: 00000004 +Pin 00000000 Dataflow: 00000001 +Pin 00000002 Dataflow: 00000002 +SB Audigy 2 ZS Audio [DF00] NumPins: 00000005 +Pin 00000000 Dataflow: 00000002 MaxChannels: 00000002 MaxBits : 00000020 MinSampleRt: 00001F40 MaxSampleRt: 0002EE00 +Pin 00000002 Dataflow: 00000001 MaxChannels: 00000008 MaxBits : 00000020 MinSampleRt: 00000FA0 MaxSampleRt: 0002EE00 +Pin 00000004 Dataflow: 00000001
Device BUS NUMBER = 00000000 Plug and Play Software Device Enumerator / (Standard system devices) / swenum.sys Instance ID: 00000884
============================ Exit WDM Device Enumeration ============================
End ENUM ASIOstop called
Start ENUM...DONE
End ENUM
A4Panel is running, showing no window, and not shutting down.
Hope this is helpful.
|
|
|
Post by Michael Tippach on Mar 6, 2005 15:03:10 GMT
Thanks to all for running the debug stuff! The results were, however, inconclusive. So I did an incredibly stupid thing yesterday: I went out and bought an Audigy 2 ZS. I've been able to reproduce the hang and can confirm that v2.2 did work. It turns out the Creative driver has a bug that reacted violently to a rather benign change I made in 2.3. If you happen to work for CT, contact me and I shall tell you where exactly your driver misbehaves. Anyway, here is the workaround, which - so far - works with my brand new Audigy: www.asio4all.com/A4Av24p3.exe
|
|
|
Post by Michael Tippach on Mar 6, 2005 18:01:43 GMT
Done some more performance tweaking. The occasional hiccups with the above pre-release should not be present anymore in the final 2.4.
|
|
|
Post by Theo on Mar 6, 2005 18:12:26 GMT
Michael,
So far so good!
Thanks for all the effort,
Theo
|
|
|
Post by Kermit on Mar 7, 2005 19:06:19 GMT
Michael, Unbelievable. How can one man work TEN times more efficiently than the whole CT driver team? ;D I strongly suggest you go on to solve E-MU cards' driver problems, on a fat payroll from Creative! Thanks for all the good work.
|
|
Sture
New Member
Posts: 1
|
Post by Sture on Mar 9, 2005 14:43:47 GMT
Hi,
does anybody know if the ASIO4ALL driver will provide 24bit 96kHz on my A2 Plat eX? Has anybody tested that? Even 24 bit and 48 kHz would be interesting if 96 kHz does not work.
Thanks for the great work!
Sture
|
|
|
Post by DJ CEL on Mar 16, 2005 16:20:33 GMT
I have a sound blaster live! 5.1 i use the software Virtual DJ v2.06 (with a legal license) and the software supports ASIO 2.0 and only works in 44.1kHz for the moment
I tried your asio4all v2.2 but the software Virtual DJ tells me it doesn't work when i use asio4all.
Your control panel in asio4all tells me it works
You can try with the demo v2.05 of the software. You can find it easily on the net
|
|
|
Post by DJ CEL on Mar 16, 2005 16:24:56 GMT
Still me I have tried with asio4all v2.4 too and it doesn't work too
|
|
|
Post by Michael Tippach on Mar 16, 2005 19:45:38 GMT
I tried this with the demo and the only place where it would let me use ASIO is in the time coded vinyl section, where I found the demo software to have a bug (or an oddity) that manifests itself like this:
You are supposed to select a driver for deck 1 and deck 2 in a combo box for each. Now, the not so funny bit is that even if you have the "activate" box unchecked for both, it would report an ASIO driver error simply because your card only has two inputs and it would need 2x2 inputs _if_ both decks _were_ activated. It would call ASIOgetChannelInfo() with an invalid channel number, rightfully get an error code in return and then mistakenly bark up the driver's tree.
This happens with _any_ ASIO driver, not just with ASIO4ALL if the soundcard in question does not have at least four input channels.
If you experience the problem the same way as I described it, you may want to contact the Virtual DJ customer support about this.
|
|