dBpoweramp Batch Ripper: Discussions

[latefordinner]

Re: dBpoweramp Batch Ripper: Discussions

I just reformatted my hard drive and reinstalled BatchRipper. Although I have copied my old Results folder, which contains the results for many batches of rips, to the new path designated in BatchRipper's configure utility, when I run BatchRipper it does not show any of my old rips in the Results from Batch menu. How can I restore my old rips to that menu so that I can read them?

Thanks.

[RipTheWorld]

Re: dBpoweramp Batch Ripper: Discussions

ah.

That would be it then. Guess I'll be signing up for a second GD3 account then!

[Spoon]

Re: dBpoweramp Batch Ripper: Discussions

You have signed up for a dBpoweramp account?, not using an existing gd3 account, the two are different.

[RipTheWorld]

Re: dBpoweramp Batch Ripper: Discussions

Nope, still not hitting GD3. I have checked and the service wasn't down.

I even re-installed everything just to make sure.

[bhoar]

Re: dBpoweramp Batch Ripper: Discussions

Fair point. They do have quite a few models.

its this one http://www.mediatechnics.com/images/...s/4drivepc.gif

4 Drives, 600 CD capacity.

btw. The shake mode doesn't seem to shake.

Ok, I think I've got that hardware variant (well, the taller version with 4 input stacks). I'll see what I can do over the weekend.

If you get a chance, would you turn on logging in the batch ripper and capture the results of a --command=V... from the log window so that I know exactly what that unit is reporting itself as?

-brendan

[Spoon]

Re: dBpoweramp Batch Ripper: Discussions

1. Stripped '(Disc 2)' from Oasis - Stop The Clocks (Disc 2) even though both FreeDB and musicbrainz said it was 'Disc 2' and it was listed as '2/2' from AMG. (AMG just didn't have the 'Disc 2' in the title). Things like this are a real pain to sort out after the event. Will also put (Disc 2) onto an album title that already has it at the end so I end up with '(Disc 2) (Disc 2)' at the end of an album.

(Disc 2) is supposed to be stripped internally, we have to try to unify the metadata, that is make AMG, GD3, MB and freedb all match. There is 'Multi CD Add to Album' option in Meta.

7. Doesn't seem to be hitting GD3 at all. When both methods are selected.

Make sure the Commercial lookup rule is set to lookup both. Also enable the Manual Input and Review to see if GD3 is there, sometimes I have seen it myself a database can go down.

[RipTheWorld]

Re: dBpoweramp Batch Ripper: Discussions

Fair point. They do have quite a few models.

its this one http://www.mediatechnics.com/images/...s/4drivepc.gif

4 Drives, 600 CD capacity.

btw. The shake mode doesn't seem to shake.

[bhoar]

Re: dBpoweramp Batch Ripper: Discussions

It is a Mediatechnics 4 drive unit. So obviously using the Mediatechnics driver.

Erm, will get photo later.

Impact? pact? Newer right-side drives (or both side drives) Fusion units? Older left-side-drive Fusion DVD or number-number-number CD units?

And I'm not being facetious. The problem with writing drivers to the hardware is that each manufacturer has many varieties with similar but not quite the same driver requirements.

If you can link to a photo that matches yours and I can compare against my equipment, as I probably have something similar, and then try to optimize the driver for it.

However, with that said: it is probably the case that most of the wait time you are seeing is due to my current conservative coding practices. Some of that wait time will be removed once the hardware error handling code is improved, which is one thing I am currently working on.

Most drivers, other than the microboards ones, shouldn't be closing and opening the tray between Accept and Insert, though. Between Reject and Insert, yes, because often the reject spindle is below the trays...but not Accept...hmm.

-brendan

[RipTheWorld]

Re: dBpoweramp Batch Ripper: Discussions

It is a Mediatechnics 4 drive unit. So obviously using the Mediatechnics driver.

Erm, will get photo later.

[bhoar]

Re: dBpoweramp Batch Ripper: Discussions

3. The actions on the robot seem a bit screwed up. When a CD is accepted as good the following happens.
- Tray ejects
- Robot picks up CD and deposits in bin and stays above bin.
- Tray closes
- Tray ejects
- Robot arm resets to above try and pauses
- Robot then picks up new CD and deposits in tray

Not sure I see the need to close the tray before picking up a new CD. Also the arm can be reset to the tray position as soon as it has dropped the accepted CD. I reckon this is costing 5-10 CDs per hour in speed!

Which robot (make/model ... and link to a picture if you can find one)? Which driver are you using?

-brendan

[RipTheWorld]

Re: dBpoweramp Batch Ripper: Discussions

Sorry. A lot of my comments come across as a bit negative, but I am honestly just trying to help make it better.

I'm starting to run some pretty good tests on it at the moment so have a bit of feedback for you.

On the whole the intelligent lookups works well. I have it setup to lookup from AMG and only defaults to GD3 when it can't find anything. I have noticed some slight problems though.

1. Stripped '(Disc 2)' from Oasis - Stop The Clocks (Disc 2) even though both FreeDB and musicbrainz said it was 'Disc 2' and it was listed as '2/2' from AMG. (AMG just didn't have the 'Disc 2' in the title). Things like this are a real pain to sort out after the event. Will also put (Disc 2) onto an album title that already has it at the end so I end up with '(Disc 2) (Disc 2)' at the end of an album.

2. The year should be customisable to just the year and not the full date (although this may have been an option I missed). Also AMG sometimes has the 'dd' field missing and replaces it with 'zz' so you get a return like '1991 10 zz' (MusicBrainz has had the 'dd' and yet it has still taken AMG!) field Doesn't look so good!

3. The actions on the robot seem a bit screwed up. When a CD is accepted as good the following happens.
- Tray ejects
- Robot picks up CD and deposits in bin and stays above bin.
- Tray closes
- Tray ejects
- Robot arm resets to above try and pauses
- Robot then picks up new CD and deposits in tray

Not sure I see the need to close the tray before picking up a new CD. Also the arm can be reset to the tray position as soon as it has dropped the accepted CD. I reckon this is costing 5-10 CDs per hour in speed!

4. Smart capitalise should have an option to be auto applied. Error in Composer field when 'Joe Blogs; John Smith' got changed to 'Joe Blogs; john Smith'.

5. An option to remove error tracks would be good. I personally have no interest in keeping them for clients.

6. Track titles always seem to loose their sub heading part 'Its Only Rock And Roll (But I Like It)' becomes 'Its Only Rock And Roll'.

7. Doesn't seem to be hitting GD3 at all. When both methods are selected.

Will have a bit more feedback later on today as I am going to run a bunch of classical music through it on one of my other machines and see how it copes.

[bhoar]

Re: dBpoweramp Batch Ripper: Discussions

Inteligent meta data is all about using 3 or 4 providers and self correcting errors, you will see it in action with CDs with spelling mistakes (which are very common in all providers).

It is on our roadmap to allow the caching of changes to meta data (will be Release 2 of Batch Ripper), we have to go through legal departments though with the commercial providers to get the ok.

Good to hear. I hope our collective comments have been useful in figuring out the best solution (programmatically).

The bigger problem is convincing the metadata folks that they aren't "giving away the farm". Not the fun part of the business...

-brendan

[Spoon]

Re: dBpoweramp Batch Ripper: Discussions

Inteligent meta data is all about using 3 or 4 providers and self correcting errors, you will see it in action with CDs with spelling mistakes (which are very common in all providers).

It is on our roadmap to allow the caching of changes to meta data (will be Release 2 of Batch Ripper), we have to go through legal departments though with the commercial providers to get the ok.

[RipTheWorld]

Re: dBpoweramp Batch Ripper: Discussions

Ah yes. Had to pull a few tricks with the graphics settings as I go in over VNC. Tricked it to 1340x840 and the image stuff appears.

Haven't really tried out the intelligent data stuff much yet. I was under the impression though that if I entered some manual data it would be cached locally to be reused. If not then its probably going to be quicker just to rip the albums with a basic name and then fill in the data later in a tag editor.

I know we can't store the lookups from the data providers. Could we store a change database though? So that all changes that are made using the meta data interface can be reapplied automatically.

I just spent 7-8 mins entering the data on a CD into the interface and then scanning the cover art. It failed the first rip so I changed the settings and put the disc back in and I had to re-enter the data again. Not so much fun!

[Spoon]

Re: dBpoweramp Batch Ripper: Discussions

The inteligent meta service works on a per track basis.