New LedFx binaries available:
Core: -- Browser-Based
Client: -- Desktop-App (needs a running Core)
CC: -- Desktop-App (Core-integrated)
More informations regarding Core, Client and CC:
expand
Core
If you don't know where to start, get this, open an internet browser, go to https://localhost:8888/ and off you go.
This is the server/backend that takes in audio, does the calculations and outputs blinking lights. Runs in the background on a Windows/Mac/Linux computer. You can then open the frontend in an internet browser, by going to https://localhost:8888/ on the same computer that is running the Core.
You can also pull up the frontend on your smartphone (or any other computer on the same network) by finding out what local IP your computer running the Core uses (most likely something like this 192.168.1.XXX, or 192.168.0.XXX) and opening a Browser on your smartphone and going to eg. https://192.168.1.123:8888/
Client
This is a Desktop App that opens the frontend of LedFx in a window on your desktop.
This app does NOT include the LedFx backend/server and cannot run LedFx by itself without the Core.
This Client app is useful for connecting to a running Core on your network (or the same machine).
CC (Client + Core = CC)
This is the Client and Core integrated into one Desktop App.
This Desktop App opens the Client frontend of LedFx in a window on your desktop AND runs the Core backend/server in the background.
This is useful for people who want the whole LedFx experience in one nice and tidy package.
With this, you can still connect to the backend server via a Client or browser.
⚠️ These builds are not signed (read this please):
Mac-Users:
Infos:
Reports as damaged, because of unsiged.
To fix it open Terminal and type in the following (with a SPACE at the end):
sudo xattr -cr
Then drag'n'drop the LedFx.app File into the terminal and hit enter -> it should ask for sudo password
Now you can open the App normally, give microphone and network permission, and you can even drag it into your applications.
Maybe at some point we might buy an apple dev-license for 99€/year, then the voodoo would not be needed anymore.
Win-Users:
Infos:
Reports as unsave, because of unsiged.
Maybe at some point we might buy a microsoft dev-license
Frontend-Changes:
Expand
- Release 2.0.107-b7
- FileDropper: Allow full ledfx config json
- Intro DIalog: adjust workflow
- Adjust Intro Dialog and some texts for settings toggles
- change default: show graphs on devices view. false -> true
- fix: click Reconnect Button in Detailed Dashboard View navigating to the Device View
- ScenePlaylist: add click on title and doubleclick on row to activate scene
- remove feature: websocket timestamp debug
Backend Changes
Expand
- Docs: MTU troubleshooting (#1278)
- Docs: Automagical year in copyright (#1273)
- Merge pull request #1272 from LedFx/mqtt-hass--some-love
- [pre-commit.ci] auto fixes from pre-commit.com hooks
- add dynamic effect dropdowns for effects and presets
- Merge pull request #1268 from LedFx/mqtt-hass--fix-if-scene-id-is-a-number
- Merge pull request #1269 from LedFx/mqtt-hass--exclude-complex-and-gap-devices
- mqtt-hass: exclude complex and gap devices
- mqtt-hass: fix if scene id is a number
- Merge pull request #1267 from LedFx/add-PixelGraphVariant-selector;-make-canvas-default
- remove red mask
- Add PixelgraphVariant-Selector; make canvas default
- Fix: none event in socket close race condition (#1266)