mvchannels and system performance

[fredisdead]

I have found that when mvchannels loops, I see visible stutters on live tv... Is there a way ti influence the runtime priority of mvchannles to avoid this? It is bad enough that I will have to abandon it if I can't find a solution! Ouch!

I am running it from a telnet window not rc.sysinit yet, if that makes a difference..

Help!

[BubbleLamp]

You should delete all the channels you're never going to get out of channels.dat. I run it all the time with no problems. BTW, there was a bug in an earlier version that caused high CPU usage. Make sure you are using 1.35.

[fredisdead]

I normally get my local sf channels in their normal 5th gen channel slots, so far it looks like all I can add is sacramento and some LA channels. Do I need to keep the SF channels in the channels.dat? Or can I delete them and reduce the size of the file and processing load without losing them? I am running the latest version of mvchannels...

Also, is there a need to keep looping mvchanels? Do they stick through reboot or get reset with service data downloads? How often do they disappear?

[BubbleLamp]

I leave the SF locals in their default locations, and move LA and SA to the 70's and 80's. You have to loop if you are moving channels to someplace other than their defaults.

[fredisdead]

I am putting the additional locals in their 'normal' 800-900's ranges. Does this meen I don't need to loop?

[BubbleLamp]

Originally posted by fredisdead
I am putting the additional locals in their 'normal' 800-900's ranges. Does this meen I don't need to loop?

No. They're default locations is the first number in channels.dat. What you will end up with is duplicate numbers, which will cause headaches. If you move, you must loop.