If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
pleasantly surprised that I was able to use Robin's Net-UDAP to
configure my new Boom which arrived this morning. So it's not just
useful for Receivers.
OK. But why would you? You can configure the Boom right out of the box with whats provided. The receiver on the other hand has to use the Controller or Net-UDAP as its only other option.
Interesting...UDAP, as I recall, stands for Ubicom Digital Access Protocol or something like that. Theoretically it can work on any player with a Ubicom processor - that would be the SB2, SB3/Classic, Transporter, Boom and of course the Receiver. It might work on an SB1, but that's a different Ubicom processor and it might not support UDAP. It definitely won't work on the SLIMP3 (Microchip microcontroller CPU) or the Controller (Samsung ARM CPU).
Boom (PQP3 - late beta, PQP1 - early beta), Squeezebox Radio (PB1 - early beta)
Mark Lanctot wrote:
> Interesting...UDAP, as I recall, stands for Ubicom Digital Access
> Protocol or something like that. Theoretically it can work on any
> player with a Ubicom processor - that would be the SB2, SB3/Classic,
> Transporter, Boom and of course the Receiver. It might work on an SB1,
> but that's a different Ubicom processor and it might not support UDAP.
> It definitely won't work on the SLIMP3 (Microchip microcontroller CPU)
> or the Controller (Samsung ARM CPU).
It does indeed work with all Squeezebox devices from SB2 onwards (except
the controller).
Aesculus wrote:
> OK. But why would you? You can configure the Boom right out of the box
> with whats provided. The receiver on the other hand has to use the
> Controller or Net-UDAP as its only other option.
Once I develop a SC plugin that uses UDAP to configure SB devices, it
will be far easier to configure a Boom or any other SB device[1] from
the SC interface than with the remote.
R.
[1] Starting with the SB2, and not including the Controller.
Goodsounds wrote:
> I have just two SB3s, but I found doing the configuration with the
> remote to be quite easy. Would this new approach make a substantive
> difference?
>
> (I ask because it isn't obvious to me what improvement might be made).
Well, I'm not going to argue that the difference will be life-changing,
but for example...
* entering a long WEP/WPA key is much easier using a keyboard
* no need to enter the SC address
Aesculus wrote:
> OK. But why would you? You can configure the Boom right out of the box
> with whats provided.
because my wireless WPA key is really long, and a mixture of letters and
digits, which is a pain to enter manually. But with Net-UDAP, I can
cut-n-paste it.
but, agreed, it's not a huge deal, just noting the fact, really.
Calum Mackay wrote:
> Aesculus wrote:
>> OK. But why would you? You can configure the Boom right out of the box
>> with whats provided.
>
> because my wireless WPA key is really long, and a mixture of letters and
> digits, which is a pain to enter manually. But with Net-UDAP, I can
> cut-n-paste it.
>
> but, agreed, it's not a huge deal, just noting the fact, really.
also, and now we're getting really lazy: I've configured three SBRs
recently using Net-UDAP, but had never even seen a Boom before mine
arrived today.
So rather than get my head around the menus, remote, and what might be
needed, I just used Net-UDAP and did exactly what I did for the SBRs.
I've been playing the Boom all day now, using iPeng, and still have yet
to use the Boom's remote or menus at all.
So I've still got to learn all that good stuff, and weather display
plugins, etc, but Net-UDAP meant I could get going with zero effort
Aesculus wrote:
> OK. But why would you? You can configure the Boom right out of the box
> with whats provided. The receiver on the other hand has to use the
> Controller or Net-UDAP as its only other option.
Once I develop a SC plugin that uses UDAP to configure SB devices, it
will be far easier to configure a Boom or any other SB device[1] from
the SC interface than with the remote.
R.
[1] Starting with the SB2, and not including the Controller.
Aesculus wrote:
> OK. But why would you? You can configure the Boom right out of the box
> with whats provided.
because my wireless WPA key is really long, and a mixture of letters and
digits, which is a pain to enter manually. But with Net-UDAP, I can
cut-n-paste it.
but, agreed, it's not a huge deal, just noting the fact, really.
cheers,
calum.
WPA key entry alone makes this well worth it. Especially for the Boom which has no number/letter buttons on the remote.
If the Boom is your only SB device then there is no reverting to the SB3 remote for key entry.
Though, I still think WiFi security settings such as key entry should be part of SC7. How or if this is ever going to happen (if even possible) I dunno.
Though, I still think WiFi security settings such as key entry should be part of SC7. How or if this is ever going to happen (if even possible) I dunno.
The only way it is possible is through the Net-UDAP plugin that Robin is planning to put together
However, WPS is planned for all the current products if your router/AP support it.
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment