Jaikoz Help

If you are running Jaikoz you need to modify the value of -Xmx within the Info.plist

You can confirm you have made the change correctly when you start Jaikoz. Click on the Console tab at the bottom and the first line should say how much memory Jaikoz has been allocated. If you cannot see the console you may have hidden the Detail Pane, make sure it is checked in View/Show View Pane.

If you are running Jaikoz you need to modify the value of -l and -m within the Info.plist

This displays a summary of the file including audio information such as the length of the track and the size of the file. If the file contains artwork you can view it full size by double clicking on the image itself.

This shows the most common editable fields such as Artist,Album and Genre, all these fields are likely to be understood and used by most music players and organisers. The Is Compilation option is not standard but is becoming a de facto standard and is likely to be better supported by other applications in the future.

This shows all the MusicBrainz Ids that can be used to lookup information from MusicBrainz, plus it shows other fields that have been populated by the MusicBrainz lookup, that do not fit into a standard ID3 field.

This shows the most common fields together with their corresponding sort field. Sort fields are useful because they can be used to sort songs in a more useful way than using the main field. For example sort fields can be used to sort individual artists by their surname, or can disregard 'The' in group names. Some of the Sort fields are only supported by iTunes and are unlikely to be recognised by other Music Players.

This shows relationships with websites such as Discogs and Wikipedia for the release or artist.

This shows the Lyrics associated with the file

This shows the artwork associated with the file. You can add additional artwork and delete existing Artwork.

The Console tab summarizes tasks you have done, plus any problems encountered. Everything written to the Console Panel, also gets written to the User Log, and everything will always be written to the User Log even if the Console Panel is not displayed.

The user log is stored in your ~/Library/Logs folder, the latest log is called jaikozuser-0-0.log, as it get larger it will be renamed jaikozuser0-1.log, and an empty jaikozuser0-0.log will be created. There is also a jaikozdebug-0-0.log that contains additional information useful to us if you have a support query with Jaikoz. You can view the logs using the /Applications/Utilities/Console application.

When enabled all MusicBrainz Recording Ids fields that are the same as in at least one other song are highlighted.

When enabled all Acoustid Fingerprint fields that are the same as in at least one other song are highlighted.

You can change the following options the Preferences/MusicBrainz/Acoustid window.

The Save Acoustic Ids to file as retrieved save the acoustic id to the file as it is retrieved. This protects you from losing your work against a system crash, because acoustic ids are always correct, no verification is required by the user

Once you have matched your songs to MusicBrainz you can submit your fingerprint/MusicBrainz Id pairings to Acoustid to help build the database. But to do this you need to get a (completely free) Acoustid key, enter that into the Acoustid keyfield

The Do not match online if already have a MusicBrainz Recording id option allows you to skip over songs that have already had a Recording id, this option is enabled by default.

If the matching MusicBrainz song has a match to a Discogs Release Jaikoz can use Discogs to retrieve additional information for the song, if you do not wish to do this then check Do not update from Discogs when matching

These preferences apply to both matching from MusicBrainz and matching from Discogs

The Prefer do not match to Various Artist Compilations and Prefer do not match to Single Artist Compilations options will give preference to matching a song on an original release such as original album or single, and will only match to a compilation album as a last resort.

The selected Preferred Country of release will give song linked to a releases in this country an improved score.

The selected Preferred Media Formats will give songs with releases of this type an improved score.

If Preferred Release Date is set to Earliest Release Date this will boost scores of releases with the earlier release dates, you can also specify Latest Release Date and No Preference

The Only match if all songs on album were matched option is useful if you have a collection that already had good metadata and you want to ensure that only really good matches based on your groupings are made but it does also mean if you have any partial albums they will not be matched to a MusicBrainz or Discogs release.If you have only this option enabled it means that any album that is matched must be completely matched but this doesn't have to be on a folder by folder basis, so for example if you have a folder containing 10 songs that failed to match any album but existing metadata in the songs creates two groupings of 5 each, then one of those grouping could be matched to a 5 track release that would be okay.If this option is enabled individual song by song matching to the best album does not take place.

You can get safer matching if Only allow match if all songs in grouping match to one album is enabled. If your songs are already organized one folder per album then songs in the folder will only be matched to a release if all songs in that folder can be matched to the same release. Usually Jaikoz is clever enough to recognise when you have a multi disc release and have created separate folders per disc as well, in this case it will only allow a match if songs in each subfolder are matched to a disc of the same release.Usually this option should be enabled because although it prevents album folders being broken up but allowances are made if Jaikoz identifies you have some have folders containing a random assortment of files, and it also identifies when you have duplicate file sin the same folder. If you disable this option then if Jaikoz fails to match the folder to an album it will then try and group the songs in the folder into smaller groupings based on their existing metadata, if this fails and matching to Discogs fails as well it then does individual song by song matching and will match each song to the best album it can find with the limited information available.

If both Only match if all songs on album were matched and Only allow match if all songs in grouping match to one album are enabled then all the songs in a grouping must match to same album and all songs on the album must be matched, so if there are 10 songs in a folder it can only match a 10 song album. If your music collection is already well organized and you have complete albums this ensures that only very high quality matches will be made to MusicBrainz and Discogs but it does also mean if you have any partial albums they will not be matched to a MusicBrainz or Discogs release.

If neither options are enabled then Jaikoz willl eventually match each song individually so if the song can be identified it will be matched. This works very well if you have a very messed up collection and just want to identify each song, it also works if you use your songs as a jukebox and are not interested in the album that the song belongs to.

This lists most of the values that can possibly be updated by MusicBrainz upon a successful match, this includes text fields and Artwork. By default all fields are populated on a MusicBrainz match if MusicBrainz has a value, but you can select to only Replace if empty or Never Alter the field.

When matching cover art Jaikoz will attempt to finest the highest quality image it can from a variety of sources, the image is added to the audio file automatically but like all tasks the image will not be saved until you save changes.

The Romanize non-Latin script artist names whenever possible uses the Latin versions of non-latin names where possible. If the artist names is in a non-Latin script such as Chinese, Japanese or Cyrillic its Latin equivalent will be used if available. This is very useful for Western speakers who typically only can only pronounce Latin script but may have music from other cultures because then it allows them to pronounce the names of any of the artists in their collection. The Latin name is often stored as an additional alias within the original MusicBrainz database, it maybe a transliteration of the original name or an alternative Latin based name that the artists is known by in the Western world. The JThink Music Server additionally links Discogs artists to the corresponding MusicBrainz artist if it exists so that now you can often get Latin names even when your songs only match a Discogs release and not a MusicBrainz release.

This is the current list of fields that can be auto populated

The Put Original Year into Year field can be used when the original album is found so that the original year is stored in the year field. When creating play-lists in some players you may want to create date based play-lists i.e. Songs from the 60's and only some players provide access to the original release year.

This lists additional values that can possibly be updated by MusicBrainz upon a successful match.

You can specify options for genres, because most players only understand the first genre linked to a song some customers put a list of genres in the grouping field as a single field to make it easier to create multiple genre based play-lists. So with Jaikoz you can also specify whether to write genres to the grouping field as well, independently of the values added to the genre field.

These preferences apply to both matching from MusicBrainz and matching from Discogs

Add EP and Single release types to release title is useful for distinguishing between a release and a single of the same name, it is common for a release to have the same name as a song on the album and if that song is released as a single there is nothing to differentiate between them.

Sometimes a recording artist may use a different name on some of their releases, this can me it harder to manage your collection. If you enable Use standard Artist name instead of name displayed on cover then the artist name will always be used in your songs metadata.

Sometimes a recording is given another name on a different release, to force a consistent name to be used enable Use standard song title instead of title displayed on cover

The Disc No field is very useful in multiple disc releases, for example to distinguish between the first track on disc 1 and the first track on disc 2. But not all applications provide access to this field so it can be useful to add to the release title by setting this option to Always Add Disc No Information to the release title. Multi-disc releases sometimes give an actual name to each disc and this can be added to the release title by setting the option to Add Disc No to the release title if disc has title.Or you can elect to do nothing special for multi-disc release by setting the option to Never add Disc No information to the release title.

This looks at the Release Id of the selected song, it then checks all the other potential matches for the other songs and selects any match that has the same Release Id. This is a nice easy way of matching a whole album of songs just by finding the best match for one song.

Displays the selected songs album details in MusicBrainz using your Web Browser

Displays the selected songs details in MusicBrainz using your Web Browser

By default songs are processed in batches of ten, after the first ten songs are processed the matches are displayed in a dialog. Whilst you are reviewing the options the next batch of songs is processed in the background. If you select OK the songs are updated to your matches. This continues until there are no more songs to process, unless you select Cancel. You can select Reset to undo any changes you have made in the current batch that you are reviewing.

The Number of songs to process before showing dialog sets how many songs are processed before displaying the potential matches in a dialog when running Manual Correct Tags from MusicBrainz.

The MusicBrainz Server field specifies what MusicBrainz server to use for lookups, this is usually http://www,musicbrainz.org, but you may want to access the beta server or setup a local server you can configure Jaikoz to use it here.

In order to submit data to MusicBrainz you need to have a user account, these are completely free and can be created at the MusicBrainz Website. If you have a user account specify your username and password in this tab in the MusicBrainz Username and MusicBrainz password fields. By submitting data to MusicBrainz you are helping to improve this open source database and maintain the most accurate music resource in existence. By submitting information for songs that you own you create an archive of information that will never be lost even if your own files get damaged. Currently the majority of information that is contributed to MusicBrainz is via their website, but you can contribute some information automatically via Jaikoz. if you do this please ensure the information you submit is accurate and of a high quality.

If you successfully create an Acoustid fingerprint for a track and you have independently found a match on MusicBrainz you can submit the pairing to the Acoustid database, so should use this task AFTER matching your songs. This helps build the Acoustid Database and means that subsequent users will be able to match to the correct MusicBrainz Id if their song has the same fingerprint even if they have no metadata. All displayed/selected pairing will be submitted.

MusicBrainz has a Folksonomy cloud that can be used to tag artists, releases and tracks with anything you like. Jaikoz uses this to add genres at releases and track level. Because genres are subjective this feature is going to become more useful as more people submit their genres, so please give it a go. Jaikoz also uses the folksonomy cloud to fix the genre field when correcting songs from MusicBrainz.

If you successfully matched a track to MusicBrainz and you have independently found the bar code for the release you can submit the pairing to the MusicBrainz database, this helps build the MusicBrainz Database. For example you may have matched a release to MusicBrainz but MusicBrainz does not contain the Bar code, however if you have the original release you can read it from the cover add it to the Bar code fields for the songs and then submit to MusicBrainz with this task.

You can rate your songs in MusicBrainz and then submit the ratings to MusicBrainz, this helps others identify the best songs for an artist they may not know so well.

You can submit a new release to MusicBrainz, either ensure a single album is listed or use the context menu to submit a new release to MusicBrainz. Your release details will be opened in your browser with most of the information completed making it much quicker than adding the release manually.

MusicBrainz can store a list of the release you own and inform you of new releases by your favourite artists. Submitting releases can be done via the website but Submit MusicBrainz Collection provides an easier way to submit all the releases loaded in Jaikoz in one go. You can have multiple MusicBrainz collections and Jaikoz allows you to submit your songs to your chosen collection.

MusicBrainz can store a list of the release you own and inform you of new releases by your favourite artists. You can remove previously added releases from your collection.

Song is a duplicate if allows you to decide how Jaikoz find duplicates. You can detect duplicates based on MB Id, Acoustid, Release Id or combinations of. It is important to understand the options available when you use Jaikoz to delete duplicates.

The When you have duplicate songs option defines what to do once duplicates have been found. They can either be deleted , moved to a special Duplicates folder or linked to the duplicate file that is not being deleted. If you want them to be moved you must specify a Duplicates Folder. If you want to link them use the Alias should be named so that option to specify if they should keep their name, be renamed to match the file they link to, or have a combination of both names.

Delete from iTunes if moving duplicates searches for these songs in iTunes and removes them from the iTunes library as well.

Cross Referencing Correct works on a column by column basis,it identifies similar values and converts all similar values to the most common value. The procedure is as follows

Local correct tasks like Local Artist Correct only modify songs that do not have a MusicBrainz Id. The reason for this is that Local Correcters are primarily provided to improve the quality of your metadata in preparation for MusicBrainz matching, so having run Autocorrecter on a group of songs you may run it again after making some manual edits to match the remaining unmatched songs, and would not expect songs that have been successfully matched to MusicBrainz to be modified further. You can make it run against all songs by checking Preferences/Local Correct/Auto Match/Do local correct on songs that already have a MusicBrainz Id

You can decide on what the Correcter deems is similar when matching by selecting options from the Auto Match Preferences . The more options you enable the more matches the correcter will make but more false positives will also occur.

Auto Format formats fields to save you from tedious typing , there are a number of options

Usually fields provides more accurate information than the filename of the song. But sometimes the field information is less accurate or missing information that can be found in the filename. However although there are some informal conventions for naming songs, files can be a named in any way the user wishes, for example

With other applications when you extract information from a filename into fields you have to specify the format of the filename and how parts combine. But as can be seen from above different filenames are often formatted in different ways so it is impossible to process a number of songs in one go.

But Jaikoz uses a special algorithm based on the general AutoCorrecter method to work out the parts by comparing the filename not only with its corresponding fields but also the fields of all the other loaded songs.

Jaikoz assumes that filenames are made up only of

The correction will take the following steps

When using Correct Tags From Filename, you need to specify two word separators. The first is this one which is used to split the filename. The second one is used to compare the split parts of the filename with the other columns.

Each record is allocated a row number numbered in the order the songs were loaded,this cannot be modified by you. The Row Menu Pop-up can be started by clicking on the row number. If you mark songs for deletion and then save changes the successfully deleted songs will disappear from Jaikoz and the songs will be renumbered

This represents the tag status, you cannot edit this field yourself.

Describes the tag versions in the file.

When you first load new files into Jaikoz it will check your Save Options. If your save options mean you want to save different tags then currently exist in the file, the version field and record status will be set to Changed. When editing this is a Selectable Combo .When saving the file it will create tag(s) of these version(s)

Warning if you edit fields which are not supported by the underlying version they will not be saved. For example if you add an Attached Picture and then select to only save a V1 Tag it will not be saved because ID3v1 does not support attached pictures.

In the Read Panel this is the root of where you loaded the files from. When you first start Save Folder Preferences/Read Folder is used as the default location to read songs from, you can shift folders from the Base Folder to the Sub Folder with the Shift Base Folder to Sub Folder action. In the Edit Panel this is the root of where you will save your files to, upon loading the file it will always start the same as for the read panel but you can modify it to an existing folder location here AutoFix will check the folder exists

In the Read Panel this will indicate the sub folder the file is within if when loading you specified includesubdirs.

In the Edit Panel this will indicate the sub folder to write the file to, upon loading the file it will always start the same as for the read panel but you can manually enter any valid sub folder name for your operating system here. AutoFix will check the sub folder is a valid name for the operating system.

This is automatically populated by the Correct Sub Folder from Metadata action, this uses output mask specified in Rename Sub Folder Preferences, you can shift folders from the Sub Folder to the Base Folder with the Shift Sub Folder to Base Folder action

In the Read Panel this is the name of the Audio File

In the Edit Panel this is the new name of the Audio File, upon loading the file it will always start the same as for the read panel, but you can manually enter any valid filename name for the operating system here. AutoFix will check the name is a valid name for the operating system, has a valid extension and does not have the same name as another loaded file.

This is automatically modified by the Correct Filenames from Metadata action, you can specify an output mask for the filename in Rename File Preferences

The artist performing on the recording.

The album that this recording belongs. More accurately refers to the release that the tracks belongs, for example it may be a single or an E.P rather than an album

This the track number of the recording on the album.

In the Edit Panel you can enter the track number, there are four accepted formats

This is automatically populated by the Correct Track Nos Action, using options specified in Track No Preferences

This the name of the recording.

Displays the first genre this Audio File belongs to

In the Edit Panel editing the field will bring up an Editable Combo you can select one from the predefined list or enter your own. Genre support multiple values opening the Pop-up Window allow you to enter additional genres.

This is automatically populated by the Correct Genres Action using options specified in Genre Preferences.

Displays the Year, actually this displays the Recording Time that can be a full date and time, but most players expect it to be just a year. The Valid formats are here

You can Auto Correct the Recording Time with the Correct Recording Times using options specified in Recording Time Preferences.

Displays a comment description. Comment is a multi value field with multiple attributes but Description is the one you are most interested.

In the Edit Panel you can edit the comment description of the first comment . A comment comprises the language it is written in,a short description of the comment, and the comment itself. Selecting Multi Field Count allows you to edit these other attribute or add extra comments

The Artist for the album, this is most useful in Various Artist compilations. This field was originally defined by ID3 as the Accompaniment but is rarely used for this purpose.

Defines the composer of a piece of music

Images can be attached to a recording such as album art. This is a multi value field with multiple attributes, a thumbnail of the first image is displayed in the View Panel

From the Edit Panel you can select Multi Field Count to add new images

An image consists of

The list on the lefthandside shows all images attached to this audio file. It shows additional attributes than cannot be modified.

Sometimes you may load an Audio File which contains an Image field but no actual picture because the tagging information was incorrectly created with another application. You can still edit this field with Jaikoz but will not see a preview until you add a new valid image.

If may contain an image field with a picture in a format not supported by Jaikoz, in this case no preview will be displayed but you can still edit the other attributes of the image.

The supported Image Types are:

This allows you to link a number of tracks by giving them the same grouping value.

Identifies that this field is a part of a set grouped with other fields with the same set number. usually applies to a disc number within a multi disc release so is more commonly known as Disc No.

Beats per minute

The MusicBrainz Artist Id allows you to access MusicBrainz Information on the Web for the associated artist.

The MusicBrainz Release Id allows you to access MusicBrainz Information on the Web for the associated release/album.

The MusicBrainz Release Artist Id allows you to access MusicBrainz Information on the Web for the associated album artist.

In Jaikoz upon a successful MusicBrainz match the MusicBrainz Recording Id is added to this field allowing you to access MusicBrainz Information for this recording. Since MusicBrainz NGS the MB Recording Id no longer uniquely identifies a track on a release, instead it identifies a unique recording of a song, this recording may then appear on multiple albums. To uniquely identify a track on a release you need the MB Recording Id, MB Release Id, Disc no and Track No.

The MusicBrainz Disc Id relates the track to the physical recording that it was taken from such as a CD pressing

The Puid is a unique acoustic identifier for the file, as calculated by MusicIP, this service is now defunct and no longer useful it has been replaced by the better Acoustid.

Amazon Id is the Amazon Identification for the associated album/release.

Release status is a MusicBrainz category used to categorize releases statuses, the allowable values are.

Release type is a MusicBrainz category used to categorize releases types, the allowable values are

Country of release for the associated release.

lyrics

Defines that this track is part of a compilation, originally used by iTunes but now in widespread use

This defines a value which should be used instead of the artist for sorting purposes.

Defines the sort name for the album artist, this is currently only used by iTunes

This defines a value which should be used instead of the album name for sorting purposes. e.g.. an album named "A Soundtrack" might preferably be sorted as "Soundtrack".

This defines a value which should be used instead of the title for sorting purposes.

Defines the sort name for the composer, this is currently only used by iTunes

The encoder that encoded the track. For some audio formats (Ogg,Flac,Mp4) modifying this field will affect the field in the Audio tab when reloaded, because they are both displaying the same field. MP3 files do not allow modification of the field in the Audio tab, so setting this field in the ID3 tag, will not affect the field in the audio tab.

International Standard Recording Code (ISRC) for the release, defined by ISO 3901, it is an international standard code for uniquely identifying sound recordings and music video recordings. IFPI has been appointed by ISO as registration authority for this standard. The ISO technical committee 46, subcommittee 9 (TC 46/SC 9) is responsible for the standard.

Catalog no of the releases, this is allocated by the Record Label.

Record label that this release was released on.

Who writes the lyrics for the song.

Remixer of the track.

Can be used to describe the mood of the song.

What format is the media, for example Vinyl or CD.

Url of an official web page that describes the release. This may contain additional information that isn’t currently held in MusicBrainz.

Url of a Discogs page that describes the release. Discogs may contain additional information that isn’t currently held in MusicBrainz.

Url of a Wikipedia page that describes the release. Discogs may contain additional information that isn’t currently held in MusicBrainz.

Url of an official web page that describes the artist. This may contain additional information that isn’t currently held in MusicBrainz.

Url of a Discogs page that describes the artist. Discogs may contain additional information that isn’t currently held in MusicBrainz.

Url of a Wikipedia page that describes the artist. Wikipedia may contain additional information that isn’t currently held in MusicBrainz.

Url of a website that provides the lyrics of a song.

Total number of discs in the release.

Total number of tracks within the disc in the release.

Custom field that can be used for whatever you want.

Custom field that can be used for whatever you want.

Custom field that can be used for whatever you want.

Custom field that can be used for whatever you want.

Custom field that can be used for whatever you want.

Beats per minutes stored using a real number instead of an integer.

MusicBrainz Release Group Id, within MusicBrainz different versions of a release all belong to the same release group.

MusicBrainz Work Id, within MusicBrainz a piece of music is called a work, this concept is particularly important for classical music.

Use to link this song to family event such as a wedding or party.

The album that this song originally was released on. Very useful for storing the original studio album of a track that you have on a compilation.

If the song is a cover this can store the original artist.

The year that the original album was released.

Quality of the recording.

The script that the songs metadata is written in

Can be used for storing arbitrary tags about the song.

Tempo of song such as Slow, Fast, Very Fast.

Rating of song from 1 to 5 stars.

Song Producer.

Song Mixer

DJ Mix

Arranger

Engineer

The language used for the metadata i.e. English, French

Acoustid Fingerprint created using the Acoustid Service

This is the size of the file

This shows the audio format. For example for MP3s this combines the MPEG Version and Layer. The version is related to the sampling rate the original file was sampled at. Most music and audio book tracks use Version 1 which can sample information at CD quality (44Mhz), whereas Version 2 and Version 2.5 can be used to sample at lower rates, typically they are used in niche applications such as sampling sound effects. For MP3 the layer will always be three, MP2 would have a value of two, and MP1 files would have a value of one.

This displays the sampling rate used to create this file,usually the higher the bit rate the better quality the encoding. If variable bit rate is used it will be shown in brackets after the average bit rate e.g. 192kbps (VBR)

The length of the audio track in seconds

The encoder that encoded the track. For some audio formats (Ogg,Flac,Mp4) this fields can be modified by editing the Encoder field in the edit tab. MP3 files do not allow modification of this field, but you can set a corresponding field in the ID3 tag.

Emphasis

Channel Mode

This displays the sampling rate of the original audio source

Is this Audio File copyrighted (MP3 only)

Is this the original Audio File (MP3 only)

Is this the Audio File private (MP3 only)

Is this the Audio File protected (MP3 only)

Is this Audio File encoded using Variable Bit Rate this means that the sampling rate varies depending on the content. This allows better quality encoding in smaller files.

The unique file identifier is used by some online music databases to identify a track. In Jaikoz upon a successful MusicBrainz match the MusicBrainz Unique Id is added to this field allowing you to access MusicBrainz Information on the Web.

The artist performing on the recording.

The album that this recording belongs. More accurately refers to the release that the tracks belongs, for example it may be a single or an E.P rather than an album

This the name of the recording.

This the track number of the recording on the album.

In the Edit Panel you can enter the track number, there are four accepted formats

This is automatically populated by the Correct Track Nos Action, using options specified in Track No Preferences

Images can be attached to a recording such as album art. This is a multi value field with multiple attributes, a thumbnail of the first image is displayed in the View Panel

From the Edit Panel you can select Multi Field Count to add new images

An image consists of

The list on the lefthandside shows all images attached to this audio file. It shows additional attributes than cannot be modified.

Sometimes you may load an Audio File which contains an Image field but no actual picture because the tagging information was incorrectly created with another application. You can still edit this field with Jaikoz but will not see a preview until you add a new valid image.

If may contain an image field with a picture in a format not supported by Jaikoz, in this case no preview will be displayed but you can still edit the other attributes of the image.

The supported Image Types are:

Displays the first genre this Audio File belongs to

In the Edit Panel editing the field will bring up an Editable Combo you can select one from the predefined list or enter your own. Genre support multiple values opening the Pop-up Window allow you to enter additional genres.

This is automatically populated by the Correct Genres Action using options specified in Genre Preferences.

Displays the Year, actually this displays the Recording Time that can be a full date and time, but most players expect it to be just a year. The Valid formats are here

You can Auto Correct the Recording Time with the Correct Recording Times using options specified in Recording Time Preferences.

Displays a comment description. Comment is a multi value field with multiple attributes but Description is the one you are most interested.

In the Edit Panel you can edit the comment description of the first comment . A comment comprises the language it is written in,a short description of the comment, and the comment itself. Selecting Multi Field Count allows you to edit these other attribute or add extra comments

Displays a User Defined URL, this should be used to specify a URL which does not fit into any of the other fields. This is a multi value field with multiple attributes

In the Edit Panel you can edit the URL of the first URL. A User Defined URL comprises a short description of the it, and the User Defined URL value itself. Selecting Multi Field Count allows you to edit these other attribute or add urls.

Any other text information not covered by any of the other fields. This is a multi value field with multiple attributes

In the Edit Panel you can edit the text of the User Defined Text Information. User Defined Text Information comprises a description of which categorises the text, and the text itself. Selecting Multi Field Count allows you to edit these other attribute or add extra information. MusicBrainz stores values in this field when there is not a suitable alternative.

Defines the composer of a piece of music

Copyright for the piece of music

The name of the application used to encode the track into an MP3. This field can be modified but it will not affect the value held in the Audio tab.

The original artist if this Audio File is a cover version

Beats per minute

The Date/Time when the original music file was encoded to MP3. The Valid formats are here

The Date/Time when the recording was originally released if this recording is a re-release. The Valid formats are here

The Date/Time when the original music file was released. The Valid formats are here

The Date/Time when the Audio File was tagged The Valid formats are here

Songwriter of the recording.

The format of the encoded recording, should always be MP3

The Edit Panel provides a combo box specifying a list of encoded recording file types.

Other people involved in the recording.

This allows you to link a number of tracks by giving them the same grouping value.

Further sub categorisation of title

The key the recording is keyed in.

The language the recording is sung in.

The Length of the recording. This is not normally used because normally the length can be accurately determined from the audio header

Musicians playing on the recording.

The format of the original recording that the Audio File was encoded from such as LP or CD

In the Edit Panel provides a combo box specifying a list of media types.

The mood of the recording such as 'Sad'

If the recording was part of a film soundtrack, the film should be specified here.

Original name of the encoding of the recording.

Original Lyricist(s)/text writer(s)

Who owns this file.

The Artist for the album, this is most useful in Various Artist compilations. This field was originally defined by ID3 as the Accompaniment but is rarely used for this purpose.

The name of the conductor on a recording

The name of the musician who Interpreted, remixed, or otherwise modified recording

Identifies that this field is a part of a set grouped with other fields with the same set number. usually applies to a disc number within a multi disc release so is more commonly known as Disc No.

Produced notice

Publisher of the recording

This contains the name of the internet radio station from which the audio is streamed.

This contains the name of the owner of the internet radio station from which the audio is streamed.

This defines a value which should be used instead of the album name for sorting purposes. e.g.. an album named "A Soundtrack" might preferably be sorted as "Soundtrack".

This defines a value which should be used instead of the artist for sorting purposes.

This defines a value which should be used instead of the title for sorting purposes.

ISRC (international standard recording code) for the recording

Specific values used in the encoding

Set subtitle

This is a URL pointing at a web page with information such as where the album can be bought.

This is a URL pointing at a web page where the terms of use and ownership of the recording is described.

This a URL pointing at a file specific web page.

This a URL pointing at the artists official web page.

This a URL pointing at the official web page for the source of the audio file, e.g.. a movie.

This is a URL pointing at the homepage of the internet radio station.

This a URL pointing at a web page that will handle the process of paying for this file.

This a URL pointing at the official web page for the publisher.

How many times has this recording been played.

Defines that this track is part of a compilation, originally used by iTunes but now in widespread use

Defines the sort name for the album artist, this is currently only used by iTunes

Defines the sort name for the composer, this is currently only used by iTunes

This lists all fields that are found within a tag which are recognised by Jaikoz but are not fully supported, Jaikoz recognises all fields specified in the ID3 Specification. Jaikoz supports all fields that are easy for uses to edit but some fields are very specialized and of limited use. These are the fields recognised but editing is not supported. Jaikoz displays the identifier and try’s to display the field value

From the Edit Panel although you cannot edit these fields you are able to remove them. If you select the Pop-up Menu and select Delete all unsupported fields are marked for removal. If you select the Multi Field Count you can elect to delete individual fields. Deleting fields will not effect the encoded recording but they may be required by an application you use to play songs.

ID3 allows users and application to define their own fields, this lists all fields that are not standard and hence not recognised by Jaikoz

From the Edit Panel although you cannot edit these fields you are able to remove them. If you select the Pop-up Menu and select Delete all unsupported fields are marked for removal. If you select the Multi Field Count you can elect to delete individual fields. Deleting fields will not effect the encoded recording but they may be required by an application you use to play songs.

Date Time fields formats are as follows, you can enter dates in any of these formats

where

The rarely used encryption scheme is not currently supported

ID3v1 supports the following fields only, and the fields have maximum fields lengths.

When saving changes the values in the Edit Panel only predefined Genres will be saved. Only one Comment is allowed. Recording Time will only save the Year part of the recording time. Characters that are not part of the Standard European Character set will not be stored

ID3v2.2 does not support sort fields, but iTunes does provide extended ID3 Tag fields. So when Sort Fields are saved to a ID3v2.2 the iTunes fields are used.

ID3v2.2 does not support the following fields, they will not be saved.

ID3v2.3 does not support sort fields, but iTunes does provide extended ID3 Tag fields. So when Sort Fields are saved to a ID3v2.3 the iTunes fields are used. Jaikoz also recognizes the alternative fields used by MusicBrainz (XSOP and XSOT).

ID3v2.3 does not support the following fields, they will not be saved.