PierreG wrote:Guess I'm the one missing something, "same thing" as what exactly? This utility shows the exact files that are being accessed by the Tracktion process, all of them, not just audio. You can view exactly what's happening when T is grabbing files to load into cache. At least this is how I understand the process.
Example: I run a T loop, I see T accessing the audio files and loading them into the cache buffers (I assume). Then as the buffers are filled, the T disk I/O goes away. I stop looping and let the playback run out towards the end, I see T grabbing (buffering) the new sections of the audio files for playback.
What am I missing here?
Glad to be of service Chico!chico.co.uk wrote:No, this is me mate, I've got the wrong end of the stick. More accurately, looking on the wrong tab.
I've managed to somehow never tick boxes for individual processes on that disk tab, and see the "disk activity" window change to show what that process is accessing. I've more usually used filemon or procmon for that kind of thing, which has its own benefits, but this is a cool wee feature I wasn't aware of.
Cheers, my bad, but kind of glad I asked, because that's handy.
(oddly, I do use the network tab in a similar way, to check network activity for individual processes, instead of using tcpview, or wireshark, so you'd think I'd have noticed how the disk tab stuff works. But apparently not)
I find Resource Monitor to be an amazing all in one monitoring tool. I use the Network tab as you do. WAY faster and straight forward for basic network probing than Wire Shark!
Happy RMing man...
PS: T 6.3.0 is poof crashing again. Happened as I was running an edit and observing RM to make sure I was describing the Disk monitoring process correctly...
Update: Don't forget the powerful RM feature under the CPU tab - Services. Great for viewing all of those potentially nasty Windows services that are grabbing CPU resources.