Comments (7)
That means there was a problem with a test run but no problem with actual
ripped data.
You said "sometimes" but I don't think it happens frequently. Do you really
configure XLD correctly ? For example, using C2 pointer on unreliable drives
will cause this kind of problem.
Original comment by tmkkmac
on 13 Sep 2011 at 4:29
from xld.
I didn't say it happened frequently. But it does happen (esp with the XLD
Secure ripper). In theory this should be impossible: the log should report
clearly whether the rip is accurate or not.
I'm not using C2 pointers.
Original comment by [email protected]
on 13 Sep 2011 at 3:15
from xld.
The rip is accurate if you trust AccurateRip. May not be accurate if not.
Original comment by tmkkmac
on 13 Sep 2011 at 3:31
from xld.
Here, it just happened again:
Track 06
Pre-gap length : 00:04:45
CRC32 hash (test run) : 50D16294
CRC32 hash : 773D1F6A
->Rip may not be accurate.
CRC32 hash (skip zero) : DB20E199
AccurateRip signature : EEFCE97D
->Accurately ripped! (AR2, confidence 2)
Part of the problem is that the way XLD writes its logs, the AccurateRip
signature doesn't match anything (it doesn't match either has or the skip-zero
hash), so there's no way to know *why* XLD thinks the rip was accurate. It
would be better if XLD said "I got THIS hash and the AccurateRip database has
THIS hash" so the user can see they are the same.
Original comment by [email protected]
on 4 Oct 2011 at 4:14
from xld.
What? XLD says "Accurately ripped" only when the database has AR signature
value calculated in XLD. AR signature shown in the log is a calculated value,
not a value from the database. It is completely different from CRC32.
Original comment by tmkkmac
on 4 Oct 2011 at 4:21
from xld.
"AR signature shown in the log is a calculated value". Fine. Calculated when?
There were two runs: a test run and the second run. The CRC32 hashes differ;
surely the AccurateRip signatures differ as well. Which one worked correctly?
And if it's the second one, why is it *always* the second one when this issue
occurs? That seems very suspicious. What I'm saying is, the log should be
written in terms that make it clear that XLD knows what it's doing and is
giving correct and helpful answers that the user can have confidence in. As it
is, I have no confidence in this track because the report seems meaningless and
self-contradictory ("not accurate" / "accurately ripped").
Original comment by [email protected]
on 4 Oct 2011 at 5:22
from xld.
The value is always calculated from the data of the 2nd (copy) run when Test &
Copy mode is enabled.
The first "not accurate" message means that the data from the 1st and 2nd run
did not match.
The second "accurately ripped" message means that the actually ripped data
(from the 2nd run) was accurately according to the AR database.
This means that the error occurred in the 1st run, but did not occurred in the
2nd run (if you trust the AR database).
Original comment by tmkkmac
on 4 Oct 2011 at 5:44
from xld.
Related Issues (20)
- can't restore preferences from backup HOT 2
- in dsd importer settings the gain adjustment option does not work HOT 3
- Get Metadata fails to retrieve track names and/or title & artwork
- Metadata code should be able to change automatically or manually. HOT 15
- XLD command line can't convert if there is "/ : " in file name
- Very slow on 2015 Macbook, no cover flow on generated i
- Very slow on 2015 Macbook, no cover flow on generated mp4 files
- Foreign language symbols do not reproduce accurately from cue files
- No access to AWS HOT 1
- FLAC Transcode optionally allow imperfections HOT 1
- Tweaks to transcode directory to iTunes HOT 1
- Display Genre and other important album info on main CD Extract/ripping screen HOT 1
- not correct recognition Russian language in the .cue HOT 8
- Converting from Matroska Audio (.mka) files
- dff to flac conversion does not work when 32-bit quantization is set HOT 1
- SACD ISO to AIFF, no cover art added HOT 12
- Save log file failed
- crop coverart to square size
- XLD does not create artist folder
- CD import inverted option
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from xld.