<br><br><div class="gmail_quote">On 29 August 2012 21:57, Anthony Giggins <span dir="ltr"><<a href="mailto:seven@seven.dorksville.net" target="_blank">seven@seven.dorksville.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br><br><div class="gmail_quote"><div><div class="h5">On 29 August 2012 19:48, 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>On 28/08/12 23:58, Anthony Giggins wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
<br>
<br>
On 29 August 2012 02:19, John Pilkington <<a href="mailto:J.Pilk@tesco.net" target="_blank">J.Pilk@tesco.net</a><br></div><div><div>
<mailto:<a href="mailto:J.Pilk@tesco.net" target="_blank">J.Pilk@tesco.net</a>>> wrote:<br>
<br>
On 27/08/12 23:53, John Pilkington wrote:<br>
<br>
Since installing 0.25-fixes on my main box I've had problems with<br>
MythArchive. I think this may be because the config settings are<br>
defined by the frontend but are being read using the hostname of the<br>
backend. The lines in the mythburn.py script read<br>
<br>
DB = MythTV.MythDB()<br>
configHostname = DB.gethostname()<br>
<br>
I've tried a direct hack in mythburn.py that looked hopeful.<br>
What would<br>
be the way of getting the frontend's 'Custom Identifier' from the DB<br>
instead?<br>
<br>
<br>
OK, it works for me (in creation of a playable DVD) if the 'Custom<br>
identifier' from Frontend Setup > General > page 2 is used as<br>
configHostname.<br>
<br>
If defined it's LocalHostName in ~/.mythtv/mysql.txt. Isn't that<br>
the file that's being phased out? config.xml doesn't have it and I<br>
haven't found it in the DB.<br>
<br>
I suspect this is also the cause of the lack of a progress log in<br>
'Create an Archive' mode, Ticket #10505, but I don't think that's<br>
done through mythburn.py and my hack doesn't change it. A usable<br>
Archive is created.<br>
<br>
A warning: while I was investigating this, a chmod called within<br>
mythburn.py walked recursively all over my home directory. I've<br>
commented that line out. There are some multi-delete sections too...<br>
<br>
<br>
John P<br>
<br>
<br>
Semi OT: is mytharchive 0.25-fixes Storage Group friendly?<br>
<br>
Tried using this for the first time since atleast 0.23 and it failed<br>
saying it couldn't locate the file from either Videos or files.<br>
<br>
Can anyone confirm?<br>
<br>
Cheers,<br>
<br>
Anthony<br>
<br>
</div></div></blockquote>
<br>
I've not used it before for anything other than recordings, now all from dvb-t, and it seems ok with Storage Groups there. The problem above will affect you if you have the 'Custom identifier' defined and you haven't made the suggested edits in mythburn.py. What will happen then depends on whatever ancient configuration it picks up.<br>
<br>
Now 'Files' shows me my full (single box) file system and seems to work on a short recording selected in that way; although when I selected a file from the mythlink output folder its reported size was several TB, mistaking Bytes for MBytes.<br>
<br>
'Videos' doesn't show any directory structure, though. Most of my videos are in iso format anyway. Maybe the magic should work there, but I haven't tried. Their names are shown.<span><font color="#888888"><br>
<br>
John</font></span><div><div><br>
<br></div></div></blockquote></div></div><br>
</div></blockquote><div> <br>Yes I see the same size reporting issues but not using the 'Custom Indentifer' so that shouldn't be a problem.<br></div><div><br>Cheers,<br><br>Anthony <br></div></div><br><br>