SubFire 5 early preview
Posted: Mon Jan 15, 2024 4:17 pm
https://subfiresuite.com/demo5/#/home
Supports:
Currently the only authentication is to have been on the same host as a SubFire 2 or 3 instance is on, or the 7-digit authentication relay (use https://subfiresuite.com/link/#/ if you don't have a SubFire 2 or 3 instance to link from).
----
Still to do for 100% parity
----
Technical History:
After enough technical and annoying issues with library upgrades and the failure to get a monorepo working in what was to be SubFire 4...I gave up. SubFire 4 won't exist. The constant arguing of incompatibilities between react18, storybook, mui, and the needs of the monorepo approach I was taking, just got too frustrating. Also, now that I am regularly coding (p)react for work, i kinda tired of dealing with that form of components and jsx at home.
So totally new approach. The new implementation is a core library (able to work in node.js server-side as well as in browsers), a 'browser' library that supports the key things around queue management, playing through the audio tag, and eventually chromecast support and then the app itself (I haven't yet split components from the app, as the build tool I have for the app doesn't support rollup/webpack). The UI design is beercss for Material You (Material 3) look and feel, and an interesting new-ish web-components w/ jsx framework called mishijs. Wave.js for the visisualizations.
I've done some early tests with the Fire TV and it looks like things will be ok, though I'll be making a few layout changes for TV display over time. The visualizers are a little sluggish on older Fire Tablets. BTW there's bugs in the visualizers and the remote receiver stuff that I'm still working on.
Supports:
- Loading from play queue
- Remembering last playing
- Inherits login from a prior SubFire 2 or SubFire 3 instance on the same client machine
- PWA installation on desktop (chromium browsers) or android - I have not tested IOS yet, but I know Safari has bugs with the UI library I am using, so I may never support it.
- MediaSession API
- Loading from playlists (including shuffle)
- Loading from SubFire "Radio" stations
- Random songs (in specific folder or whole system)
- Save Play Queue
- Receiving remote routing from a SubFire 2 or 3 player. (my current workaround for not having 'browsing' up yet)
Currently the only authentication is to have been on the same host as a SubFire 2 or 3 instance is on, or the 7-digit authentication relay (use https://subfiresuite.com/link/#/ if you don't have a SubFire 2 or 3 instance to link from).
----
Still to do for 100% parity
- Albums (incl id3 and the various queries
- Music Directory browsing (filesystem)
- Artist-Album browsing (ID3 tags)
- Bookmarks
- Login by entering credentials directly
- chromecast
- See what firetablet's cast to fire tv does
- A number of minor changes for the TV beta
----
Technical History:
After enough technical and annoying issues with library upgrades and the failure to get a monorepo working in what was to be SubFire 4...I gave up. SubFire 4 won't exist. The constant arguing of incompatibilities between react18, storybook, mui, and the needs of the monorepo approach I was taking, just got too frustrating. Also, now that I am regularly coding (p)react for work, i kinda tired of dealing with that form of components and jsx at home.
So totally new approach. The new implementation is a core library (able to work in node.js server-side as well as in browsers), a 'browser' library that supports the key things around queue management, playing through the audio tag, and eventually chromecast support and then the app itself (I haven't yet split components from the app, as the build tool I have for the app doesn't support rollup/webpack). The UI design is beercss for Material You (Material 3) look and feel, and an interesting new-ish web-components w/ jsx framework called mishijs. Wave.js for the visisualizations.
I've done some early tests with the Fire TV and it looks like things will be ok, though I'll be making a few layout changes for TV display over time. The visualizers are a little sluggish on older Fire Tablets. BTW there's bugs in the visualizers and the remote receiver stuff that I'm still working on.