PDA

View Full Version : Dropping support for previous hardware ?



forestcaver
2010-02-03, 12:26
I notice that the server software for the touch is not going to support either the slimp3 or the squeezebox1 - are logitech phasing out support for older hardware versions ? If so, this will clearly influence my buying decision - I was planning on buying new hardware (probably a touch, as and when it is available), but would be inclined to not bother if logitech are dropping their support....
(I searched on the site but could find no information - does anyone know ?)

Cheers,
Andy

ChrisOwens
2010-02-03, 12:31
If the older players are not working with 7.5.0, please make sure there's a bug on that. There is no plan to remove support!

forestcaver
2010-02-03, 12:37
Thanks Chris - that's reassuring. Does that apply to the server software that will run *on* the touch, "tinySC" ?
Also, are you planning on releasing the stripped down server software to the community to allow installs on, for example, NAS devices or other small devices ?

Cheers,
Andy

andyg
2010-02-03, 12:45
TinySBS can't support SB1 or Slimp3. If you have those devices, run the normal server as you have already been doing for years. :)

You can download the embedded version here: http://downloads.slimdevices.com/nightly/?ver=7.5-embedded

ftlight
2010-02-03, 13:01
You can download the embedded version here: http://downloads.slimdevices.com/nightly/?ver=7.5-embedded

What's the difference between the regular and embedded versions of 7.5?

Bill

andyg
2010-02-03, 13:14
See http://wiki.slimdevices.com/index.php/Nightly_Builds

aubuti
2010-02-03, 13:16
Hey, thanks to whoever edited that wiki page to include the link and blurb for 7.5-embedded. That was needed.

forestcaver
2010-02-03, 13:41
Are there any plans to support slimp3 and sb1 in the embedded? Or are there technical reasons why they will never be supported?

Cheers,
andy

kdf
2010-02-03, 14:08
both devices are supported if run as a server on a PC. They are not
supported when run as "tinySBS" on the touch device. This is due to
additional overhead in the protocol for these devices. The embedded
branch can be run in a mode for a full server or for use on the Touch.
The term "embedded" is used to reflect the focus but not the limitation.
>
> Are there any plans to support slimp3 and sb1 in the embedded? Or are
> there technical reasons why they will never be supported?

bhaagensen
2010-02-03, 14:45
So 7.5 embedded aka. TinySC will not support SLIMp3 nor SB1. The wiki-page says that 7.5 embedded will eventually be merged with the mainline code. Does that imply that SLIMp3/SB1 support will be dropped as of that version?

aubuti
2010-02-03, 15:01
So 7.5 embedded aka. TinySC will not support SLIMp3 nor SB1. The wiki-page says that 7.5 embedded will eventually be merged with the mainline code. Does that imply that SLIMp3/SB1 support will be dropped as of that version?
No. As kdf said in his post, 7.5-embedded is _not_ the same thing as TinySC. 7.5-embedded supports SliMP3/SB1 if it is run on a regular server (pc or NAS). The only limitation with respect to SliMP3/SB1 is if it is run on the Touch.

bhaagensen
2010-02-03, 15:04
aubuti: I missed that... somehow. Thanks.

mherger
2010-02-03, 23:18
> No. As kdf said in his post, 7.5-embedded is _not_ the same thing as
> TinySC.

What we refer to as TinySC/TinySBS is just one configuration of the embedded code. It's the configuration used on SB Touch which disables a few memory intensive features using startup parameters.

You can make any embedded installation a TinySBS by adding those parameters. The code of the two is the same.

--

Michael

JJZolx
2010-02-03, 23:41
Wouldn't labeling the embedded branch 7.6 end some of the confusion over the terms 'embedded' and 'TinySC'? I don't know if the branching model supports this, before 7.5 is officially released, but I think it would make things simpler for everyone involved.

indifference_engine
2010-02-04, 03:13
> No. As kdf said in his post, 7.5-embedded is _not_ the same thing as
> TinySC.

What we refer to as TinySC/TinySBS is just one configuration of the embedded code. It's the configuration used on SB Touch which disables a few memory intensive features using startup parameters.

You can make any embedded installation a TinySBS by adding those parameters. The code of the two is the same.

--

Michael

Is it possible to turn off those "memory intensive features" on the regular SBS to save resources if I don't have anything older than an SB3?

mherger
2010-02-04, 03:33
>> You can make any embedded installation a TinySBS by adding those
>> parameters. The code of the two is the same.
>
> Is it possible to turn off those "memory intensive features" on the
> regular SBS to save resources if I don't have anything older than an
> SB3?

Yes, that's exactly what I wanted to say with the above paragraph :-). Those parameters will be available to any SBS installation running the embedded branch (or the future 7.6 or whatever it'll be called)

forestcaver
2010-02-04, 13:05
Just to be really, really clear :-) I think I understand the position now - is this right:

1) There is a rearchitecture of the server to allow a smaller footprint, that supports SB1 and slimp3.
2) This allows an install on the touch, that disables support for SB1 and slimp3 due to memory limitations on the touch.
3) This branch will be merged back to the main stream soon and then the server install (not on the touch) will allow a configurable smaller footprint that still supports SB1 and slimp3 on, for example, NAS boxes.

Sorry to labour the point, I am just trying to make sure I understand.

Thanks for all the replies so far...

Cheers,
Andy

pablolie
2010-02-05, 17:27
both devices are supported if run as a server on a PC. They are not
supported when run as "tinySBS" on the touch device. This is due to
additional overhead in the protocol for these devices..[

In 4 words: they are too "slim"...!? :-)

It's fascinating because back in 2005 0r 2006 there were passionate religious discussions about the need to keep devices as slim and dumb as possible, while others talked about the fancy UI limitations that imposed.

And now we have similar discussions about adding better settings backup functionality for these smarter devices. :-)

Moore's Law always gets us into these paradigm shifts. :-)