<br clear="all">"Faithless is he, that says 'farewell', when the path darkens."<br><br>
<br><br><div class="gmail_quote">On Tue, Jun 19, 2012 at 9:13 AM, John Pilkington <span dir="ltr"><<a href="mailto:J.Pilk@tesco.net" target="_blank">J.Pilk@tesco.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 19/06/12 13:31, Brian Sanders wrote:<br>
<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
On Tue, Jun 19, 2012 at 8:11 AM, John Pilkington <<a href="mailto:J.Pilk@tesco.net" target="_blank">J.Pilk@tesco.net</a><br></div><div class="im">
<mailto:<a href="mailto:J.Pilk@tesco.net" target="_blank">J.Pilk@tesco.net</a>>> wrote:<br>
<br>
On 19/06/12 12:45, Brian Sanders wrote:<br>
<br>
I am running .25 pulled again last night, and complied on CentOS<br>
6.2.<br>
<br>
<br>
You make this sound routine. Do you have a custom build<br>
script/environment?<br>
</div></blockquote>
<br><div class="im">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I don't have a custom script, but I did bang my head against it for a<br>
weekend before I got my CentOS 6 environment compiling. I have pulled<br>
specific files from multiple different repos, and had to specify some<br>
environment variables until it would finally compile. I just figured<br>
once I got it working it would be worth it so I could pull and<br>
re-compile to test for bugs. Last night was my first re-compile and I<br>
did need to run "./configure --qmake=/usr/lib64/qt47/bin/<u></u>qmake" to tell<br>
it which qmake to use.<br>
<br>
Looking back, it might have been a good idea to keep notes, a blog,<br>
wiki, or something about what I did do. I just assume most people will<br>
use the repos that seem to be working now.<br>
</blockquote></blockquote>
<br></div>
I've tried to convert from top-posting, which gets unfavourable responses here :-)<br>
<br>
Yes: I use ATrpms and SL6, but Axel clearly has more on his plate than he used to, and the current build dates from early May. I just wondered if you had an easy alternative.<div><div class="h5"><br>
<br></div></div></blockquote><div><br></div><div>Oops, I'll try and switch up my posting :)</div><div><br></div><div>No I don't have a simple solution. My box now will compile so it now is simple, but if it were to die getting it back to the correct configuration would be a hassle I am sure.</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
In my attempts to understand the channels I think I am seeing<br>
a bug in<br>
importing previous channel scans. I'll try and explain what I<br>
am doing<br>
and see if anyone knows if this is me or a bug I should file.<br>
<br>
I have a new FiOS setup, and just trying to see what my<br>
HDHomerun can<br>
find. When I run mythtv-setup, I find my tuner and do a scan to<br>
find<br>
channels. This takes HOURS to run, but at the end it finds<br>
channels of<br>
multiple different types (DVB, ATSC, MPEG, etc). It even finds some<br>
"conflicting" channels. Not being 100% sure I added everything<br>
it found<br>
to the list. Then I hit the button to fetch from my schedules<br>
direct<br>
account, which as I understand it should try and map the XMLID<br>
tags to<br>
my channels. I end up with very few channels having XLMID tags<br>
and some<br>
that are repeated across multiple channels.<br>
<br>
Not fully understanding what all the different types of channels<br>
are, I<br>
decided to delete all channels with the channel editor. This<br>
works as<br>
expected, and I was going to just import one type of channel and see<br>
what they are. Instead of scanning, I select to import from a<br>
previous<br>
scan. It shows the scan I did just prior and this time I select to<br>
import only the ATSC (the first ones it finds) and deny all the<br>
rest. I<br>
even told it to delete XYZ number of "unused" transports. This<br>
is where<br>
the bug seems to be through. No matter what I do, nothing is ever<br>
imported from my previous scan. I have tried importing<br>
EVERYTHING like<br>
I did after the scan was successful, I have tried only importing<br>
some<br>
types, and nothing changes. After doing the "import" the screen is<br>
blank looking and hitting finish and going to the channel editor<br>
shows<br>
no channels.<br>
<br>
<br>
I use dvb-t and importing previous scans seems useless; it doesn't<br>
touch the contents of the Transports screen. I know that I need 5<br>
(for SD) or 6 (for HD as well) transports, and I know which they<br>
are, and can use the linking mechanism. I can't now enter them from<br>
the keyboard but I can delete any that I don't want. I'm in the UK.<br>
<br>
Maybe something in Ticket #10217 will help?<br>
<br>
<br>
I finally decided last night to try one more full scan. This time I<br>
imported Everything except the conflicting channels. Sure<br>
enough the<br>
full scan adds all the channels I asked for, but alas my XLMTV<br>
ID's are<br>
still very far from correct. I also avoided importing "conflicting"<br>
channels this last time, so I really don't know if I missed any<br>
channels<br>
as I am not really sure what hundreds of "unused" transports,<br>
DVB/ATSC/MPEG/SETC/ etc is telling me.<br>
<br>
I would just play around with this more to try and figure out<br>
what all<br>
these things are, but scanning takes multiple hours and it seems<br>
that<br>
importing the same scan multiple times is just not working. Between<br>
doing the 2 scans last night, I pulled from git again, did a<br>
make dist<br>
clean, and re-compiled and installed my mythtv to try and ensure<br>
this<br>
wasn't already fixed. It still wouldn't import, and that is<br>
when I did<br>
a second scan to try and get some channel data back.<br>
<br>
So I guess in summary my issues are...<br>
<br>
1) Importing previous scans seems to fail (and costs many hours<br>
to re-do)<br>
2) with my FiOS I really don't know what the different types are...<br>
which ones should I import?<br>
3) What are conflicting channels and "unused" transports?<br>
4) How do XMLID tags get matched to Schedules Direct? Matching<br>
most my<br>
channels by hand could take a lot of time. Is there some<br>
mapping that<br>
others might have found, or if I do this by hand can I somehow<br>
keep my<br>
mappings so others can benefit from my time doing it?<br>
<br>
I have a HDHomerun Prime that I will be testing once I feel<br>
comfortable<br>
with my HDHomerun and FiOS. I just didn't want to mess with the<br>
cable<br>
card and getting that setup until I at least am familiar with<br>
the setup<br>
process. It has been a few years since I have run my mythtv at<br>
home.<br>
<br>
</blockquote>
<br>
</div></div><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
So you are saying that importing previous scans doesn't seem to work for<br>
you either? I would really like to play around with (or have find<br>
an explanation of) the different types of channels and "transports." I<br>
just can't possibly spend 2+ hours scanning for each iteration I want<br>
to explore.<br>
</blockquote></blockquote>
<br></div>
Yes. I haven't been able to use it. I don't know how much code is shared for DVB-T and FiOS and I really don't know how HDHR or FiOS work, but in my last test I had to do a full scan, with no transports defined, then delete unwanted transports and all channels, and then do a linked scan of all known transports. I don't know if you could do something similar. Prior knowledge of the transport structure is a great help, and the terminal output of mythtvsetup during and after a scan is informative.<div class="HOEnZb">
<div class="h5"><br>
<br></div></div></blockquote><div><br></div><div>How do you know what an "unwanted" transport is? I guess you probably have more familiarity with the signiling side than I do currently. My knowledge stops at... I expect QAM on my unencrypted channels... and I assume Transports to be different frequency ranges for the different channels?</div>
<div><br></div><div>Also you mention a linked scan? I have only done a full scan, and attempted to import a scan. Is a linked scan another option that perhaps I can try? What does it do differently?</div><div><br></div>
<div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">
<br>
<br>
______________________________<u></u>_________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org" target="_blank">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/<u></u>listinfo/mythtv-users</a><br>
</div></div></blockquote></div><br>