illustrate
Products            Buy            Support Forum            Registrations            About           
 

dBpoweramp Batch Ripper: Discussions

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • bhoar
    replied
    Re: dBpoweramp Batch Ripper: Discussions

    Originally posted by Spoon
    I always thought that very problamatic discs would be taken out of Batch Ripper and ripped in CD Ripper, atleast that is what I would do.
    Hmm. Let me give you a part-actual/part-hypothetical example, Spoon. I did the following with other software, but let's imagine I'm doing it with yours:

    I loaded the last 800 CDs of my sister's ~2000 CDs into one of my machines last month. I set the unit to reject discs that were damaged or missing metadata. Over a day and a half, it ripped about 650 of them and rejected about 150 (I was manually clearing the reject pile and also right-click rejecting discs that were ripping for over an hour with no progress).

    I then had 150 discs that might have been rejected due to one of several reasons: a) missing metadata, b) disc damage, c) disc needs cleaning, d) temporary network outage between me and metadata providor(s) or e) unknown and/or unrepeatable cause (e.g. transient problem due to drive firmware bug). I manually check the read sides to put b and c type discs into my clean/buff pile and take care of those, returning them to the reject stacks when done.

    However, I don't want to manually run the CD Ripper on the remaining 150, I want to use an automated process. And, of course, I don't want to have to pay to re-lookup these 150 either when using premium metadata.

    Of course, what I want and what I get aren't always the same.

    But I suspect that ripping services will have a similar workflow: first let the device sort out the problematic discs in the first run, do some quick hit cleaning/buffing (if service offered), resubmit rejected discs and then...(decision tree will differ here)...

    -brendan
    Last edited by bhoar; January 08, 2008, 02:12 PM.

    Leave a comment:


  • EliC
    replied
    Re: dBpoweramp Batch Ripper: Discussions

    Originally posted by Spoon
    I always thought that very problamatic discs would be taken out of Batch Ripper and ripped in CD Ripper, atleast that is what I would do.
    Ideally, in the future I would like the batch ripper to be able to move problematic discs between the 4 different drives in my robot and see if any of them can rip the disc without my intervention. This would potentially cost 8 lookups.

    One possible solution is that the metadata is not downloaded by the batch ripper until AFTER a successful rip...

    Leave a comment:


  • Spoon
    replied
    Re: dBpoweramp Batch Ripper: Discussions

    I always thought that very problamatic discs would be taken out of Batch Ripper and ripped in CD Ripper, atleast that is what I would do.

    Leave a comment:


  • bhoar
    replied
    Re: dBpoweramp Batch Ripper: Discussions

    Originally posted by LtData
    Remember that the meta-data providers are the ones dictating the restrictive terms, not Spoon. However, a time-limit might be acceptable, but who knows.
    Right - just wanted to keep that idea (idea=a limited-time premium metadata/art cache of a week or a month) in Spoon's head for any future negotiations.

    We're not trying to get a two-for-one (or dozens-for-one) deal/steal on premium lookups, but since this tool will more often be used multiple times on problem CDs (unlike other batch ripping products), it's more of a fairness issue.

    While most discs for a collection go through only once, problem discs (whether the problem is lookup related or damage related) may go through two to four times.

    An alternate method, which would require re-architecting the batch ripper, would be putting off all premium meta-data lookups until after all CD audio ripping is completed. There might be contractual reasons this wouldn't be allowed, though.

    -brendan

    Leave a comment:


  • LtData
    replied
    Re: dBpoweramp Batch Ripper: Discussions

    Remember that the meta-data providers are the ones dictating the restrictive terms, not Spoon. However, a time-limit might be acceptable, but who knows.

    Leave a comment:


  • Spoon
    replied
    Re: dBpoweramp Batch Ripper: Discussions

    Install the lastest R13 alpha, that is needed to show the Ripper.

    Leave a comment:


  • RipTheWorld
    replied
    Re: dBpoweramp Batch Ripper: Discussions

    Originally posted by EliC
    I think the key is that its a batch ripper and the user does not want to sit around and watch to cancel tracks. That is why we need more power in changing settings to skip tracks and if something can be done to skip tracks or cancel rips more elegantly (software seems to temporarily freeze when stopping a rip) that would help too.
    Totally agree. When you are doing hundreds of CDs a day it is not practical to monitor all of the different machines all of the time. For example there could be a time limit on trying to achieve the error corrections.

    I also cannot seem to bring up the ripping windows for each individual rip job, nothing happens at all.

    I'm not overly happy about the prospect of having to pay for each lookup every time I do the same lookup, I agree that maybe a time limit on it would be a good compromise.
    Last edited by RipTheWorld; January 07, 2008, 01:30 PM.

    Leave a comment:


  • Spoon
    replied
    Re: dBpoweramp Batch Ripper: Discussions

    Correct

    Leave a comment:


  • bhoar
    replied
    Re: dBpoweramp Batch Ripper: Discussions

    Originally posted by Spoon
    No commercial meta data povider will allow us to cache their meta data, the large ripping houses would at the end of the year end up with the whole database
    This policy does seem rather rude on their part, esp. when using dbpoweramp for dealing with problematic discs (a forte of the program) that may require several rip attempts. Next time you sit down with them, perhaps you can suggest a time-limit based cache (e.g. each matched lookup record can be cached for 30 days, maximum or perhaps as little as 7 days).

    As a business owner, being charged several times for the same data means I will end up having to limit my rip->reject->clean/buff->resubmit cycles to the frustration of customers who will end up with larger reject piles to deal with on their own. Or I may just not use premium metadata at all, which means no album art (with dbpa that is...with ripstation they still pull the amazon art if available when using only freedb).

    Originally posted by Spoon
    > Is there no way to benefit from the CDRipper AMG license that I acquired by
    > purchasing the registered version of CDRipper?

    We are bound by the rules of the providers, AMG are allowing 400 lookups with the CD Ripper AMG license (it took many weeks of negotiating that).
    I take it you meant "Batch Ripper AMG license" above? The CD Ripper AMG license is limited only by time, correct?

    -brendan
    Last edited by bhoar; January 06, 2008, 02:41 PM.

    Leave a comment:


  • EliC
    replied
    Re: dBpoweramp Batch Ripper: Discussions

    Originally posted by Spoon
    >Batchripper will get stuck on a given track of a CD and will keep trying to rip
    >that track for

    You can right click on the drive line and see the ripper behind, how may frames it is re-ripping.
    I think the key is that its a batch ripper and the user does not want to sit around and watch to cancel tracks. That is why we need more power in changing settings to skip tracks and if something can be done to skip tracks or cancel rips more elegantly (software seems to temporarily freeze when stopping a rip) that would help too.

    Leave a comment:


  • Spoon
    replied
    Re: dBpoweramp Batch Ripper: Discussions

    No commercial meta data povider will allow us to cache their meta data, the large ripping houses would at the end of the year end up with the whole database

    ---------------------
    >I've noticed that the app crashes pretty consistantly if you exit without
    >first stopping the rip. (app inactive, no CDs in drives).

    Yes this is on my todo list.

    ------------------------
    >Batchripper will get stuck on a given track of a CD and will keep trying to rip
    >that track for

    You can right click on the drive line and see the ripper behind, how may frames it is re-ripping.

    ---------------

    >Does that mean that ripping to a single file is already done? I can't find any
    >way to do it (in the batch ripper or in the regular ripper).

    There is Rip as One in R13 alpha, batch ripper will not offer single image ripping upon release.

    >Is it planned to be able to choose a lookup order via the meta providers?

    Your best bet would be to use a profile with freedb only, and reject any cds with no meta data, then use a different provider. The power of batch ripper will come from using 3 providers at the same time.

    -----------------
    >I assume that Batchripper is using freedb. (Can I verify which database it is using?)

    The next release will correctly portray which provider is active.

    > Is there no way to benefit from the CDRipper AMG license that I acquired by
    > purchasing the registered version of CDRipper?

    We are bound by the rules of the providers, AMG are allowing 400 lookups with the CD Ripper AMG license (it took many weeks of negotiating that).

    >"Ray Charles - Pure Genius; The Complete Atlantic Recordings (1952-1959) Disc 1 - 01 - The Sun's Gonna Shine Again,"
    >"Pure Genius; The Complete Atlantic Recordings (1952-1959) Disc 3,"

    If the providers are not consistant it is difficult for batch ripper to 2nd guess the correct storage.

    Leave a comment:


  • EliC
    replied
    Re: dBpoweramp Batch Ripper: Discussions

    commercial or not, I would think the meta data from a source should be placed in the cache, especially if you pay for it.

    As for the TOC in FLAC, its up to FLAC's developer to add support. For a work around, I have requested that spoon include the option to write the TOC to a separate file in the album directory.

    See my thread in the wishlist forum regarding optimizing the sweet spot to have the option to avoid discs that take to long to rip.

    Leave a comment:


  • peterfs
    replied
    Re: dBpoweramp Batch Ripper: Discussions

    Originally posted by latefordinner
    One problem, however, keeps cropping up with my Sony XL1B3. Batchripper will get stuck on a given track of a CD and will keep trying to rip that track for hours until I cancel the CD and let it move to the next. This problem seems to happen most often in multi-CD sets (boxed sets).
    Yep, that's really annoying. It'd be great to have a way to skip ripping a track if the re-rip frame count goes above a settable number.

    Particularly with the XL1B3, if there's ever a reason to restart a session (say after a power outage), it would be great to be able to specify a starting slot number. As it is, if I don't want to re-rip a bunch of discs, I have to eject everything loaded and reload the ones that haven't been ripped.

    While I'm on a wish list binge, another thing would be to store the TOC in flac encoded files. Certain meta-data providers (GD3 being the example I know of) use that to differentiate CD's in their database; if I want to contribute album art or other metadata to their database, a) I can't specify which album it is without it being in the drive, and b) I can't re-download the album because there's no way to keep track of which ones I've accessed or contributed.

    Apparently, metadata content accessed from GD3 is not inserted in the dbPoweramp cache. Is that deliberate? I could understand why if batch ripper is considered a commercial application.

    In spite of the above occasional problems, I have to say that it's very satisfying to successfully rip 100+ CD's unattended.

    - peter

    Leave a comment:


  • latefordinner
    replied
    Re: dBpoweramp Batch Ripper: Discussions

    A few additional issues:


    1. Presumably because I have exhausted the AMG lookups, Batchripper is now returning less-reliable metadata. It no longer picks up any album art, and sometimes the wrong artist (or a garbled name for the artist) appaers. Also, on multi-CD sets, Disc 1 will appear, for example, as "Charlie Parker - Jazz at the Philharmonic 1946," while Disc 2 appears as "D 2) - D 2)," Disc 3 appears as "Charlie Parker - Jazz at the Philharmonic 1949," and Disc 4 appears as "sc 5) - sc 5)"--in other words, there is no uniformity. I assume that Batchripper is using freedb. (Can I verify which database it is using?) Is there no way to benefit from the CDRipper AMG license that I acquired by purchasing the registered version of CDRipper?

    2. The lack of uniformity sometimes leaks into the saving of filenames. For example, I am using FLAC, and on a Ray Charles multi-disc set, some tracks are saved in the Ray Charles folder with the disc number appearing in the file name, e.g., "Ray Charles - Pure Genius; The Complete Atlantic Recordings (1952-1959) Disc 1 - 01 - The Sun's Gonna Shine Again," while other tracks appear in subfolders within the Ray Charles folder, e.g., folder name "Pure Genius; The Complete Atlantic Recordings (1952-1959) Disc 3," which then contains the tracks from that disc.

    Is there a way to edit the metadata to make everything under artist Ray Charles uniform so that all the tracks appear in the main Ray Charles folder? What about for erroneous metadata, where, for example, the lookup misidentifies the artist, CD title, and tracks (Diana Krall's "From This Moment On" appears as a single track--"with Me"--from Melissa Dori Dye)? Is there any easy way to mass-edit metadata?

    Batchripper is already a very useful product and will become even more so, I am sure, when it enters the next beta phase.




    Originally posted by kevinoconnor
    According to the development status thread for the batch ripper, the stuff left to do is:

    MusicBrainz
    Inteligent meta data,
    Album Art scanning / import

    Does that mean that ripping to a single file is already done? I can't find any way to do it (in the batch ripper or in the regular ripper).

    Leave a comment:


  • kevinoconnor
    replied
    Re: dBpoweramp Batch Ripper: Discussions

    According to the development status thread for the batch ripper, the stuff left to do is:

    MusicBrainz
    Inteligent meta data,
    Album Art scanning / import

    Does that mean that ripping to a single file is already done? I can't find any way to do it (in the batch ripper or in the regular ripper).

    Leave a comment:

Working...