DJ mix ARs

[gnu_andrew]

In some cases, a DJ mix AR may apply to a subset of tracks e.g.
http://musicbrainz.org/show/release/?releaseid=750140 and
http://musicbrainz.org/album/0988110a-0882-472a-a41b-b2957d81c520.html

In such a case, it doesn't make sense to apply the DJ mix AR to
individual tracks as the mix is a relationship between tracks (e.g. X
mixed track 1 into track 2), not something relating to the content of
one (X mixed songs Y and Z to create track 1).

I've proposed adding each artist with a DJ mix AR to the release (e.g.
http://musicbrainz.org/show/edit/?editid=11071676) but this is not
ideal either as the track range isn't represented.

I think ideally MBz needs a way of specifying an optional range of
tracks for a DJ mix: http://bugs.musicbrainz.org/ticket/5336

Any thoughts?
--
Andrew :-)

Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)

Support Free Java!
Contribute to GNU Classpath and the OpenJDK
http://www.gnu.org/software/classpath
http://openjdk.java.net

PGP Key: 94EFD9D8 (http://subkeys.pgp.net)
Fingerprint: F8EF F1EA 401E 2E60 15FA  7927 142C 2591 94EF D9D8

_______________________________________________
MusicBrainz-users mailing list
MusicBrainz-users@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-users

[Oliver Charles-2]

On Mon, Aug 24, 2009 at 2:24 PM, Andrew John
Hughes<gnu_andrew@...> wrote:
> I think ideally MBz needs a way of specifying an optional range of
> tracks for a DJ mix: http://bugs.musicbrainz.org/ticket/5336
>
> Any thoughts?

In NGS, we're rethinking how we display ARs. Currently, we show each
AR per track, but I think the idea now is to display the tracklist,
and then group the relationships underneith. This would give the
following:

Tracklist:
1. Foo
2. Bar
3. Baz

DJ Phat Tunes dj-mixed tracks 1-2

On the data side though, tracks 1 & 2 both have track level ARs. If
this is the case, then doing track level ARs is the correct way to go
about it. It won't look correct on the site at the moment, but come
the NGS server being ready, it will display correctly.

--
    Oliver Charles / aCiD2

_______________________________________________
MusicBrainz-users mailing list
MusicBrainz-users@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-users

[Chad Wilson-2]

Andrew John Hughes wrote:

> In some cases, a DJ mix AR may apply to a subset of tracks e.g.
> http://musicbrainz.org/show/release/?releaseid=750140 and
> http://musicbrainz.org/album/0988110a-0882-472a-a41b-b2957d81c520.html
>
> In such a case, it doesn't make sense to apply the DJ mix AR to
> individual tracks as the mix is a relationship between tracks (e.g. X
> mixed track 1 into track 2), not something relating to the content of
> one (X mixed songs Y and Z to create track 1).
>
> I've proposed adding each artist with a DJ mix AR to the release (e.g.
> http://musicbrainz.org/show/edit/?editid=11071676) but this is not
> ideal either as the track range isn't represented.
>
> I think ideally MBz needs a way of specifying an optional range of
> tracks for a DJ mix: http://bugs.musicbrainz.org/ticket/5336
>
> Any thoughts?
>  

Come to think of it, we're going to have to decide how we handle DJ
mixed versions of tracks with respect to works I guess. Won't that
necessitate linking each DJ-mixed track to its original work; thus still
require per-track ARs?

_______________________________________________
MusicBrainz-users mailing list
MusicBrainz-users@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-users

[gnu_andrew]

2009/8/24 Oliver Charles <oliver.g.charles@...>:

> On Mon, Aug 24, 2009 at 2:24 PM, Andrew John
> Hughes<gnu_andrew@...> wrote:
>> I think ideally MBz needs a way of specifying an optional range of
>> tracks for a DJ mix: http://bugs.musicbrainz.org/ticket/5336
>>
>> Any thoughts?
>
> In NGS, we're rethinking how we display ARs. Currently, we show each
> AR per track, but I think the idea now is to display the tracklist,
> and then group the relationships underneith. This would give the
> following:
>
> Tracklist:
> 1. Foo
> 2. Bar
> 3. Baz
>
> DJ Phat Tunes dj-mixed tracks 1-2
>
> On the data side though, tracks 1 & 2 both have track level ARs. If
> this is the case, then doing track level ARs is the correct way to go
> about it. It won't look correct on the site at the moment, but come
> the NGS server being ready, it will display correctly.
>
> --
>    Oliver Charles / aCiD2
>
> _______________________________________________
> MusicBrainz-users mailing list
> MusicBrainz-users@...
> http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-users
>

It may display correctly but that's merely an artefact of the chosen
MBz site layout. The semantics of the data would still be incorrect.

With NGS, the separation between the DJ-mix AR applied to tracks and
that applied to releases becomes more distinct.  The AR I'm talking
about would still need to apply to the tracklist, as it only has
meaning with regard to the relationship between individual tracks on
the release.  The actual DJ mix takes place over track boundaries.  In
that sense, it's akin to compiled, though I can't think of any cases
where we know X compiled half the CD and Y compiled the other half.

A track AR however would presumably be an attribute of a work under
NGS, as such as DJ mix is a new creation consisting of two or more
works.  This is exactly why these don't work as track ARs as only one
work is involved per track.  To represent that as a track AR, you've
had to create some psuedo-work pairing each track.

On the subject of this new display, which relationships are going to
be shown in this manner? Would this include artist->work and
artist->recording?  If so, I can quickly see that display becoming
overly noisy and hard to read, as an average compilation album would
end up with something like:

1. Foo
2. Bar
3. Baz

X composed track 1
Y produced track 1
Z sang lead vocal on track 1
E composed track 2
F produced track 2
G sang lead vocal on track 2

Imagine that for the average compilation:
http://musicbrainz.org/album/1cc4ed3d-16b3-4bb7-b523-32e7e420acd4.html
You can even see it with some of the Mixmag CDs where I've added full
ARs: http://musicbrainz.org/release/b3796110-aef1-4ff5-9ceb-c1b9c86e1fad.html

If you split those out from under each track, it's going to lead the
reader to constantly jumping up and down the screen matching AR track
numbers to track titles manually.
--
Andrew :-)

Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)

Support Free Java!
Contribute to GNU Classpath and the OpenJDK
http://www.gnu.org/software/classpath
http://openjdk.java.net

PGP Key: 94EFD9D8 (http://subkeys.pgp.net)
Fingerprint: F8EF F1EA 401E 2E60 15FA  7927 142C 2591 94EF D9D8

_______________________________________________
MusicBrainz-users mailing list
MusicBrainz-users@...
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-users