Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Xstatic]

I am beginning to discover errors in rips and in the report logs the secure ripping gives.

On aug.9 I ripped a song and got a report.
It said the rip was ok and stated 4 or 5 instances where it had to reread 2 times to get good data.

When I get reports like that, I always mark the position in the report and hit play to check it.

Almost always when the reports state a reread it, states to have done so in the very first seconds of a track - never in the middle or at the end. That is peculiar I think.

Well, this track I mention I just heard in full for the first time, and it is overall full of flaws and ticks.

The report says it was done ok, but the playback reveals many errors, and not just in the beginning of the track.

Would be willing to email both report and track for investigation if that would be relevant.

Jesper.
Media Jukebox PLUS 8.0.382
Install Path: C:\Programmer\J River\Media Jukebox\

CPU: Intel Pentium 4 1809 MHz MMX
Memory: Total - 523 MB, Free - 314 MB
OS: Microsoft Windows XP  Workstation 5.1 Service Pack 1 (Build 2600)

Internet Explorer: 6.0.2800.1106
ComCtl32.dll: 6.00.2800.1106
Shlwapi.dll: 6.00.2800.1106
Shell32.dll: 6.00.2800.1106
wnaspi32.dll: Internal ASPI Layer

[Xstatic]

John T, you asked about the cd-drive model and if this was a one-time experience.

Your reply is gone because of the board breakdown.

CD-drive model is Plextor PX-W2410a.

I believe you already have this drive around, because of an earlier trouble-shoot...

I have experienced this once in a rare while.
Every time it has happened, the rip report has stated that 2x rereads had to be done to get good data.

What is funny about all the rip reports, is that the rereads always occur in the very beginning of a track, never in the middle or in the end of a track. I have wondered about this.

Rereads in secure rips only occur when the cd is minor or severely scratched. Sometimes MJ gives up and I use EAC to spend the entire night to rip a track.

So, to get back on the track:
This particular case was a used and slightly scratched cd that I ripped from.

As I said in the first post: If it could be of any help I will mail you both the report and the track.

Jesper.

[phelt]

This does not help with your MJ problem, but have you tried the latest version of Plextools for secure ripping? If you're in Europe, you should have gotten the app with your burner. Update page is here:
http://www.plextor.be/english/technical/downld_util.html

I've heard some good reports about its secure mode, specifically relating to rip speed.

[Xstatic]

Thx for the tip and the thought phelt.

I fooled a little bit around with Plextools 6 months ago.
But then I had some trouble with the drive, windows wouldnt recognise it etc.

Plextor support advised me to remove Plextools, and then everything was fine again...!

Maybe the new version is better, I'll try it for sure.

[Xstatic]

Have conducted some more tests.

I ripped a few songs from a scratched cd using digital secure.

2 of the 3 tracks had errors that needed rereading.
In the rip report it said 4 places or so that 2x rereads had to be done to get good data.
Again those rereads were according to the report performed in the first 5 seconds of the tracks.

But, again, the whole track is filled with errors when listening to it.

Did the same test with Plextools (thx Phelt, no prob's with their new version) and EAC, and they pick up the errors as they come and reread and correct to the best of their ability, and produces a better end result.

It seems as if MJ doesnt recognize some of the errors, and only those that are in the beginning of the track?

[Xstatic]

John T, did  you have time to look at this, and do you have any comments about it?

[JohnT]

I have not had a chance to do any further testing as yet. One of the machines here has the same drive as you have (plextor 24/10), I will try installing on my machine and try some scratched CD's to see if I can replicate the problem. I'm kind of up to my neck with CD burning right now, but will try to do this sometime this week.

[Xstatic]

np

[Xstatic]

Listened to another tune today that I ripped 3 months ago. It was ripped with MJ 8.xx. The secure report said two times reread in the beginning of the track, and the rest was ok.

And again there were errors on most of the track.

I have only encountered errors in rips where the report also states rereads.

[Xstatic]

Am I the only one to experience differencies between the rip reports and the actual result?

In that case, what can the cause be?,

1) Defect in cdrom drive in the reporting to MJ?

2) Small "bug" in MJ's ability to read data/error reporting from this particular drive?

Maybe the way error reporting is done is different than in EAC, but I have always experienced the error reporting in EAC to be accurate...