Bug Blasting
Today we release a new version of SongKong. Not many new features in this release but we have blasted away thirty bugs. Many of these were obscure ones that had only been reported once, but there were some larger ones in there as well.
We hope with the next release we should be able to virtually eliminate all the remaining bugs. This should help reduce time spent on ongoing support and let us concentrate on some really cool new features.
OSX iTunes Bug
We have found that the later versions of OSX Sierra no longer have the Java Applescript library installed. SongKong requires this to update iTunes, and it wasn't accurately reporting the issue either. This new release comes with the missing library as part of the SongKong installation.
Saving Unchanged Songs
Too often SongKong was re-saving songs that had not actually had any changes since the previous Fix Songs task. This could make the report a little confusing, and increased the total processing time, especially if SongKong was configured to update iTunes. We have now fixed this, note in the report the Songs Saved bar chart only shows files that have actually been changed. It is the Songs Completed bar chart that shows the successful completions, to highlight this it is now the last bar in the bar graph.New Feature:Windows Path Length option
We have one new feature in this release (for Windows users only). On Windows the file path is limited to 259 characters, but this is only a limit of Windows not the underlying file system and it can be rather limiting sometimes, for example Classical releases.Whilst is usually wise to adhere to this limit for files that are intended to be usually be used on Windows it is not so necessary for external or networked drives that are only temporarily being accessed via Windows.
For example you may be using SongKong on Windows to access a Linux NAS drive. Whilst SongKong can run on Linux a NAS will not not let you use the GUI, you'll be limited to using command line. And in some cases it will not be possible to install SongKong in the first place, so this is quite a common scenario.
You can use the new Limit File path to Windows Explorer 259 Character Limit option to not set the limit, or set the limit only for local NTFS/FAT32 drives, this is the default.
No comments:
Post a Comment