View Full Version : Miami Locals problem SOLVED...(not via channels.dat)
TheBigDog
01-31-2002, 03:36 PM
I finally solved my Miami locals problem. I have been getting these locals in my 2-99 range NATURALLY w/ my EMU system no matter what I do. I have had people told me to adjust channels.dat to HIDE those channals. It would work but it causes more work load to your already processor intensive mvchannels.tcl (I try to keep as little stuff as possible in channels.dat, that will speed up your guide / system.) After further investigation, I finally figured out what the problem is and now my MN locals NATURALLY occurs in my 2-99 range w/o having channals.dat to do it.
The fix is EMU related and I know that this forum doesn't like EMU talk so I wouldn't discuss it here, but you can PM me and I let u know what I did.
Mod, if you think this is out of line, please delete my post at your discretion.
DealDatabase is truely a great community. I have learned so much from it!!!
Rayjet
01-31-2002, 03:56 PM
So, are you running without mvch?
TheBigDog
01-31-2002, 04:12 PM
now that I have figured out how to get my local channals NATURALLY in the 2-99 range, I only use mvchannels.tcl to add LA and NY lcoal channels.
Rayjet
01-31-2002, 04:38 PM
BD,
Can I PM you? I'd like to know what you're doing... I had to kill mvch, it was really slowing me down..
TheBigDog
01-31-2002, 04:49 PM
yup, pm me.
genericuser
01-31-2002, 04:59 PM
Hmmm....
Does the answer to this age old problem have anything to do with READING?????????
Sorry, big dig, I couldnt resist :-)
TheBigDog
01-31-2002, 05:12 PM
Originally posted by genericuser
Hmmm....
Does the answer to this age old problem have anything to do with READING?????????
Sorry, big dig, I couldnt resist :-)
I remember you helped me on this problem at one point but your suggestion was to edit channels.dat, which works well, but I think there is another way to do it, which is what I found out upon reading... :)
Meathead
01-31-2002, 05:26 PM
I would be interested in this as well.
genericuser
01-31-2002, 05:27 PM
Yeah, there certainly is and you got it. Good job!
It is the way I do it and it helps cut down the job mvchannels has to do. Good catch.
TheBigDog
01-31-2002, 05:31 PM
Originally posted by genericuser
Yeah, there certainly is and you got it. Good job!
It is the way I do it and it helps cut down the job mvchannels has to do. Good catch.
Thanks genericuser. but w/o your help I would have gotten to this point, so I really appreciate your help.
mxzhead
01-31-2002, 06:27 PM
yes big dog please pm me as well.
thanks
TheBigDog
01-31-2002, 06:39 PM
I am sorry guys, you have to PM me otherwise I would loose track of who I have received request or who I have just received a reply to my post.
PM me and I will send you the info.
AlphaWolf
01-31-2002, 06:50 PM
Just thought I would comment, the first 4 LA and NY channels, as well as chicago 66, are just duplicate feeds of channels you already have (hence why EVERYBODY gets them) and there is no point in adding them. If you want to see those channels without any hacking, just tune to the east or west feeds of NBC, ABC, CBS, or FOX, and you will see that they are exactly the same as their 900s counterparts.
Also theres an easier way to do all of this, use selectlocals.tcl only add the locals you want, and it will remove any locals you don't add the wildcards for. You should only use mvchannels.tcl if you want to eliminate (or relocate) duplicate channel numbers when adding multiple sets of locals.
TheBigDog
01-31-2002, 06:58 PM
Originally posted by AlphaWolf
Just thought I would comment, the first 4 LA and NY channels, as well as chicago 66, are just duplicate feeds of channels you already have (hence why EVERYBODY gets them) and there is no point in adding them. If you want to see those channels without any hacking, just tune to the east or west feeds of NBC, ABC, CBS, or FOX, and you will see that they are exactly the same as their 900s counterparts.
Also theres an easier way to do all of this, use selectlocals.tcl only add the locals you want, and it will remove any locals you don't add the wildcards for. You should only use mvchannels.tcl if you want to eliminate (or relocate) duplicate channel numbers when adding multiple sets of locals.
I have never used selectlocals before, but if you only want the local that you should get AND if you are running EMU, then you don't even need to run any script if you follow the method that I have found.
Again, I am sure what AlphaWolf mentioned will work, but when it comes to my TiVo, I would like to run as little script on the background as possible unless neccessary. That's just my preference.
TheBigDog
01-31-2002, 10:17 PM
I have received quite a few request since I posted this thread. And I have also seen some common questoins, so here I will try to ansewr them instead of answering them individually.
If you follow the exact procedure, you should get your own locals at 2-99 range without even running ANY script.
If you want to relocate these locals to 900, you will need to run the mvchannels script (w/ MN locals in your channels.dat to move them)
If you want to have NY and LA locals, then you will NEED to run the mvchannels script. (But STILL, the advantage of doing it this way is that you won't have to include your own locals in your channels.dat anymore IF YOU JUST WANT THEM TO BE IN THE 2-99 RANGE.) This is exactly how I do it right now as I have my MN locals in the 2-99 range and my NY and LA locals in the 900s range. Since the more line you have in yout channels.dat, the more the mvchannels.tcl needs to do, it is advantages to just let the MN locals to show up NATURALLY in 2-99.
Below is a sample of what i have in my channels.dat
# Format---
# Name : Number : Alt.Num : fsid : subobjid : [0,1,2]
#
# 0 - Hide channel
# 1 - Map to 0-99 channel number
# 2 - Map to 900s channel number
# # - Comment out to ignore
#
LA2:2:938:2859:1796:2
LA4:4:939:2859:1798:2
LA5:5:940:2859:2270:2
LA7:7:941:2859:1800:2
LA9:9:942:2859:1802:2
LA11:11:943:2859:1525:2
NY2:2:880:2859:1742:2
NY4:4:881:2859:1744:2
NY5:5:882:2859:1745:2
NY7:7:883:2859:1746:2
Notice I don't have any MN locals there.
Now if you want to have all of your locals in your 900s range, then of course you will have to include those MN locals in the channals.dat.
But anyway you won't have those damn Miami locals popping up in your 2-99 range if you follow the procedures.
AlphaWolf
01-31-2002, 11:59 PM
Note that selectlocals.tcl only needs to be run once, and its changes last through reboots. It does not loop, and there is no need whatsoever to add it to rc.sysinit. When you run it the first time, the channels appear instantly when the script completes, no waiting about 2 hours or so for the channels to show up normaly.
Also I will state again, that it doesn't do you any good to add the 4 NY channels, nor the LA channels (with the exception of 5 and 9) as they are nothing but duplicate feeds of the national broadcasts of east and west ABC, NBC, FOX, and CBS. (in fact it would behoove you to remove them even if you live in LA or NY since it reduces the overhead of the extra channels being in the guide)
If you want a small example, see what differences you can spot between LA4 and 383 ;)
TheBigDog
02-01-2002, 12:45 AM
I have never used Selectlocal.tcl and maybe someone could educate me. So if I am using EMU and if I use the script to select MN, will Miami locals appear together w/ MN locals at the 2-99 range?
dtv killer
02-01-2002, 11:28 AM
Orpheus
02-02-2002, 12:11 AM
I use emu too and have used selectlocals.tcl but couldn't get rid of the MI local feed. I removed selectlocals and made the changes that BD describes and voila, no locals but the ones I want. It seems that selectlocals.tcl works fine if you don't use emu, but if you do you'll want to check out the changes made in this thread.
Thanks again BD,
O
TheBigDog
02-02-2002, 01:57 PM
I am glad that it is working out for you, Orpheus. :)
TheBigDog
02-04-2002, 12:55 AM
'
JustCuz
03-12-2002, 11:03 AM
Originally posted by Orpheus
I use emu too and have used selectlocals.tcl but couldn't get rid of the MI local feed. I removed selectlocals and made the changes that BD describes and voila, no locals but the ones I want. It seems that selectlocals.tcl works fine if you don't use emu, but if you do you'll want to check out the changes made in this thread.
Thanks again BD,
O
The MI feed, at least on my machine, was the result of using an FF locals byte. Clear the locals byte to 00, and the MI channels go away. Hope this helps!
vBulletin® v3.7.3, Copyright ©2000-2008, Jelsoft Enterprises Ltd.