moomin1465 / cmediadrivers

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

Random fall back to 2.1 #4

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
No way to reproduce the problem. The system falls back to 2.1 from time to 
time, and then goes back to 5.1.

What is the expected output? What do you see instead?
All ouput (AC3/DTS) is correctly passed through SPDIF, but my AV receiver 
randomly detects it at 2.1 instead of 5.1.

What version of the driver are you using? On what operating system?
1.1.8 on XP

Please provide any additional information below.

Original issue reported on code.google.com by jso...@gmail.com on 22 Feb 2008 at 10:11

GoogleCodeExporter commented 9 years ago
what receiver do you have (manufacturer / model)?
what software do you use? does this happen with both DTS and AC3 media streams 
or 
just with AC3?

Original comment by dogb...@gmail.com on 24 Feb 2008 at 11:14

GoogleCodeExporter commented 9 years ago
hi dogber1

Thanks for your answer, and sorry for multiposting, but I had errors when 
posting so 
I thought it didn't work.

My receiver is a Cambridge audio model Azur 540R.
For audio playback I am using mediaportal + AC3Filter + reclock, and it does 
happen 
with AC3 and DTS.

regards 

julien

Original comment by jso...@gmail.com on 24 Feb 2008 at 10:04

GoogleCodeExporter commented 9 years ago
Hi dogber1,
  First thanks for the great driver.  I think I am having a similar problem to 
Julien.  

Starting from a fresh install of Windows XP I installed your driver and 
everything 
was working great.  I have several DTS cds and the all played correctly through 
my 
reciever.

After a few days, my system no longer plays DTS cds correctly.  My reciever 
will 
flash as if it picked up a source change, recognize the files as normal stereo, 
and 
play static.  If I run the setup program for your driver again, the reciever 
will 
flash during the install (as if it picked up a new source), and the DTS cds 
start 
working correctly again.  If a reboot the system, DTS stops working and I have 
to 
reinstall the driver.

I tried re-installing Windows XP and the same thing happened again.  Everything 
worked fine for a few days, and then suddenly stopped.  

In both cases I noticed that DTS had stopped working shortly after running a 
Windows 
Update and installing a virtual drive program.

I am running:

Windows XP
Diamond Multimedia Xtreme 7.1 Sound (XS71)
Connected via Digital Coax to Onkyo TX-SR601 receiver

Original comment by jacobhy...@gmail.com on 6 Mar 2008 at 1:13

GoogleCodeExporter commented 9 years ago
Hi,

thanks for the report. 
My guess is that an application which is started during bootup messes with the 
volume sliders, specifically the wave volume slider - it must be maxed out for 
the 
kmixer being bitperfect. Another possible cause could be an application which 
has 
opened a recording or playback stream on the soundcard (e.g. skype) - the 
hardware 
requires the same sample rate for both the recording and playback stream, so a 
44.1kHz DTS wave stream gets converted to 48kHz by the kmixer if a 48 kHz 
recording 
stream has been opened by some other application. This results in the described 
"flicker" of the DTS signal.
In order to circumvent the kmixer, foobar in conjunction with the kernel 
streaming 
plugin might be worth a try.
I'd like to hear back from you whether you were able to resolve this issue or 
not.

Cheers,

dogbert

Original comment by dogb...@gmail.com on 6 Mar 2008 at 1:34

GoogleCodeExporter commented 9 years ago
Hi Dogbert,
  Thanks again for the feeback, it solved my problem.  I think I must have 
inadvertantly adjusted the mixer setting for wave output.  Windows was just 
defaulting back to that setting every time a rebooted.  Sorry if this 
information is 
already posted elsewhere on your site.

Thanks, 
Jacob

Original comment by jacobhy...@gmail.com on 7 Mar 2008 at 1:36

GoogleCodeExporter commented 9 years ago
jsoyer, that's a bug of ReClock - uninstalling it and using ffdshow instead 
solves 
the problem on my system.

Original comment by dogb...@gmail.com on 20 Apr 2008 at 4:46