<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 21/01/12 06:59, Jean-Yves Avenard wrote:
<blockquote
cite="mid:CANpj82Khqh-yZyi_Xq33fKMfMOpvo3viSyQSvy4quiq5fh==BA@mail.gmail.com"
type="cite">Hi<br>
<br>
On Saturday, 21 January 2012, Gordon McCrae <<a
moz-do-not-send="true" href="mailto:gordon.mccrae@gmail.com">gordon.mccrae@gmail.com</a>>
wrote:<br>
<br>
<br>
> 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 Scan For
Changes is triggered from the Watch Videos 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>
<br>
None of which explain why if the same file is present twice, it is
only showed once.<br>
<br>
All it explains, is that no matter what the file name is, it will
show under the same name due to the files having the same hash.
<fieldset class="mimeAttachmentHeader"></fieldset>
</blockquote>
Here's an example from the output of MythFrontend when I scan for
new media:<br>
<br>
<SNIP><br>
2012-01-21 12:02:01.940 Adding : : /DATA/VIDEOS/0<<< TV
>>>/001: 12.01.21 @ 11.55/Red Dwarf - Confidence and
Paranoia.mpg : e62547eaec23c306<br>
2012-01-21 12:02:02.204 Adding : : /DATA/VIDEOS/0<<< TV
>>>/002: 12.01.21 @ 07.25/Transformers Prime - Untitled.mpg
: ed041579031109bd<br>
<SNIP><br>
2012-01-21 12:02:03.271 Hash 73a3ae071609fd6e already exists in the
database, updating record 32898 with new filename
/DATA/VIDEOS/0<<< TV >>>/007: 12.01.20 @
18.55/Transformers Prime - Untitled.mpg<br>
2012-01-21 12:02:03.513 Hash b195f6834bd418be already exists in the
database, updating record 32894 with new filename
/DATA/VIDEOS/0<<< TV >>>/008: 12.01.20 @
11.55/Boston Legal - Thanksgiving.mpg<br>
2012-01-21 12:02:03.623 Hash c038794038de1ac8 already exists in the
database, updating record 32892 with new filename
/DATA/VIDEOS/0<<< TV >>>/009: 12.01.20 @
08.55/Farscape - Prayer.mpg<br>
<br>
So basically, the master field is the HASH value, not the filename,
it's a secondary field and is changed when you scan for new media,
so you can never see the two copies of the same file, only one entry
for the HASH value with one of the file names.<br>
<br>
The "oddity" I see, is that if I do have duplicates (I used to
create links to the most recently added videos and put them in the
"NEW VIDEOS" folder), then the filename flip-flops between the
proper one and the link.<br>
<br>
Cheers<br>
Gordon<br>
</body>
</html>