 
|
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 |
216.99.100.2
In Reply to: RE: Thanks: my result ... posted by ThomasPf on February 15, 2009 at 18:17:15
My latency result with Foobar playing looks like the following; quite a bit higher, but I gather not the cause of the problem ...
___
Feanor's Classical Music Survey: 250 Compositions
Feanor's stereo configuration
Edits: 02/15/09Follow Ups:
First off, 12us is really low... even the 125 max with the player playing seems more than acceptable. Have you let DPC run for a long while and seen if it spikes... I'm guessing you have.ok here's my weird thing I just found on my system.
Was checking again what my DPC ran at with the player on; before have only checked it with the player off.
With the player off,,, I get a steady 62us
With the music running,,, it bounces from 12us to 20us... That's right, it's lower with me playing music ... now that's weird.Vista64prem http://www.phasure.com/index.php?topic=352.msg4021#msg4021 > WAV/CUE files on HDDs via fW400;[XXHE player Q1 2 processor appt.#3;player priority normal;thread priority realtime];> pci FW800> FireFace800> StelloDAC
Edits: 02/15/09
You may be seeing measurement artifacts, e.g. the system clock is synchronizing the measuring processes with the measured processes.
If you use the Windows task manager you can set it to look at the delta value of I/Os and paging operations. This may help you isolate problem entities.
I run my audio computer without a paging file. This completely eliminates the possibility of paging overhead. If you don't have enough RAM you won't be able to do much multi-tasking with 500 MB of RAM, but at least if you run out of memory you get a hard error and not a mysterious glitch.
Tony Lauck
"Diversity is the law of nature; no two entities in this universe are uniform." - P.R. Sarkar
Right now my page file is drive C where the page file is located, while my music file source is drive F, and external USB drive. The system "recommends" 754 MB and it's set to 756 MB.
I don't understand such things very well, but according to Task Manager, the single most active process in terms of I/O reads is lsass.exe -- explanations of what this is for are technobabble to me. The largest single user of page file is one of several instances of syshost.exe
___
Feanor's Classical Music Survey: 250 Compositions
Feanor's stereo configuration
That lsass report seems quite strange. There is a virus that masquerades as it. It sneaks by because it uses upper case "eye" instead of lower case "el" which look the same with the usual system font. You can tell the difference if you change the system font to something like times roman.
John S.
However there is no "Isass.exe" on my machined unless it's somehow hidden. Also I have run a complete virus scan without finding anything.
___
Feanor's Classical Music Survey: 250 Compositions
Feanor's stereo configuration
Have you had a chance to look at perfmon results during these glitches?
CPU usage loafs along between 1% and 3%. There is no spike when a glitch occurs. There is basically no network usage.
___
Feanor's Classical Music Survey: 250 Compositions
Feanor's stereo configuration
What do you see as paging activity?
Are you playing you music from the local drive or from the Windows Home server you mentioned in a different post? If it is remote you should see a rather steady stream of data over the netowrk.
Cheers
Thomas
But then you are using a weird player. Hahaha
Question for you, what type of computer are you using, how old is it and what is the Front Side Bus speed?
It's aN HP small-footprint with Pentium 4, 2.66GHz processor, with 0.5GB RAM. It appears to be an Intel chipset, maybe 82801(?), and an Intel graphics controller, 82865G.
___
Feanor's Classical Music Survey: 250 Compositions
Feanor's stereo configuration
I feel part of your problem is that you definitely do not have enough Ram, so I would address that issue and see what happens.
Vincent
I agree that 512MB is a bit tight on the RAM. However, if that is the problem you should be able to see the glitches correlated to disk i/o and paging when you look at your perfmon history.
This assumes that a task kicks in every 30s or so and causes heavy paging traffic which might interfere with your playback.
Do you see anything special in perfmon when these glitches happen?
Cheers
Thomas
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 ]
