Skip to main content

Topic: AccurateRip drive offset query failure: Drive not present in the database (Read 1020 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.
AccurateRip drive offset query failure: Drive not present in the database
Since I updated to foobar 1.3.16 my drive is no longer in the database according to the message I get when I click on 'Auto' in the Drive Settings dialog. Funny because it used to be in the database. I checked the accuraterip drive offsets database and it's still there although it's missing a letter which I think stands for the color (black).

Drive in database: LG Electronics - GH24NSC0
My drive: LG Electronics - GH24NSC0B

So what is going on? I know my drive offset but I'm just curious.

  • spoon
  • [*][*][*][*][*]
  • Administrator
Re: AccurateRip drive offset query failure: Drive not present in the database
Reply #1
GH24NSC0S has never been in the database, perhaps you updated the firmware recently and it changed the reported name?

Re: AccurateRip drive offset query failure: Drive not present in the database
Reply #2
It must've been in the db because when I clicked on Auto, it would come up with offset of 6. That's how I know it was 6. I never looked it up before. After the last foobar update, it no longer worked. I didn't update the ROM in the drive if that's what you mean.

Re: AccurateRip drive offset query failure: Drive not present in the database
Reply #3
And it's not "GH24NSC0S." GH24NSC0 is in there now.

  • kode54
  • [*][*][*][*][*]
  • Administrator
Re: AccurateRip drive offset query failure: Drive not present in the database
Reply #4
Google is not helping me to find what keyboard layout has the S and B keys next to each other.

  • spoon
  • [*][*][*][*][*]
  • Administrator
Re: AccurateRip drive offset query failure: Drive not present in the database
Reply #5
GH24NSC0B has never been in the database either (I am checking the file listing which is for each known drive), even if something happed to purge the drive submissions, the file would still remain with 0 bytes.

  • Porcus
  • [*][*][*][*][*]
Re: AccurateRip drive offset query failure: Drive not present in the database
Reply #6
What does Windows (device manager) and other ripping applications (e.g. dBpoweramp / EAC/ CUERipper) call it?

Re: AccurateRip drive offset query failure: Drive not present in the database
Reply #7
Uh,
HL-DT-ST DVDRAM GH24NSC0 ATA Device

Under Details/Hardware IDs
IDE\CdRomHL-DT-ST_DVDRAM_GH24NSC0________________LI00____
IDE\HL-DT-ST_DVDRAM_GH24NSC0________________LI00____
IDE\CdRomHL-DT-ST_DVDRAM_GH24NSC0________________
HL-DT-ST_DVDRAM_GH24NSC0________________LI00____
GenCdRom

Re: AccurateRip drive offset query failure: Drive not present in the database
Reply #8
I'm not sure why anyone is saying it is "not in the database."
I'm referring to http://www.accuraterip.com/driveoffsets.htm
Do I have the wrong database?

Here's a screen shot. A simple Ctrl F and search for GH24NSC0...

  • Porcus
  • [*][*][*][*][*]
Re: AccurateRip drive offset query failure: Drive not present in the database
Reply #9
I'm not sure why anyone is saying it is "not in the database."
Who said that, except yourself in your original posting? ;)

Everyone finds it as long as you do not want to include the "B". What was the problem?

Re: AccurateRip drive offset query failure: Drive not present in the database
Reply #10
I'm not sure why anyone is saying it is "not in the database."
Who said that, except yourself in your original posting? ;)
See reply's #1 #5. Hello?
Everyone finds it as long as you do not want to include the "B". What was the problem?
What?

  • Porcus
  • [*][*][*][*][*]
Re: AccurateRip drive offset query failure: Drive not present in the database
Reply #11
GH24NSC0 is in the database, and has been since long? None of us say otherwise?
So it identifies as GH24NSC0 by absolutely everything except possibly foobar2000 - and it is no issue that the database never had GH24NSC0B (nor GH24NSC0S, funny typo)?

Re: AccurateRip drive offset query failure: Drive not present in the database
Reply #12
I don't know what happened behind the scenes but it's working again.

Let me reiterate: AFTER the foobar update 1.3.16, the "auto" offset was returning an error "drive not found." BEFORE the 1.3.16 update, the "auto" offset was NOT returning an error and set the offset to 6.
  • Last Edit: 03 November, 2017, 05:09:35 PM by guerrilla77