 
|
Audio Asylum Thread Printer Get a view of an entire thread on one page |
For Sale Ads |
|
|
Audio Asylum Thread Printer Get a view of an entire thread on one page |
For Sale Ads |
68.43.175.248
In Reply to: RE: OK Re-testing with Main PSU powering HDD posted by theob on March 28, 2009 at 04:23:15
,
Follow Ups:
I really believe it is power related: always seem to be more frequent metallics when power line is noisy(noisy today good time to test). Also after I tried internal sata power feed I put back the gd and tried a different power cord to pc (still running juli analogue outs) listened for a while then rehooked up the Dac1 and it was metallic right from the start. Switched back to juli@ and I started noticing a 'beginning of the metallics'---lots of static---when I switched tracks not always but sometimes. But if I just indexed cplay to next track then back again to previus track it would go away. So, I don't know, I'm starting to think maybe power and/or cpu load related might be the issue.
Why are you convinced its not the cpu?
I'm liking it very much (maybe after 3-4 days its broken in now). Even though the shortcomings I mentioned vs Dac1 are still there, at 150 host clock control, eist disabled, new devices disabled I am starting to think I like it better. Even with the small ground loop I'm getting, I just love the highs, midrange. While the bass is not as tight (as Dac1) its plumpy in a graceful, musical way. Dynamics perhaps not as good but still better than anything I have heard (save dac1 via cplay/cmp).Many music files that were hard. borderline unlistenable through the dac1 are now much better.
Edits: 03/28/09
Here is Windows Task Manager data(just to see if anything here is amiss):cpu usage: 44%-64%
Handles: 1162
threads: 120
processes: 14Physical memory: 251k
available: 74K
sys cache: 91kcommit charge:
total: 164k
limit: 239k
peak: 164kkernel memory:
tot: 8k
paged: 6k
nonpaged: 3KAnything pop as out of the ordinary?
I am running 192/146, at 150 host clock control all else per latest spec.Also since I lowered host clock control I noticed cpu usage go up and my metallics come more often than before (while listening to dac1). Also I notice when I reboot the pc is re-setting host clock control to auto , multiplier to auto and dram timing to auto.
Since I suspect my root cause may be power related I tried plugging my audio pc, power line conditioner(Hydra) into a different outlet--> however I got the same result: the metallics after 5 minutes of play time.
Also since posting the above I noticed some services wer still started so after I closed all (except the 2) I get 997 handles; 100 threads; 13 processes while running cmp/cplay. Cpu peak usage still about the same as above.
Edits: 03/29/09 03/29/09
During playback, you should only have 12 processes. Check that you only have the 2 required services running (often Crytographic Services starts when doing thing in device manager and must be manually stopped).
If not stable at 150, then try 160 or 165.
Problem appears to be power related because you can't create it when using FD. Standard HDD causes a significant power spike (and associated ground noise) when transitioning from idle to sequential read. Using main PSU doesn't help either!
I was hoping you were doing the test with a laptop drive - any chances of this?
gotta buy one so unless absolutely necessary I won't (just bought a new hdd). If you feel I should I will though. you mean just for music files right? I won't have to reload windows again to set up a new os partition, I hope.
I have 13 processes while running: cicsplay; cicsremote;cmp; juliapan; svchost; lsass;services; winlogon (aka minlogon);crss; smss; system;system idle process. Which one is un-necessary?
Edits: 03/29/09 03/29/09
Tried running cplay (w/o cmp engaged) off of fd and it went metallic right away. Tried running off of fd with cmp engaged and 1st time it stuttered (had to reboot). After reboot it started but went metallic right away.My conclusion is that at 160 hcc and eist disabled I'm getting the problem even on fd. Cpu related?
I upped clock back up to 165.
Edits: 03/30/09
had to bump up hcc to 175 to avoid anomalies: stuttering, noise (static-y almost like a metallic overlay but goes away by re-indexing)
Edits: 03/31/09
after I implemented nopae and checked services each time I reboot to get back to only 2 services. I have to say the sound is very, very good. Cics yes this is a great foundation to build on.The mids, highs are absolutely best I have heard in my sys. If I lost any soundstage, bass to the dac1 I pick it back up with nopae.
While I love the sound I'm bordering on instability. I get the fuzzies almost metallics when cplay swithches tracks or reloads in a track. But I re-index it manually and its ok. I hate to keep asking but doesn't it sound like borderline processor performance? I know you said it probably isn't but there's not much left in my pc to suspect as root cause of my issue. (Follow up: Running music files off flash drive fixes this noise issue for awhile, but had to go back up to 155 hcc.)
But bravo on new spec!!
As you can see I think my sys is right at the borderline of stability (or at least this crazy noise I now get in the juli@ analogue out mode).
Edits: 04/01/09 04/01/09 04/01/09 04/01/09
... the tics, drop outs, metallics, fuzzies got so bad today I could not listen to cplay 20 so I loaded cplay 18 back in. Not a tic, drop out, no fuzzies, no anamolies.
Its interesting because I get about the same cpu usage as cplay 20 and 18 is not as good sonically but something about my machine does not allow cplay 20 to play w/o problems.
Does this make any sense to you?
bump
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:
Top of Page ]
[ Contact Us ]
[ Support/Wish List ]
[ Copyright © 2025, Audio Asylum, all rights reserved ]
