bonze Wrote:
> OK- I've read through this thread and a few others and now I'm not sure
> whether I have the 'problem' or not.
Bad form to reply to one's own post, but I've just found the setting I
required.
Server Settings>Behaviour>Compilations>'Group Compilations Together'
Hadn't spotted t
OK- I've read through this thread and a few others and now I'm not sure
whether I have the 'problem' or not.
I have ripped a compilation CD to .flac and placed it into folder
/ext/mnt/music/Various Artists/album.
Each of the 15 tracks on the CD has a different artist.
Browsing with slimserver, b
Philip Meyer Wrote:
> In Mp3Tag, there's options to tell the software what version of ID3 tags
> to read/write. It could be that you are seeing correct tags, but some
> other version tags are not being cleared in your case by simply opening
> and closing.
> You could try looking in another taggi
You guys speak of retagging all the files to eliminate multiple albums
caused by "various artist" cds, but I store my files as .wav files. I
also store my files in the format:
Music/[Artist]/[Album] [Year]/[Title].wav
Thus, when version 6.3 scans my music, instead of having 485 albums I
have 9
>Seems there is a lot of stuff going on about this, however all theories
>put forward so far do not seem to account for what is happening to
>me mainly as I keep each disk (and each album) in a distinct folder
>and my problem is not cured by opening the files in MP3Tag and resaving
>the files.
On 29-Jun-06, at 12:03 PM, ModelCitizen wrote:
kdf, get your self a glass of wine or a beer or whatever stimulant
dings
your bell and listen to some music!
but if I did that, my last.fm profile wouldn't be HALF as funny
-kdf
___
discuss mail
kdf, get your self a glass of wine or a beer or whatever stimulant dings
your bell and listen to some music!
MC
--
ModelCitizen
Squeezebox2 > Benchmark Dac1 > Naim NAC 82 > Naim NAP 250 > Shahinian
Arcs.
Music catalog: http://modelcitizen.mine.nu/music.txt
-
Quoting ModelCitizen
<[EMAIL PROTECTED]>:
kdf Wrote:
just to chime in...I have not seen this problem with 6.3.0. If any of
the hundreds who installed nightly builds during pre-release saw it,
they chose to remain silent.
I'm sure that if anyone willing/able to fix it can reproduce it with a
kdf Wrote:
> just to chime in...I have not seen this problem with 6.3.0. If any of
> the hundreds who installed nightly builds during pre-release saw it,
> they chose to remain silent.
> I'm sure that if anyone willing/able to fix it can reproduce it with a
> specific case, it will get fixed asa
dip Wrote:
> As far as I understand, if the ALBUMARTIST tag is set (you mentioned it
> is set to "Various Artists") then slimserver doesn't try to detect
> compilations automatically. In this case the COMPILATION tag is not
> automatically set and therefore the group compilations option does not
On 29-Jun-06, at 5:59 AM, Ledwidge wrote:
I removed 6.3, removed the slimsever directory, removed any remaining
regedit entries. But still there are multiple entries in both titles
and tracks when I reinstall 6.2.2 or even 6.2.1 !
6.3 left something somwhere, any ideas ???
slimserversql.db p
I removed 6.3, removed the slimsever directory, removed any remaining
regedit entries. But still there are multiple entries in both titles
and tracks when I reinstall 6.2.2 or even 6.2.1 !
6.3 left something somwhere, any ideas ???
--
Ledwidge
---
Ledwidge Wrote:
> I found that 6.3 not only created multiple albums but repeated tracks
> for no reason. On various CDs I now have double tracks i.e. 1,1, 2,2
> etc etc.
> They are all in seperate directories, all in flac and many are not
> compilations.
> Even when I remove 6.3 the fault remains
I found that 6.3 not only created multiple albums but repeated tracks
for no reason. On various CDs I now have double tracks i.e. 1,1, 2,2
etc etc.
They are all in seperate directories, all in flac and many are not
compilations.
Even when I remove 6.3 the fault remains. How can I FULLY remove 6.3.
Finnie,
That's it. Select the relevant tracks, click "part of compilation" so
that it shows a clear tick (rather than a greyed out one or a blank
box). Then do a full clear and rescan in slimserver (a search for new
music won't do it).
--
Siduhe
--
ModelCitizen Wrote:
> Yup, setting the compilation tag has worked. All compilation listings
> are back to normal now. Cheers!
> MC
Hi there,
Does anyone know when using Tag&Rename how you set the compilation
flag.
There is a tick box for "Part of a compilation" or something like that.
I as
ModelCitizen Wrote:
> Anyway. I'm giving up now and setting the Compilation = 1 tag, deleting
> the database and rescanning. If that doesn't work it's back to 6.2.2.
> MC
Yup, setting the compilation tag has worked. All compilation listings
are back to normal now. Cheers!
MC
--
ModelCitizen
S
As far as I understand, if the ALBUMARTIST tag is set (you mentioned it
is set to "Various Artists") then slimserver doesn't try to detect
compilations automatically. In this case the COMPILATION tag is not
automatically set and therefore the group compilations option does not
apply. You have eith
I think I found another case where Group compilations is not working
correctly. I noticed this with my remaining WMA files. All artists
from the tracks are showing up under Browse Artists, as is the artist
"Various Artists"
Album is stored in the music directory as Various Artists\Album.
Each
I forgot to mention one difference between our structures. In my
structure the ALBUM tag is always identical to the directory name
containing the files (e.g. "The Disco Years - CD1"). As far as I
understood in your structure the ALBUM tag would be "The Disco Years
(CD1)" but the directory structur
I also have for each physical disk a separate directory, i.e. for an
album comprising two disks I have two separate directories.
My structure is
music folder/artist/album name/tracknumber-artist - title.flac
for "normal cases" and
music folder/artist/album name - CD1/tracknumber-artist - titl
I am grateful for your help but I'm afraid it doesn't help. What you
call the cache I call the database and as I state quite unclearly
above, I delete it each time I attempt a rescan to cure the problem.
Any more suggestions very welcome.
BTW. There is a difference in the way you and I hold our f
I use a mixture of ogg and flac files and the same tags as you except
comment. I also have for each album a separate directory. A further
suggestion is that sometimes I had strange results (like double
entries) although I made a wipe and rescan. After manually deleting the
cache file everything wa
Thanks very much for the suggestion dip. I have indeed checked the
extended tags and what I state above is definitely correct for all my
Various Artist albums (at least) - the only tags used are tracknumber,
artist, title, album, genre, year, comment.
Any other suggestions very welcome, especially
Did you check in mp3tag only the standard tags shown on the left pane in
the predefined input fields or did you also check the "hidden" tags
which you can see if you choose a song with the right mouse and choose
the "tags" item from the context menu?
I had the problem that for some of my songs th
ModelCitizen Wrote:
>
> All my files are flac, all tagged using MP3Tag.
> Each disk is held in a separate directory, i.e.
>
> Music Folder/Artist - Album [Label,Year]/disc 1
>
> I only populate the title, artist, album, tracknumber, genre, year and
> comments fields. These are the tags support
Am I right in thinking that this issue has not been raised as a
SlimServer bug? If so, it seems to me that it probably should be, just
to ensure that 6.3 does not go out with this problem still included.
All my files are flac, all tagged using MP3Tag.
Each disk is held in a separate directory, i.
On 6/18/06, parkmad <[EMAIL PROTECTED]> wrote:
This rant is not directed at you, but at Slim Devices. Why should Ihave to spend the next couple hours redoing my folder structure to
correct something that used to work? You ABSOLUTELY do not have to do this. You can continue to use 6.2.2 as you al
I have for each album a separate folder. But with the present version of
6.3.0 Slimserver detects not a single compilation album. I have to set
for all songs of compilation albums the COMPILATION flag to 1 otherwise
I have over thousand artists instead of about 250. I use the latest
nightly of 6.3
Thanks Ceejay, I guess I will have to do that.
This rant is not directed at you, but at Slim Devices. Why should I
have to spend the next couple hours redoing my folder structure to
correct something that used to work? Using 6.2.2, I don't have the
Internet radio functionality I used to have,
parkmad -
see the thread I linked to earlier ... I think slimserver will be
happier if you have one folder = one album (ie not as you have it).
http://forums.slimdevices.com/showthread.php?t=23295
Ceejay
--
ceejay
ceej
It is happeing with me with FLAC files.
My folder structure is:
/FLAC/Artist/Album/tracks
One album per folder and compilation albums are stored in the same way,
meaning a different folder is created for different artists for the same
album.
--
parkmad
---
Siduhe Wrote:
>
> Do I have the following right ?
>
> It only happens on albums with multiple artists;
> It only happens with mp3s;
> It only happens where both ID3v1 and ID3v2 are present.
>
> I will also try a test album to see if having ID3v2.3 or ID3v2.4 makes
> any difference.
I have my
JJZolx Wrote:
> Has anyone filed or reopened a bug report on this? It would be good to
> avoid releasing 6.3 with this bug.
>
> How are you guys organizing your files - one album per folder, or do
> you have some cases where tracks from different albums reside in the
> same folder?
One album p
In case it is of use to users or the developers I can confirm that I am
having NO problems with compilation albums on latest 6.3 nightly on
WinXP Pro.
1. All files are FLAC.
2. No Compilation tag set.
3. One album per folder in /FLAC/Artist/Album/tracks format (The
compilation albums are stored a
Has anyone filed or reopened a bug report on this? It would be good to
avoid releasing 6.3 with this bug.
How are you guys organizing your files - one album per folder, or do
you have some cases where tracks from different albums reside in the
same folder?
--
JJZolx
Jim
-
I am also seeing this issue. I have been using 6.2 and I do not have
multiple entries for albums that have multiple artists. Because I
noticed the URL availability issues with Shoutcast, I tried 6.3 and
that fixed that issue, but then albums with mutiple artists showed as
individual album entrie
Jeff, not to worry - it doesn't.
I don't know how else to explain myself here but I'm obviously not
doing a good enough job - this is *not* a specific designed behaviour
with 6.3.0 - It is a problem that only seems to affect some compilation
albums (in my case about 50 out of over 800). If you
Jochen Wrote:
> I can confirm that slimserver 6.3 handles my compilations in a strange
> way, generating multiple album entries for each artist. Adding the
> COMPILATION tag to the affected albums solved this just fine (after a
> rescan).
If this is the case in the final version, then 6.3 is not
I can confirm that slimserver 6.3 handles my compilations in a strange
way, generating multiple album entries for each artist. Adding the
COMPILATION tag to the affected albums solved this just fine (after a
rescan).
--
Jochen
First, there is a wiki page on this topic but there has been some
discussion on whether it needs updating. Since the designed behaviour
for 6.3 is, I believe, changed then it probably does. It is at
http://wiki.slimdevices.com/index.cgi?VariousArtistsLogic
Second, there are other threads on this
>I have recently hit the same problem, und used the same fix
>COMPILATION = 1 and ALBUM ARTIST = Various Artists
>
You shouldn't need to ever set ALBUMARTIST="Various Artists".
If you have different ARTIST tag values for different tracks on the same album
title (in the same folder only, I think -
I have recently hit the same problem, und used the same fix
COMPILATION = 1 and ALBUM ARTIST = Various Artists
However .. I could not get this to work with WMA compilations, and
after mucho hair pulling and cursing converted them all to FLAC .. all
was ok then.
As a side point, I found that when
Sorry if my post wasn't clear: let me explain - my post was only
intended to be in response to the question:
WHAT DO I DO IF I UPGRADE TO 6.3.0. AND I SEE MULTIPLE COPIES OF THE
SAME ALBUM WITH JUST ONE SONG IN BUT I HAVEN'T MADE ANY CHANGES TO THE
DATABASE ?
My solution was simply to open each a
On 6/14/06, Siduhe <[EMAIL PROTECTED]> wrote:
JJZolx Wrote:> Are you saying that 6.3.0 has no way of recognizing compilations without
> an explicit COMPILATION tag? That's going to cause a ton of grief if> true.Nope, just if you use a COMPILATION tag that you will need to reset it(or at least that
Siduhe Wrote:
> Nope, just if you use a COMPILATION tag that you will need to reset it
> (or at least that was my experience). If you don't have it, don't need
> to do anything other than force the album title (again, only my
> experience with an XP setup).
What do you mean when you say "reset"
JJZolx Wrote:
> Are you saying that 6.3.0 has no way of recognizing compilations without
> an explicit COMPILATION tag? That's going to cause a ton of grief if
> true.
Nope, just if you use a COMPILATION tag that you will need to reset it
(or at least that was my experience). If you don't have
On 6/14/06, JJZolx <[EMAIL PROTECTED]> wrote:
Siduhe Wrote:> This appears to be caused by the slightly different way that
6.3.0 deals> with album tags. Possibly to do with the removal of common album> titles.>> To resolve: open the affected album in a tagger, select all songs> force the album ti
Can someone from Slim Devices please review this and at least provide an
option to keep it compatible with 6.2.2 behaviour!
--
brookheather
brookheather's Profile: http://forums.slimdevices.com/member.php?userid=4317
View
Siduhe Wrote:
> This appears to be caused by the slightly different way that 6.3.0 deals
> with album tags. Possibly to do with the removal of common album
> titles.
>
> To resolve: open the affected album in a tagger, select all songs
> force the album title and reset the compiliation tag.
This appears to be caused by the slightly different way that 6.3.0 deals
with album tags. Possibly to do with the removal of common album
titles.
To resolve: open the affected album in a tagger, select all songs
force the album title and reset the compiliation tag.
Bit of a pain (I had to do
51 matches
Mail list logo
