More > JRiver Media Center 28 for Windows
NEW: Audio CRC
Matt:
Media 28.0.9 and newer add an "Audio CRC" checksum field that will be filled by the audio analysis.
This value is calculated for 16-bit and 24-bit stereo files. The files will often need to be lossless (since a lossy format like MP3 is 64-bit).
The value we calculate matches common rippers like EAC (and saved in the *.log files of EAC).
I needed a way to check some files to see if they matched the rip, so thought adding this to MC made sense.
BigCat:
Great news, Matt!
benjy:
--- Quote from: Matt on April 30, 2021, 09:11:33 am ---Media 28.0.9 and newer add an "Audio CRC" checksum field that will be filled by the audio analysis.
--- End quote ---
Will there be a way to scan your library to check for corruption or changes? For example, if disk blocks went bad or if a file was somehow modified since the CRC was calculated?
In the event that one intentionally edits an audio file after the original CRC is calculated, will there be a way to update the checksum so that the file is not flagged during any library corruption check.
If one runs audio analysis on a file and the CRC changes from the last value, how will it be handled? Since filesystem / disk corruption occasionally happens, I hope that a new analysis flags the discrepancy for further action by the user instead of just silently updating the original value.
Having the ability to detect corruption and changes is very cool. Thanks!
Matt:
Maybe there should be another database field "CRC Changed" that is normally just false.
If something causes a CRC change, it could set it to true.
Then if you searched your library for any true values, you would find changes?
I'm the paranoid guy that invented a verify feature for Monkey's Audio so I routinely check my whole collection!
Vocalpoint:
--- Quote from: Matt on May 10, 2021, 01:12:15 pm ---Maybe there should be another database field "CRC Changed" that is normally just false.
If something causes a CRC change, it could set it to true.
Then if you searched your library for any true values, you would find changes?
I'm the paranoid guy that invented a verify feature for Monkey's Audio so I routinely check my whole collection!
--- End quote ---
+1 I like this a lot!
But I think any CRC record check (or potentially a couple fields) should record date logic - especially a Modified Date so we can see exactly when a CRC was changed for troubleshooting purposes. Having the system simply state that the CRC has changed does not really help me determine when something has changed.
And while relying on the Windows Modified date should be good enough but quite frequently - but in many cases - it's not.
VP
Navigation
[0] Message Index
[#] Next page
Go to full version