bits;607801 Wrote:
> I agree it doesnt need to be complicated. The correct usage is for 'n'
> random songs to be generated ahead at any given point. This allows for
> correct use of the UI such as "current playlist". This worked perfectly
> on 7.5.x and is broken under certain common use cases fo
Hi,
I am still trying to set up Squeezecenter on my DNS-323 NAS. I am using
7.6.0-31644 because more recent versions give 'this'
(http://forums.slimdevices.com/showthread.php?t=84884) error.
Scanning is aborted immediately after starting because the scanner
thinks the database is in the root fol
bits;607801 Wrote:
> Also buffering over wifi. How much data is really going over the
> connection to the player when these random songs get generated at the
> server?
Many changes made to the 7.6 server have been done solely for the sake
of running on the terribly underpowered Touch. Unfortuna
erland;607710 Wrote:
> There is no reason to make this complicated, just make sure to add
> tracks immediately when the current track reaches the last track in the
> playlist.
I agree it doesnt need to be complicated. The correct usage is for 'n'
random songs to be generated ahead at any given p
Wirrunna;606543 Wrote:
> Version: 7.6.0 - r31861 on WinXP does not pick up the MIP status of a
> new album in a "Look for new and changed music" scan. Workaround
> (obviously) is to do a "clear and rescan".
In addition to MIP integration being broken in 7.6 for new/changed, a
full rescan causes
bits;607657 Wrote:
>
> Ideas:
> -Do not reset the delay timer on track changes
> -Reset the 15 second time but ensure it never takes more than 25
> seconds before the action must be executed
>
> "Fixes" that keep with this idea that you can postpone required
> operations indefinitely.
> -increa
Fried;607336 Wrote:
> Well, I'm running Ver. 7.5.4 - r31858 of Squeezebox Server running on a
> WHS controlled by a web interface on a notebook and this very annoying
> bug is still present.I did a wipe & rescan (takes 2 1/2 hours for my
> 2800 albums and 40k records).
It's fixed in 7.6 beta squ
Ok, thanks I will do that :).
Correction though, The Itunes library file is stored on the NAS,
however maintained by Itunes in MAC OS, yes. SBS is running on QNAP
SSOTS. So Mac OS is not at all involved running the SBS, only on the
NAS. And the problem is not there in my current version 7.5.1 for
Phil Leigh;607639 Wrote:
> I agree that we don't all agree. It seems very odd to me that you would
> generate a random mix and then skip through ALL of initial track
> list...
15 seconds is a fair bit of a song. I see it as easy that a user may
decide to skip 10 songs in a row after hearing less
JJZolx;607644 Wrote:
> If you use the web interface then you can easily move to the last track
> in the playlist without skipping 'through' all of the tracks.
>
> Seems to me that Random Mix should at least be intelligent enough that
> if you skip on the last track in the playlist it would add a
Phil Leigh;607639 Wrote:
> I agree that we don't all agree. It seems very odd to me that you would
> generate a random mix and then skip through ALL of initial track
> list... I've never done that and I use random mix a lot. I might
> occasionally skip the first 1 or even 2 tracks... but never al
I don't think you you have to skip trough all tracks just decide when it
on it last leg that you want to skip before 15s has gone of that last
track
IF you have a powerful server you can increase the limits to lets say
100-200 tracks or somesuch, and it would not happen that often ?
That you want
awy;607635 Wrote:
> I'm not sure that we do agree.
I agree that we don't all agree. It seems very odd to me that you would
generate a random mix and then skip through ALL of initial track list...
I've never done that and I use random mix a lot. I might occasionally
skip the first 1 or even 2 tra
bits;607585 Wrote:
>
>
> I believe we all agree more songs must always be generated and not
> depend on getting 15 seconds into a song.
I'm not sure that we do agree.
--
awy
awy's Profile: http://forums.slimdevices.com
Bugs are marked FIXED when a suitable change is checked into the
source-code repository. They are marked CLOSED when an official release
with that fix is made.
Note that this specific fix (Slim repository checkin 31775 which was
included in Touch f/w 7.5 r9289 nightly) related to the embedded se
I don't understand the way bug reporting works.
This bug ist tagged FIXED RESOLVED but it isn't.Should I file a new
bug?
Thx, Fried
--
Fried
Fried's Profile: http://forums.slimdevices.com/member.php?userid=3
View this
16 matches
Mail list logo
