Spit Player is a ubiqutious widget-based desktop application. It has modular ui and behavior, including audio playback/library, Phllips Hue integration or voice control features. Uses VLC under hood & css for looks. Built around plugins and widgets.
Is this ready? Yes. Executable downloads are not provided, but can be easily built. Well tested on Windows 8.1 and 10. Linux and OSX compatible, but largely untested.
Can look like this:
Can do this:
You decide. This application has been born out of frustration with how applications today look and are used. The major use cases are:
Ever lost your entire library or song ratings due to corrupted database file? Ever wanted to have song chapters or other cool features? Ever needed multiple playlists or display/manipulate your songs in a way that wasn't possible for some reason?
This application addresses a lot of such issues. However, it may lack features you may be used from other media players, so it may not be for you.
Ever wanted to do things your way?
Pluggable parts of the applications are called widgets and can be developed or changed while the application runs. This application provides several useful widgets, but most importantly the necessary infrastructure to manage and use them conveniently, such as modular layout, different widget launch strategies, be it different types of windows or even separate process.
If you know Java/Kotlin, you can make your own app with a simple text editor and literally few lines of code. Just write your code, hit save and watch as it auto-compiles and reloads in UI. All that with included support for powerful type-safe configuration, skins and access to the internals.
See how.
The voice assistant is largely separate, but also integrated functionality capable of full real-time interaction with user. It uses multiple AI models for text-to speech, llm, speech-to-text to provide for voice control over devices as well as actual chat. It supports voice cloning, multiple speakers, and more.
See voice assistant documentation
Download link coming in the future. Building from the latest sources:
- Download & prepare project
- Build the application
./gradlew buildbuilds the application./gradlew jarcreates jar & copies dependencies to/lib- Application is now build in app directory
- Deploy application
- Run application
- Customizable - User uses the application how he wants, not how it was designed to be used. Therefore, emphasis on customization, skins, settings, etc.
- Portability - No installation (or need for java or other programs), run from anywhere, little/no trace, everything is packaged along. Any OS.
- Modular functionality - User can launch or use only selected components he is interested in and ignore everything else as if it was never there.
- Modular user interface - User has the ability to 'make his own gui'. Completely custom component layout. He can create all-in-one GUI or use separate windows or - anything really.
- Fancy features like: rating in tag, time comments, good image support, advanced & intuitive library management, etc.
- Library independence - Moving & renaming files will not result in loss of any information. Every single bit is in the tag. Always. If you move on to different application or lose your library - you never lose data. Ever again.
- Usability - Ease of use and efficient workflow due to minimalistic and unobtrusive graphical user interface design. Think shortcuts, swiping, icons, intuitive use, etc.
- Responsive - fast and responsive. Minimal modal dialogs. No modal or blocked windows while your library is scanning that big fat audio collection
- Sexy - Your way of sexy if you know a tiny bit about css.
- anything Vlc player can play
Song database:
- small footprint: in 10s of MBs for 10000s audio files
- big: 40000 files no problem
- fast: library is loaded into main memory (RAM).
- no dependency: song files always store all data in their tag, moving or renaming files poses no problem.
- no inconsistencies: displayed song metadata can only be out of sync with real data if the tag is edited by an external application (or as a result of a bug)
- no data loss guarantee: losing database has no effect at all, it can be completely rebuilt anytime. The library serves as a persistent cache, not as data storage.
Management system is only as good as its user interface. There are powerful tables that try to be as flexible as possible. Tables:
- big: 30000 songs in playlist no problem (although good luck loading it at the app start...)
- smart columns: set visibility, width, sorting (multiple column), order of any column for any song attribute
- visual searching: by any (textual) attribute (artist, composer, title, etc) simply by writing. Scrolls 1st match (to center) and highlights matches - so they 'pop' visually - which doesn't strain your eyes that much. Its fast (no CTRL+F, just type...) and convenient.
- powerful filtering - CTRL+F. Shows only matches. Filtering here is basically constructing logical predicates (e.g.: 'year' 'less than' '2004') and it is possible to use any combination of attributes (columns), 'comparators' and permissible values. Filters can be inverted (negation) or chained (conjunction).
- group by - e.g. table of groups of songs per attribute (e.g. year or artist) Searching, filtering and sorting fully supported of course.
- multiple column sorting by any attribute (artist, year, rating, bitrate, etc)
- cascading - link tables to other tables as filters and display only selected songs (e.g. show songs of author A's albums X,D,E in year Y in three linked tables reacting on table selection). Basically library widgets allow linking selection of the table as an input, while simultaneously providing its selection as an output to other tables. Use however library widgets (each having 1 table) you wish and link them up in any way you want.
Spit Player supports reading & writing of song tags
- individually
- by group
- using Tagger to write the same data to multiple tags (songs may share an artist)
- using Converter to write multiple data to multiple tags (e.g. using titles from a track list)
Supported are:
- all file types (see at the top), including wma and mp4 (which normally can not have a tag)
- all fields (comprehensive list later), including rating, playcount, color, timed comments.
The aim is to be interoperable with other players, where possible. Noteworthy or nonstandard supported tags include:
- values are in percent values independent of implementation (mp3=0-255, flac/ogg=0-100)
- floating values (0-1). Values like {1,2,3,4,5} are obsolete, illogical and nobody agrees on what they mean. Use the full granularity (limited only by tag (1/255 for mp3, 1/100 for other formats)) and pick graphical representation (progress bar or any number of "stars" you want). Basically rate 1) how you want 2) all audio types the same 3) be happy the value is in the tag 4) visualize the rating value as you want - be it 3 stars or 10 or a progress bar.
- interoperable with other players (POPM frame), but most of them will only recognize the value in their own way
- number of times the song has been played (the exact definition is left upon the user, who can set up the playcount incrementation behavior arbitrarily, or edit the value manually (increment/decrement/set arbitrary number - it is your collection, accept your power!).
- the data are written in custom tag (in mp3, written also in
POPMframe counter)
- comments associated with specific time/part of the song. They can be added during playback on the seeker and viewed in popup menus.
- the GUI makes it really easy to add or edit these and takes no space, since uses the seekbar and popup windows.
- the data are written in custom tag
- just in case you want to associate songs with a colors, you can.
- using custom tag
- image in tag can be imported/exported, but I advise against placing images in audio tags, consumes space and is semantically incorrect (cover is album metadata, not song metadata).
- cover read from file location is supported too, looking for image files named:
- song title.filetype
- song album.filetype
- cover.filetype or folder.filetype
All settings and entire user interface layout serialize into a human-readable and editable files. These can be edited, backed up or switched between applications.
Most of the functionalities are implemented as widgets, that can be loaded, closed, moved and configured separately. Multiple instances of the same widget can run at once in windows, layouts or popups.
Widgets' source files can be created and edited in runtime and any changes will be immediately reflected in the application. This means that if you are a developer you can simply edit code of the .java file, hit save and watch as the widgets are (recompiled and then) reloaded with previous state and configuration.
Controls for playback, like seeking. Supports song chapters.
Table or playing songs. Of course, it is possible to use more of them once. Very handy to have a side-playlist sometimes.
Shows cover and song metadata. Supports cover download (url drag & drop) and rating.
Tag editor
Object-object converting facility.
- Displays data as text while allowing user to apply function transformations. Handy file renamer and per-song group tagger. Supports object lists, text transformations, manual text editing, regex, writing to file etc.
- Provides set of functions that transform java objects (such as String or File). User can then set some kind of input
(formally
List<INPUT>) and apply and chain these transformation functions (on every element of the list) to get some result (List<OUTPUT>). It may sound confusing at first, but it is an intuitive and very powerful thing, particularly when combined with the ability to see the transformation output as a text at every step and the ability to manually edit that text and reuse it as an input for further transformation. The final output can be used as text or for an action, such as- file renaming
- tagging
This makes it possible to import song titles from copy-pasted track list found on web by 'cleaning' it up with text line transformations (remove x characters from start, etc.) rather than manually. Changing extension or names of a bunch of files is a piece of cake.
Song tables. User can link them up, so they display increasingly filtered/specialized content. For example, 1st table can display all artists (all unique artists in entire song library), 2nd table linked to 1st would display all unique albums of songs by any artist/s selected in the 1st table. So on until Nth table displays the songs. Combinations are endless. In addition, because of the modular gui, you can set up table size and position as you wish and the layout is not restricted to area of the window (layout has own virtual space, like virtual desktops). Lastly, in is possible to set up widgets (in this case individual tables) to be 'passive' until user allows them to load properly - it is possible to create a multiple views with lots of tables with practically no performance impact at all (by using views only when needed and have them 'sleep', but be prepared and configured all the time).
Image viewer - displays an image
Displays images and thumbnails for images in a directory
- Can also be set up to display directory of the currently playing song (or any song for that matter). Useful to show more than a song cover, if you have more album images.
- has slideshow mode
- has a 'theater mode' intended to use as fullscreen album cover slideshow with a 'now playing' info overlay
Configuring facility displaying settings for either:
- application
- widget
- JavaFX scene-graph
- other java object implementing Configurable. There are methods to turn plain java objects into Configurable. For example using annotations on fields or using JavaFX properties.
Displays hierarchies:
- application modules
- file system
- scene graph (this is taking the idea from the ScenicView app and works basically the same). When used with the combination of Settings widget it is a great way to debug the application scene-graph (yeah from within the application)
Displays System.out in a TextArea, meant for developers
Configurable icon bar/dock. User can add/remove custom icons executing some predefined.
Plots custom mathematical function in a graph
The application in its self-contained form:
- is executable on its own
- requires no installation or preinstalled software
- runs from anywhere
- does not require internet access
- does not write to registry or create files outside its directory apart from temporary files
The Interface is minimalistic but powerful and fully modular.
Modules (widgets) are part of layout hierarchy, which can be manipulated, saved or even loaded as standalone application.
- minimalistic - shows only what is important, no endless headers and borders taking up important space. With headless and borderless window mode 100% of the space is given to the widgets.
- powerful - infinite virtual space, horizontally scrollable, zoom-able
- layout mode - temporary 2nd ui layer allowing user to edit and configure the layout, widgets and more, alleviating normal user interface from all this
- completely skinnable (css)(skin discovery + change + refresh does not require application restart)
- can provide input and output (e.g. playlist table has selected song as output)
- inputs and outputs can be bound - when output value changes, it is passed into the listening input of other widget
- inputs can be set to custom values
- the whole system is displayed visually as editable graph
- can load lazily - be passive until user explicitly requests loading with mouse click.
- widget management: Gui gives the ability to divide layouts into containers for widgets. These allow resizing, positioning, swapping, adding, removing and many more widget operations.
- Individual containers form nested hierarchy that can be configured at any level easily through user interface, navigating with left (down) + right (up) mouse click in layout mode.
- multiple layout support/virtual layout space. Switching layouts by dragging them horizontally (left,right) opens new space for more layouts. This provides virtually infinitely large and conveniently navigable working space.
- snap to screen edges and other windows, screen-to-screen edges also supported.
- auto-resize when put into screen edges and corners (altogether 7 different modes - all, left/right half, right half, top-left/top-right/bottom-left/bottom-right quadrant)
- system tray, taskbar, fullscreen, always on top
- mini mode - a docked bar snapped to the top edge of the screen
- multiple screen support
- multiple windows
- configurable notification positions (corners, center) + window/screen oriented
There are multiple improvements over standard JavaFX Controls, mostly using custom Skin set by css.
The changes are documented in the source code:
- SpitComboBox
- SpitLabelSkin
- SpitListCellSkin
- SpitListViewSkin
- SpitScrollBarSkin
- SpitScrollPaneSkin
- SpitSliderSkin
- SpitSplitPaneSkin
- SpitTableCellSkin
- SpitTableViewSkin
- SpitText
- SpitTextAreaSkin
- SpitTreeCellSkin
- SpitTreeTableCellSkin
- SpitTreeTableViewSkin
- SpitTreeViewSkin
- global hotkey supported - shortcuts don't need application focus if so desired
- media keys supported
- customizable (any combination of keys: "F5", "CTRL+L", etc)
- large number of actions (playback control, layout, etc)
- navigation: No more back and up buttons. Use left and right mouse buttons to quickly and seamlessly navigate within user interface.
- icons: No ugly buttons doing the unexpected. Icons are designed to visually aid user to understand the action. Decorated with tooltips. Some are also skinnable or change to visualize application state.
- tooltips: Everywhere. And big too. Explain all kinds of functionalities, so read to your heart's content. There are also info buttons opening information popups.
- units: No more '5000 of what questions', everything that needs a unit has a unit, e.g. filesize (kB,MB,...), time duration, bitrate, etc. Multiple units are supported when possible, e.g., using 2000ms or 2s has the same effect. This is all supported in application settings or in table filter queries.
- validation: Designed to eliminate input errors by preventing user to input incorrect data. Warning icons signal incorrect input. Really helps with writing regular expressions.
- defaults: Every setting has a default value you can revert to.
- shortcuts: Quick & easy control over the application anytime.
- smart ui: Notifications that can be closed when they get in the way or keep being open when mouse hovers over. Throw notifications manually or put whole widgets in it. Tables or docked window that monitor user activity. Click-less ui reacting on mouse hover rather than click.
- Configurable playcount incrementing strategy: at specified minimal time or percent of song playback
- Web search with a query, e.g. search album on Google (opens default browser)
- Cover downloading on drag&drop
- Cool animations & effects
- Smart and intuitive drag&drop system
- area that can be dropped on is visually highlighted and displays icon and description of the action that would be executed
- individual components supporting drag&drop can cover each other
- Crisp images in any size. Images load quickly and don't cause any lag (not even the big ones), images around 5000px are handled just fine, apart from the inevitable memory footprint.
Show
This is the application module, containing the source code for the functionality.
For now, the sources are provided with no licence.
Which does not mean anything is permitted, it is the opposite. This may change in the future.
This is a collection of source codes for widgets for this application, found in app/widgets. For portability reasons, each widget specifies its licence. Usually it is The Unlicense.
This is collection of useful utility methods/extension, with primary intention of supporting the player module of this project.
All the sources, unless specifically stated otherwise in the source code file, are under The Unlicense.
This is a collection of demonstrative projects found on the internet, mostly contributed as answers on stackoverflow.com.
The sources are provided with no licence.
Which does not mean anything is permitted, it is the opposite. This is because it would be too time-consuming to find the
authors/contributors and figure things out. If you need to use the code, the files contain information about where to find the authors of the code.