![]() |
![]() |
#1 |
Member
Join Date: Dec 2005
Location: St.Petersburg, Russia
Posts: 4
|
![]()
Most quality ripping standards require 'MD5 locking' of files. Personally I think it is very bad idea because modifing tags, calculating RG values, etc, modifies file checksum. Then there is no use of it at all. My idea is to add stream checksum feature which would be written to MPC header and couldn't be modified. This would give a possibility to implement fast checking for broken streams (instead of checking each frame) and remove the need of useless MD5 file locking.
|
![]() |
![]() |
![]() |
#2 |
Admin
Join Date: Jul 2004
Posts: 372
![]() |
![]()
Changing the header in that way will break compatibility. However, someone could code a little tool that writes the stream's MD5 checksum to an APEv2 tag, and compares the stream's checksum to the checksum in the tag.
|
![]() |
![]() |
![]() |
#3 |
Member
Join Date: Dec 2005
Location: St.Petersburg, Russia
Posts: 4
|
![]()
Good idea.
![]() |
![]() |
![]() |
![]() |
#4 |
Member
Join Date: Dec 2005
Location: St.Petersburg, Russia
Posts: 4
|
![]()
By the way, since new stream version is on it's way to release, maybe my wish could be reviewed?
![]() |
![]() |
![]() |
![]() |
#5 | |
Musepack developer
Join Date: Sep 2006
Location: Villeurbanne - France
Posts: 36
|
![]() Quote:
|
|
![]() |
![]() |
![]() |
#6 |
Musepack developer
|
![]()
i think an md5 packet of the audio stream is a good idea... hell, perhaps you could have both md5 and error codes...
an md5 and par2 with every musepack file ![]() |
![]() |
![]() |
![]() |
Thread Tools | Search this Thread |
Display Modes | |
|
|