<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 20/01/12 22:07, Nick Rout wrote:
<blockquote
cite="mid:CALmzFLajA=tmj0G8da9YjVNNatwOAE75_4gqeWSC3wr9DjQW2g@mail.gmail.com"
type="cite">
<pre wrap="">On Sat, Jan 21, 2012 at 11:01 AM, Jean-Yves Avenard <a class="moz-txt-link-rfc2396E" href="mailto:jyavenard@gmail.com"><jyavenard@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I've found an issue today with mythvideo.
For some reason, one video never showed up in the listing, no matter how
many scan I performed.
Turned out I had the exact same file in another folder (the folder where I
first ripped everything), same file but different name.
The file is only listed once..
A tad confusing
</pre>
</blockquote>
<pre wrap="">
It's the fact that the files are hashed, and once scanned it is never
looked at again even if you change the file name or location (unless
you move it right out of the scan path)
_______________________________________________
mythtv-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a>
<a class="moz-txt-link-freetext" href="http://www.mythtv.org/mailman/listinfo/mythtv-users">http://www.mythtv.org/mailman/listinfo/mythtv-users</a>
</pre>
</blockquote>
It is in fact "looked at" again (at least in my 0.24.1 system). You
get a message stating that it's found an entry with the same hash,
but different name and updates the database entry to reflect the new
file name.<br>
<br>
There's commentary in the Wiki that states "The location of any
video content will be updated automatically based off a matching
hash, with no loss of metadata, next time a <i><b>Scan For Changes</b></i>
is triggered from the <i><b>Watch Videos</b></i> menu."<br>
<br>
What also happens though is that it also seems to flip-flop between
the two names (assuming there's tow duplicate entries) each time you
rescan. Raymond Wagner produced a script to remove duplicates
blindly from the database so that there was only 1 unique entry.<br>
<br>
You can also run mythfrontend and save the output to a file then
look through it for the duplicate messages and sort them out
manually, giving you the opportunity to resolve the problems a
little cleaner.<br>
<br>
Cheers<br>
Gordon<br>
</body>
</html>