Active TopicsActive Topics  Display List of Forum MembersMemberlist  Search The ForumSearch  HelpHelp
  RegisterRegister  LoginLogin
Chat Board
 Top 40 Music on Compact Disc : Chat Board
Subject Topic: DBpoweramp Post ReplyPost New Topic
Author
Message << Prev Topic | Next Topic >>
AdvprosD
MusicFan
MusicFan


Joined: 12 June 2020
Location: United States
Online Status: Offline
Posts: 358
Posted: 08 January 2025 at 5:33pm | IP Logged Quote AdvprosD

Lately, I have been ripping a lot of my old 30+ year old TM Century HitDiscs. I've pretty much settled on using DBpoweramp as my app of choice, since WMP doesn't seem to have quite the accuracy
I prefer. For the most part, things are going great, except I have a couple questions someone might know the answer to.

Q1, How does DBpoweramp know what the wav files look like from other computers, or other rips? The app states that the files I rip are compared to other users and either my rips "Agree" with
others who have ripped the same content or not. This question asks, how is this agreement achieved?

Q2, Is there any advantage of using EAC instead of DBpoweramp? EAC still seems to have functions I am not qualified to use. Prior to DBpa, rips I did were mostly WMP and didn't experience nearly
any of the frame issues I see from time to time. As a test, I ripped a HitDisc with WMP and it seems to sound OK. Though DBpa just attacks each track to death with thousands of frame issues.
Fortunately, I haven't had but one disc like this. All other discs seem to be an easy rip, unless rot has consumed the content. In either case even WMP won't properly read the disc and has
problems during the rip process. Such as delays in the process, or things like causing the CD Rom to spin up and down repeatedly with no data recovered.

Today, I had something really odd happen. While using an external USB connected CD Rom, I completed the so-called test procedure to help DBpa make sure the drive was able to rip to specs.
After which, (With the tray fully ejected), I happened to touch the rip button and the rip process started without a disc in the drive. The rip completed with all tracks verified. I went to the folder
where the rips are supposed to write to, and found 700mb of data in that folder. Though the data is listed as tracks ripped by me, there is no audio. Just a flat line for the full time of
each track. I'm really perplexed by this and am wondering if DBpa downloads an image on my hard drive each time I use the app. An image that is used for comparison maybe? One that disappears
after the rip process is completed?

I still have the folder handy, in case there's some way to analyze it for future reference. Or, I have 700mb less of hard disk space until I decide to delete it.


Dave

__________________
<Dave> Someone please tell I-Heart Radio that St. Louis is not known as The Loo!
Back to Top View AdvprosD's Profile Search for other posts by AdvprosD
 
whyaduck
MusicFan
MusicFan


Joined: 10 March 2016
Online Status: Offline
Posts: 32
Posted: 08 January 2025 at 7:34pm | IP Logged Quote whyaduck

DB uses accuraterip

https://www.google.com/search?q=what+is+accuraterip&udm=14
Back to Top View whyaduck's Profile Search for other posts by whyaduck
 
whyaduck
MusicFan
MusicFan


Joined: 10 March 2016
Online Status: Offline
Posts: 32
Posted: 08 January 2025 at 7:37pm | IP Logged Quote whyaduck

whyaduck wrote:
DB uses accuraterip

https://www.google.com/search?q=what+is+accuraterip&udm=14


EAC has some more advanced features than DBPoweramp they are almost never needed.

If the rip checks out in accuraterip you are fine. Literally the math can not lie.



Back to Top View whyaduck's Profile Search for other posts by whyaduck
 
aaronk
Admin Group
Admin Group


Joined: 16 January 2005
Location: United States
Online Status: Offline
Posts: 6536
Posted: 08 January 2025 at 8:35pm | IP Logged Quote aaronk

AdvprosD wrote:
Q1, How does DBpoweramp know what the wav files look like from other computers, or other rips? The app states that the files I rip are compared to other users and either my rips "Agree" with others who have ripped the same content or not. This question asks, how is this agreement achieved?


Both dbPoweramp and EAC use the same AccurateRip database. It works through something called a checksum, which is a "fingerprint" of an audio track. Once the track is ripped, a 32-character checksum value is generated that summarizes the audio it ripped. If the audio is different between two tracks even the slightest bit, the checksum value that is generated will be wildly different. When many users are submitting their rip results to the database, a track can be verified as accurate when the checksums match.

__________________
Aaron Kannowski
Uptown Sound
91.9 The Peak - Classic Hip Hop
Back to Top View aaronk's Profile Search for other posts by aaronk Visit aaronk's Homepage
 
prisdeej
MusicFan
MusicFan


Joined: 02 July 2011
Location: United States
Online Status: Offline
Posts: 284
Posted: 08 January 2025 at 8:43pm | IP Logged Quote prisdeej

I've always used EAC, Dave, and rely solely on AccurateRip. DB uses
the same, and your rips are noted. Perhaps someone else can chime in
with your other questions.

__________________
Dave L.
Back to Top View prisdeej's Profile Search for other posts by prisdeej
 
mjb50
MusicFan
MusicFan


Joined: 28 April 2021
Location: United States
Online Status: Offline
Posts: 320
Posted: 09 January 2025 at 5:09pm | IP Logged Quote mjb50

There's nothing EAC does that dBpoweramp doesn't, as far as things that affect rip quality. dBpoweramp is more user-friendly. More people are familiar with EAC though because it's free.

A previous disc's layout (track lengths) being remembered, the empty drive ripping silent versions of those tracks, and then the fact that they verify (in AccurateRip? or just against successive reads?) is absolutely, positively bizarre! I've never heard of anything like it before. It might be a drive "feature" or maybe something unique to dBpoweramp or both.

As for the hard-to-rip disc, that's how it goes. It's bad and the drive reports problems when the ripper tries to read it.

dBpoweramp, EAC, XLD (for Mac), and several other rippers can be configured to do a "secure" rip. In this relatively slow mode, as they proceed, they re-read the disc to make sure each read returns the same data. Damaged or defective discs tend to return random data, but if you read the same spot enough times, you might get the same data twice, and as long as it wasn't the result of caching, it's likely to be correct.

The drive itself may slow way down when reading these bad portions, making painfully slow progress or just giving up altogether. Sometimes you can configure some firmware settings in the drive to make it more or less fussy. Meanwhile, the ripping software gives you many options as well. However, some discs are just beyond saving, at least with whatever drive you have (some drives do better than others).

https://www.dbpoweramp.com/help/dmc/CDadvanced.htm explains some of the settings. If you have more questions, you probably should ask in the dBpoweramp forum.
Back to Top View mjb50's Profile Search for other posts by mjb50 Visit mjb50's Homepage
 
Hykker
MusicFan
MusicFan


Joined: 30 October 2007
Location: United States
Online Status: Offline
Posts: 1394
Posted: 10 January 2025 at 6:40am | IP Logged Quote Hykker

Dumb question perhaps, but is there any advantage to using one of these programs vs just ripping with Adobe Audition?
Back to Top View Hykker's Profile Search for other posts by Hykker
 
AdvprosD
MusicFan
MusicFan


Joined: 12 June 2020
Location: United States
Online Status: Offline
Posts: 358
Posted: 11 January 2025 at 10:05am | IP Logged Quote AdvprosD

mjb50 wrote:

A previous disc's layout (track lengths) being remembered, the empty drive ripping silent versions of those tracks, and then the fact that they verify (in AccurateRip? or just against successive reads?) is absolutely,
positively bizarre! I've never heard of anything like it before. It might be a drive "feature" or maybe something unique to dBpoweramp or both.


Yes, it was kind-of bizarre watching the rip process begin and end with no disc in the drive.

I wouldn't have thought much of it, if it wasn't for all the silent tracks in that new folder. They are all wav files, though completely silent. Just freaky!

__________________
<Dave> Someone please tell I-Heart Radio that St. Louis is not known as The Loo!
Back to Top View AdvprosD's Profile Search for other posts by AdvprosD
 
mjb50
MusicFan
MusicFan


Joined: 28 April 2021
Location: United States
Online Status: Offline
Posts: 320
Posted: 12 January 2025 at 10:29am | IP Logged Quote mjb50

Hykker, Audition and any other tool is fine, but normally they just try to be fast and don't go out of their way to check for and resolve possible errors. "Secure" rippers like Exact Audio Copy, XLD (for Mac), CUERipper, and dBpoweramp, if so configured, read the disc at least twice and try to resolve any data inconsistencies by repeatedly re-reading smaller chunks. They may also check external databases (AccurateRip or CUETools Database) to see if your rips match other people's.
Back to Top View mjb50's Profile Search for other posts by mjb50 Visit mjb50's Homepage
 
Hykker
MusicFan
MusicFan


Joined: 30 October 2007
Location: United States
Online Status: Offline
Posts: 1394
Posted: 12 January 2025 at 12:42pm | IP Logged Quote Hykker

OK thanks for the info. Maybe I'll have to give it a try...I've got a bunch of old Dr. Demento shows I'd like to rip (or at least lift some
of the songs), but most of 'em give so many read errors as to be unusable.
Back to Top View Hykker's Profile Search for other posts by Hykker
 

If you wish to post a reply to this topic you must first login
If you are not already registered you must first register

  Post ReplyPost New Topic
Printable version Printable version

Forum Jump
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot delete your posts in this forum
You cannot edit your posts in this forum
You cannot create polls in this forum
You cannot vote in polls in this forum



This page was generated in 0.0518 seconds.