Par2Par: p2p PAR2 sharing for CD rip repair

[EliC]

Re: responses very

No problem, just hoping for some news. 8 months is not exactly short term in the tech world

[Spoon-]

Re: responses very

These things take time for everything to fall into place, it is not going to be done in the short term.

[EliC]

Re: responses very

Any word, thoughts, plans, timeframe on when we may start to see this? Its been 8 months since you mentioned it.

[dbfan]

Re: Par2Par: p2p PAR2 sharing for CD rip repair

No

[EliC]

Re: Par2Par: p2p PAR2 sharing for CD rip repair

We will be doing our own better version.

Holy s**t !

I take it you will not be implementing CTDB?

[rlvlcv]

Re: Par2Par: p2p PAR2 sharing for CD rip repair

That's great Spoon. Is there someplace I could find out more about the plans? Thanks!

[Spoon-]

Re: Par2Par: p2p PAR2 sharing for CD rip repair

We will be doing our own better version.

[rlvlcv]

Re: Par2Par: p2p PAR2 sharing for CD rip repair

Is there any chance of revisiting this feature request?

[EliC]

Re: Par2Par: p2p PAR2 sharing for CD rip repair

So you want to create an entirely sepperate database? I would think it would make more sense to tie it to AR.

spoon just said AR doesnt have access to this data. Whatever is easier to implement. It doesnt even need to be a database, just a sufficient sample size.

[Vulcan]

Re: Par2Par: p2p PAR2 sharing for CD rip repair

it would not have to be reported w/ AR, but certainly r12 will have this data and could easily auto-upload the info.

So you want to create an entirely sepperate database? I would think it would make more sense to tie it to AR.

[EliC]

Re: Par2Par: p2p PAR2 sharing for CD rip repair

it would not have to be reported w/ AR, but certainly r12 will have this data and could easily auto-upload the info.

[Spoon-]

Re: Par2Par: p2p PAR2 sharing for CD rip repair

It would need a fundamental change to accuraterip (it has no interaction with CD drive so does not know about c2 errors, etc).

[EliC]

Re: Par2Par: p2p PAR2 sharing for CD rip repair

clearly it would need to report somewhere centrally. This data could be collected when AR results are reported.

[Spoon-]

Re: Par2Par: p2p PAR2 sharing for CD rip repair

Reporting to where? a log file?

[EliC]

Re: Par2Par: p2p PAR2 sharing for CD rip repair

It is a very rough, idea/proposal.

"Damaged files can be repaired. A single byte error in a 10MB file might only requires the use of recovery data from a PAR file that is only 100KB in size."

I think a rough idea of the average wav size from a large db sample, and an average number or errors or size of errors would help to decide how big of a correction file to create.

There must be a balance between the size of the correction file and the amount of data that could be corrected. If the above numbers are linear and the average wav is 50Mb, then to correct 1 byte you would need 500KB. Is 1Mb enough to correct the average number of errors? Anything greater then 5Mb/song is probably asking users to store to much.

As I suggested above, the best thing to do would be a p2p system. You would need to get the right pressing of the disc. To do this you would search on a number of disc features: number and length of tracks, CRC match of other tracks that had an accurate rip, track gain (from replay gain calculations) could all be used to identify the correct disc/pressing on the p2p network


[COLOR=Red]Spoon, could you add a reporting of data from the new CD ripper to start building a db of average wav size and average number of errors in songs with errors?[/COLOR]