title
Products            Buy            Support Forum            Professional            About            Codec Central
 

Help Request: Setup Errors and Strange Results from New ASUS BW-16D1X-U

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • MusicArchivist

    • Aug 2022
    • 3

    Help Request: Setup Errors and Strange Results from New ASUS BW-16D1X-U

    Well, I'm feeling a bit stupid today. Hopefully someone can help me figure my way out of the confusion.

    I have a new ASUS BW-16D1X-U that I've been setting up. I. think my settings are accurate (other than feeding in a simulated screwed up disc for AccurateRip setup, which I don't have one to sacrifice at the moment).

    Searching the forums, I've seen a small number of references to this drive. But it seems there might be some funky things up with the offset.

    Initially, the database was apparently giving people a +667, with users seeing +6 from key discs. in November, 2020 Spoon mentioned the drive would be purged from the database to allow it to be correctly configured.

    You can see some examples of the issues in these two threads, the latest being April, 2022:
    I'm embarking on ripping ~1,000 CD's and want to get AccurateRip to work correctly. My problem is that I believe the drive offset listed in AR's database is incorrect. I have a ASUS - BW-16D1H-U, and the database shows an offset value of +6, but this is based on only 2 submissions. My drive appears to have an offset of +667.

    Mr. Spoon, I wrote you several weeks ago about an error I had that was like one of several years ago where my old dvd recorder in the database is no longer recognized, and the new dvd rec order not in the database cannot be configured and is considered not to exist resulting in black colour-coded expedited rips. Oddly, it is



    On one disc I tried, it gave the following on every track:
    AccurateRip Verified Confidence 26, Using Pressing Offset +6
    AccurateRip Verified Confidence 3, Using Pressing Offset -6

    On the next disc, every track had this offset, with confidence number varying slightly for obvious reasons:
    AccurateRip Verified Confidence 46, Using Pressing Offset +670
    AccurateRip Verified Confidence 31, Using Pressing Offset +680
    AccurateRip Verified Confidence 14, Using Pressing Offset +6


    I guess I'm supposed to just keeping feeding the beast until it figures it out? But It didn't match to anything in the database. That first disc I mentioned is clipping the ends of songs slightly, in multiple players. The second disc has nearly 10 seconds of silence at the end of tracks.

    The strange thing is that both of those results rendered accurate tracks, as you can see above. How can it get an Accurate score over '1' if it's clipping the end of the track off?

    My sleep-deprived conclusion is that neither 6 or 667 sound like they would be appropriate for the drive then?

    No DSP effects added, and I'm being (intentionally) wasteful and have it set as FLAC Uncompressed. If any other settings need to be confirmed, let me know.

    It's been several years since I used any of the dBpoweramp-related suite of products, and I'm now using the latest builds. My previous primary external drive never encountered this issue.

    Any of you with more synapses firing than me (which will probably be all of you) please help this confused guy out. 12 hour shifts 7 days a week, for the last ~100 consecutive days, taking care of a family member on hospice has left me a bit mentally fried.

    Thanks in advance! It is very much appreciated.
  • Spoon
    Administrator
    • Apr 2002
    • 44505

    #2
    Re: Help Request: Setup Errors and Strange Results from New ASUS BW-16D1X-U

    Yes keep feeding CDs.
    Spoon
    www.dbpoweramp.com

    Comment

    • christopherfest

      • Jul 2023
      • 3

      #3
      Re: Help Request: Setup Errors and Strange Results from New ASUS BW-16D1X-U

      Please tell me you were eventually able to get it working? I am on CD 30 right now and still no luck. Also the +6 message

      Comment

      Working...

      ]]>