Don't know if it's related to the same problem, but running 6.5b on
linux (deb package), I have problems accessing Slim Device Picks and
ShoutCAST (LMA is fine). I don't know how long this has been a problem
as I haven't tried in ages. With d_plugins set I get the following
error:
Can't call met
The FLAC tag readers are essentially the same for 6.3 and 6.5.
DISCNUMBER is changed into the internally used DISC keyword.
DISCNUMBER works fine.
--
MrC
MrC's Profile: http://forums.slimdevices.com/member.php?userid=468
Philip Meyer Wrote:
> I went through the same issues a few weeks ago with disk numbers not
> working correctly for a multi-disk compilation album (FLAC). I think I
> was using DISCNUMBER="1/2", but I should have been using DISC=1. I
> believe DISCNUMBER only works for mp3 (ID3 tags, not ogg), w
I went through the same issues a few weeks ago with disk numbers not working
correctly for a multi-disk compilation album (FLAC). I think I was using
DISCNUMBER="1/2", but I should have been using DISC=1. I believe DISCNUMBER
only works for mp3 (ID3 tags, not ogg), whereas DISC is always okay.
I installed the 6.3.0 version of May 6, 2006 and playlists work again.
Then I installed the 6.3.0 version of May 8, 2006 and alle playlists
dissapear as soon as I make a scan for playlists only (same behavior as
with the 6.3.0 version of May 17, 2006).
I again went back to the May 6, 2006 version
Thanks Triode...
I ran the build-modules.pl script and it fixed the issue. Should have
thought of that, but the error message was somewhat misleading...
cheers
#!/ben
--
bklaas
bklaas's Profile: http://forums.slimdevices.c
If you edit Slim/Utils/Prefs.pm to change:
use "YAML::Syck" to use "YAML" does it start?
Do you have to compile modules via the build script? If so you may be
trying to run with an old version of the YAML::Syck binary and it will
be necessary to run the build script again.
--
Triode
-
Well after a new nightly and deleting the db, my Aerosmith album is
tagged with TRACKNUMBER 1 and DISCNUMBER 1 etc
Both show correctly in the track info but the album appears to be being
lasted alphabetically. Then everytime I refresh and view the album again
- the first track has moved to the en
Craig Wrote:
> Good Point I'll try that but DISCNUMBER 1 of 2 did show up in track info
> until a few days ago.
>
> So what is the standard? if there is one?
>
> TRACKNUMBER 1 -> whatever
> DISC 1
> DISC 2
> DISC 3
TRACKNUMBER is correct for track number. But I'm not sure which is
more accepte
I updated my subversion tree and restarted slimserver and now it's
complaining about my slimversver.conf file being corrupt. Conf file
looks fine, and I even tried using a backed up version of
slimserver.conf from several days ago. Still won't start.
[EMAIL PROTECTED] /usr/local/slimserver $ svn
I've just downloaded the latest nightly and removed the cache so I'll
see how it is when it's done.
I guess the gain mods are recent? I know when I started using MC they
weren't being picked up by Slimserver so I stopped saving them to tags
and did it with Foobar Instead.
My PC that runs MC is cu
Craig Wrote:
> H, that's interesting.
>
> As you can see in another thread I'm having trouble with DISCNUMBER at
> the moment. I use MC all the time but created another library field
> called DISCNUMBER and save that in the tags instead.
>
> I see you're also translating their gain tags, I'
JJZolx Wrote:
> I guess maybe we should have asked if disc and track numbers appeared to
> be correct in the track info. If so, fiddling with tags is probably be
> a waste of time. It it's already correct, there's nothing to fix in
> the tags.
>
> Try a reinstall of 6.5?
Good Point I'll try t
Craig Wrote:
> I changed Aerosmith's A Little south of Sanity to use DISC = 1 or 2 and
> also tried chaging TRACKNUMBER to TRACK.
>
> The Disc and track numbers are showing up ok in the track info but this
> is how it is being sorted
I guess maybe we should have asked if disc and track numbers a
H, that's interesting.
As you can see in another thread I'm having trouble with DISCNUMBER at
the moment. I use MC all the time but created another library field
called DISCNUMBER and save that in the tags instead.
I see you're also translating their gain tags, I've always found their
calcul
I changed Aerosmith's A Little south of Sanity to use DISC = 1 or 2 and
also tried chaging TRACKNUMBER to TRACK.
The Disc and track numbers are showing up ok in the track info but this
is how it is being sorted
Walk on Down
Hole in My Soul
Crazy
Monkey on My Back
Livin' on the Edge
Mama Kin
Cry
J. River's MC and its FLAC decoder uses 'DISC #' rather than DISCNUMBER
for FLAC files. The following (and attached) patch translates this to
SlimServer's internal DISC tag.
--- Slim/Formats/FLAC.pm2006-05-18 01:02:52.0 -0700
+++ Slim/Formats/FLAC.pm.new2006-05-18 11:21:38.00
All my multiple albums are tagged as DISCNUMBER 1 of 2 etc and the tag
just isn't showing up anymore.
I'll change a couple to use DISC as you said and see how it goes.
Craig
--
Craig
Craig's Profile: http://forums.slimde
Craig Wrote:
> I have parallel installations of 6.2 and 6.5 so I can switch between
> them whenever I like,
>
> I've never had success with DISCNUMBER = 1 though, that's why I took
> the X of Y approach and it's worked well untill recently.
It works as expected for me in 6.5.
Is it only the "X
kdf wrote:
> Quoting darbyweb
> <[EMAIL PROTECTED]>:
>
>>
>> Thanks for that Kevin.
>>
>> So i'm guessing the formatting bit will dissapear from settings pages
>> sometime soon :)
>
> your guess is as good as mine.
>
>> Or do they now have another use
>
> time and date strings do appear
I have parallel installations of 6.2 and 6.5 so I can switch between
them whenever I like,
I've never had success with DISCNUMBER = 1 though, that's why I took
the X of Y approach and it's worked well untill recently.
Craig
--
Craig
Quoting darbyweb <[EMAIL PROTECTED]>:
Thanks for that Kevin.
So i'm guessing the formatting bit will dissapear from settings pages
sometime soon :)
your guess is as good as mine.
Or do they now have another use
time and date strings do appear elsewhere.
honestly, I don't know why th
Thanks for that Kevin.
So i'm guessing the formatting bit will dissapear from settings pages
sometime soon :)
Or do they now have another use
Dean.
--
darbyweb
--
http://www.samares.net
Its our home !!
--
Strange. I just use 'DISCNUMBER = 1' etc., but disc 1 gets displayed
first.
Could this be related to your switch from 6.2 to 6.5? (I think that can
make things glitchy--sometimes you have to wipe & rescan or just delete
the database outright & rescan. Ugly, I know.)
--
windowshade
---
I've always used DISCNUMBER = 1 of 2 and it's worked ok, I've just
changed some DISCNUMBER tags to just 1 or 2 and they were picked up as
disc # but disc 2 was sorted first !!
The same files are being read fine in 6.2.2 so something has changed
somewhere.
Craig
--
Craig
--
The ReplayGain tags aren't being read in all of my mp3 files. A
specific mp3 file has these tags set (output of strings |
tail -20):
Code:
U``$
"`eR
aGUK
VLAME3.89
(beta)UU
I'm running SlimServer Version: 6.3.0 - 7431 - Windows XP - EN -
cp1252.
I've had no problems with playlists and I made a minor change to a
playlst and ran a re-scan without issue.
Have you checked the Unix permissions on the playlist files ??
What's the output of the debugging flags during a re
I just tried to reproduce this but on a Windows test system (with the
latest nighlty of 6.3.0). But with this Windows version my playlists
don't dissapear and everything is ok.
So is this a Linux related problem or only a problem related to my own
configuration (in this case I don't want to file
Pat Farrell wrote:
> Christopher Key wrote:
>> Could you try ./slimserver.pl --d_startup
I've reformatted the content below to make it a little more readable
>
> (beatles)root#/home/pfarrell/incoming/SlimServer_v2006-05-17>
> ./slimserver.pl --d_startup
> Got @INC containing: /home/pfarrell/inco
The Adblock extension wasn't causing the problem, but something in my
rules was.
I've discovered that there is a new version of Adblock called Adblock
plus which has some speed impovements (and more) over the older
version.
The fix for the problem I saw was to add an exception rule for
localhost
30 matches
Mail list logo