Aaah... ripping my hair out!

Here´s the thing; I want a proper album information-field (you know, instead of showing the album name over and over again, it just shows up one time but with some info about codec/year/album length etc.) but i have to write the code for it, _without_ the use of %tracknumber% as somekind of "container" for this info.
Because if i´ve figured it all out right, the first track of the album will (obiously) act as tracknumber 1, and i will then tell foobar that "on tracknumber1; show this info (albumname/codec/whatever)"?

And here is the hook:
Since some of my mp3s doesn´t have any tracknumber specified in the id3tag, tracknumber cant act as the "container" of the album info. I can absolutely NOT tag add the tracknumber to the id3tag since these mp3s are original group-releases (albums that have been ripped and released under very specified and strict rules, which by a checksum-file follows. the checksum-file will mark the release as bad if i edit some of the id3-info, and thereby the release will loose it´s original value.).

So how should i really do this? What other meta-tag should i use with $select so the album info can view correctly? Shouldn´t i use metadata at all? My mind is getting pretty f-ed up by this time . Hoping for some answers atleast .

A group that releases "under very specified and strict rules" and yet "some of my mp3s doesn't have any tracknumber specified in the id3tag"? lol @ scene releases, are you trying to apply foobar to legitimate mp3 use or only for strange illicit bootlegs?

In an effort to be helpful, is there any information whatsoever that exists to distinguish track order with your releases? Maybe filename? Maybe directory structure? You might also be able to use foo_custominfo to store track-specific information without writing to tags and avoiding "the checksum-file will mark the release as bad". Using some sort of cue sheet or apl file might also be a decent solution.

Yeah i know, some things about "the scene" can be very ironic sometimes. And if you point it out to someone you get flamed like never before... ;D

But yeah, sounds like you got some good ideas. The songs filename does always begin with either "01_songname" or "a1_songname", so maybe that could be of use, the two first digits/characters? How would i translate this into something that foobar understands, codewise? Im pretty new to this foobar-scripting thing so assistance is encouraged! ...

Otherwise, wouldn´t it be possible to make use of the m3u-files that come with the albums?

Well, i shall take a look at foo_custominfo now, thanks for the tip.

Okey, i´ve installed foo_custominfo and it seems to work out well.

Now i just need a little bit of help with writing this script. I want to have the opportunity to mark all the tracks of an album, rightclick on them and click on a command like "Number tracks from 1-10". Song one will then get the custominfo tag "1", song two will get the tag "2", etc.

So basicly i need a script that counts from 1 to 10.

$left(%filename%,2) will cut out first two characters if it helps. I think it's better than dealing with all the hassle of adding information with custominfo.

The masstagger has a feature called "Auto Tracknumber" - use that to number your files. Be carefull: you want to have the tracks in the right order in your playlist before doing that.

No, not very ironic. Just plain stupid.

As for the checksum files: There are several programs that can write md5 or sfv checksum files themselves, so you can make your own checksums after tagging the files and won't break the very specified and strict rules.

What is ironic is the fact that this group that doesn't seem to care about essential tags calls MP3 bootlegs "original" and even you apply some sort of "original value" to MP3 files.

btw: The only use of these checksum files is for you to be able to check whether your download is correct or not.