dBpoweramp Music Converter R14.3

[d2b]

Re: Stepping back to R14.2 from the beta version 14.3

I've love it if your employer could see what outstanding abilities you've demonstrated on this.

twit...There's no need to be condescending.

It's not at all obvious to a first time user of this Action Item (Format Value "PUBLISHER": %organization%) that it creates a new PUBLISHER field with the value associated with the ORGANIZATION field. What "Format Value" means is not at all obvious as a standalone expression, especially when the question was about changing field names, not values. If you already know what this action item does, then presumably it's obvious to you.

The second part of JJ's action group (Remove fields "ORGANIZATION") is self-defining.

A slight problem with this two-part combined action item is that, if run twice by mistake, the new PUBLISHER tag is removed as well because there is no longer an ORGANIZATION tag. One must proceed carefully here.

While this topic may appear to be off-thread, the issue is important to us here because Spoon has proposed to change TOTALTRACKS and TOTALDISCS to TRACKTOTAL and DISCTOTAL in version 14.3. If these tags don't exist in the earlier form in some of our existing library files because they were ripped with another application, running a two-part action group in mp3tag could have disastrous results. The procedures need to be carefully examined first, so that correct action items are run oh the appropriate files.

d2b

[garym]

Re: Stepping back to R14.2 from the beta version 14.3

JJ's response is the approach I was thinking would do what you are seeking.

http://forums.mp3tag.de/index.php?showtopic=15982&view=findpost&p=65344

Are those steps not working? I'd follow up to that post with any feedback as to what is not working as expected from his suggestions or for additional clarification. I'm assuming you've played around a bit to get the hang of how action groups work?

Edit: or even steveheros post. Seems to solve your issue? Youll need to clarify more as to which step is not clear or not working.

[twit]

Re: Stepping back to R14.2 from the beta version 14.3

(removed doublepost)

[twit]

Re: Stepping back to R14.2 from the beta version 14.3

Gary...

I did post this question on the forum but received only complex, convoluted responses that take several steps not clearly explained. Those explanations were not clear either...and I'm no dummy.

"dvdr" suggested that it was a straightforward procedure to do this, but his/her explanation made no sense. What I'm looking for is an answer, not a place to continue asking questions.

Thanks...

d2b

Uhhh, the issue seems to much more with your self-assessment of your abilities than anything else. You've recently posted two questions on the mp3tag forums:

http://forums.mp3tag.de/index.php?showtopic=15809&start=0&p=64638&*entry64638

http://forums.mp3tag.de/index.php?showtopic=15982&st=0&p=65343&*entry65343

In both cases, you received a detailed, accurate and easy-to-follow response in less than an hour from JJ. Others chimed in with additional alternatives. You never bothered to provide a single response to either thread, so your judgment of the reponses being "....complex, convoluted responses that take several steps not clearly explained" is not only wholly inaccurate but insulting in that you came to this conclusion without posting a single clarifying question.

I've love it if your employer could see what outstanding abilities you've demonstrated on this.

[garym]

Re: Stepping back to R14.2 from the beta version 14.3

Gary...

I did post this question on the forum but received only complex, convoluted responses that take several steps not clearly explained. Those explanations were not clear either...and I'm no dummy.

"dvdr" suggested that it was a straightforward procedure to do this, but his/her explanation made no sense. What I'm looking for is an answer, not a place to continue asking questions.

Thanks...

d2b

Can you post a link to the answer you received. I'll take a stab at adding more info. Perhaps I'm missing somwthing, but seems it should be an action that batch copies info to new fields and then deletes old fields. Then again I assume you've tried field mapping within dbpa when ripping so I'm also confused myself as to why that wouldn't work. I'm still running 14.2 so can't directly test.

[d2b]

Re: Stepping back to R14.2 from the beta version 14.3

I'm fairly certain this is doable in mp3tag (which I also use). They have a very helpful forum with some real gurus that can give you the steps/code. I'd recommend posting your question about doing this over there. Regards. Gary.

Gary...

I did post this question on the forum but received only complex, convoluted responses that take several steps not clearly explained. Those explanations were not clear either...and I'm no dummy.

"dvdr" suggested that it was a straightforward procedure to do this, but his/her explanation made no sense. What I'm looking for is an answer, not a place to continue asking questions.

Thanks...

d2b

[garym]

Re: Stepping back to R14.2 from the beta version 14.3

@ dvdr



Sorry, but it does not appear to be easy for me to do what I need to do. I wish to keep the tag value and change the field name. For example, first assume this tag already exists as a VorbisComment: ORGANIZATION=Warner Brothers

Then assume that I wish to change the tag's field name so that it is like this: PUBLISHER=Warner Brothers

After this change is made, the ORGANIZATION field should not longer appear in the file.

How do you program mp3tag to do this? I do not find any way to make this happen.

d2b

I'm fairly certain this is doable in mp3tag (which I also use). They have a very helpful forum with some real gurus that can give you the steps/code. I'd recommend posting your question about doing this over there. Regards. Gary.

[d2b]

Re: Stepping back to R14.2 from the beta version 14.3

@ dvdr

So you just load your collection, set it to "format tag" and tell it to read the newer, for you useless tags, and apply the value to the tag you need to use. I do these automated tag changes, too, quite often - it's easy & straightforward.

Sorry, but it does not appear to be easy for me to do what I need to do. I wish to keep the tag value and change the field name. For example, first assume this tag already exists as a VorbisComment: ORGANIZATION=Warner Brothers

Then assume that I wish to change the tag's field name so that it is like this: PUBLISHER=Warner Brothers

After this change is made, the ORGANIZATION field should not longer appear in the file.

How do you program mp3tag to do this? I do not find any way to make this happen.

d2b

[PeterP]

Re: dBpoweramp Music Converter R14.3 (Vorbis Comment Requests)

Any software other than mp3tag having trouble reading ID3v2.3 date/year tags written by dB? Mp3tag author is aware of this problem and a fixed version should be out soon.
I've tested various mainstream software and see other significant problems (everyone else allows only digits to be written to ID3v2.3 TYER, usually up to four digits).

[dvdr]

Re: Stepping back to R14.2 from the beta version 14.3

@ d2b
Hi, in case you need to easily batch-update your tags, here's a suggestion: use mp3tag (mp3tag.de).
It supplies easy batch-updating of tags and can be programmed, too.
So you just load your collection, set it to "format tag" and tell it to read the newer, for you useless tags, and apply the value to the tag you need to use. I do these automated tag changes, too, quite often - it's easy & straightforward.
In terms of advanced formatting, I can even do a programmed update like "replace separators from , / or : with; Then format composer = forename surname to composersort = surname, forename then import covers using a certain naming-scheme and finally sort and rename all files in a programmable folder/naming,structure" and all that in one go....
So imho it's worth checking it out, if you plan to use the advantages fo the 14.3-release...

[Spoon-]

Re: Stepping back to R14.2 from the beta version 14.3

You have to uninstall R14.3 then install R14.2

If there is a reference to a tagging standard on the official site we will adopt it, the previous was a guess taken 10 years ago in the absence of such....

[d2b]

Stepping back to R14.2 from the beta version 14.3

I've yet to understand the rationale for changing these default FLAC tags:

TOTALTRACKS --> TRACKTOTAL
TOTALDISCS --> DISCTOTAL

What applications support the proposed changes? I've only seen a vague, outdated suggestion on the xiph.org web site that proposed these two tags. (FWIW, that web site appears to be stagnant at best, and the email moderator has so far failed to moderate attempts to post messages.)

Our radio station library is heavily invested in the 'former' tags, and the current 14.3 beta release doesn't permit us to continue using them. So, the question is: "How do I reinstall 14.2 over the current 14.3 beta version that I have on this machine?"

d2b

[PeterP]

Re: dBpoweramp Music Converter R14.3

So TYER contains YYYY and TDAT contains DDMM?

Yes, just like http://id3.org/id3v2.3.0 says. Not every application out there enforces this strictly though.

[d2b]

Re: dBpoweramp Music Converter R14.3 (Vorbis Comment Requests)

Spoon, et al...

Please consider these requests for the 14.3 release, and certainly for version 15 when development commences:

1. Add Publisher as an additional option for mapping Label in the Configuration > Codecs > Advanced Options > FLAC ID Tagging > Vorbis Comment Mapping *1.

Reason: Publisher is a better description than either Label or Organization, especially since so many CDs are 'published' by independent artists rather than record companies. Furthermore, J. River Media Center uses Publisher to describe this tag. Lastly, audio books are not published by record labels.

2. It is imperative to us that all FLAC tags entered with a semicolon/space combination between multiple entries on the same line be written as individual tags. This happens for some tags such as Composer and Style,but not for tags like Producer, nor does it happen for custom tags like Performer that we created.

Reason: There are VorbisComment recommendations that the Performer tag be entered in this format: PERFORMER=John Doe (Lead vocals, acoustic guitar, banjo, mandolin). If this is done when there are four or five performers or even more on a track, each with multiple roles and instruments, the single-line tag that results is too long to be handled by dbpoweramp and other applications, including the PC's operating/file systems. According to the VorbisComment recommendations, multiple entries under a field name should each have their own FLAC tag.

3. Add an option so that the track length, if written as a FLAC tag (LENGTH=X), can be written as mm:ss rather than in milliseconds.

Reason: This seems like it ought to be a no-brainer, even if it is has to be added included as an optional choice rather than by default.

4. Add an option to permit (force) FLAC tag field names to be written in all uppercase format, even though the VorbisComment standards specify that letter case should not matter.

Reason: Upper case field names appear to be the defacto standard for FLAC files and for the other tools that read and/or tag them. It makes it much easier to identify FLAC tags with a hex file viewer. At least one application that we use requires upper case field names in order to display the track title and artist correctly.

Items 1 & 2 above are our highest priority, but because of Items 3 and 4, we have to post-process ripped albums using mp3tag in order to obtain usable files. We also cannot use dbpoweramp to enter Performer tags because they end up too long, requiring that we post-process albums using mp3tag to add/create the Performer tags. The workflow because of this is daunting, to say the least, when it could and should be possible to do this all in one fell swoop using CD Ripper.

TIA for considering these requests.

d2b

[mville]

Re: dBpoweramp Music Converter R14.3

The new dB version manipulates ID3v2.3 TYER/TDAT fields strictly according to the specification. If it turns out that most of other software cannot handle this properly, we will loosen the standard compliance to allow better compatibility.

So TYER contains YYYY and TDAT contains DDMM?