DaddyLive, PlutoTV, XUMO, M3U/XMLTV, SamsungTV, Plex, TVGuide interfaces (appliance)

Sterling Rorden

I was thinking about giving this a try but I have some questions.

My Tvheadend server runs on Ugoos X3 Cube running CoreELEC 19. Will this be usable in CoreELEC?

I currently use Tvheadend for my local OTA channels. But I live in a fringe reception area and sometimes the signal strength drops too low. OTA would be my preferred method of watching/recording with Locast as a backup.

How would the redundant channel numbers be dealt with in the guide?

Sterling Rorden

Interesting!
I'll have to read up on how to install it on CoreELEC. I may be able to stumble through it.
Thanks

Sterling Rorden

Any suggestion on which Entware Python3 package I should install? I'd like to keep the installation light but I don't want cause problems by leaving something out that is needed. I was thinking the Python3-light package.

Sterling Rorden

OK, so I really don't know what I'm doing but I'm trying.

I installed Entware and Python3-light.
I downloaded the source file tvheadend-locast-0.8.5.zip and unzipped it to /storage/tvheadend-locast.

I edited config_example.ini with my Locast username and password and saved it as config.ini in the /storage/tvheadend-locast folder.

When I issue the "python3 tvh_main.py" command (I've SSH'd in using Putty) from the tvheadend-locast folder I get the following error:

CoreELEC:~/tvheadend-locast # python3 tvh_main.py
Traceback (most recent call last):
File "/storage/tvheadend-locast/tvh_main.py", line 10, in <module>
from lib import main
File "/storage/tvheadend-locast/lib/main.py", line 20, in <module>
import logging

ModuleNotFoundError: No module named 'logging'

Did I do the folder extraction and location placement correctly?

Sterling Rorden

I may have got it installed correctly or I may not have. If I had to do it over again I would have installed the complete Python3 version, there were a lot of missing modules.

I was getting errors when I tried to install the '_ssl' module so I tried it without the '_'. It seemed like it tried to reinstall Python3. However, I no longer got any missing module errors when I ran the 'python3 tvh_main.py' command.

But I did get the errors below:
CoreELEC:~/tvheadend-locast # python3 tvh_main.py
Unable to load pip module to install upgrades
Unable to load cryptography module, will not encrypt passwords
2021-06-05 07:02:02,177-WARNING:main #########################################
2021-06-05 07:02:02,177-WARNING:main MIT License, Copyright (C) 2021 ROCKY4546

2021-06-05 07:02:02,289-ERROR:authenticate locast Unable to login due to invalid logins. Clear config entry login_invalid to try again

Do I keep the '< >' around the username and password in the config.ini file?

When I enter URL http://[IP]:6077/ I get to the cabernet page and can get to the XML/JSON links.

Should I try to integrate into Tvheadend or do I have some problems I need to resolve first?

Thanks

Sean Micklem

I'm just a user like yourself but the issue with the cryptography module is discussed earlier in this thread, but basically you don't really need it, it just adds extra security if you have it. It is completely optional. See https://tvheadend.org/d/7455-daddylive-plutotv-xumo-m3u-xmltv-samsungtv-plex-tvguide-interfaces-appliance?r=44150#message-44150

Don't know about the pip module thing in CoreELEC but did you tryopkg install python3-pip ? May not be anything that obvious but worth a shot, although I have no idea how much space it takes up. But you don't need it if you have no interest in the cryptography. If you do install pip, then you should be able to dopip3 install cryptography to get the cryptography module.

Youdo not keep the angle brackets. For the username you use the email address that you log into the Locast site with, and for the password you use the password. But no angle brackets. A previous message in this thread mentions how to clear login_invalid (see next to last paragraph at https://tvheadend.org/d/7455-daddylive-plutotv-xumo-m3u-xmltv-samsungtv-plex-tvguide-interfaces-appliance?r=44145#message-44145), but it's just an entry in your config.ini file that you have to delete AFTER fixing your username and password. Once you get all that fixed you should be good to go.

Hope this helps. I suggest scrolling through the previous posts, right now this thread is only five pages long so it shouldn't take that long and it may help answer your current and even possibly some future questions.

Sterling Rorden

I saw the cryptography comment but I didn't realize that was associated with pip. I don't need cryptography so I won't worry about not being able to install pip module.

I got my login fixed, thanks.

I guess I'm on to integrating into Tvheadend.

Sterling Rorden

I have some questions about setting up the grabber.

How do I use the tv_grab_url file? Will it work on my CoreELEC box? Do I just copy and paste the text into a file? Where do I put the file and does it matter what I name it?

I already use Zap2EPG for my OTA EPG data. Should I just continue to use that for Locast also since the data is the same?

Thanks

Sean Micklem

G Kazaroth wrote:

> Next the tv_grab_url is located where all the tv_grab* files are located. If you go to the tvheadend > Configuration > Channel/EPG > EPG Grabber Modules, The PATH variable normally shows where the files are located. This is normally found in the /usr/bin directory. After you place the file in the folder, restart tvheadend to pick up the file.

To be a bit more clear about that, if you go to tvheadend > Configuration > Channel/EPG > EPG Grabber Modules, in the left hand pane you will see a list of EPG Grabbers, all of which should be disabled (have an orange dot next to them) except the ones that are enabled (those will have a green dot with a check mark ✔ inside next to them). On my system, the one I have enabled is called "Internal: XMLTV: tv_grab_file is a simple grabber that just read the ~/.xmltv/tv_grab_file.xmltv file" and the path is /usr/bin. That just means that there is a script called tv_grab_file in the /usr/bin directory, but that script is looking for a file at ~/.xmltv/tv_grab_file.xmltv. In this case the ~ refers to tvheadend's user, not your user, which is normally the hts user unless you have changed it. So in reality it's looking for a file called /home/hts/.xmltv/tv_grab_file.xmltv. So what you have to do is copy or move the xmltv.xml file to that location and then run the grabber. For example, one way to do that would be this (the first line assumes that Tvheadend runs as the hts user):

sudo su hts
cd /home/hts/.xmltv
wget -q --retry-connrefused --tries=5 --timeout=180 http://server_ip_address:6077/xmltv.xml

mv -f xmltv.xml tv_grab_file.xmltv

Replace server_ip_address so the URL is correct. After doing all that then you have to run the internal grabber in Tvheadend - you can do that by going to tvheadend > Configuration > Channel/EPG > EPG Grabber and click the button that says "Re-run Internal EPG Grabbers".

If that works then you can automate the process by putting the above commands in a shell script (you may need to specify full paths to the commands and files in that case) but instead of puttingsudo su hts in the script itself, you'd instead run the script as the hts user. What I'd do is become the hts user (usingsudo su hts) and then usecrontab -e to create a cron job that would run as the hts user, and have that run the script at whatever time you like. Then I'd set up Tvheadend to grab the file, by going to tvheadend > Configuration > Channel/EPG > EPG Grabber and in the "Internal Grabber" section, in the box that says "Cron multi-line" set the time for it to run the grabber, which would be maybe 15 minutes or a half hour after you run wget (to give it time for the download to complete), using the same time format you would use when creating a Cron job.

But that is just one way to do it, and maybe not the best way. There is another method that uses sockets. Quite some time back I found an article that discusses both methods at https://freetoairamerica.wordpress.com/2014/12/03/some-hints-for-getting-free-to-air-satellite-channels-into-the-electronic-program-guide-in-kodi-or-xbmc-or-another-frontend/ (that article primarily discusses the use of zap2xml) but since I already had it set up to use the grabber file I never bothered with the sockets method.

Tvheadend has a lot of moving parts, so to speak, and this is one area where it can get really confusing if you don't understand how all the parts work together. There may be an easier way to do this but if so I'm not aware of it.

EDIT: You may wonder why I'm not using the grabber mentioned in item 2 of the first post in this thread. It's partly because I'm already familiar with using tv_grab_file, but also because the instructions for using that one just aren't complete enough. For one thing the screenshot is so small as to be unreadable, but for another that grabber doesn't just automatically show up in Tvheadend's list of grabbers. I am guessing that at a minimum you'd need to copy that grabber file to the /usr/bin directory (and make sure it is executable and owned by the root user) and then restart Tvheadend before Tvheadend would even find it. But I am not certain of that. If that's all that is required then it could simplify things, I just wish that screenshot were about two or three times larger, so you could actually read it. But I tend to stick to what I am familiar with.

Sterling Rorden

Sean Micklem wrote:
> G Kazaroth wrote:
> > Next the tv_grab_url is located where all the tv_grab* files are located. If you go to the tvheadend > Configuration > Channel/EPG > EPG Grabber Modules, The PATH variable normally shows where the files are located. This is normally found in the /usr/bin directory. After you place the file in the folder, restart tvheadend to pick up the file.
>
> To be a bit more clear about that, if you go to tvheadend > Configuration > Channel/EPG > EPG Grabber Modules, in the left hand pane you will see a list of EPG Grabbers, all of which should be disabled (have an orange dot next to them) except the ones that are enabled (those will have a green dot with a check mark ✔ inside next to them). On my system, the one I have enabled is called "Internal: XMLTV: tv_grab_file is a simple grabber that just read the ~/.xmltv/tv_grab_file.xmltv file" and the path is /usr/bin. That just means that there is a script called tv_grab_file in the /usr/bin directory, but that script is looking for a file at ~/.xmltv/tv_grab_file.xmltv. In this case the ~ refers to tvheadend's user, not your user, which is normally the hts user unless you have changed it. So in reality it's looking for a file called /home/hts/.xmltv/tv_grab_file.xmltv. So what you have to do is copy or move the xmltv.xml file to that location and then run the grabber. For example, one way to do that would be this (the first line assumes that Tvheadend runs as the hts user):
>
> sudo su hts
> cd /home/hts/.xmltv
> wget -q --retry-connrefused --tries=5 --timeout=180 http://server_ip_address:6077/xmltv.xml > mv -f xmltv.xml tv_grab_file.xmltv
>
> Replace server_ip_address so the URL is correct. After doing all that then you have to run the internal grabber in Tvheadend - you can do that by going to tvheadend > Configuration > Channel/EPG > EPG Grabber and click the button that says "Re-run Internal EPG Grabbers".
>
> If that works then you can automate the process by putting the above commands in a shell script (you may need to specify full paths to the commands and files in that case) but instead of puttingsudo su hts in the script itself, you'd instead run the script as the hts user. What I'd do is become the hts user (usingsudo su hts) and then usecrontab -e to create a cron job that would run as the hts user, and have that run the script at whatever time you like. Then I'd set up Tvheadend to grab the file, by going to tvheadend > Configuration > Channel/EPG > EPG Grabber and in the "Internal Grabber" section, in the box that says "Cron multi-line" set the time for it to run the grabber, which would be maybe 15 minutes or a half hour after you run wget (to give it time for the download to complete), using the same time format you would use when creating a Cron job.
>
> But that is just one way to do it, and maybe not the best way. There is another method that uses sockets. Quite some time back I found an article that discusses both methods at https://freetoairamerica.wordpress.com/2014/12/03/some-hints-for-getting-free-to-air-satellite-channels-into-the-electronic-program-guide-in-kodi-or-xbmc-or-another-frontend/ (that article primarily discusses the use of zap2xml) but since I already had it set up to use the grabber file I never bothered with the sockets method.
>
> Tvheadend has a lot of moving parts, so to speak, and this is one area where it can get really confusing if you don't understand how all the parts work together. There may be an easier way to do this but if so I'm not aware of it.
>

> EDIT: You may wonder why I'm not using the grabber mentioned in item 2 of the first post in this thread. It's partly because I'm already familiar with using tv_grab_file, but also because the instructions for using that one just aren't complete enough. For one thing the screenshot is so small as to be unreadable, but for another that grabber doesn't just automatically show up in Tvheadend's list of grabbers. I am guessing that at a minimum you'd need to copy that grabber file to the /usr/bin directory (and make sure it is executable and owned by the root user) and then restart Tvheadend before Tvheadend would even find it. But I am not certain of that. If that's all that is required then it could simplify things, I just wish that screenshot were about two or three times larger, so you could actually read it. But I tend to stick to what I am familiar with.

Thanks, but this sounds a little beyond my skillset at this point. But, I agree, it would be better if you could see the example image.

Sterling Rorden

I've made some progress. The Locast channels show up in my Kodi Tvheadend client and they will play. However, the channel numbers start at 10000 and increase sequentially from there but not in actual channel number order. Are they supposed to be that way? The correct channel number does show up in the description.

But the EPG is not populating. I copied the text of the tv_grab_url file into a text file called tv_grab_url and saved it in the same location as the other tv_grab* files. I've enabled it in the EPG Grabber Modules tab, left the Priority as 3 (Zap2EPG has a Priority of 5), put http://[HOST]/xmltv.xml in the Extra arguments field, and re-ran the internal grabbers. It looks like there may be some extra characters in the example screenshot but I can't read them. And no Locast channels are showing up in the EPG Grabber Channels tab as far as I can tell. Locast channels do show up in the main channels tab.

Also, what would be the best way to automatically start Tvheadend-locast when I reboot CoreELEC? I'm assuming I can put the command in an autostart.sh file (any hints on the syntax?) but don't know if that is the proper way. I saw the locast.service file but I don't know if I'm knowledgeable enough to use it or if it will work on CoreELEC.

Thanks

Sterling Rorden

I'm talking about the Tvheadend client addon in Kodi having channel numbers that start from 10000, both in the Channels view and the EPG (it looks similar to your TVGUIDE screenshot but the numbers are in the 10000s and there is no show data).

The tvheadend server web interface is showing all the Locast channel numbers as 0 in the Channels tab. The EPG source field is blank.

Sterling Rorden

I'm assuming that's a space between -u and http://your ip address:6077/xmltv.xml.

The TVHeadend log shows:

2021-06-06 14:51:27.813 xmltv: /storage/.kodi/addons/service.tvheadend42/bin/tv_grab_url: grab /storage/.kodi/addons/service.tvheadend42/bin/tv_grab_url
2021-06-06 14:51:27.824 spawn: Executing "/storage/.kodi/addons/service.tvheadend42/bin/tv_grab_url"
2021-06-06 14:51:27.833 spawn: /storage/.kodi/addons/service.tvheadend42/bin/tv_grab_url: line 6: can't open 1: no such file
2021-06-06 14:51:27.841 spawn: wget: unrecognized option '--retry-connrefused'
2021-06-06 14:51:27.844 spawn: BusyBox v1.32.1 (2021-06-06 11:42:06 CEST) multi-call binary.
2021-06-06 14:51:27.844 spawn: Usage: wget [-c|--continue] [--spider] [-q|--quiet] [-O|--output-document FILE]
2021-06-06 14:51:27.844 spawn: [-o|--output-file FILE] [--header 'header: value'] [-Y|--proxy on/off]
2021-06-06 14:51:27.844 spawn: [--no-check-certificate]
2021-06-06 14:51:27.844 spawn: [-P DIR] [-S|--server-response] [-U|--user-agent AGENT] [-T SEC] URL...
2021-06-06 14:51:27.844 spawn: Retrieve files via HTTP or FTP
2021-06-06 14:51:27.844 spawn: --spider Only check URL existence: $? is 0 if exists
2021-06-06 14:51:27.844 spawn: --no-check-certificate Don't validate the server's certificate
2021-06-06 14:51:27.844 spawn: -c Continue retrieval of aborted transfer
2021-06-06 14:51:27.844 spawn: -q Quiet
2021-06-06 14:51:27.844 spawn: -P DIR Save to DIR (default .)
2021-06-06 14:51:27.844 spawn: -S Show server response
2021-06-06 14:51:27.844 spawn: -T SEC Network read timeout is SEC seconds
2021-06-06 14:51:27.844 spawn: -O FILE Save to FILE ('-' for stdout)
2021-06-06 14:51:27.844 spawn: -o FILE Log messages to FILE
2021-06-06 14:51:27.844 spawn: -U STR Use STR for User-Agent header
2021-06-06 14:51:27.844 spawn: -Y on/off Use proxy
2021-06-06 14:51:27.845 xmltv: /storage/.kodi/addons/service.tvheadend42/bin/tv_grab_url: no output detected

2021-06-06 14:51:27.845 xmltv: /storage/.kodi/addons/service.tvheadend42/bin/tv_grab_url: grab returned no data

When I type the command: ./tv_grab_url -u http://192.168.1.83:6077/xmltv/xml

I get the below response:

CoreELEC:~/.kodi/addons/service.tvheadend42/bin # ./tv_grab_url -u http://192.168.1.83:6077/xmltv/xml ./tv_grab_url: line 6: can't open 1: no such file
wget: unrecognized option '--retry-connrefused'

BusyBox v1.32.1 (2021-06-06 11:42:06 CEST) multi-call binary.

[-P DIR] [-S|--server-response] [-U|--user-agent AGENT] [-T SEC] URL...

Retrieve files via HTTP or FTP

--spider Only check URL existence: $? is 0 if exists
--no-check-certificate Don't validate the server's certificate
-c Continue retrieval of aborted transfer
-q Quiet
-P DIR Save to DIR (default .)
-S Show server response
-T SEC Network read timeout is SEC seconds
-O FILE Save to FILE ('-' for stdout)
-o FILE Log messages to FILE
-U STR Use STR for User-Agent header

-Y on/off Use proxy

Line 6 of my tv_grab_url file is:

if (( $# < 1 ))

C Island

I think you have a 'slash' instead of a period

Try this:

./tv_grab_url -u http://192.168.1.83:6077/xmltv.xml

Sterling Rorden

G Kazaroth wrote:
> Thank you for the information and working this. The change will help others using minimal Linux OSes. It looks like the wget executable for CoreELEC does not have the options, so I can make a change and have you pull it down to try it, or you can make the change yourself which is probably the simple answer. If you can change the line in the grabber file where the "wget" command is from
>
> wget -q --retry-connrefused --tries=5 --timeout=20 -O - $url
>
> to
>
> wget -q -T 20 -O - $url
>

> According to the Usage statement above, that should work. Let me know if you get the data dump.

First, thanks for your help! I don't mind doing what little I can do to help. It's nothing compared to what you've done.

I'm now just getting the following error:

CoreELEC:~/.kodi/addons/service.tvheadend42/bin # ./tv_grab_url -u http://192.168.83:6077/xmltv.xml ./tv_grab_url: line 6: can't open 1: no such file

wget: download timed out

One thing. This may sound stupid but I couldn't figure out how to directly download the file from Github. I used Windows to cut and paste the text into WinSCP text editor to create the file. I've had problems before where using Windows to copy has caused problems. Could this be the problem?

Sterling Rorden

C Island wrote:
> I think you have a 'slash' instead of a period
> Try this:
>

> ./tv_grab_url -u http://192.168.1.83:6077/xmltv.xml

Yea, I pasted the wrong section into the message above but I did try with the ".".

Sterling Rorden

G Kazaroth wrote:
> It is very possible that the editor you used added a control-M to the end of the line. I ran a test with the ctrl-M and got a WARNING in the cabernet log
>
> WARNING: "GET /xmltv.xml%0D HTTP/1.1" 501 -
>
> Since some windows editor add Ctrl-Ms to the end of the line, you could have this issue. Check the cabernet log to see what happened. It looks like the wget command worked, but got an unknown response from cabernet. If this is true, you probably need to learn a little vi since you are working in linux. Here is a brief list of commands once you "vi file"
> :q! quits without saving
> :qw writes updates and then quits
> ctrl-G goto end of file
> shift-A goto end of line
> ESC exit editor mode
> x deletes current character
> i starts insert mode
> dd deletes current line
> yy copies current line

> p pastes line from yy

I opened the cabernet.log file in the data/logs folder but it is empty.

I tried re-running the internal EGP grabbers to see what it would do. It got stuck in a loop and kept repeating the following information in the Tvheadend log:

2021-06-06 17:49:57.869 subscription: 0025: No input source available for subscription "127.0.0.1 [ | Kodi Media Center ]" to channel "29.1L ION"
2021-06-06 17:49:59.869 subscription: 0025: No input source available for subscription "127.0.0.1 [ | Kodi Media Center ]" to channel "29.1L ION"
2021-06-06 17:50:00.653 http: 127.0.0.1: HTTP/1.1 HEAD /imagecache/15 -- 404
2021-06-06 17:50:01.904 subscription: 0025: No input source available for subscription "127.0.0.1 [ | Kodi Media Center ]" to channel "29.1L ION"
2021-06-06 17:50:03.635 http: 127.0.0.1: HTTP/1.1 HEAD /imagecache/19 -- 404
2021-06-06 17:50:03.904 subscription: 0025: No input source available for subscription "127.0.0.1 [ | Kodi Media Center ]" to channel "29.1L ION"
2021-06-06 17:50:05.910 subscription: 0025: No input source available for subscription "127.0.0.1 [ | Kodi Media Center ]" to channel "29.1L ION"
2021-06-06 17:50:06.645 http: 127.0.0.1: HTTP/1.1 HEAD /imagecache/15 -- 404
2021-06-06 17:50:07.933 subscription: 0025: No input source available for subscription "127.0.0.1 [ | Kodi Media Center ]" to channel "29.1L ION"
2021-06-06 17:50:09.741 http: 127.0.0.1: HTTP/1.1 HEAD /imagecache/19 -- 404
2021-06-06 17:50:09.933 subscription: 0025: No input source available for subscription "127.0.0.1 [ | Kodi Media Center ]" to channel "29.1L ION"
2021-06-06 17:50:11.933 subscription: 0025: No input source available for subscription "127.0.0.1 [ | Kodi Media Center ]" to channel "29.1L ION"
2021-06-06 17:50:12.665 http: 127.0.0.1: HTTP/1.1 HEAD /imagecache/15 -- 404
2021-06-06 17:50:13.933 subscription: 0025: No input source available for subscription "127.0.0.1 [ | Kodi Media Center ]" to channel "29.1L ION"
2021-06-06 17:38:10.310 subscription: 0025: No input source available for subscription "127.0.0.1 [ | Kodi Media Center ]" to channel "29.1L ION"

2021-06-06 17:38:12.299 http: 127.0.0.1: HTTP/1.1 HEAD /imagecache/15 -- 404 ....

I opened the tv_grab_url file in vi but I don't know how to tell if something is wrong.

Sean Micklem

Just a couple of general thoughts here worth mentioning, although they may not be all that helpful, but on the off chance...

First, don't just assume that CoreELEC includes bash. Some lightweight, single purpose distributions are built around BusyBox or something similar and only include the sh shell. sh is rather limited compared to bash, so a script written for bash may or may not run in sh (or whatever shell CoreELEC includes). I would enterwhich bash at a command prompt; if bash is installed it should show a path such as /usr/bin/bash on the following line. If nothing is printed, that means bash is not installed, or is not in your path, and that means some scripts will break.

Second, if you have a file and you are not sure whether it contains Windows-style line endings, you can run the dos2unix command on it. I believe the proper syntax is simplydos2unix filename but I would runman dos2unix to be certain. dos2unix is included in many Linux distributions, or can be added from a distribution's repositories, and you can runwhich dos2unix to see if you already have it. I think it may even be included in Windows now, but I don't use Windows at all, so can't be certain of that. It's a lot easier than manually searching for ^M characters or something similar (also, if you are like me and prefer nano to vi, you don't have to learn a different editor).

Sterling Rorden

Good progress.

I copied tv_grab_url v 0.8.6a over and ran dos2unix on it (CoreELEC has both bash and dos2unix).

I still get the line 6 no such file error when I re-run the internal EPG grabbers. The cabernet log has the following at the same time:

2021-06-07 07:27:24,629-INFO:web_handler [192.168.1.83] "GET /xmltv.xml HTTP/1.1" 200 -

However, the EPG is populating and things seem to work correctly. I can view shows, record shows, set timers, etc.

My channel numbers still start with 10000 in the Kodi Tvheand client and don't corelate with the actual channel numbers, but I can work around that if necessary.

I'm assuming the best way to get cabernet to run on system restart is to create an autostart.sh file with the correct command, correct?

Thanks guys for all your help!

Sterling Rorden

G Kazaroth wrote:
> I think I have answers.
>
> 1) channels in Kodi EPG have 10000 numbers.
> Follow step 3 and add channel numbers to the number column in TVHeadend
>
> 2) You may have OTA grabbers enabled.
> I noticed in your log that tvheadend is running scans. This is normally associated with OTA grabbers. In the old days, stations would broadcast tvguide data over the channel itself and could be obtained directly from the station instead of going to zap2it or the like. This is no longer happening and it just causes the tuner to use up streams. Recommend disabling all OTA grabbers in the "EPG Grabber Modules" tab.
>
> 3) Still getting the line 6 no such file error.

> I agree with Sean. Based on some tests it looks like you do not have BASH shell installed on CoreELEC at the location in the script. type "which bash" and see if it is located at /bin/bash. This is where the script expects to find the executable. If you find it elsewhere, copying it to the /bin location will correct the issue.

1) I'm assuming you mean manually add the channel numbers (don't mind - just want to be clear). However, I have a question. What would happen if I use the same channel numbers as the corresponding OTA channels and record the same show both OTA and from Locast? I want to mainly use OTA for recordings but have Locast be a backup incase my reception drops.

2) I currently have an OTA grabber running as low priority but will disable it.

3) The command "which bash" returns the following:
/usr/bin/bash
Can I just change the first line in the script to "#!/usr/bin/bash"?

« Previous Page Next Page »