Jaikoz Help

The Minimum run-time requirements are a computer with 512MB of RAM and 10MB free disk space

Jaikoz is available for both Intel and PPC Macs, 32bit or 64bit

You can start Jaikoz by selecting if from the Application folder. If you wish you can add Jaikoz to the Dock and start it from there

If you do not have yet have Java 1.5 installed you will see this dialog

In which case, please download from the Apple website and retry. Otherwise unless there is a licensing problem jaikoz should now start

This section discusses problems starting Jaikoz due to problems with your Java configuration

Java is not recognized as an internal or external command,operable program or batch file..

There is a problem with your JRE Installation. Please ensure that Java is installed and can be found in your path

Unable to load helpset

There is a problem with your JRE Installation. Please ensure that Java is installed and can be found in your path

To uninstall Jaikoz just drag it from the Application Folder to the Trash

Warning this section is for experienced users of Java only

By default Jaikoz allows upto 800MB to be used for storing the information about your loaded files, this is additional to about 100MB that is required to run Jaikoz. If you are attempting to load many songs (more than 10,000) you may get a warning that memory is low, if your computer has sufficient memory you can increase the maximum value of memory than can be used you will be able to load larger amount of files if you require it. You should not set the memory to the actual amount that your system has because your computer requires some memory to run the operating system and other programs, additionally trying to load too many files may place too high a CPU load on your computer and could severely effect performance. If your computer only has 512MB of memory or less you should reduce the value as appropriate.

Jaikoz is usually run using Jaikoz.app from the Finder, but you can also run it using jaikoz.sh using the Terminal, memory is adjusted differently depending on which file you use.

Jaikoz uses two log files, jaikozuser0-0.log contains the same information as is written to the Console Panel, it contains general information about what you've done within Jaikoz. The jaikozdebug0-0.log file contains warnings and debugging information that helps diagnose problems when running Jaikoz. These files are held in the within your log folder, for example /Users/paul/Library/Logs/Jaikoz and are renamed when they get to a certain size, the latest file is always called jaikozuser0-0.log, the next most recent is called jaikozuser0-1.log. if you require support with Jaikoz it is important to send both types of log files, to help diagnose the problem. The amount of logging written to the jaikozdebug0-0.log file can be adjusted, if you have a problem that you can reproduce it would be helpful if you could increase the amount of information logged, recreate the problem, send the logs and then return the logging to the normal levels.

You can send your logs and other support files from within Jaikoz by selecting Advanced/Create Support Files and then emailing the zip file created.

The following parameters effect logging

-l2 -m2

The -l2 parameter specifies how much logging output should be generated by Jaikoz, the -m2 parameter specfies how much output should be generated when reading and writing files. The number 2 can be replaced by any value from 1 to 7, a value of 1 is the minimum and a value of 7 is the maximum. Setting a high value will noticeably slow the performance of Jaikoz, so changes should only be made temporarily to diagnose a problem.

Jaikoz is usually run using Jaikoz.app from the Finder, but you can also run it using jaikoz.sh using the Terminal, logging is adjusted differently depending on which file you use.

This section explains the terminology used within Jaikoz and the main components of Jaikoz

The Toolbar provides access to most useful and commonly used commands. The Toolbar can be displayed or hidden from the View Menu.

The Tag Browser makes it very easy to quickly filter your loaded records to a more manageable size. The Genre list, groups together all the genres contained in your tracks, if you select a particular Genre only tracks containing that Genre will be displayed. The Artist and Album lists will be updated with only the Artist and Albums for tracks containing that genre, you can select an Artist or Album to further refine your choice, alternatively you can select all genres but limit by an Artist or Album. Note the lists are not case sensitive, and ignore therefore capitalization. The Tag Browser can be displayed or hidden from the View Menu. The Tag Browser makes it easy to work on subsets of your loaded records at a time.

The View Panel can be displayed or hidden, it displays tagging information as it currently exists in the saved file

The Edit Panel is always displayed, it contains the Edit Tab and the Edit ID3 Tab

.

The Edit Tab starts with the same information as the View Tab showing most of a files metadata in an audio format independent way, but it is here you can edit the tag information. The fields are designed so that they can be edited inline wherever possible in an easy to understand format, the fields are similar to those within iTunes, but with additional information from MusicBrainz displayed. For example there are separate fields for all the MusicBrainz fields whereas within ID3 many of these are stored within the User Defined Text field. Usually you can edit a field by click on the field and start typing, some fields provide a combo box with a list of options. If the field is a multi value field it is the first field that is displayed in the table, to edit additional values click on the small numbered button to provide access to the additional values. The Edit Panel can show upto eighty different fields but by default only the more commonly used ones are shown, you can show more columns for just the Edit Panel using the column control in the right handside corner of the Edit Panel. If you also want the same columns to be displayed in the View Panel you should use the 'Settings/Table Settings' Menu Item.

For MP3s the Edit ID3 Tab can also be used to modify fields, this tab maps more directly to how fields are actually stored in the file, it also gives access to additional fields that are not yet in the Edit Tab

The Detail Panel shows details of the currently selected file in a series of tabs (with the exception of the Console tab). As you select different files the detail tab gets updated automatically, (with the exception of the Read Only Summary Tab) you can edit values in the Detail tab and the changes will take effect immediately in the Edit Panel and vice versa. This provides a powerful alternative to the Edit Panel for making modifications and enables quick access to fields that may not be displayed in the Edit panel by default or without scrolling. The tabs are similar to the tabs from the GetInfo option within iTunes, but with additional information from MusicBrainz displayed. You can use the Up and Down arrows to change the selected record, selection is based on the record selected in the Edit Panel, selections within the View Panel have no effect.

The Status Bar at the bottom of the screen shows how many records are loaded, how many records are actually visible due to filters and are any filters active.

Jaikoz has been designed to allow you to do your editing as quickly and easily as possible. Is it particulary good if you have a large music collection, if you have ever used another tagger then you will find time spent using Jaikoz well spent.

Save Changes will save the files that you have modified and delete any files that you have marked for deletion. You can run it from the Main Menu in which case it will apply the changes to all files visible in the Edit Tab. Or from the Popup Menu so that it only is done for selected files, or as a task within the Autocorrecter so that it is applied to all files processed by the Auto Correcter

Force Save will resave files even if you have not modified any fields. This can be useful if you wish to resave a file because you want to modify the way it is saved. For example you may wish to save a file with unsynchronization either enabled or disabled. You can run it from the Main Menu in which case it will apply the changes to all files visible in the Edit Tab, or from the Popup Menu so that it only is done for selected files.

Save and Move saves any changes and then moves the files to the specified folder, this is an easy way to move a set of processed files to another folder. By default it will create the subfolder hierachy underneath the selected folder using the values in the subfolder fields for the selected files, but you can move the files without creating the subfolder hierachy by unchecking the Create subfolders hierachy option. You can run it from the Main Menu in which case it will apply the changes to all files visible in the Edit Tab, or from the Popup Menu so that it only is done for selected files.

Save and Copy saves any changes and then copies the files to the specified folder, this is an easy way to make a copy of processed files to another folder. By default it will create the subfolder hierachy underneath the selected folder using the values in the subfolder fields for the selected files, but you can move the files without creating the subfolder hierachy by unchecking the Create subfolders hierachy option. You can run it from the Main Menu in which case it will apply the changes to all files visible in the Edit Tab, or from the Popup Menu so that it only is done for selected files.

If you click on a column you can sort it in ascending order, click on it again and it will be sorted in descending order. if you click on the Row Number column the records will be sorted by row number this will be the same order as when they were originally loaded into Jaikoz

The size of a column can be set so that it fits exactly wide enough to display the title and all the data within the column by double-clicking on its header boundary with the next column header. It can also be increased or decreased by selecting the right hand side of the column header and dragging it inwards or outwards

The column order can be changed by selecting the middle of the column header and dragging it to the new location

Selecting the column control button in the top right corner of the table, allow you to quickly make changes to the table view.

Pack All Columns trys to set the width of all the visible columns so that they are wide enough to display the data within them. If Horizontal Scroll is enabled then the columns can be as wide as required upto a limit of 500 pixels for any single column, if horizontal scroll is disabled then all the visible columns have to fit onscreen. The Pack Selected Column is available if you have selected a field before clicking the column control button, this will pack the selected column so it is just wide enough to display all the field values.

You can scroll down the list to make individual columns visible or invisible

The column control button only effects the table for which it is selected, changes are not synchronized to other tables

If there is any whitespace at the start or the end of the value it will be coloured the Whitespace Colour (default pink). This is very useful for identifying white space at the end of a field,if you have ever wondered why two field that appear to have the same value are not listed together in an Audio Player it is probably because one contains white space or undisplayable characters.

You can temporarily highlight fields that match a particular rule, the matching fields are coloured the Highlight Colour (orange). Currently there are two highlight rules available

When enabled only songs that contain the same combination of Musicbrainz Id and AmpliFIND Id same as at least one other records are displayed. This function is very useful for finding and possibly deleting duplicate versions of the same song.

When enabled only records containing a Unique File Id field that is the same as at least one other records are displayed. This function is very useful for finding and possibly deleting duplicate versions of the same song.

When enabled only records containing a Unique File Id field are shown. This function is useful for checking tracks corrected by MusicBrainz.

When enabled only records that do not contain a Musicbrainz Id field are shown. This function is useful for finding tracks that have not been matched by MusicBrainz, that may need matching manually

When enabled only records containing a AmpliFIND Id field that is the same as at least one other records are displayed, filter status is also shown in the status bar. This function is very useful for finding and possibly deleting duplicate versions of the same song.

When enabled only records containing a AmpliFIND Id are shown. This function is useful for listing tracks that have been matched by AmpliFIND.

When enabled only records that do not contain a AmpliFIND Id field. This function is useful for finding tracks that have not been matched by AmpliFIND

Find Missing tracks generate a list of all the albums in your selected files, and the tracks within each album. It then compares the list to all the tracks you have loaded in Jaikoz to find matching tracks. It then generates a list of all missing tracks and all matching tracks. Within the html report if the album is a Various Artists album then the individual artist name will be listed for every track, if not then it is not displayed because it is assumed the same Artist will be on every track in the album. These lists can be viewed and saved as a html file, or as a cvs file, cvs files can easily be loaded into spreadsheets.

The matching is done based upon the MusicBrainz Unique Id and the MusicBrainz Album Id because this is the only accurate way to identify albums, and allows us to distinguish between albums of the same name by different artists. This means you should not run this report unless your tracks have been matched by MusicBrainz. The information in the Matching Reports shows the information as stored on the MusicBrainz Server rather than in your files, so for example if you have a track with Unique id of e785f700-c1aa-4943-bcee-87dd316a2c30 and the value of Artist in your file is 'Farming Incodent' but in the Musicbrainz Server it is 'The Farming Incident' then 'The Farming Incident' will be displayed, the report is done this way as it is intended to show what you dont have/have in relation to the details on MusicBrainz.

This option is only available when you have exactly one track selected, and that track has a MusicBrainz Unique File Id. It will open the MusicBrainz page for the track in your browser.

This option is only available when you have exactly one track selected, and that track has a MusicBrainz Artist Id. It will open the MusicBrainz page for the artist in your browser.

This option is only available when you have exactly one track selected, and that track has a MusicBrainz Album Id. It will open the MusicBrainz page for the album in your browser.

This option is only available when you have exactly one track selected, and that track has a AmpliFIND id (PUID). It will open the MusicBrainz page for the PUID in your browser.

This option is only available when you have exactly one track selected, and that track has a Amazon Id (ASIN). It will open the Amazon page for the album in your browser.

This option is only available when you have exactly one track selected, and that track has a Release Discogs Url. It will open the release on Discogs in your browser.

This option is only available when you have exactly one track selected, and that track has a Release Wikipedia Url. It will open the release on Wikipedia in your browser.

This option is only available when you have exactly one track selected, and that track has a Artist Discogs Url. It will open the artist in Discogs in your browser.

This option is only available when you have exactly one track selected, and that track has a Release Wikipedia Url. It will open the release in Wikipedia your browser.

Play Song, plays the song using your default Music Player , or configured Music Player

Fields copied from within a Jaikoz table can be pasted to other applications

You can only select a fields froma single column to be copied at any time, if you select fields from more than one column the copy will not take place.

Select some fields to paste into and select Paste provided all fields accept the copied value the paste will take place.If the field to be copied has multiple values only the first value will be pasted to the paste fields. If the paste area is larger than the copy area, the copied fields will be cycled through again to populate the required paste area. For example you can copy data from the Artist field to the Album field but not to an Attached Picture field because it wouldn't make any sense. In some cases the data is automatically formatted so it is valid for the pasted field, this is known as Auto Fixing. For example if you paste a value from an Artist field to the Filename field for an mp3 file it appends the (MP3) suffix to the filename and checks that you have not already loaded a file with the same filename.

If the field to be pasted contains multiple values selecting this value will paste all values into the selected fields.

Pastes the previously copied values to the start of the currently selected fields in the edit pane, (separated by a space character).

Pastes the previously copied values to the end of the currently selected fields in the edit pane, (separated by a space character).

Sets the currently selected fields to the value you enter in the popup window.

If you have selected some fields in two separate columns this swaps the fields in one column with the fields in another

If you have selected some fields in two separate columns, this option will copy the contents of the fields in the right column into the start of the fields in the left column (separated by a space character)

If you have selected some fields in two separate columns, this option will copy the contents of the fields in the left column into the start of the fields in the right column (separated by a space character)

If you have selected some fields in the track no column, this option renumber the fields starting from the value of the first field (based on the current sort order), or starting from one if the first field has no value. The renumbering is based on the current order of the files, the numbering takes into account your Track No Preferences

You can delete a field, this is different to setting the field to empty, the field will no longer exist in the Audio File after saving changes

You can delete the whole song. You are most likely to do this if you find you have duplicate files of the same recording.

You can undelete a song that you previously marked for deletion.

Revert to Saved will reset the records to their currently saved value. Any changes you have made but not saved will be lost.

Undo is a simple field based Undo it does not currently support stepping back multiple undos, if you select a number of fields and select Undo, their values will revert to the saved value.

MusicBrainz is an online database of information on more than nine million songs. This is a community based database with contributions by over 200,000 people, with a comprehensive system of moderation ensuring the data is extremely accurate. Additionally many of these songs have associated Acoustic Ids provided by AmpliFIND, allowing a song to be identified by the actual music, so it can do a match even if you have no metadata. AmpliFIND also provides an online database and a number of Music Mixing and Music Identification services, this is the very latest technology and is much more powerful than other systems that only allow a match by metadata.

Discogs is another online database of information similar to Musicbrainz, Discogs also allows you to buy and sell records and CD's to other Discogs users. We use Musicbrainz and Discogs to get the best possible coverage of your song library.

Jaikoz allows to lookup your songs by both the acoustic id and the metadata making it very accurate, no decisions have to me made by you whilst the correction is progressing so you can go away and do something else more interesting and review the changes when complete. Jaikoz compares your track acoustically with the AmpliFIND database and if it finds a match it retrieves the acoustic id. It can then be used to contact the MusicBrainz Server to find matching tracks and meta-data. Sometimes multiple tracks may be returned but unlike other systems Jaikoz can use its its AutoMatch algorithm to determine which is the correct match in most cases. It does this by comparing the meta-data in the records returned from MusicBrainz with the record it is trying to match. As a user this means you can run Jaikoz against MusicBrainz and the corrections will be done without any additional intervention required from yourself. This is very useful because the creation of Acoustic ids and lookup in the MusicBrainz Database can take a while if you want to correct many files so is best run unattended for a large number of files. If a match is found Jaikoz will always write a record to the Unique File Identifier which provides a link back to the Music Brainz Website. It also writes values to many of the other fields such as the Music Id (PUID), Artist Id, Album Id, Disc Id, AmazonId, artist, album, title, year, album artist, release status, release type, release country and track number if they do not exist already on your file, or if they are allowed to be overwritten based on your AutoFormat Preferences.

This attempts to find an acoustic match for your track in the AmpliFIND database. In order to get a successful match the song must exist in the AmpliFIND database and your song must be of sufficient quality so that it sounds similar enough to the song in the AmpliFIND database, if an Acoustic Id is found it will be added to the AmpliFIND Id field within your song. Acoustic matching takes a few seconds per track but the Acoustic Id for a track never changes so there is no need to regenerate it, it only has to be done once. Because the Acoustic Id for a particular file will never change, the Acoustic Id will be automatically saved to file as it is retrieved. By default Jaikoz does not submit unknown tracks to AmpliFIND because analysing unknown tracks take significantly longer, but this option can be enabled. When you submit an unknown track to AmpliFIND it will not give you an Acoustic Id immediately, you have to wait 24 hours and then retry retrieving acoustic ids for the unknown track. By this time the track should have been added to the AmpliFIND database and you will normally able to retrieve an acoustic id for it.

This attempts to find a match in the MusicBrainz Database, using metadata such as artist, album and title, track duration and track number and/or the Acoustic Id. Jaikoz groups your songs by album if they have album field specified and/or by folder and first of all try to find a matching release on Musicbrainz for all the songs in the grouping, a sophisticated algorithm analyses potential matches and selects the one that matches all songs the best and is most similar to your preferences including preferred country and media format. If no suitable match is found Jaikoz then does song by song matching based on the metadata, and then for remaining songs it matches based on acoustic ids. Jaikoz will complete as many fields as it can from MusicBrainz if they are enabled in your AutoFormat options.

Because different customers use Jaikoz in different ways there are a number of preferences you can change

This attempts to find a match in the Discogs Database, using metadata such as artist, album and title, track duration and track number. Jaikoz groups your songs by album if they have album field specified and/or by folder and first of all try to find a matching release on Discogs for all the songs in the grouping, a sophisticated algorithm analyses potential matches and selects the one that matches all songs the best and is most similar to your preferences including preferred country and media format. If no suitable match is found Jaikoz then does song by song matching based on the metadata. Jaikoz will complete as many fields as it can from Discogs if they are enabled in your AutoFormat options, by default if the song has already been matched to a Musicbrainz release only empty fields will be modified by Discogs

If you are an editor of Musicbrainz you may find the Only match if matches to Musicbrainz release option useful. When this is enabled Autocorrect from Discogs will only try to match to Discogs if the song has a Musicbrainz Id, and will only accept the match if the Discogs metadata is a good match with the existing Musicbrainz metadata. This is a a very useful way of finding links between Musicbrainz and Discogs that you can then add to the Musicbrainz release as a Discogs Relationship Type.

The Match Settings also apply to Discogs

Discogs categorises releases by styles and sub categories called genres. With Jaikoz you can complete the genre field using styles and/or genres, and select how many genres you want to link to any one song. 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 playlists. 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.

For each (selected) track this finds upto ten potential matches in the MusicBrainz Database, a similar algorithm is used as for the AutoCorrect from Musicbrainz but is track based instead of release based , and instead of automatically selecting the best match, upto ten matches are displayed and it is your decision to select a match or not. Matches by Acoustic Id are shown first, then matches by meta data - sorted by their rating. Each choice is displayed on a separate row for each release event so that you can select the Release Date, Record Label and Catalog No to select when there are multiple choices. You can modify what fields are displayed and in what order and these changes are preserved. The last column contains either Search for the master record or View for the choices, if you select View Jaikoz opens the release in Musicbrainz so that you can look in more detail. If you select Search it opens Musicbrainz Search you can then select one of the results or search again to find the track that you want, then select the tagger button on the webpage and Jaikoz will use this selection.

If you select the popup menu for a song you have some further options. Match Songs to Selected Release 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. View Track in Musicbrainz and View Release in Musicbrainz open the selected match in Musicbrainz so that you can check al the details.

By default records 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 there are no more records 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.

Jaikoz can retrieve the lyrics for many of your songs using an online database.

For each (selected) song this checks that they already have a MusicBrainz Id, and if they do retrieve the latest information from MusicBrainz for this Id and updates the relevent fields in the record if they are enabled in your Format options. If the track does not have a MusicBrainz Id but it does have a Musicbrainz Release Id then Jaikoz tries to find the correct track on the release by comparing the trackname, track number and track duration. If Musicbrainz contains a link to a Discogs Release Id the songs will also be updated with any more information available from Discogs.

This has a number of uses:

For each (selected) song this checks that they already have a Release Discogs Url, and if they do then Jaikoz retrieves the latest information from Discogs for this Release Id and tries to find the correct track on the release by comparing the trackname, track number and track duration of the tracks with the Discogs release information. Jaikoz then updates the relevent fields in the record if they are enabled in your Format options. The Release Discogs Url can be added after a successful Musicbrainz lookup but if you're song does not have one you can search on Discogs for it yourself and add it manually.

Whether or not you have already tagged your track from Musicbrainz, Discogs may contain additional information that is not included in the Musicbrainz Database. You can also use this to help identify information that you can be added into Musicbrainz. Discogs Cover Art is generally higher quality than is available from Musicbrainz.

The MusicBrainz Server field specifies what MusicBrainz server to use, currently there is only one but it is expected there will be mirror servers available in the future.

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.

Often artwork is not embedded into the metadata but held as a separate file, sometimes it is not available at the same time and has to be retrieved later. But cover art is much more useful if it is embedded into the metadata because only then will it be displayed in Music players such as iTunes and iPods. Correct Artwork checks the folders of the songs you are correcting and adds any image files it finds to the audio file unless they have already been added. The following formats are supported JPEG,PNG and GIF

There are options you can make that apply to Correct Artwork and when getting artwork from a Musicbrainz or Discogs match

Many applications only show the first image, so you may decide to only add the first image by setting the value of Maximum artwork images that can be added to song.

You can resize large images using Resize Artwork if dimensions larger than (pixels), very large images will make your songs correspondingly large.

You can ignore artwork smaller than a certain size using Ignore artwork smaller than this (pixels)

By default Local Artwork Correct ignores folders containing more than fifty songs because it is unlikely that the folder contains only a single album, but sometimes this is the case and you can remove this restriction by checking Preferences/Local Correct/Artwork Correct/Allow Artwork to be loaded from folders containing more than 50 songs

Song is a duplicate if allows you to decide how Jaikoz find duplicates. You can detect duplicates based on Musicbrainz Id, AmpliFIND Id or MusicBrainz Id/AmpliFIND Id

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.

If Remove Undisplayable Characters is selected control characters can be removed.

If you have a number of songs that you wish to adjust the data for the chances are at least some of them are by the same Artist and from the same Album. However if the source for these files are different the Metadata may be subtletly different,this means that when you try and play all tracks by a particular group or artist they do not all appear. For example the following artists are all different,but only slightly

Which is the correct answer?

Item five is a misspelling so it is not this,item four is not that easy to read but is the accepted format for some audio encoders, any of the others could conceivably be ok. The correct answer really depends upon your personal preference. AutoFormat allows you to automatically modify values to to your personal taste.Are all these artists the same band, as a human reading this document it should be obvious that they are but to a computer it is not. But AutoMatch can detect these similar values, again the similarity is defined by you.

Cross Referencing Correct trys to work out which is the correct value to use by a combination of comparing similar values, and user options. Local Correct is available for the following fields

This shifts the last folder in the base folder over to become the first folder in the Sub Folder field, this is normally used in conjunction with the Correct Sub Folder From Tags action.

This shifts the first folder in the sub folder field over to become the last folder in the Base Folder field, this is normally used in conjunction with the Correct Sub Folder From Tags action.

This modifies the Filename to reflect the values of the fields within the tag. The AutoCorrecter applies the formatting mask specified and generates a new filename. It may be better to use the Album Artist rather than the Artist in your mask because when you have compilation albums because for these albums the Album Artist is usually Various Artists whereas the Artist field would change on a track by track basis, for regular albums both values would normally be the same.

It is usually useful to stores songs on your computer in multiple subfolders for example by having a different subfolder for every artist. The AutoCorrecter applies the formatting mask specified and generates a subfolder. It may be better to use the Album Artist rather than the Artist in your mask because when you have compilation albums because for these albums the Album Artist is usually Various Artists whereas the Artist field would change on a track by track basis, for regular albums both values would normally be the same.

These fields are not part of the tags themselves but provide important information about the Tags

Be careful when modifying these files, if your files are already in a Music Library such as iTunes, because it may prevent iTunes from finding them. It is recommended that you run Jaikoz on your files before you add them to iTunes.

These are the fields that can be directly view and edited within the View and Edit Panels, and the Detail Panel. These fields should be supported by most Audio Formats.

These are the fields displayed in the View Audio Tab, this is for your information only you cannot modify these values.

These are fields that directly correspond to a field in the ID3v24 Specification, each of these fields can be seen as a column with the View and Edit Panels

Jaikoz recognises a small number of additional fields that are not part of the ID3 standard, but are in widespread use.

These are groupings of ID3 fields that are not fully supported by Jaikoz

The Id3 View Merged Tab and ID3 Edit Panel show a view of the tag data as it would be stored in ID3v24. When changes to tags are saved to some other version some conversion has to occur.

Jaikoz supports Ogg Vorbis Comments of any size. However many Music Players will only read upto 64kb of Metadata for this reason you might want to be careful when adding Metadata to not exceed that limit

Ogg Vorbis does not allow empty values so if you save a value with an empty value it will actually be deleted fron the file.

There is no offical way to add cover art to Ogg Vorbis but Jaikoz supports the common defacto standard of base64 encoding the image as used by Audio shell http://www.softpointer.com/AudioShell.htm, a restriction of this is that only one image can be added. For maximum compatbility with other applications you should try to add images that are not too large, so that the 64kb limit is not reached

Jaikoz supports all the fields within the Metadata View for use with OggVorbis. Other fields within OggVorbis are not currently shown within Jaikoz but will be preserved.

Jaikoz supports M4a Files, Mp4 Audio Files and M4p Audio Files. Jaikoz will not open mp4 files that contain video, only audio tracks. Jaikoz can open and edit Protected Audio Files, this does not effect the protection mechanism

Jaikoz can safetly edit protected files, the only functionality that is not available is the generation of Acoustic Ids for these files because the audio cannot be decoded.

Jaikoz supports writing values to Mp4 fields all the fields within the Metadata View. Other fields within Mp4 are not currently shown within Jaikoz but will be preserved. Note Mp4 does not allow multiple values to be entered for any fields, except for artwork. So if you add multiple values for any field (other than artwork) only the first field will be saved.

Jaikoz supports Flac of any size. However many Music Players will only read upto 64kb of Metadata for this reason you might want to be careful when adding Metadata to not exceed that limit

Flac does not allow empty values so if you save a value with an empty value it will actually be deleted fron the file.