mp3 title formating

[iron2000]

In the Preferences=>General Preferences->Titles
we can set the title format.

In the in_mp3.dll configuration we can set it too.

Whats the use of having 2 places to set it?


I am having problems with the playlist with all the 5 series so far. I think I posted aboout it before.

[siebe83]

Prefs (Ctrl+P) > Titles > 'Use advanced title formatting when possible'

If this option is NOT checked, Winamp will use the title formatting as defined in the various input plugins. The formatting in in_mp3.dll config will be used for mp3 files, the formatting in in_midi.dll config (on Display tab) will be used for midi files, etc. If a plugin doesn't have a title config option (eg. in_wm.dll), it'll just display the filename (without extension).
If that option IS checked, it will always try to use the advanced title formatting rule as defined under Prefs > Titles. It will use this data to display info:

• when "Prefs (Ctrl+P) > Media Library > tab Library Options > click 'Modify Settings' button > 'Use Library title information for Playlist Item Formatting'" is checked it will use the data from the Media Library
• when that same option is checked, but the file is not found in the Media Library database, it will use the guessing method as set here:
  Prefs (Ctrl+P) > Media Library > tab Watch Folders > click 'Configure' button
  For tags that are set NOT to be guessed, the following point applies.
• when that same option is not checked, the info for the various tags (title, artist, album, etc.) will be provided by the various input plugins. The input plugin has to support this (some Input plugins only send the '%title%' tag, mostly just the filename (because some input formats don't support tags, for instance)).

I hope that covers it all...

Now as for your specific problem: what's the problem exactly?
"I think I posted aboout it before." > What did you try to solve it?
What are your title settings (i.e. all the ones I mentioned above)?
Is it related to title config options at all? If files don't play at all, I don't think it's related to that?
When does this problem occur? file format? file properly tagged? etc. etc.

[iron2000]

My last post:

http://forums.winamp.com/showthread.php?s=&threadid=168953

My config
ATF string
$if2(%comment%,'[???]')[' ['$num(%tracknumber%,2)']']': '$if2(%artist% ,'[???] ')'- '$if2(%title%,$filepart(%filename%))

in_mp3.dll
left as default


Didn't really try to solve it as it seems random.

Happens to mp3 files.
But only some in the list not all.

The file plays.
But when Winamp starts it produces a dummy entries with weird title format, same song length but doesn't play.
Seems like the dummy entries always appear above the playable entry.

The dummy entry only appears when you restart the player after you play the affected song.
Example:
Play song.
Close player.
Open player.
Dummy entry appear on above the affected song.
Repeat process and another dummy appears.

[siebe83]

Mmh, odd...

Do you have ANY 3rd-party plugins?
Could you confirm this also happens with a clean install?

I don't think this is related to the title config options? What if you use the default ATF string, the same happens?

If you right-click one of those 'dummy entries' > View file info..., what do you see? What's the path?

[iron2000]

Real path
X:\Awaiting\JAM Project\YuGiOh DUEL MONSTERS GX CW - Battle Communication!!.mp3

Dummy Path
G:\Program Files\Winamp\JAM Project (version 2) [02]: JAM Project - Battle Communication!!

It looks a bit like my ATF.

My only 3rd party plugin is the in_mpc.dll.

The current install is a clean install.

I think I know what caused it.
I found that in the affected files the comment goes to the next line(linebreak, enter).
And maybe because my ATF deals with comment therefore causing this problem.

Changing the comment to only one line sems to solve the dummy problem. Repeated the prevous stated process with an edited comment and no dummy appears.

Is this considered as a Winamp bug?

[siebe83]

I'll try to reproduce this when I got some more time. Hopefully tonight. If it is reproducable, I guess it would be considered as a bug.

[siebe83]

Reproduced!
I tested this with a clean install of Winamp 5.08d.

My ATF rule:
%artist% - $if2(%title%,$filepart(%filename%)) - %comment%

My test file, tagged with Alt+3 tag editor in Winamp:
Filename: Artist - Title.mp3
%artist% = Artist
%title% = Title
%comment% = This comment tag
has two lines
(i.e. after 'tag' I just hit the enter key)
See screenshot for details.

[siebe83]

Reproduce method:
1. Drag file to playlist
2. Close Winamp
3. Re-open Winamp

Again, for details see the screenshot.

It's clearly related to the way Winamp stores the title info in winamp.m3u. It's stored including the hard return in the comment tag. After re-starting Winamp, it will think the second line is the actual path, while the old path is seen as a second entry. Metadata of the old path is read again, and stored to winamp.m3u when Winamp is closed, so the same thing will happen again.

I think it's a bug/glitch. Winamp can't handle multiline comment tags in ATF.
I searched the Bug Reports for a bit, but didn't find anything related.
(I did find this, but I couldn't reproduce it)

I don't know about ID3v2 standards, but seeing that you can make multiline comment tags in Winamp, I'd say it should support them in ATF as well.

[DrO]

i wonder if there's a way to work around this ie hitting return in an edit control like those on the id3 dialog effectively creates 2 characters (new line and carriage return -> \r\n). now don't hold me to this, but the m3u format works on using those as a new entry as we've found by this issue.

so how to solve it... it may (since i'm not sure at the moment) be able to make something to work around this so that this \r\n pair is blocked or altered to a preset character. i'm sure the title hooking api in 5.x can be used to fix this issue.

as for the handling being a winamp issue, i'm not too sure since allowing multi-line comments goes against the m3u/pls formats *shrugs* personally i think winamp should either show the comment part upto the end of the first line or make all of the lines wrap so that this would be handled better. dunno since i never use the comment field anyway so not sure on what the general consensus on such a work around fix would be

[edit- > i'm probably rambling with this post so i hope something of it will make sense [/edit]

-daz

[siebe83]

Heh, I think it makes sense

Dunno what would be a better fix. I hardly use the comment field either, so... I don't think there's a lot of people anyway that use multiline comment fields AND also put the comment tag in their ATF rule. So I don't know how many users such a fix would affect.

Btw, in repsonse to what you said about \r\n... When I edit the tags in another program (Mp3/Tag Studio, which I usually use), it only creates one character between the two lines. It isn't even correctly displayed in the Alt+3 info box (screenshot), but on exit, it IS saved as a hard return into winamp.m3u:

#EXTM3U
#EXTINF:251,Artist - Title - This comment tag has
two lines
C:\Geluiden\Testmap\Artist - Title.mp3

Dunno...
(I also don't know wether that one character would be \r or \n; I guess it's \n but dunno...)
This extra information might be completely useless, but since I noticed I thought I should mention.

[edit]
Mmh, in Mp3tag it isn't even possible to create multiline comment tags...

[jaysjr]

ATF formating

I have Youtube files...

Filename is youtube - artist - title.mp4

I cannot get the ATF to drop the youtube give me just artist and title..

suggestion please


jay

[Aminifu]

I have Youtube files...
Filename is youtube - artist - title.mp4
I cannot get the ATF to drop the youtube give me just artist and title..
suggestion please

jay

You could download a free file renamer and use it to remove the "youtube - " character string from your filenames. Then the ATF $filepart(%filename%) command would work.

Much easier than a complicated ATF command to convert unwanted leading characters to spaces and then trimming leading and trailing spaces from the result.

[loubat]

You could download a free file renamer and use it to remove the "youtube - " character string from your filenames. Then the ATF $filepart(%filename%) command would work.

Much easier than a complicated ATF command to convert unwanted leading characters to spaces and then trimming leading and trailing spaces from the result.

Similar question: would it be easier to edit the tags to remove a leading "The" from the artists, or is there not some way to have Winamp ignore a leading "The"? When I sort a playlist by title, it puts "The Beatles" etc in the "T's" instead of the "B's."

[Aminifu]

Similar question: would it be easier to edit the tags to remove a leading "The" from the artists, or is there not some way to have Winamp ignore a leading "The"? When I sort a playlist by title, it puts "The Beatles" etc in the "T's" instead of the "B's."

Yes WA is inconsistent in how it treats the article "The" in an artist name tag. It some places (like the media library listings) the article is ignored and in other places (like the playlist editor) it is not.

Over time many have complained and proposed various ways to deal with this, so far nothing has changed. Each user learns to deal with this issue in whatever manner that suits them best.

[loubat]

So mass editing of the tags it is! Thanks for the reply.