|
Audio Asylum Thread Printer Get a view of an entire thread on one page |
For Sale Ads |
89.58.168.188
In Reply to: RE: Lets try these tests posted by cics on May 30, 2009 at 11:20:40
Cics,
I can already comment on the second test:
My version of the metallics occurs even when cplay just continues playing and moves to the next track - then (at random) metallics can occur or not. I restart the track, sometimes once more, sometimes again, rarely again, and sooner or later the track starts without metallics. I could discover no pattern whatsover yet to give me a hint on possible causes (other than the combination of latencies maybe).
However, since I am currently focussed on getting the system optimized for Buffalo32s first, it isn't an issue for me for the time being, i feed it with 16/44.1 since it does upsampling anyway. Once that is running fine I'll try 24/192 and will report.
Best,
Robert
Follow Ups:
you said '...My version of the metallics occurs even when cplay just continues playing and moves to the next track - then (at random) metallics can occur or not. I restart the track, sometimes once more, sometimes again, rarely again, and sooner or later the track starts without metallics. I could discover no pattern whatsover ...' --------- was very close to my experience before I went 2.5" hd, fanless cooling except ----when metallics were bad (real bad) only a reboot would make them go away. Now that I am into 2.5" hdd, fanless cpu cooling and using sox I get metallics much less frequently and I get the kind that are less than 'real bad' (except for other day). yesterday, with using only keyboard to navigate within a file I got none. Also with sox I have not yet gotten any at auto track changes or loads.
Robert I found out that cpu voltage and speed settings affect my metallics. I am right now at .85 volts (as set in bios) and 157 host clock control. I'm sure your equivalent but very low settings may impact your metallics.
what's very frustrating to me is I can hear more purity @ 150 hcc but I get the problem more frequently plus sometimes I get instabilities (system shuts down). So finding the sweet spot is perhaps different for all of us. One thing though I believe impacts metallics, is power supply purity. I am using the P4 Ryelands cap mod which is great sonically but I'm not sure it makes my sys more 'metallic' resistant. Others with linear external ps P4 feeds may want to comment how it may effect metallics. As I recall you use a linear ps for P4 so maybe it just depends on voltage/speed levels plus whether you use juli@ or not.
one last thing I have a benchmark too but I like juli@ analogue out better. When using Lynx did I understand correctly that you can only go digital out with an AES cable? Is there no i2s out with Lynx?
Theo,
I am at 0.76785 (not sure about the last three digits, can't look it up since I am not at home today) and host clock at 150MHz, that's stable but lower values don't work (have to restart from BIOS). At that values everything was fine with Lynx AES-16.
IMHO power supply purity does not help to cure the metallics - I am on pure battery power with well-sized caps (so I think) for P4 and P24 and got the metallics just the same as when I power everything with the Antec (I have tested that already). Maybe things are different when I power Juli@ externally as suggested by Alfred/sonics, will test in the next few days.
However, my task for the next few weeks is to go from Juli@ via i2s to Buffalo32S and optimize power supply (and possibly also caps and resistors?) in that chain. Since Buffalo32S does upsampling I output 16/44.1. Once that is running fine, I will switch to 24/192 and 24/178 (thanks Jean) and see if the metallics are back and how stable and effortless Juli@ can perform. Will report.
And yes, as far as I know you can only go out digital from Lynx with their breakout cable that provides you with an AES/XLR plug which I ran into the Benchmark DAC1, worked absolutely stable and reliable. I tried both to find any possible way to (i) go out i2s and (ii) power the AES16 externally, but failed with both (probably could find a way for (ii) but (i) is impossible AFAIK, Lynx techs have confirmed this). Otherwise I would happily stay with Lynx without any doubt.
Cheers
Robert
thanks for info.
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: