On Sep 6, 2010, at 11:47 PM, erland wrote:
> Ok, this is a problem we need to solve.
>
> Andy, if you are reading this, is there any way to handle this in the
> Audio::Scan module ?
>
> If not, is there some other metadata that could be added to the MD5 in
> similar way as I did with audio size to make sure each track on a cue
> sheet get a unique identity ? Some track offset maybe ?
OK, Audio::Scan could let you provide an alternate starting byte offset for the
calculation, then you could run it on the same file with the start offset of
each track (which is already stored in the database) and get different
checksums.
How about:
Audio::Scan->scan_info( $file, { md5_size => 1024, md5_offset => $track_start }
);
FYI in the next version of Audio::Scan the default md5_offset is determined by:
audio_offset + (audio_size / 2) - (md5_size / 2);
So a user-supplied md5_offset would just override that default.
> Philip Meyer;574862 Wrote:
>>
>> I have a single .mov file that SBS understands (and just plays the
>> audio content). This appears in the Duplicates log as:
>>
>> NOCHECKSUM-NOSIZE M:\Music\Phil's Music\Progressive Rock\Thom
>> Yorke\Other\Rabbit In Your Headlights.mov
>>
>> I guess your code doesn't understand .mov files, but SBS can.
>>
> Andy, if you are reading this, is there any way to handle mov files in
> the Audio::Scan module ?
Hmm, if it's handled OK by SBS that means Audio::Scan is being used. We don't
use any other format modules now. Can you send me the file that doesn't work?
http://wiki.slimdevices.com/index.php/Large_File_Upload
_______________________________________________
beta mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/beta
