Song Only Matchingupdates song fields such as SongTitle and TrackArtist without breaking up the grouping because it does not update release fields such as TrackNo and AlbumArtist However often Jaikoz can identify the song just not the album, since songs are usually available on multiple albums and usually the song can be correctly identified by its acoustic fingerprint but the particular album the customer has is not in the database. By default Jaikoz groups tracks logically and only allows a match if a release can be found that the complete set of tracks can be matched to, if only some tracks can be matched then no changes are made. Song Only Matching (Pro Only) SongKong has Song Only Matching. And allow functions be saved independently so they can be used by multiple file naming masks.
#Songkong pro plus
Multiple Filenaming Masks SongKong has improved file-naming, We will a add a list of pre created rename masks to Jaikoz, that can be edited plus new masks can be created and saved.
We want to update Jaikoz so that it has the same functionality as the improved SongKong Features. SongKong Feature Parity There are some features in SongKong that should be part of Jaikoz as well, in some cases they are an improved version of a Jaikoz implementation. We want to eventually allow you to create arbitrary edit tabs with arbitrary columns but think a good starting point would be tabs that roughly mimic the detail tabs, namely an Info, MusicBrainz, Sorting, Relations, Mood, Classical and Custom The solution is to have multiple Edit tabs, we already have this in the form of Edit and ID3 Edit tabs, we want to extend the Edit tab to have different type of Edit tab. The trouble is that Jaikoz supports nearly 200 different metadata fields and the temptation is to display all of them but this can make the application rather slow and cumbersome, in particular changing the column ordering by drag and drop is very slow. Tabbed Spreadsheet Edit View The idea of the spreadsheet editing was always to let you display any columns you like and in any order you like to suit you. But an improvement in start up speed will not be seen until we have converted all the preferences so that the Xml file does not need to be used. We are going to replace the Xml file with a properties file, this is quite a task because it affects all preferences, but in the last two versions of Jaikoz we have used a properties file for new preferences so we have made a start on this. With hindsight there was no need to use an Xml file instead of a standard properties file, there is no need to encrypt it and Jaikoz does not need to read more than a few items at start up.
Slow Start Up Time Jaikoz is slower than it could be to start up, and this is mainly because it has to read the user options, this is an encrypted Xml file. We are pleased to announce our plans for Jaikoz X, the tenth major version of Jaikoz.įirstly there are some important improvements we want to make how Jaikoz generally works.
0 kommentar(er)
