Cmd.exe

[bones71]

I am having a problem with the new 6.14 beta I noticed it going real slow for a while now. Brought up the windows task manager and it shows cmd.exe using anywhere from 90% to 100% cpu. I end the process then it works perfect. Then it restarts and slows everything down. This is happening on my server and client machines at first I thought maybe a virus or something did registry scans virus scans. couldn't figure it out. Then I left task manager open On my client. Opened sage no cmd.exe. As soon as I start a show for playback cmd.exe starts and slows sage down. end process and fine. Why is this happening? Anybody else having this problem?

[jlabrue]

Originally Posted by bones71

I am having a problem with the new 6.14 beta I noticed it going real slow for a while now. Brought up the windows task manager and it shows cmd.exe using anywhere from 90% to 100% cpu. I end the process then it works perfect. Then it restarts and slows everything down. This is happening on my server and client machines at first I thought maybe a virus or something did registry scans virus scans. couldn't figure it out. Then I left task manager open On my client. Opened sage no cmd.exe. As soon as I start a show for playback cmd.exe starts and slows sage down. end process and fine. Why is this happening? Anybody else having this problem?

I believe I know exactly what your problem may be, I had the same thing happened. I had installed the latest Comskip stvi with the new version of Sage. The default setting or at least the one causing this was for it to start processing at the start of a show. I think the default configuration for that was to kick off comskip.exe and I did not use that utility but I instead used DirMon/SA. By turning off the option to start processing something on watch it stopped happening. I don't the exact path but it was in the Setup/Advanced/Comskip section I believe

John

[bones71]

Thank you I actually figured it out kinda I went back to the stock stv then it was fine installed comskip and it happened again so I went back to the old comskip. I also use dirmon and show anylizer. Now I can shut off the processing like you said and go back to the new comskip. Thanks Again.

[sandor]

Originally Posted by bones71

Thank you I actually figured it out kinda I went back to the stock stv then it was fine installed comskip and it happened again so I went back to the old comskip. I also use dirmon and show anylizer. Now I can shut off the processing like you said and go back to the new comskip. Thanks Again.

just had this same problem, and disabling the scan on watch option worked perfect!

[JREkiwi]

Start on Watch should be disabled by default.

If you are using it though, you can fix up the comskip.cmd for less impact by editing it and adding -n to any comskip commands you are using ie: comskip -n

I've slipped a modified comskip.cmd into the current download 1.3.6

John

[rockwella]

you people are geniuses...search and you shall find...but really, this works perfectly for the cmd.exe thing.....check it out.

[waynedunham]

Thanks guys, I was pulling my hair out trying to figure out why CMD.EXE kept popping and chewing up 50% cpu every time I tried to play a video on the server.
At first I thought it was because I also just added my HDHomerun with the Sage update, but then noticed that it also did on SD files.

[hemicuda]

looks like this bit me too. cmd.exe using 100% of cpu.

[JREkiwi]

I assume that everyone having a problem has at some stage enabled Start on Watch and configured either the sample script or selected their own app to run.

If that's not the case please let me know, but it should be disabled by default.

Maybe I also need to change the setup panel for Start on Watch

The app/script specified in Start on Watch will only run if Start on Watch is Enabled.

When Start on Watch is Disabled the Setup panel will show it as Disabled
When Start on Watch is Enabled the Setup panel will show it as Configure

The default is Disabled

In the Start on Watch options, if Run if no Comksip files is true then the script will only run if there are no matching comskip files for the video playing. If it's false the script will always run when a video starts playing.

To reduce the impact if running comskip add -n to any comskip command strings ie: comskip -n

None of this has anything to do with using Comskip Manager to run comskip while recording.

John

[hemicuda]

JREkiwi...

that is correct. it is only when using the Start on Watch option that this happens, and only since I upgraded Sage and the STVi. Since I changed 2 things at once I can't be of any help to which one is a contributor. I'll try the -n switch when the wife's 'important' shows have recorded and see what happens. It'll probably turn out to be some little nit-picky setting that's off by a gnat's hair.

Edit: BINGO!!!

Good thing I had copied the entire Sage folder to my USB backup drive before I did the upgrade. Turns out I'd not specified (read: didn't edit the file after install) the absolute path to comskip.exe in comskip.cmd. I also specify the absolute path to the ini just to be safe. The -n option WAS already in you're original cmd file when I checked, but right now I'm not using the -n.
Now all is well in Mudville again

You'd think as much time as I spend on this machine it would know by now what I want it to do with out explicit instructions.

[JREkiwi]

Thanks hemicuda, I've sorted out the cause.

The sample script was calling comskip, which of course if comskip.exe wasn't in the same directory the script would end up running itself and looping. This is bad as people have noticed.

I've change the sample script in the download so that it is calling comskip.exe, which will mean the script will not loop if Start on Watch is enabled without the script being customized.

John

[hemicuda]

Originally Posted by JREkiwi

The sample script was calling comskip, which of course if comskip.exe wasn't in the same directory the script would end up running itself and looping. This is bad as people have noticed.

Dang.. as much simple coding as I've done in Linux and DOS and I didn't notice the missing .exe until your post.

[JREkiwi]

Originally Posted by hemicuda

... I didn't notice the missing .exe until your post.

How do you think I feel? I've looked at the import and the script code a bazillion times since I spotted this thread and it wasn't until your comment about comskip.exe that it finally clicked. Thanks. Now lets get your slow captions fixed.

John