1/23/2024 0 Comments Beatunes 4i'm downgrading bak to yosemite, el capitan's incompatible with too many things including my art program, evidently- Emmit May 19, 2016 :(- Holger Plankermann May 22, 2016Īlright i've had enough. Meh! El Capitan photos app uses an lib format incompatible to Yosemite version. Will I brick my #Apple MBA completely? Or will it still be usable in the morning?- Michael Mahlberg May 25, 2016 Removed QuickTime for Windows dependency (32bit).Downloading OS X El Capitan.Added index column to visible columns popup.Added fingerprint icon to Get Info pane.Improved "Album Info" to more often show actually useful info.Improved "Analyze New"-behavior: Use last sync as reference point.Improved performance, via coalesced database writes (reduced disk IO).Fixed DNS lookup during database ops (caused by URL.equals()).Fixed writing of last played date on Windows.Fixed missing artist in Album Info pane. ![]() Fixed some English capitalization rules.Fixed relative salience error on 0 BPM.As always, you can download it from the download section of the website. The 32-bit version does not depend on Apple's QuickTime anymore, which turned out to be a serious security risk.The Windows installer is now properly signed (I know, this should have happened a long time ago).Specifically for Windows, there are two other important items: To make a long story short-the inspector has been rewritten and the results are much better now. ![]() Results are more accurate, if the lyrics are available. Prior to inspection, you can let beaTunes determine song languages automatically via the corresponding analysis task. For those of you, who've never noticed its existence, this inspector only shows problems, if the song language is known (different language, different rules). For beaTunes 4.6, the English capitalization rules received some well-deserved love. Pretty much with every minor (not micro) beaTunes update, an inspector gets a little makeover. BTW: the shipped implementations for Groovy and JRuby have been updated. Examples can be found in the beaTlet tutorial as well as on GitHub. But thanks to the Nashorn extensions, it's relatively easy for your JavaScript code to interact with beaTunes. Because JavaScript uses prototypical and not class-based inheritance, plugins are created in a slightly different way. You may remember that Groovy, Jython, and JRuby are already supported. It may just be a matter of time, until all the little things are resolved.Īs we're already talking technical stuff-there's good news for JavaScript hackers! beaTunes now officially supports JavaScript as plugin scripting language. Luckily, the Oracle Java team is working hard to bring better HiDPI support to Java 9 and hopefully backports some fixes in the process. Those are presented by the Java Runtime Environment and pretty impossible to fix without patching the runtime itself. Still, if you're using Windows with a high-resolution display, you will eventually notice some left-over rough edges, e.g. ![]() To this day, there is still plenty wrong with it, so I had to build a few workarounds. What was holding me back, was Java 8's lack of HiDPI support for Windows. Yay! No more squinting to read an artist's name! As Windows hardware has slowly caught up with Apple's early Retina offensive and the Windows OS has started to support HiDPI displays much better, it was definitely time for this step. Probably the most important new feature is the much improved high-resolution display support for Windows (sometimes referred to as HD or 4k). I'm proud to write that today beaTunes 4.6 will be available for download as a free update for existing beaTunes 4 customers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |