Minimum CPU requirements for comskip?

[blade]

I was thinking of running comskip on my sage server; however, it's a rather slow system and I was afraid it might not have enough power to process the shows. I have no idea how much power is needed. :O

The server is a Celeron 366@550mhz with 288mb of ram. It's a dedicated box so it does nothing but run Sage. If absolutely necessary I could upgrade it to something around a 1 ghz Celeron or P3, but would rather not waste money upgrading such ancient hardware unless absolutely necessary.

I don't mind if it takes a long time to process the shows, as long as it can keep pace with the recordings. For example if I record 9 hrs in a day I'd like for it to be able to process 9 hrs worth of video in a day. I hope that makes sense.

[malore]

On my 2.4Ghz machine it takes around 10 minutes to do a hour show. Just run comskip manually from the dos prompt on a half hour show and you'll be able to estimate how long it would take to process a days worth of shows. It will also show you timing information while it's running.

>comskip.exe filename.mpg

[blade]

Thanks, I'll give it a try.

[blade]

Well it seems my old celeron wasn't quite stable at 550mhz. The system would freeze up while running comskip. I never had a single crash just running it as a sage server.

I slowed it back down to 366mhz and it processed a 30 minute show in just over 30 minutes. It appears that even those of us with very old hardware can still use comskip.

Now if I can just figure out how to get the client box to use the comskip text file I'll be in business, but that's for another thread I guess.

[malore]

Yeah, running the CPU at 100% for a half hour would probably test the stability of an overclocked CPU. You should be able to find the answers to most of your comskip question in the main comskip thread. Basically to use comskip with a client machine the client machine has be able to access the shows with the exact same path as the server uses. So if the server records on the D: drive and you can map the Server to the D: drive on the client you're golden, otherwise most people setup the server to use UNC paths for the record directories (example \\server\c). I recall that switching to UNC will only work on newly recorded shows.

I've never used the client, so I don't have any first had experience. Good luck.

[blade]

Thanks for the help, I was one directory off with my drive mapping. It's working perfectly now.