danielt3 / cmediadrivers

Automatically exported from code.google.com/p/cmediadrivers
1 stars 0 forks source link

Sound popping when using ASIO out from Foobar, and Winamp #69

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What soundcard to you have (make, model, chip)?
St-lab CMI 8768 (7.1?)

What steps will reproduce the problem?
1. install foobar from offical homepage: http://www.foobar2000.org/download
2. install asio support 1.2.7, download from foobar's components' page @
http://www.foobar2000.org/components/author/Peter
3. set CMI8738/68 as virtual asio device in foobar (according to the guide
on their homepage)
4. start playing some music

What is the expected output? What happens instead?
Expected is normal playback, but the sound is popping almost every
second... I've tried to increase the buffer size in foobar (I've read it
somewhere), but it didn't help either, so thus I think there is maybe
something in connection with the cmediadriver

What version of the driver are you using? On what operating system? What
version of the operationg system are you using (32 or 64 bit)?

1.2.4
WindowsXP 32bit SP2, with no other fixes

What ports of the soundcard are affected by the bug (e.g. SPDIF, Mic-In)?
Analogue out

Please provide any additional information below.

I've also tried it with winamp using some asio output plugins (one
downloaded from winamp's offical homepage, and an other from somewhere
else, and I also remember popping, but there was some problem with the
sound output it was disappearing after configuring the plugin(sometimes
after reconfiguring too) and cmedia control panel was needed to be opened
and that cured the problem, but this seemed that buggy for me to drop the
idea of asio in winamp, thus i've tried Kernel streaming which seemed to be
ok (expect for taking a few seconds to load a file from playlist, instead
of immediate normal loading), but then BlueScreen error(BSOD) came  with
the whole system freezing,I've tried this 2 times, so I thought that this
whole thing with winamp ASIO/KS would be buggy,and i don't want any blue
screens(and I've googled too and KS has caused such things for people with
other hardware than cmedia too) thus I've tried foobar, but this popping
remained... and I don't really want to try KS in foobar...

thanks,
Viktor

Original issue reported on code.google.com by gazsi...@freemail.hu on 6 Mar 2010 at 9:29

GoogleCodeExporter commented 9 years ago
Thanks for the report.

KS is usually quite stable: I can only remember having issues with BSODs in 
Vista 
when I tried to play files from a network drive with KS. Usually, KS is 
preferable 
to ASIO because you don't need a wrapper. 

I'll have a look once I get some time (argh!).

Original comment by dogb...@gmail.com on 10 Mar 2010 at 7:48

GoogleCodeExporter commented 9 years ago
Thank you for the idea, I've tested KS again, but this time I had uninstalled
asio4all before the test, and I've been listening to music for an hour this 
afternoon
without a problem... Do you think asio4all driver can cause KS to crash the 
computer?
Or maybe this was one thing, as I have a special hardware setup with a PC 
protector
card from rogev.com, and it also has a driver loaded... And with the first 
setup I
tried with asio4all installed, with KS it also took a few seconds to start a 
single
song in winamp to play, but this time it worked....
Although I'm still interested in what would cause this ASIO problem:)

Original comment by gazsi...@freemail.hu on 10 Mar 2010 at 10:47

GoogleCodeExporter commented 9 years ago
presumably, the parts of the ASIO driver run in ring0 kernel mode, so yes - 
they can 
crash a machine. Also, the Windows kernel is anything but bug free. It's easy 
to 
crash the system even from user mode.

Original comment by dogb...@gmail.com on 19 Mar 2010 at 10:07

GoogleCodeExporter commented 9 years ago
that's not good news... :)

Original comment by gazsi...@freemail.hu on 21 Mar 2010 at 12:36