DirMon, ShowAnalyzer, and SageTV

[Gaurav]

Originally Posted by Jere_Jones

The latest version has a checkbox for subfolders. Unfortunately, it is not compatible with Windows 2000.

Jere

i use win2k and the option works on my pc.

[dmacafee]

It would have saved me a couple of hours trying different things and then
reading the ShowAnalyzer and DirMon threads if there was a download
link marked Win2K for version 2.3 of Dirmon. Otherwise it it is working great
thanks.

Dave

[Jere_Jones]

Good call, that. I'll make that happen!

Jere

[scoobz18]

I was wondering why my shows start getting analyzed while it is recording when I checked wait until file is complete...

[user777]

I have the same issue. It is the only standing in the way of a perfect setup...

Jere, could you explain how Dirmon2 .5.x makes the determination that the file is complete? How about target drive idle?

My System:

SA .6.2 (registered) - processing DVR-MS files
DirMon .5.4
MCE 2005
DVRMSToolbox (used only for comskip add-in)

[Jere_Jones]

Originally Posted by user777

Jere, could you explain how Dirmon2 .5.x makes the determination that the file is complete?

Basically, DM2 checks the size of the file, waits for 1 second and then checks it again. If they are the same, then DM2 assumes the file is finished.

Originally Posted by user777

How about target drive idle?

Basically, DM2 checks the free space on the drive. Then it waits for 2 seconds and checks again. If the free space has dropped, then the drive isn't idle.

I really wish there was some sort of API that would let me know if the drive was reading and/or writing, but if there is, I don't know about it. The same for if the file is finished. Anyone know one?

The only real solution I see is making the wait time configurable. Can anyone think of a better solution? I'm open for suggestions.

Jere

[user777]

Jere, thanks so much for the follow up! You have done some great work with SA and DirMon, thank you!

I believe I know what the problem is (on my system anyway) and some potential solutions.

Cause of Problem:

My system has a SATA (Serial ATA) Hard Drive with NCQ (Native Command Queuing) enabled, Write Caching enabled, and large pagefile. With the system configured this way the computer writes to the recording file in 2 minute intervals, during the two minute intervals the file size and total disk free space does not change at all. Then it updates the file with about 100MB of data (for a non-HD show) and repeats the cycle.

Potential Solutions (keep in mind, I don?t code):

• As you mentioned, add the ability to configure the wait time between the next file size check to find the File Is Finished status. If the file size is still the same after X (in my case 2 minutes), then kick off the job. Sounds like to be the easiest solution.

• For Windows systems, tie into the perfmon counter for ?Disk Writes/sec?, ?Disk Write Bytes/Sec?, or ?%Idle Time? of the PhysicalDisk Object to determine Drive Is Idle status. Visually looking at perfmon while a show completes seems to indicate this would work well.

• Perhaps a more universal way to find Drive Is Idle status would be to tie into the drives S.M.A.R.T. status. I believe this includes disk activity and a quick search seems to come up with some utilities with APIs. I have no idea if this will work and I am sure this would be the most difficult solution?

I see all the time you spend replying and working on this free utility, so I figured I would spend some of my time to give this some real thought? I hope this helps!!

Scott

[Jere_Jones]

Originally Posted by user777

Cause of Problem:

Originally Posted by user777

My system has a SATA (Serial ATA) Hard Drive with NCQ (Native Command Queuing) enabled, Write Caching enabled, and large pagefile. With the system configured this way the computer writes to the recording file in 2 minute intervals, during the two minute intervals the file size and total disk free space does not change at all. Then it updates the file with about 100MB of data (for a non-HD show) and repeats the cycle.

Holy Cow! 2 MINUTES! That would certainly explain it! Thank you very much for this information. It also explains why some people have trouble with live detection. Basically, when SA runs out of data it waits for a while and then checks for more data. More data means continue on. No more data means finish up. I'll have to figure something out. Much thanks for this. I didn't even realize this was possible.

Originally Posted by user777

Potential Solutions (keep in mind, I don?t code):

Originally Posted by user777

• As you mentioned, add the ability to configure the wait time between the next file size check to find the File Is Finished status. If the file size is still the same after X (in my case 2 minutes), then kick off the job. Sounds like to be the easiest solution.

• For Windows systems, tie into the perfmon counter for ?Disk Writes/sec?, ?Disk Write Bytes/Sec?, or ?%Idle Time? of the PhysicalDisk Object to determine Drive Is Idle status. Visually looking at perfmon while a show completes seems to indicate this would work well.

• Perhaps a more universal way to find Drive Is Idle status would be to tie into the drives S.M.A.R.T. status. I believe this includes disk activity and a quick search seems to come up with some utilities with APIs. I have no idea if this will work and I am sure this would be the most difficult solution?

Option 1 is easy enough. I'll probably end up doing something similar inside of SA.
Option 2 is a little harder. The problem (as I understand it) is that the hooks vary depending on which OS is being used. Of course, this is also the option that will create the most accurate result. Certainly worth looking into.
Option 3 is not really workable. I, personally, disable SMART at the motherboard level. I'm sure I'm not the only one.

Originally Posted by user777

I see all the time you spend replying and working on this free utility, so I figured I would spend some of my time to give this some real thought? I hope this helps!!

Originally Posted by user777

Scott

It absolutely helps. Thank you!

Jere

[klunde]

Originally Posted by user777

As you mentioned, add the ability to configure the wait time between the next file size check to find the File Is Finished status. If the file size is still the same after X (in my case 2 minutes), then kick off the job. Sounds like to be the easiest solution.

You could also try to rename the file, if you can rename it noone else has the file open for writing...

[Jere_Jones]

That's a good idea, but I don't think many users would be happy about me renaming their files, even if I did rename them back.

Jere