dBpoweramp R16 Discussions

[Dat Ei]

Re: dBpoweramp R16 Discussions

Hey schmidj,

If you enter or recover from the metadata source different genres or years for different tracks, all is well until you open the "review metadata from individual providers" page. At that point, the software, without warning, overwrites the genre and year tags for every track after track one with the data already entered for track one. This has screwed me up on numerous occasions when I've wanted to quickly correct something like the composer field on a bunch of tracks and have therefore opened the "review" page where it is easy to copy and paste stuff between tracks, only to discover that it has messed up my recently entered genre data. Please fix this.

I second that! Even if one quits the review dialog with escape, which means "cancel" / closing the dailog without any change in data in the windows style guide, the original data is lost.


Dat Ei

[schmidj]

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?

[schmidj]

Re: dBpoweramp R16 Discussions

I finally got around to downloading the beta and have exercised it a little. I really like the clean look and use of appropriate color.

Now I realize that the update is only part way done, but there are two issues in R15 and earlier that are still there, both have caused me grief. I'm hoping they can be addressed in the final release:

If you enter or recover from the metadata source different genres or years for different tracks, all is well until you open the "review metadata from individual providers" page. At that point, the software, without warning, overwrites the genre and year tags for every track after track one with the data already entered for track one. This has screwed me up on numerous occasions when I've wanted to quickly correct something like the composer field on a bunch of tracks and have therefore opened the "review" page where it is easy to copy and paste stuff between tracks, only to discover that it has messed up my recently entered genre data. Please fix this.

The other issue, also involving the "review metadata from individual providers" page: If you make an entry in the Genre or Year boxes, and then move the cursor elsewhere on the screen, even clicking outside either box, those boxes don't loose the focus. If you then use the scroll wheel or the arrow keys to scroll down the screen, instead of scrolling the screen, it scrolls through the different presets for Genre or Year, messing up the data you just entered. The only way to move the focus is to actually click on one of the boxes that does not scroll, like one of the titles. I've had this happen literally hundreds of times, even though I well know how it behaves, as it is anti-intuitive. Can you please have those boxes loose the focus when the cursor isn't over them, or at least allow a click anywhere outside the box, like in a blank part of the screen, remove the focus. Please!!

Now, I'll be sorry to loose AMG. Much of my collection is Caribbean music, Soca and such. The stored metadata there is very sparse, and often AMG is the only provider who has metadata. I'll be experimenting to see how Discogs compares. The FreeDB data, if present, is often such a mess as to be useless, and completely lacks important fields, such as composer (I've looked at their raw database, there are very few tags in it). If there is a cost issue, it might work if there were a subscription system with the necessary handles in the ripper where individuals could subscribe to a different metadata provider and have it link to the ripper.

[MartinGr]

Re: dBpoweramp R16 Discussions

Hey MartinGr,
AMG support will be discontinued: clickclack!

Isn't that a problem of the databse content, but not the dBpa version?

Dat Ei

Oh, sorry. I thought I've read a long time ago, that AMG will be replaced by a database from the same distributor, with a different name. But I suppose I understood that wrong.

And of course: the composer problem is a problem of the database. Perfect Meta doesn't help here much, because only Discogs seems to provide this information (?). But if AMG isn't available anymore, I'll have to live with that.

Thanks,
Martin

[Dat Ei]

Re: dBpoweramp R16 Discussions

Hey MartinGr,

AMG is out at the moment? Or will it stay like this?

AMG support will be discontinued: clickclack!

I had a lot of completely wrong composer entries with the new beta... (songwriter details are very important to me when I tag my collection)

Isn't that a problem of the databse content, but not the dBpa version?


Dat Ei

[MartinGr]

Re: dBpoweramp R16 Discussions

AMG is out at the moment? Or will it stay like this?
I had a lot of completely wrong composer entries with the new beta... (songwriter details are very important to me when I tag my collection)

[Spoon-]

Re: dBpoweramp R16 Discussions

Is modification date, editing tags updates the modified date.

[Dat Ei]

Re: dBpoweramp R16 Discussions

What timestamp decides on newer or older? Creation or modification date?

And if it is the modification date, will dBpa consequently update the modification date in the future, if one edits the metadata?


Dat Ei

[Spoon-]

Re: dBpoweramp R16 Discussions

It is the DSP Effect Conditional Encode. You can set to skip the file, unless the source is older than destination. However there is no way to delete obsolete files.

[Dat Ei]

Re: dBpoweramp R16 Discussions

Hey Spoon,

I have questions regarding your post "Batch Converting For Car", or to be concretely regarding this two sentences:

dBpoweramp will be setup to write the files to a location on the HDD, and later as new music is added to my main collection, Batch Converter will convert just the new files, saving time.

The conditional encoding effect enables Batch Converter to be loaded at a later date and only new tracks (which match filter) to be encoded, saving time.

How will Batch converter detect new files or new tracks?

Will the algorithm do something like a sync:
- convert sources missing at the destination,
- convert sources that are younger (creation timestamp or modification timestamp) than existing destinations,
- delete obsolete files at the destination?
That would be very helpful in case one has edited metadata for one's lossless source files and want to update the lossy copies in several collections.

Is it possible to overwrite the feature to convert all files and not only new files?


Dat Ei

[Salem874]

Re: dBpoweramp R16 Discussions

You are on the insider build program?:

https://forum.dbpoweramp.com/showthr...eginConversion

Yes i am actually... Just replied to that thread,

[Spoon-]

Re: dBpoweramp R16 Discussions

You are on the insider build program?:

https://forum.dbpoweramp.com/showthread.php?37608-All-WMA-Rip-Conversion-Attempts-clEncoder-BeginConversion

[Salem874]

Re: dBpoweramp R16 Discussions

Can you still convert from ALAC to something else e.g. flac, without getting an error?

Conversion from ALAC to FLAC works flawlessly

[mville]

Re: dBpoweramp R16 Discussions

I'm trying to convert from ALAC to WMA Lossless, but get an error on when converting, with the error reading "Windows Media Audio 10: Error Starting WMA Writing (unknown reason). (clEncoder::BeginConversion)"

Any ideas what is causing this, or how i can get it converting again?

Can you still convert from ALAC to something else e.g. flac, without getting an error?

[Salem874]

Re: dBpoweramp R16 Discussions

Run the linked program, then install R15 64 bit, then R16 64 bit.

I've finally got round to doing this...But unfortunately i'm still unable to convert to WMA (Lossless).

I'm trying to convert from ALAC to WMA Lossless, but get an error on when converting, with the error reading "Windows Media Audio 10: Error Starting WMA Writing (unknown reason). (clEncoder::BeginConversion)"

Any ideas what is causing this, or how i can get it converting again?