PDA

View Full Version : softsqueeze version



Peter =?iso-8859-1?Q?N=F5u?=
2004-09-03, 01:40
hi

I seem to recall loading softsqueeze version 1.2 from the web interface
this morning before heading to work (running latest nightly on a win2000
box, vith latest java beta). This somehow worked, despite tellings of the
opposite. Here at work however, loading SQ by clicking in the web iterface
of my server, doesn't work, so I download SoftSqueeze from sourceforge.net.
But there I can only find version 1.0. How come?

Using the web interface, browsing my collection down to the individual
leaf/song level, I get the option of downloading the song. This works
internally (on the same LAN as the server) but doesn't work "from work"
(through my firewall etc). I get the strange error message "c is not a
registred protocol" or "s is not a registred protocol". What port/protocol
is in use here? Any way to allow downloading of entire folders/albums "with
one click"

best,
peter

kdf
2004-09-03, 01:52
Quoting Peter Nġu <dkmj (AT) nou (DOT) com>:

> hi
>
> I seem to recall loading softsqueeze version 1.2 from the web interface
> this morning before heading to work (running latest nightly on a win2000
> box, vith latest java beta). This somehow worked, despite tellings of the
> opposite. Here at work however, loading SQ by clicking in the web iterface
> of my server, doesn't work, so I download SoftSqueeze from sourceforge.net.
> But there I can only find version 1.0. How come?

does your office run a caching proxy? We have one where I work and its a bloody
nightmare. even running archiving scripts within the local network will end up
grabbing the wrong files if they have the same date and filename. it seems to
conveniently ignore the time part of the stamp. Webstart has reported problems
with Java 1.5 beta, so that could be a cause if you have 1.4 at home. 1.5 is
required for sync, but you lose webstart for now.

>
> Using the web interface, browsing my collection down to the individual
> leaf/song level, I get the option of downloading the song. This works
> internally (on the same LAN as the server) but doesn't work "from work"
> (through my firewall etc). I get the strange error message "c is not a
> registred protocol" or "s is not a registred protocol". What port/protocol
> is in use here? Any way to allow downloading of entire folders/albums "with
> one click"

it should be converting to http, but if you have shortcuts stringing your
library together from several locations, it wont work yet.

-kdf

rtitmuss
2004-09-03, 02:19
Peter,

I have just uploaded Softsqueeze 1.2 onto Sourceforge for you. Sorry I
never got around to doing this earlier.

Note that this version will only work with recent nightlies, and it is
included in the slimserver. You only need to download this version from
sourceforge if you are using Softsqueeze to listen over the web.

Regards,
Richard


Peter Nġu wrote:

> hi
>
> I seem to recall loading softsqueeze version 1.2 from the web
> interface this morning before heading to work (running latest nightly
> on a win2000 box, vith latest java beta). This somehow worked, despite
> tellings of the opposite. Here at work however, loading SQ by clicking
> in the web iterface of my server, doesn't work, so I download
> SoftSqueeze from sourceforge.net. But there I can only find version
> 1.0. How come?
>
> Using the web interface, browsing my collection down to the individual
> leaf/song level, I get the option of downloading the song. This works
> internally (on the same LAN as the server) but doesn't work "from
> work" (through my firewall etc). I get the strange error message "c is
> not a registred protocol" or "s is not a registred protocol". What
> port/protocol is in use here? Any way to allow downloading of entire
> folders/albums "with one click"
>
> best,
> peter
>
>
>

Peter =?iso-8859-1?Q?N=F5u?=
2004-09-03, 03:27
At 10:52 2004-09-03, you wrote:

>does your office run a caching proxy? We have one where I work and its a
>bloody
>nightmare. even running archiving scripts within the local network will
>end up
>grabbing the wrong files if they have the same date and filename. it seems to
>conveniently ignore the time part of the stamp. Webstart has reported problems
>with Java 1.5 beta, so that could be a cause if you have 1.4 at home. 1.5 is
>required for sync, but you lose webstart for now.

I use 1.5 beta 2 at all locations. That's why I was surprised to see it
work this morning. Thought it was fixed in the SQ version 1.2 (somehow
circumnavigating the java bug). Or was I dreaming?

Have to look into the proxy-question, although I don't think they run one.

> >
> > Using the web interface, browsing my collection down to the individual
> > leaf/song level, I get the option of downloading the song. This works
> > internally (on the same LAN as the server) but doesn't work "from work"
> > (through my firewall etc). I get the strange error message "c is not a
> > registred protocol" or "s is not a registred protocol". What port/protocol
> > is in use here? Any way to allow downloading of entire folders/albums "with
> > one click"
>
>it should be converting to http, but if you have shortcuts stringing your
>library together from several locations, it wont work yet.

My library is one location with one link included for all "compilations". I
sometimes remove the link not to clutter the selections with billions of
artists that only appear once...

Are you saying, this particular one link is the culprit? The song I was
trying to download was in my main directory/location.

/peter

kdf
2004-09-03, 10:03
Quoting Peter Nġu <dkmj (AT) nou (DOT) com>:


> My library is one location with one link included for all "compilations". I
> sometimes remove the link not to clutter the selections with billions of
> artists that only appear once...
>
> Are you saying, this particular one link is the culprit? The song I was
> trying to download was in my main directory/location.
>
> /peter

it might be. the routine to create that link looks for a match in the path to
the path supplied as Music Path. I have noticed that when other paths are
pulled in, this routine tends to not match, thus not properly convert to a nice
http link.

It seems similar in symptoms to this reported bug:
http://bugs.slimdevices.com/show_bug.cgi?id=425

-kdf