Threaded Mode | Linear Mode

simoncn · 22-09-2014, 08:57

(22-09-2014 00:59)gvalente Wrote: Hello again

I have discussed the bug with the guys at Auralic and been told that it should be taken care of with the next version of DS Lightning.

Thanks, this is good news.

Quote:One related query:

Following your suggestions (and the ones of other members of the forum)

I have looked back through my responses to this thread and I don't believe I suggested that you make this change. The best approach is to use [Disc n] tagging and use a control point point that supports this correctly.

Quote: I have changed slightly the way I tag multiple discs and instead of using the format Album Name (Disc n) I changed it into Album Name, Disc n. Now I can see all of the separate discs. However, they do not show up progressively in Lightning DS.

For example, when I sort/display by genre I would see

Album A
Album B, Disc 1
Album C
Album D
Album B, Disc 2

I have noted that this is due to the second set of names (other than Artist) which are tagged. Is there any way to correct for this or, if not, how could I prevent albums to be indexed using also additional artist names? I do not normally use or report tags other than the main artist of the album. However, perhaps using dbPoweramp those names (including composer etc.) are included automatically. Any suggestions on how to deal with the issue above?

Thanks in advance.

Are you getting this sort order in Kinsky as well as Lightning DS?

If you are getting this sort order in Kinsky, this might be because you are using the MinimServer option Album.sortTags={Artist, Album} and the artist name for Album B, Disc 2 is different from the artist name for Album B, Disc 1. You could fix this by tagging both Album B, Disc 1 and Album B, Disc 2 with the same AlbumArtist tag while leaving the Artist tags as they are currently.

If you not getting this sort order in Kinsky, this is a problem with how Lightning DS is doing the sorting and you will need to contact Auralic for advice on how to fix it.

scrutney2 · 22-09-2014, 22:11

I'm curious - why does Minimserver require the track name to be appended with (Disc n) in order to separate multidisc albums, rather than using the discnumber tag, in the same way as (for example) iTunes?

simoncn · 22-09-2014, 23:09

(22-09-2014 22:11)scrutney2 Wrote: I'm curious - why does Minimserver require the track name to be appended with (Disc n) in order to separate multidisc albums, rather than using the discnumber tag, in the same way as (for example) iTunes?

It's the album name, not the track name.

MinimServer also reads the DISCNUMBER and DISCSUBTITLE tags. See this section for full details.

gvalente · 23-09-2014, 00:13

(22-09-2014 08:57)simoncn Wrote:
(22-09-2014 00:59)gvalente Wrote: Hello again

I have discussed the bug with the guys at Auralic and been told that it should be taken care of with the next version of DS Lightning.

Thanks, this is good news.

Quote:One related query:

Following your suggestions (and the ones of other members of the forum)

I have looked back through my responses to this thread and I don't believe I suggested that you make this change. The best approach is to use [Disc n] tagging and use a control point point that supports this correctly.

Quote: I have changed slightly the way I tag multiple discs and instead of using the format Album Name (Disc n) I changed it into Album Name, Disc n. Now I can see all of the separate discs. However, they do not show up progressively in Lightning DS.

For example, when I sort/display by genre I would see

Album A
Album B, Disc 1
Album C
Album D
Album B, Disc 2

I have noted that this is due to the second set of names (other than Artist) which are tagged. Is there any way to correct for this or, if not, how could I prevent albums to be indexed using also additional artist names? I do not normally use or report tags other than the main artist of the album. However, perhaps using dbPoweramp those names (including composer etc.) are included automatically. Any suggestions on how to deal with the issue above?

Thanks in advance.

Are you getting this sort order in Kinsky as well as Lightning DS?

If you are getting this sort order in Kinsky, this might be because you are using the MinimServer option Album.sortTags={Artist, Album} and the artist name for Album B, Disc 2 is different from the artist name for Album B, Disc 1. You could fix this by tagging both Album B, Disc 1 and Album B, Disc 2 with the same AlbumArtist tag while leaving the Artist tags as they are currently.

If you not getting this sort order in Kinsky, this is a problem with how Lightning DS is doing the sorting and you will need to contact Auralic for advice on how to fix it.

Hi

It is indeed another Lightning DS bug. It has been confirmed in an email correspondence with Auralic. In any case, is there anyway to prevent Minimserver to index albums by Composer (actually to provide that tag at all in the first place)? In fact, the odd ordering arises as dbPoweramp add composer as one of the tags and Lightning DS seems to order alphabetically in terms of composer when albums are sorted by genre... I thought that a way around is to prevent Minimserver to read the composer tag so that only album name and artist are kept when ordering.

By the way you are right, it was not you to suggest the , Disc n alternative but one of the readers of this forum.

Thanks.

simoncn · 23-09-2014, 09:25

(23-09-2014 00:13)gvalente Wrote: Hi

It is indeed another Lightning DS bug. It has been confirmed in an email correspondence with Auralic. In any case, is there anyway to prevent Minimserver to index albums by Composer (actually to provide that tag at all in the first place)? In fact, the odd ordering arises as dbPoweramp add composer as one of the tags and Lightning DS seems to order alphabetically in terms of composer when albums are sorted by genre... I thought that a way around is to prevent Minimserver to read the composer tag so that only album name and artist are kept when ordering.

By the way you are right, it was not you to suggest the , Disc n alternative but one of the readers of this forum.

Thanks.

You can prevent composer information being sent to the control point by removing the Composer.displayRole={artist} option from the tagCustom property and restarting MinimServer. If you want to prevent MinimServer reading composer information from your files, you can remove Composer from indexTags and/or itemTags and restart MinimServer.

Peter StreamMagic · 23-09-2014, 19:35

(23-09-2014 09:25)simoncn Wrote:
(23-09-2014 00:13)gvalente Wrote: Hi

It is indeed another Lightning DS bug. It has been confirmed in an email correspondence with Auralic. In any case, is there anyway to prevent Minimserver to index albums by Composer (actually to provide that tag at all in the first place)? In fact, the odd ordering arises as dbPoweramp add composer as one of the tags and Lightning DS seems to order alphabetically in terms of composer when albums are sorted by genre... I thought that a way around is to prevent Minimserver to read the composer tag so that only album name and artist are kept when ordering.

By the way you are right, it was not you to suggest the , Disc n alternative but one of the readers of this forum.
I was convinced this was the right sollution for this problem.
I even looked it up in the minim instruction, probably reading it with my eyes closed and my brain asleep!
Pretty weird though the CA streammagic controlpoint reacting the same way the Lightning DS from Auralic does. Now I am in doubt if I have to inform the CA app developers (again) since in this respect the app does function pretty well.

Sorry!

Regards,

Peter.

Thanks.
[/quote]

You can prevent composer information being sent to the control point by removing the Composer.displayRole={artist} option from the tagCustom property and restarting MinimServer. If you want to prevent MinimServer reading composer information from your files, you can remove Composer from indexTags and/or itemTags and restart MinimServer.
[/quote]

simoncn · 23-09-2014, 20:04

(23-09-2014 19:35)Peter StreamMagic Wrote: I was convinced this was the right sollution for this problem.
I even looked it up in the minim instruction, probably reading it with my eyes closed and my brain asleep!
Pretty weird though the CA streammagic controlpoint reacting the same way the Lightning DS from Auralic does. Now I am in doubt if I have to inform the CA app developers (again) since in this respect the app does function pretty well.

Sorry!

Regards,

Peter.

No need to apologise! This style of tagging can be used to make MinimServer treat each disc as a completely separate album. For some control points that have problems with the way MinimServer presents multidisc albums, this might be the only solution.

gvalente · 24-09-2014, 03:59

(23-09-2014 19:35)Peter StreamMagic Wrote:
(23-09-2014 09:25)simoncn Wrote:
(23-09-2014 00:13)gvalente Wrote: Hi

It is indeed another Lightning DS bug. It has been confirmed in an email correspondence with Auralic. In any case, is there anyway to prevent Minimserver to index albums by Composer (actually to provide that tag at all in the first place)? In fact, the odd ordering arises as dbPoweramp add composer as one of the tags and Lightning DS seems to order alphabetically in terms of composer when albums are sorted by genre... I thought that a way around is to prevent Minimserver to read the composer tag so that only album name and artist are kept when ordering.

By the way you are right, it was not you to suggest the , Disc n alternative but one of the readers of this forum.
I was convinced this was the right sollution for this problem.
I even looked it up in the minim instruction, probably reading it with my eyes closed and my brain asleep!
Pretty weird though the CA streammagic controlpoint reacting the same way the Lightning DS from Auralic does. Now I am in doubt if I have to inform the CA app developers (again) since in this respect the app does function pretty well.

Sorry!

Regards,

Peter.
Thanks.

You can prevent composer information being sent to the control point by removing the Composer.displayRole={artist} option from the tagCustom property and restarting MinimServer. If you want to prevent MinimServer reading composer information from your files, you can remove Composer from indexTags and/or itemTags and restart MinimServer.
[/quote]
[/quote]

Hi Peter

thanks for your suggestion. I decided to apply your solution in any case as it provides me with a better picture of the library. It is a matter of preference after all!

Giorgio

gvalente · 24-09-2014, 04:01

(23-09-2014 20:04)simoncn Wrote:
(23-09-2014 19:35)Peter StreamMagic Wrote: I was convinced this was the right sollution for this problem.
I even looked it up in the minim instruction, probably reading it with my eyes closed and my brain asleep!
Pretty weird though the CA streammagic controlpoint reacting the same way the Lightning DS from Auralic does. Now I am in doubt if I have to inform the CA app developers (again) since in this respect the app does function pretty well.

Sorry!

Regards,

Peter.

No need to apologise! This style of tagging can be used to make MinimServer treat each disc as a completely separate album. For some control points that have problems with the way MinimServer presents multidisc albums, this might be the only solution.

Hi Simon

I was told again that even this bug should be ironed out in the new version of the Lightning DS. So thanks for your patience and suggestions and for providing constant support to Minimserver's users. It is really greatly appreciated!

knirpslinn · 18-02-2015, 18:57

Is there any way to get MinimServer to read the Discnumber tag and use it to "separate" multi-disc sets in a future version?

I'm bouncing between Asset and Minim and I really don't want to re-tag 100's of albums.

I know it's a minor thing, but there are times when I only want to hear the 2nd or 3rd disc of a set - and yes I could just use Asset since it's already set up.

I have to say, MinimServer is a great piece of software. Thanks!