dBpoweramp R16 Discussions

[ac16161]

Re: dBpoweramp R16 Discussions

SPOON,

I installed 16.9 over 16.8, 16.8 was writing meta data into ripped tracks. 16.9 IS NOT WRITING META DATA IN TRACKS. I have 10 albums, All but two had lookups from different sources, two I had to type in NONE of them have any Meta data them, I did not change any settings between 16.8 and 16.9, I DO NOT have Disable Tag Writing checked (I just check that). The only tags in the files are Replay gain tags, not even the album art is there. I'm dropping back to 16.8.

Additional:

I installed 16.8 over 16.9 and now it all works again, I re-ripped the same albums and the meta data is now in the files.

Same here: installed 16 Beta 9 over registered 15 today, ripped one album to FLAC, not a single tag written to the files. I changed the disc 1/2 entry before ripping but otherwise no intervention on my part.

[MTWolf]

Re: dBpoweramp R16 Discussions

SPOON,

I installed 16.9 over 16.8, 16.8 was writing meta data into ripped tracks. 16.9 IS NOT WRITING META DATA IN TRACKS. I have 10 albums, All but two had lookups from different sources, two I had to type in NONE of them have any Meta data them, I did not change any settings between 16.8 and 16.9, I DO NOT have Disable Tag Writing checked (I just check that). The only tags in the files are Replay gain tags, not even the album art is there. I'm dropping back to 16.8.

Additional:

I installed 16.8 over 16.9 and now it all works again, I re-ripped the same albums and the meta data is now in the files.

Hello Spoon,

I am really enjoying dBpoweramp R16 so far, particularly the updated user interface.

I do have a bug to report:

When entering metadata for a disc that currently has none via the track listing area, the artist is not correctly updated - it is shown in the track listing window but not in the top toolbar and when ripping, the track artist is not assigned. This can be easily duplicated by clearing the metadata for a disc then entering the metadata via the track listing area for a couple of tracks, then click on the first and observe that there is no artist shown in the top toolbar, then rip the track and observe that the track is not assigned the artist.

I also have an improvement suggestion:

When entering metadata via the track listing area, I have noticed that the behaviour is to advance to the next field as shown in the track listing window when pressing enter, though since I prefer to enter all of the track titles then enter all of the track artists, I would prefer that enter advanced to the same field for the next track - perhaps this could be an option? I have noticed that using the down arrow appears to achieve this, however only if the field is not modified, if the field is modified, using down arrow advances to the next field for the track instead. I have also noticed some apparent random behaviour when using the arrow keys to navigate within a field but cannot seem to duplicate this behaviour sufficiently.

Cheers,

Jason.

[schmidj]

Re: dBpoweramp R16 Discussions

Linkman,

A lot of the reason for using dBPoweramp is because it comes as close to guaranteeing your rips are good as possible. I had ripped close to 2000 CD's to m4a, using, at various times, Itunes and Winamp. Better than 5% of the albums had at least one bad rip, and I wouldn't find out until I listened to the whole album. So I am reripping those CD's, in addition to the ones I hadn't ripped, all to FLAC as well as m4a, using dBPoweramp. Gracenote had a pretty small percentage of the Soca releases in its database, I submitted data for many of the CD's I ripped with Winamp. AMG is the only database I've found with a substantial number of the Soca/Calypso CD's entered.

If Spoon isn't going to develop an interface to work with the new AMG database (which I assume will contain all the entries in the old database, just in a different format) I wish he would provide some handles so a user could develop his/her own software interface to work with other databases, either private or Internet based. I realize that there may be serious business considerations involved in dropping AMG, as there are in using or not using other online databases. However that should not stop individuals from developing their own interfaces, if they are able to license personal use of non-supported databases.

[jsmulree]

Re: dBpoweramp R16 Discussions

Hello Spoon,

I am really enjoying dBpoweramp R16 so far, particularly the updated user interface.

I do have a bug to report:

When entering metadata for a disc that currently has none via the track listing area, the artist is not correctly updated - it is shown in the track listing window but not in the top toolbar and when ripping, the track artist is not assigned. This can be easily duplicated by clearing the metadata for a disc then entering the metadata via the track listing area for a couple of tracks, then click on the first and observe that there is no artist shown in the top toolbar, then rip the track and observe that the track is not assigned the artist.

I also have an improvement suggestion:

When entering metadata via the track listing area, I have noticed that the behaviour is to advance to the next field as shown in the track listing window when pressing enter, though since I prefer to enter all of the track titles then enter all of the track artists, I would prefer that enter advanced to the same field for the next track - perhaps this could be an option? I have noticed that using the down arrow appears to achieve this, however only if the field is not modified, if the field is modified, using down arrow advances to the next field for the track instead. I have also noticed some apparent random behaviour when using the arrow keys to navigate within a field but cannot seem to duplicate this behaviour sufficiently.

Cheers,

Jason.

[Spoon-]

Re: dBpoweramp R16 Discussions

Genre was fixed in last update.

About the artist, you mention that refreshing populates the whole details correctly? if so then I do not think CD Ripper is at fault, as the code is self contained, it does not carry over from last time, we correctly work with tab to populate later items, it must be the CD drive which is missing the tab char on the first read...

[MTWolf]

Re: dBpoweramp R16 Discussions

Elaborate please on this. The Album Artist is only set for track 1?

The CD-Text loads and leaves the Artist and Album Artist fields blank, Only the First Track has an Artist and sometimes the compilation flag is set (again I suspect the following).
I suspect it is caused by the TAB character not correctly being interpreted as DITTO (same as previous entry).

In the example dump I included you'll see that the Artist for track 1 is filled in and all subsequent tracks have a TAB character (0x09) for Artist. The Artist for Track 2 is a TAB and therefor should be filled with the artist from Track 1, Artist for Track 3 is a TAB so it should be filled with the Artist from Track 2, Repeat for all Tracks/Fields containing a TAB. TAB can be used in any of the fields to Ditto the data from the same field in the previous track Entry.

Also, were the bugs documented in the following ever addressed?

https://forum.dbpoweramp.com/showthread.php?37111-CD-TEXT-bug-inconsistency

Thank You.

[linkman]

Re: dBpoweramp R16 Discussions

So I just did a little metadata experiment. I grabbed nine Soca/Calypso CD's, never ripped by me, all in the 10 to 15 year old range. Just pulled 9 in a row from a shelf, not specially selected. I looked to see who had metadata. 8 of the 9 were in AMG. One was in no database. One was in Discogs (and AMG) (and in Accuraterip). One was in FreeDB (and AMG) (and in Accuraterip). Two were in GD3 (and in AMG). None were in MusicBrainz. Given that I still have several thousand Caribbean CD's to rip, and only do it when I have spare time, this is a major issue to me. I do not relish the thought of entering manual metadata for three or more times as many CD's as I do now. Is there any solution?

Have you tried the missing ones with iTunes? I find that Gracenote has a very thorough catalog. I would hate to rip several thousand without a robotic changer though (QQ ripper with a supported changer could be your friend here).

[Spoon-]

Re: dBpoweramp R16 Discussions

The bug with CD-Text where the album artist is made the artist for only the first track still exists.

Elaborate please on this. The Album Artist is only set for track 1?

[mville]

Re: dBpoweramp R16 Discussions

Can that be considered a general request: trim (start and end) all metadata (not just from CD-Text). I've gotten burned by that a number of times with metadata from various sources. Just generally trimming all metadata would be nice.

Thanks,
Mike

Excellent suggestion.

[Michael Sargent]

Re: dBpoweramp R16 Discussions

Trailing Spaces are not trimmed from CD-Text strings (artist,title,genre,album,etc).

Can that be considered a general request: trim (start and end) all metadata (not just from CD-Text). I've gotten burned by that a number of times with metadata from various sources. Just generally trimming all metadata would be nice.

Thanks,
Mike

[MTWolf]

Re: dBpoweramp R16 Discussions

Another two glitches, R16 Beta 8,

Trailing Spaces are not trimmed from CD-Text strings (artist,title,genre,album,etc).

The bug with CD-Text where the album artist is made the artist for only the first track still exists.

Block of example CD-TEXT data for cd that comes up as with album artist as artist for first track.
(PT - PACK TYPE; E - EXTENSION; TR - TRACK NUMBER; Sq - SEQUENCE; U - UNICODE; b -BLOCK NUMBER; CP - CHARACTER POSITION; CRC not shown)
PT E TR Sq U b CP TEXT
80 0 00 00 0 0 00 - 57 69 6C 6C 00 53 74 2E 20 41 70 6F
80 0 01 01 0 0 07 - 6C 6F 6E 69 61 00 4E 65 62 75 6C 61
80 0 02 02 0 0 06 - 00 42 65 61 63 68 65 64 00 53 61 6D
80 0 04 03 0 0 03 - 65 00 57 69 73 74 00 42 69 67 20 48
80 0 06 04 0 0 05 - 6F 6C 6C 6F 77 00 48 65 61 64 69 6E
80 0 07 05 0 0 06 - 67 20 48 6F 6D 65 00 53 6F 6D 65 77
80 0 08 06 0 0 05 - 61 79 00 53 65 65 2C 20 4B 6E 6F 77
80 0 09 07 0 0 09 - 00 00 00 00 00 00 00 00 00 00 00 00
81 0 00 08 0 0 00 - 4A 75 6C 69 61 6E 6E 61 20 42 61 72
81 0 00 09 0 0 12 - 77 69 63 6B 20 00 09 00 09 00 09 00
81 0 04 10 0 0 00 - 09 00 09 00 09 00 09 00 09 00 09 00
8F 0 00 11 0 0 00 - 00 01 09 00 08 03 00 00 00 00 00 00
8F 0 01 12 0 0 00 - 00 00 00 00 00 00 00 03 0D 00 00 00
8F 0 02 13 0 0 00 - 00 00 00 00 09 00 00 00 00 00 00 00

[MTWolf]

Re: dBpoweramp R16 Discussions

Spoon,

Minor issue R16 Beta 8. I now understand some of the problems with not being able to submit a new cd to Freedb. One cd I use as a test case shows the problem. It is not in any database, Perfect match review show no information, but it has CD-Text. The Submit To FREEDB is grayed out. I ran the cd through my Software and found that in fact there is a match in Freedb, but it is the wrong disc. So the lookup is getting an answer but not the right one. There is no indication of this, except the Grayed out submit button. The button should NOT be grayed out, and I should be able to submit the cd in a different category than the one returned (ROCK) since it is a JAZZ cd.

Test cd is Ron Davis: Pocket Symphronica (correct spelling) Rally Records REA-ED-5886 UPC 625712588624 No Data from other lookups, no data shown for FREEDB.

CDDB ID 930c430b MBID c2femhocun7oFxb99GBjmBAmA9E-
Freedb lookup http://freedb.freedb.org:80/~cddb/cd...opment&proto=5
MusicBrainz Freedb Lookup http://freedb.musicbrainz.org:80/~cd...opment&proto=5
MusicBrainz Lookup http://musicbrainz.org/ws/2/discid/c...mA9E-?&fmt=xml


Thanks.

[Spoon-]

Re: dBpoweramp R16 Discussions

Their servers are being taken offline, no one can access it.

[schmidj]

Re: dBpoweramp R16 Discussions

That is unfortunate. Is there any way of getting or accessing a legacy copy of the old AMG database and continuing to use it, with, let us say DBPA 15? I wouldn't mind paying them their $12/year (or thereabouts) membership fee for access. Going from 90% metadata to 10% or 20% is an awful hit for me.

[Spoon-]

Re: dBpoweramp R16 Discussions

We cannot do anything about AMG, it goes off line in a matter of months. The replacement is not AMG, even though it is the same company, it is a totally different database and we are not going to implement it for R16.