|
Audio Asylum Thread Printer Get a view of an entire thread on one page |
For Sale Ads |
76.226.230.15
In Reply to: RE: If you can now be sure it is not the DAC ... posted by rickmcinnis@dogwoodfabrics.com on April 03, 2009 at 09:31:13
great suggestion. are you suggesting the traffic between ram and cpu (presumably directed by southbridge) is amiss? make sense for my data. but why does my pc work with cplay 2.0 b18 but not 2.0 b19 or b20?
Follow Ups:
it has something to do with, I am surmising, how cPLAY instructs the hardware. But, I seem to remember you having this problem with THAT version (the one you say is working) at one time. Feel free to correct me.
I think it has to do with re-booting. Whatever is bothering IT is cleared at re-boot and eventually IT gets corrupted again. Or maybe it has something to do with installation, but that seems tenuous.
Are you saying you ALWAYS get the metallic sound with #20 even at start-up?
If so, maybe it has something to do with the new instructions set? I am not a computer guy, I can get see the concepts but the details - I have no knowledge.
In my experience there is such a thing as a defective MB. I would give this a try. At least, it is a simple swap!
Bye,
Rick McInnis
gosh I'm sure I know less than you but I do know I played cplay 2.0 b 18 for 6 days no trouble initially then I moved on to version 19/20. The last several days(2 or 3 I think) I've been playing 18 no troubles and this is with eist disabled, hcc set at 150, 146 src @ 192 Khz(the most aggressive settings). It seems like (emphasis on the seems!!) that all the cplay versions associated with IMPROVED ASIO EFFIENCY have ultimately failed (in the sense of metallic sonics eventually). Not when I boot up 20. it sounds great for anywhere from 5-35 minutes before it goes metallic. Let me try to be clear about what the 'metallic overlay' I describe, sounds like. If you go into program files and delete one of the two Juli@ files (like juli@Pan) and then play cplay it sounds exactly like that. I tried it once just to see if it would work and if it worked how it would sound. So I believe that somehow my rig is overwriting or deleting or otherwise corrupting my juli@ drivers when I play 19 or 20 or 15, 16, 17 but not 18.When I was into 19 and went back to 18 I got the metallics if I didn't reboot (right after running 19 into the metallics). Once I rebooted 18 was fine indefinitely.
Edits: 04/03/09 04/04/09
My gut is I don't think it is hw unless my processor or mobo can't handle version 20. I ran task mgr on both versions and cpu load is about the same. So I conclude processor at least is ok. But why would mobo work ok with 18 but not 20? Still no good answer.
Also I'm working with some other inmates in an effort to figure this out. I ran a torture test (with bios @ load optimized defaults) to see if I pass or fail. I ran an hour or so with no failures so my conclusion is mobo or processor are probably ok.
But then when I ran cplay it would not start. I got a cplay error diagnostic saying that I didn't have enough memory. Very strange, this could be related to my problem because when I rebooted all was ok. Cplay 20 then ran great for 30 minutes (no metallics) but didn't sound good (remember all 'load optimized defaults' in bios). So I then lowered host clock control to 150 (and reset all bios per cics spec except core voltage) and it went metallic right away. I began upping hcc until I got stable cplay @ 190 but it still sounded hard. So leaving the clock @ 190 I began lowering core voltage, got to .9 volts and boom: metallic. So I concluded that the bios levels that got me no metallics sounded bad with cplay 20. I reset all bios to all of cics specs, reloaded 18 and I get stable playback and decent sonics.
Still sound like the mobo to you? Kind of does to me but appreciate your feedback.I'm running the torture test now at cics bios specs.
Edits: 04/04/09
Dear Theo,
I do not think anyone has suggested the processor.
From the little I know (part of the more you know the more you discover you don't know syndrome) none of those tests would detect problems with the southbridge which the processor instructs which paths to open and close as needed.
Why a malfunction there would make the noises you are hearing is completely beyond me. BUT, I know I ruined an MB by stressing the SB and it no longer worked at all. I surmise that something has stressed your SB and that is why it is acting the way it does.
In any case, spending seventy dollars to verify this is a pittance in comparison to replacing your DAC, which you considered at one time. And, until this is verified you are completely in the dark. Not to say you might chance upon something else that turns out to be the problem, but barring that, this is about as important a place to start as one can think of.
Until you are sure it is NOT the MB it is next to impossible to help you. All any of us can do is throw suggestions to you and these are going to become increasingly arcane since you have tried just about everything BUT replacing the MB.
One good thing about this is that it should not require any reloading of software or re-implementing cics's settings. If it does, then that would mean your previous MB was not only corrupting itself but also the HDD.
And, if it doesn't help at all you have a back up or a board, I feel sure, you would have no trouble selling.
Bye,
Rick McInnis
ok I've got a new mobo installed. I had to reflash F6x drivers and reset bios but ok now and it boots ok.
I'll let it run a few days with cplay 2.0b vs 18. Once burned in and stable I'll try to see if it affected my noise while running cplay 2.0b version 20.
Went metallic after 35 minutes of cplay 2.0b vs 20 playback. I guess it is really the cpu now.
Sidebar note though: the new mobo sounds way better than old. Very solid bass and apparently more dynamic.
If new cpu doesn't do it I'm done with the quest--nowhere else to go.
thank you rick as always you're there to offer help.
Post a Followup:
FAQ |
Post a Message! |
Forgot Password? |
|
||||||||||||||
|
This post is made possible by the generous support of people like you and our sponsors: