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. Once the right library is selected, you may need to synchronize via the File menu, if beaTunes isn't doing it automatically. ![]() When hovering over the items with the mouse, beaTunes will show all root-folders for each library in the tooltip (screenshot). To identify which one it is, open the beaTunes general preferences and open the combo box that lists the existing libraries. Now save the preferences2.xml file, start beaTunes and select the library we just modified. Once that is done, you can remove the now empty -element for folder_b. All you need to do to combine both libraries into one, is to move the -element describing folder_b to the -element containing folder_a. In essence, this describes two folder-based libraries: One based on folder_a and one on folder_b. If you're using multiple, folder-based libraries, you should see something like this: Then take a look with your favorite text editor, e.g. On Windows, simply copy the mentioned path and paste it into the File Explorer's path field.īefore you open the file, please make sure that beaTunes is not running. ![]() On OS X, ~/Library/ is hidden-use Go -> Go to Folder. Unfortunately, the folders are a little hard to find on both operating systems. Despite this, beaTunes 4 is capable of basing folder-based libraries on more than one folder-but it requires a tiny bit of hacking.īeaTunes stores information about music collections in a file called preferences2.xml, which is stored in the folder ~/Library/Application Support/beaTunes/ on OS X and in %LocalAppData%\tagtraum industries\beaTunes\ on Windows. By default, folder-based libraries are based on a single folder and the beaTunes user interface does not let you add other folders. Folder-based libraries are those, that have nothing to do with iTunes, but basically contain all songs in a given base folder ( more info). A question that comes up every now and then is how to use multiple base-folders in a folder-based library.
0 Comments
Leave a Reply. |