<div class="gmail_quote">2012/5/30 Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com" target="_blank">mtdean@thirdcontact.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 05/30/2012 03:03 AM, Thomas Pontoppidan wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2012/5/29 Michael T. Dean<div><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 05/29/2012 03:36 AM, Thomas Pontoppidan wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
During this weekend I finally chose to reinstall my backend - moving from<br>
an old Fedora install to MythBuntu. For different reasons I decided to go<br>
against recommendations and not move the entire database. I only<br>
transferred my recordings following this guide<br>
<a href="http://www.mythpvr.com/mythtv/tips/migrate-recordings.html" target="_blank">http://www.mythpvr.com/mythtv/<u></u>tips/migrate-recordings.html</a><br>
.<br>
<br>
</blockquote>
Yes. Google should be kicked off the Internet for allowing that ancient,<br>
outdated, incorrect, can-corrupt-the-db-data (as it can completely break<br>
your character encoding) post to be #1.<br>
</blockquote>
<br>
Well, I won't blame Google - after all it was my decision to not follow<br>
official directions:-)<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
From a normal frontend the recordings are playing fine, but HLS doesn't<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
seem to work - I try to stream to Torc for IOS, but the "prepare stream"<br>
stays at 0%. If I make a new recording it streams fine so I'm guessing some<br>
new fields in the recordings table are missing? Is there any way to add the<br>
missing info (if my assumption is correct) to the database?<br>
<br>
</blockquote>
Best solution is to do a proper restore of your complete pre-upgrade<br>
database and let MythTV Do The Right Thing.<br>
<br>
</blockquote>
Looking back that is probably what I *should* have done, but I am not sure<br>
I'm up for that now - I spent most of a day setting up the new database,<br>
mostly because I wasn't satisfied with the old setup (non-standard<br>
keybindings,<br>
</div></blockquote>
<br>
can be reset to defaults by going into mythfrontend Utilities/Setup|Edit Keys, then using MENU to select "Reset All Keys to Defaults" ( <a href="http://www.gossamer-threads.com/lists/mythtv/commits/487153#487153" target="_blank">http://www.gossamer-threads.<u></u>com/lists/mythtv/commits/<u></u>487153#487153</a> ) on any frontend whose key bindings you want to reset.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
bad tuner setup,<br>
</blockquote>
<br>
which could have been reset/cleared by using mythtv-setup to do a "Delete all capture cards"<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
flawed channel lists etc.).<br>
</blockquote>
<br>
and a "Delete all video sources" (not "Delete all video sources on <hostname>").<div><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Going back would<br>
require me to do it all over again:-)<br>
</blockquote>
<br></div>
But would make the rest of your system function properly--and without any concerns over the integrity of your database schema or data.<div><br>
<br>
<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">
If you decide you want to waste hours re-configuring everything for no<br>
benefit, at least do a proper partial restore:<br>
<a href="http://www.mythtv.org/wiki/Database_Backup_and_Restore#Partial_restore_of_a_backup" target="_blank">http://www.mythtv.org/wiki/<u></u>Database_Backup_and_Restore#<u></u>Partial_restore_of_a_backup</a> (and take note of<br>
<a href="http://www.mythtv.org/wiki/Database_Backup_and_Restore#Partial_restore_when_upgrading_MythTV" target="_blank">http://www.mythtv.org/wiki/<u></u>Database_Backup_and_Restore#<u></u>Partial_restore_when_<u></u>upgrading_MythTV</a>).<br>
<br>
</blockquote>
I already did reconfigure the entire setup and according to the links I<br>
would need to do some preparation on the old setup - obviously not possible<br>
now that the system is already upgraded:-(<br>
<br>
Guess I will have a closer look at the tables while I consider the<br>
"complete restore" option:-(<br>
</blockquote>
<br></div>
Right, I'm suggesting you either do a full restore--and then use MythTV tools to clean up what you don't like--or start over with a supported partial restore. I can't guarantee that HLS would work with your old recordings if you do the partial restore using the restore script, but at that point, I'd be motivated to help debug the issues, since I wouldn't have any reason to assume your DB is corrupt.</blockquote>
<div><br></div><div>Thanks for your input - I will definitely use the proper procedure next time! But this time I just can't imagine starting over after all the work I've done:-)</div><div><br></div><div>Anyway, problem seems to be solved: I found a difference in paths in the "livestream" table during HLS streaming - for new recordings it pointed to the recording's real location while the old recording entry would point to "myth:@"host-from-the-old-setup"/"file". After updating the hostname in the recordings table and restarting mythbackend streaming works fine!</div>
</div>