silver_ice
New elf
- Joined
- Jan 6, 2023
- Messages
- 37
Following up this thread - https://auschristmaslighting.com/threads/brisbane-se-qld-mini-2026-25-july.17433/page-5
So I gave a talk at the Sydney and Brisbane Minis about how to effectively use wifi to enable density and, in the fun cases, run a show across multiple locations. The ;tl;dr is use FPP remote mode and multi-sync and just sync timestamps/timecodes, instead of trying to stream full pixel data across possibly unreliable wifi. The difference is a couple of bytes a second vs 10+ megabytes a second (depending on your show size). It also makes you a bit more resilient on a couple of fronts - splitting your show across multiple controllers, you can lose one and still limp along. Further, you could lose your network for a period of time - things would still run and stay mostly in-sync (until the current track ended). The caveat of course is you need to a) have multiple controllers that can run Falcon, or at least speak FPP Remote and b) you have to distribute your media to all your controllers (since playback is controller local).
Anyway, I've been getting into Falcon Player 10 - all the basic stuff is there and still seems to work fine but there are a couple of changes around wifi that may affect you and that is a) the move to the new OS version (Debian Trixie) and not building in 3rd party wifi drivers anymore. This should actually result in broader wifi hardware compatibility as well as making it much easier to have a good idea if your little wifi dongle will work.
AS it turns out, I have 4 x HE123's on the bench at the moment, all with a mix of wifi adapters in Falcon Player 10 and as expected, all working fine - I have a mixture of RTL8188 chipsets (https://www.aliexpress.com/item/100....order_list.order_list_main.23.2b821802r9b74U)
And Atheros AR9271 chips (https://www.aliexpress.com/item/100....order_list.order_list_main.17.2b821802r9b74U) - these are nice since they have the detachable antenna which wil be nice to connect to a bulkhead connector and put outside the enclosure for my far away controller
I've also got a couple of Baldrick8's here - going to hook them up to some of these HE123s to show you FPP Remote can also bridge and make the Baldrick "wireless" if that is of interest.
Anyway, no real point to this post other than to continue the Briz mini thread and throw myself open to questions now that I have a full bench setup with a bunch of different configurations I can try, so if anyone has questions, fire away
So I gave a talk at the Sydney and Brisbane Minis about how to effectively use wifi to enable density and, in the fun cases, run a show across multiple locations. The ;tl;dr is use FPP remote mode and multi-sync and just sync timestamps/timecodes, instead of trying to stream full pixel data across possibly unreliable wifi. The difference is a couple of bytes a second vs 10+ megabytes a second (depending on your show size). It also makes you a bit more resilient on a couple of fronts - splitting your show across multiple controllers, you can lose one and still limp along. Further, you could lose your network for a period of time - things would still run and stay mostly in-sync (until the current track ended). The caveat of course is you need to a) have multiple controllers that can run Falcon, or at least speak FPP Remote and b) you have to distribute your media to all your controllers (since playback is controller local).
Anyway, I've been getting into Falcon Player 10 - all the basic stuff is there and still seems to work fine but there are a couple of changes around wifi that may affect you and that is a) the move to the new OS version (Debian Trixie) and not building in 3rd party wifi drivers anymore. This should actually result in broader wifi hardware compatibility as well as making it much easier to have a good idea if your little wifi dongle will work.
AS it turns out, I have 4 x HE123's on the bench at the moment, all with a mix of wifi adapters in Falcon Player 10 and as expected, all working fine - I have a mixture of RTL8188 chipsets (https://www.aliexpress.com/item/100....order_list.order_list_main.23.2b821802r9b74U)
[ 41.985304] usb 1-1: RTL8188FU rev B (SMIC) romver 0, 1T1R, TX queues 2, WiFi=1, BT=0, GPS=0, HI PA=0[ 42.087281] usb 1-1: RTL8188FU MAC: 00:2e:2d:30:76:05[ 42.141382] usb 1-1: rtl8xxxu: Loading firmware rtlwifi/rtl8188fufw.binAnd Atheros AR9271 chips (https://www.aliexpress.com/item/100....order_list.order_list_main.17.2b821802r9b74U) - these are nice since they have the detachable antenna which wil be nice to connect to a bulkhead connector and put outside the enclosure for my far away controller
[ 10.418142] usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 50980[ 10.456725] systemd[1]: Finished systemd-modules-load.service - Load Kernel Modules.[ 10.493430] systemd[1]: Finished systemd-network-generator.service - Generate Network Units from Kernel Command Line.[ 10.539122] systemd[1]: Started systemd-journald.service - Journal Service.[ 10.654884] ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits[ 11.382289] ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.3[ 11.406917] ath9k_htc 1-1:1.0: FW RMW support: OffI've also got a couple of Baldrick8's here - going to hook them up to some of these HE123s to show you FPP Remote can also bridge and make the Baldrick "wireless" if that is of interest.
Anyway, no real point to this post other than to continue the Briz mini thread and throw myself open to questions now that I have a full bench setup with a bunch of different configurations I can try, so if anyone has questions, fire away